Skip to Content
Odoo PLM app icon

Odoo PLM

Odoo PLM: Changing a Bill of Materials Without Breaking Production

PLM answers a question that only becomes urgent once: what happens to the manufacturing orders already running when the bill of materials changes. Without a controlled process the answer is usually that somebody edits the BoM and finds out later.

What Odoo PLM actually is

PLM adds a controlled change process to products and their bills of materials. Instead of somebody editing a BoM, a change is requested, described, approved and then applied, producing a new version while the old one remains.

It is Enterprise and it sits on top of Manufacturing.

Whether you need it comes down to one question: how much does it cost you when a BoM changes badly? For a business making occasional changes with one person responsible, disciplined use of the chatter is genuinely adequate. For a business where engineering, purchasing and production can all initiate a change, or where you must later prove what specification a particular batch was built to, the absence of a controlled process is a liability that shows up at the worst moment.

Engineering change orders

An ECO records what is changing, why, who requested it, and what it affects. It moves through approval stages and applies on acceptance.

Two parts of that are worth dwelling on.

The reason. An ECO that says "update BoM" is a record that something happened and nothing about why. Six months later, when someone asks whether a component was changed for cost, for supply, or because it was failing, the answer needs to be on the record. Insisting on a real description is the cheapest quality improvement in the whole module.

The approval routing. Different changes carry different risk. A packaging substitution and a change to a load-bearing component should not require the same signatures. Stages let you route them differently, and doing so keeps approval meaningful rather than ceremonial.

Versions, and the problem they solve

When an ECO applies, it creates a new BoM version. The previous one is retained, and manufacturing orders created against it continue to use it.

This is the whole reason the module exists. Editing a live BoM changes what every future order consumes, including orders that are already released, already picked and already part-built. The consequences range from a component shortage that stops the line to a batch built to neither the old nor the new specification, which is the one nobody wants to explain to a customer.

Versioning also gives you the answer to "what was this batch actually built from", which is a question that arrives with a warranty claim or a recall and needs to be answerable in minutes.

Where PLM will fight you

It is Enterprise and it needs Manufacturing configured properly first. Change control over a BoM structure that is already wrong just formalises the wrongness.

It is not CAD data management. Drawings attach as documents. Native CAD file versioning, assembly relationships and viewer integration are not in scope, and businesses with heavy CAD workflows will run a dedicated PDM system alongside and connect them.

Process discipline is the actual requirement. The app cannot stop someone editing a BoM directly if they have the rights to. Change control is a policy that the module supports; access rights are what enforce it, and that pairing has to be deliberate.

Approval routing can be over-built. The same warning as everywhere else. Five approvers on a trivial change means changes get batched, and batching change control defeats it.

Effectivity dates need care. Applying a change from a future date, or on stock exhaustion, is often what you actually want, and it needs thinking through rather than accepting immediate application by default.

How it connects to everything else

PLM works on products and bills of materials from Manufacturing, and changes flow into work orders and routings. Purchasing is affected whenever a component changes, so the vendor pricelist and reordering rules for the old and new parts both need attention as part of the change rather than after it. Quality control points may need updating when a specification moves. Documents attached to the ECO travel with the change history. Inventory carries the stock of the superseded component, and deciding what happens to it is part of the change, not a separate cleanup.

That last point is the one most often forgotten. A change that leaves four hundred obsolete components on a shelf has a cost, and the ECO is the right place to have decided about it.

Where to start

Get bills of materials correct and Manufacturing running properly before adding change control on top. Decide who is permitted to edit a BoM directly and remove that right from everyone else, because the process only holds if the bypass is closed. Define two or three approval routes by risk rather than one for everything. Insist that every ECO carries a real reason. Then run a real change through it, including the decision about existing stock and open purchase orders, and see what the process missed.

FAQ

Odoo PLM, answered.

Is Odoo PLM available in Community?

No, PLM is an Enterprise app and it requires Manufacturing. Community users can edit bills of materials directly, which works but leaves no controlled change process, no version history and no approval trail.

What is an engineering change order?

A controlled request to change a product or its bill of materials. It holds what is changing and why, routes for approval, and applies the change on acceptance, creating a new BoM version rather than overwriting the old one.

What happens to manufacturing orders already in progress?

They continue against the BoM version they were created with. That is the entire point of versioning: a change applied today does not silently alter an order that was already released to the floor with components already picked.

Can changes be approved by different people depending on type?

Yes. Approval stages on the change order route to defined approvers, so a minor substitution and a change affecting a safety-critical component can follow different paths with different sign-off.

Does it hold engineering drawings and documents?

Documents attach to the product and the change order, so drawings and specifications travel with the change. It is not a CAD data management system, and businesses needing CAD versioning and native file handling should expect to run a dedicated PDM tool alongside.

Do we need PLM if we change our BoMs rarely?

Probably not. A business making a handful of controlled changes a year can manage with discipline and the chatter. PLM earns its place when change is frequent, when several people can initiate it, or when you must prove what was built to which specification.

Related

Keep exploring.

Other Odoo apps we have written up in the same depth.

With CODEerts

Want this set up properly?

We are certified Odoo partners. We implement, customise and support Odoo PLM, and we publish our own apps on the Odoo Store.

See how we can helpBook a call