Skip to main content

BOM Versioning

Recipes change. You adjust quantities, swap out a component, add a cost line, or reformulate entirely. BOM versioning tracks these changes so you always know exactly what went into each build.

How Versioning Works​

Every BOM has a version number, starting at 1. Each product can have multiple BOM versions, but only one can be active at a time. The active version is what Partsemble uses when you execute a build.

BOM versions have three statuses:

  • Active — the current version, used for all new builds
  • Archived — a previous version, preserved for history
  • Draft — a work-in-progress version (not used for builds)

Creating a New Version​

When you edit a BOM and save your changes, Partsemble creates a new version automatically. The process works like this:

  1. You open the BOM and click Edit
  2. You make your changes (adjust quantities, add/remove components, update cost lines)
  3. You click Save
  4. Partsemble archives the current active version and creates a new active version with your changes

The version number increments automatically. If you were on version 3, the new version is version 4.

info

Editing always creates a new version — you can't modify a version in place. This is by design. It means every build in your history references the exact BOM version that was used, and that version's data never changes after the fact.

Viewing Version History​

On the BOM detail page, the Version History section lists all versions for the product. Each entry shows the version number, status, date created, and who created it.

You can click on any archived version to view its components, cost lines, and notes. This is useful for auditing past builds or understanding how a recipe has evolved.

You can also view all versions for a product by navigating to the product's BOM page — it shows the active version by default with access to the full history.

What Happens to Existing Builds?​

Each build records which specific BOM version was used. When you create a new version, existing builds are not affected — they continue to reference the version that was active when they were executed.

This means you can confidently change a recipe knowing that your historical cost data and build records remain accurate.

When to Create a New Version​

Common reasons to version a BOM:

  • Quantity adjustment — you discover that 1.8 sheets of steel per unit works better than 2.0
  • Component substitution — you switch from supplier A's hinges to supplier B's
  • Adding a component — you add a new gasket or nameplate to the product
  • Cost line update — labor costs have changed and you want to reflect the new rate
  • Process change — you reworked the assembly and multiple components changed

There's no limit to the number of versions a BOM can have. Version frequently — it's the right way to keep your records accurate.

Reverting to an Old Version​

If you need to go back to a previous recipe, you can create a new version based on an archived one. View the archived version, use it as your starting point, and save. This creates a new version (with a new version number) that matches the old recipe.

Partsemble doesn't have a one-click "revert" button because going back to an old version is a meaningful decision that might need adjustments. Creating a new version from an old one gives you the chance to review and modify before activating.