A bill of materials is not fixed. As a product changes, its BOM changes, and a manufacturer needs to manage those changes rather than let the BOM drift. This piece explains BOM versioning and revisions in Odoo, and the difference the edition makes.
Why BOM versioning matters
The BOM feeds planning, purchasing, production, and costing. So a change to a BOM is consequential, and a manufacturer needs to know which version of a BOM is current, what changed from the previous version, and why. Without that, a BOM change is a silent edit: nobody can reconstruct what the BOM used to be, the floor may build to a version that is no longer correct, and there is no record of the decision. BOM versioning is the discipline of making BOM change controlled and traceable.
The controlled approach: PLM in Odoo Enterprise
Odoo's full, controlled answer to BOM versioning is its product lifecycle management capability, which is part of Odoo Enterprise. With PLM, BOM change is managed through engineering change orders. Rather than editing a production BOM directly, a change is raised as an engineering change order, which carries the change through a controlled path: the change is described, reviewed, and approved before it becomes the production BOM. PLM maintains a controlled history of BOM versions, so a manufacturer always knows which version is current and what each change was.
For a manufacturer whose products change often, or whose industry demands controlled, documented change, this PLM-based approach is the right answer, and it is a reason such a manufacturer should plan on Odoo Enterprise.
What Community users can do
The PLM capability is not in Odoo Community. A manufacturer on Community that needs some discipline around BOM change is not without options, but it works more manually.
Use the record's history. Odoo records keep a history of changes and discussion. A Community manufacturer can record the reason for a BOM change in the BOM's history, so there is at least a trail of what changed and why.
Use naming conventions for versions. Where a manufacturer needs to preserve old versions of a BOM, it can use deliberate naming or referencing conventions to mark versions, keeping a superseded BOM archived rather than deleted.
Use review steps. A change can be routed for review using activities before it is treated as final, giving a degree of approval discipline.
This is a workable approach for lighter needs, but it is honestly a workaround. It does not provide the controlled engineering-change-order process that PLM does, and a manufacturer with serious change-control needs should weigh moving to Enterprise.
How to decide what you need
A manufacturer should match the approach to its needs. If products are stable and change rarely, the manual Community approach, with changes recorded in the history, may be sufficient. If products change often, or if the industry requires controlled, documented, approved change, the controlled PLM approach in Enterprise is what the manufacturer genuinely needs, and the edition decision should reflect that.
The takeaway
BOM versioning and revisions matter because a BOM change affects planning, purchasing, production, and costing. Odoo's controlled answer is PLM with engineering change orders, part of Odoo Enterprise, which manages BOM change through review and approval and keeps a controlled version history. Community users can manage change more manually through record history, naming conventions, and review steps, but for serious change control, PLM in Enterprise is the proper tool. For how we approach Odoo for manufacturers, see our manufacturing work.