Plan the production changeover before applying a BOM revision

A bill of materials (BOM) revision needs an agreed changeover: who approves it, when it becomes usable and which production orders it changes. Put those decisions in the software brief before replacing a component or assembly instruction.

The operator should be able to see the revision assigned to the current order. A proposed revision needs a visibly different state until the agreed release process is complete.

Keep the test revision separate

Odoo 19 PLM keeps changes and tests in a revised BOM without affecting the version used in production until the changes are applied.[1] Ask how your proposed system separates those versions; do not assume every platform follows the same process.

In an illustrative assembly order, revision A is in production while revision B proposes a component change and awaits approval. Saving B should not tell the operator to start using it. Keep the changed component and its quantity visible to the reviewer, along with any affected operation.

Make required approval enforceable

Odoo distinguishes required approvers from optional approval and comments. Its documentation warns that Apply Changes can work without prior approval if no approver is configured as required.[2] A named reviewer on a screen is therefore not enough evidence that the configuration blocks an unapproved change.

Agree who may propose, approve and apply a revision. During the demonstration, try applying it from an account that lacks the required authority. Keep the decision and the revision it covers together, so a later edit does not borrow an earlier approval.

Define which orders switch

Microsoft Dynamics 365's planning engine selects a valid BOM version by site, with date and quantity criteria also required.[3] Those rules are specific to that planning process, but they show why a single "latest version" badge can leave a buyer's question unanswered.

Specify the changeover for new orders and orders already queued. Write a separate decision for work in progress: retain its approved revision, or pause it for an authorized amendment. An urgent correction belongs in the team's agreed stop-and-review procedure, not a silent substitution.

Odoo's "As soon as possible" option applies a change to the production BOM when an authorized user applies it.[1] Check what the selected setting actually does. A saved effective date is not a substitute for verifying which revision appears on the production order and shop-floor screen.

Test the change against real order states

In a test environment, keep an order on revision A and leave B awaiting approval. Confirm that the operator still sees A. Complete the required review, apply the agreed changeover and inspect both the queued order and the order already in progress.

Retain the revision used for earlier material consumption and output records. A template update should not rewrite what an earlier order actually consumed.

Rootscratch's Manufacturing & Production Systems service can cover bills of material, production orders and material reservations.[4] Bring two material-list versions and one order caught between them. Equipment integration and automated scheduling remain separate scope decisions.[4]

Sources

[1] https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.html — Odoo 19: engineering change orders and production BOM revisions [2] https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/plm/management/approvals.html — Odoo 19: required, optional and comment-only ECO approvals [3] https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/master-plan-bom-version-determined — Microsoft Dynamics 365: determine the BOM version [4] https://rootscratch.com/services/manufacturing-production-system — Rootscratch: Manufacturing & Production Systems