A product change rarely affects only one isolated thing. It can touch the bill of materials, the routing, and more, and managing change that reaches across them is the real work of engineering change. This piece is about it.
Why engineering change reaches across
A product is defined by more than one thing: its bill of materials, what it is made of, and its routing, how it is made. A genuine product change often touches more than one of these. A change to what a product is made of may also change how it is made. A change that affects a sub-assembly affects the products that use that sub-assembly. So an engineering change is rarely a single edit in a single place; it is a change that has to be made coherently across the parts of the product definition it touches. Managing engineering change well means managing that reach.
The risk of uncoordinated change
The danger of a change that reaches across BOMs and routings is uncoordinated change: the BOM is updated but the routing is not, or a change to a sub-assembly is made but its effect on a product that uses it is missed. The result is an inconsistent product definition, where the parts no longer agree, and that inconsistency causes real problems in production, planning, and costing. Managing engineering change is, in large part, making sure a change that reaches across is made completely and consistently, with no part left out of step.
How Odoo's PLM helps
This is where Odoo's PLM capability, with engineering change orders, earns its place. An engineering change order is a controlled wrapper around a change, and it is the mechanism for managing a change that reaches across the product definition. Rather than the change being a scatter of separate direct edits, hopefully all done, hopefully all consistent, the change is a single ECO, which carries the whole change, across the BOM, the routing, and what it touches, through one controlled, reviewed, approved process. The ECO is what makes a multi-part change a single managed thing rather than a set of uncoordinated edits.
Review catches the reach
The review step of the ECO workflow is especially important for change that reaches across. Review is where the full reach of a change is considered: does this change to the BOM also require a change to the routing; does this change to a sub-assembly affect the products that use it; what does the change touch that is not immediately obvious. A genuine review catches the reach of a change before it is applied, so the change is made complete. Without that review, a change that reaches across is the most likely kind to be made incompletely, with a consequence missed.
Where-used analysis and the reach
A practical tool for understanding the reach of a change is where-used analysis: tracing from a component or a sub-assembly to everything that uses it. When a change touches a component or a sub-assembly, where-used analysis shows the full set of products affected, which is exactly what the change has to be coordinated across. Used as part of managing engineering change, where-used analysis makes the reach of a change visible, so it can be managed deliberately rather than partly missed.
The takeaway
Managing engineering change across BOMs and routings in Odoo means handling a change that reaches beyond one isolated place, touching the bill of materials, the routing, and the products affected, coherently and completely. The risk is uncoordinated change leaving the product definition inconsistent. Odoo's PLM, with engineering change orders, manages a multi-part change as a single controlled thing, the review step catches the full reach, and where-used analysis makes that reach visible. For how we approach Odoo for manufacturers, see our manufacturing work.