BOM revisions and locking
Every saved product recipe change is a BOM revision. A product has one current revision, and manufacturing orders copy that current revision when they are created.
How Revisions Work
Section titled “How Revisions Work”Recipe edits append a new revision instead of rewriting the old one. Each revision records its components, constraints, operation costs, output quantity, recipe basis, creator, timestamp, and note. Saving the same recipe payload again is a no-op, so revision history only grows when the business recipe changes.
| Revision | Note | By | Status |
|---|---|---|---|
| 4 | Swapped perlite grade | A. Wells | Current |
| 3 | Added lot age rule | A. Wells | - |
| 2 | Initial spring recipe | M. Vela | - |
| Rule | Effect |
|---|---|
| Append, don’t overwrite | Previous revisions remain available for history. |
| One current revision | New manufacturing orders copy the current revision. |
| Order snapshots | Later recipe changes do not alter already-created orders. |
Locking A BOM
Section titled “Locking A BOM”A product recipe can be locked to prevent normal edits. The product records whether it is locked, when it was locked, and who locked it. An authorized inventory administrator can edit or unlock it, and a recipe change still creates a new revision.
Members allowed to inspect a locked recipe see the component grid and current estimated costs in read-only form. Ingredient selection, quantity editing, constraint controls, and row mutation actions remain unavailable until an authorized inventory administrator unlocks or edits the recipe.
Recipe Basis: Unit Vs Batch
Section titled “Recipe Basis: Unit Vs Batch”The revision stores whether quantities are based on a unit or a batch. Unit recipes scale by output quantity. Batch recipes scale by whole batch count; the manufacturing order’s expected output controls finished-good expected supply. See Discrete and batch production for order behavior.