Understanding BOM version history

See how Bom version snapshots work, where to find history, and how to interpret the snapshots.

Laminar automatically preserves a complete history of every change made to a Bill of Materials (BOM). Each saved update—whether it’s the initial creation, a full edit, or a lightweight field change—becomes a permanent versioned snapshot. These snapshots give you clear visibility into how your assemblies have evolved over time, what changed, and who made the update.

Why Versioning Matters

BOMs naturally change as designs evolve and requirements shift. Versioning ensures that:

  • You can always review what changed and when it changed.
  • You maintain a reliable audit trail for internal reviews and compliance.
  • Teams collaborate safely without overwriting or losing earlier revisions.
  • Every version of the BOM remains accessible long after the update.

Each version is an immutable snapshot—once recorded, it cannot be altered.

Where to View BOM History

Version history is available directly inside any BOM you open.

History Drawer

  1. Open an existing BOM.
  2. Click the History toggle in the right‑side drawer.
  3. You’ll see a list of all past versions including:
    • Version number (V1, V2, …)
    • Timestamp
    • The user who made the change
    • A set of changed‑field chips indicating what was updated

Opening any entry displays a read‑only snapshot of the BOM exactly as it existed at that moment.

Both the drawer and the main detail views show the same version data.

What a Version Includes

Each version snapshot contains:

  • General information: title, description, associated product/project
  • Items: full list of components, part numbers, and quantities
  • Attachments: all files linked at the time of the snapshot
  • Approval state: any approval decisions that existed then
  • Diff summary: key fields that changed compared to the previous version
  • Audit info: who made the change and when

Snapshots live in a dedicated versions collection and never change once created.

How Versions Are Created

Laminar generates a new version automatically whenever you update a BOM through any supported flow:

  1. Creating a BOM
    After the initial save, Laminar records version 1 immediately.

  2. Editing via the form
    Saving changes in the edit form creates a new version capturing all updates.

  3. Quick field updates
    Even small changes—like updating a description, changing a product or project, or modifying approval fields—create a new version.

Versions increase sequentially for each BOM: V1, V2, V3, and so on.

Reading a Version Snapshot

When reviewing a version, key areas to focus on include:

Changed‑Field Chips

These highlight what was modified since the previous version.

Product & Project Labels

Laminar resolves product and project names for readability while keeping the original IDs visible.

Component List

Each item is displayed with:

  • Component name or SKU
  • Component ID
  • Quantity recorded at the time

Approval State

Snapshots preserve the exact approval status at that time, even if the current BOM’s approval has changed later.

Snapshots are read‑only and cannot be edited. While rollback isn’t available yet, versioning gives you clarity, confidence, and traceability across your entire BOM workflow.

Summary

BOM versioning in Laminar provides a complete, trustworthy timeline of every change your assemblies go through. Whether you are reviewing edits, coordinating across teams, or preparing documentation for quality processes, version snapshots provide a reliable reference of how the BOM looked at any point in time.