Odoo PLM: change control for bills of materials and engineering teams

What Odoo PLM actually does

Odoo Product Lifecycle Management (PLM) is an app under the Inventory & MRP umbrella that gives manufacturing teams a systematic way to test, collaborate on, and iterate across the full product lifecycle, from concept and design through manufacturing, marketing, and post-launch support, with approvals that let key stakeholders review changes before they go live.

PLM does not replace your bills of materials or routings. It layers change control on top of the BoMs and routings already owned by the Manufacturing app. The unit of change is the Engineering Change Order (ECO), and PLM organizes work into two areas: Change management, covering ECOs, ECO types and stages, and version control; and Project management, covering approvals.

Because Odoo PLM sits inside the same database as Manufacturing, Quality, Inventory, and Documents, an engineer revising a BoM and a planner consuming that BoM on a Manufacturing Order are working from one shared data model, with no integrations to maintain.

Engineering change orders: the unit of change in Odoo PLM

An Engineering Change Order (ECO) tracks, implements, and can revert change versions made to products and bills of materials. ECOs can be created directly inside an ECO type, or generated automatically from feedback emailed to the ECO type's email alias, which is useful for capturing change requests from operators, suppliers, or quality teams.

Each ECO carries two decisions that shape how it lands on the production BoM:

The 'Apply on' field determines whether the ECO changes the Bill of Materials or the Product only. The 'Effective' field controls timing: 'As soon as possible' makes the ECO live on application, while 'At Date' schedules it.

• →Pressing 'Start Revision' creates a copy of the production BoM, stored under a Revision smart button, with the next version number (V2, V3, and so on).
• →Engineers edit components and operations on that archived copy, flagged 'Archived', so the production BoM is untouched while work is in progress.
• →A 'BoM Changes' tab shows a colour-coded diff against the live BoM: blue = added, black = unchanged, red = removed. An 'Operation Changes' tab does the same for routing operations.
• →When the ECO reaches a verification stage, designated approvers review it; once accepted, 'Apply Changes' archives the original production BoM, promotes the revised BoM to production, and updates the Version field on the BoM's Miscellaneous tab.

ECO types and stages: shaping the change pipeline

Every Odoo ECO belongs to an ECO type, and every ECO type has its own Kanban pipeline of stages. This is one of the features that distinguishes Odoo PLM from a simple document workflow: you can model different change processes for different business situations.

Each ECO type separates ECOs into their own project in the PLM Overview, so collaborators only see the BoM improvements relevant to them. Common examples include New Product Introduction, BOM Updates, Component Change, Product Improvement, and Firmware Update. An optional email alias on each type auto-generates ECOs into the type's first stage.

Stages are user-defined, with sensible defaults of New, In Progress, Validated, and Effective. Two kinds of stage do the heavy lifting:

Verification stages list required approvers (with role, user, and an Approval Type of 'Is required to approve') who are notified when an ECO enters the stage. Closing stages, with the 'Allow to apply changes' flag set, apply BoM and operations changes and update all pending and future Manufacturing Orders to the latest BoM version. A good baseline is at least one verification stage and one closing stage per ECO type.

BoM version control and traceability

Odoo PLM version control is BoM-centric. Every applied ECO bumps the BoM's version number, and the full revision history is one click away.

Version control stores former assembly instructions, component details, and past product design files, keeping historical detail out of the production BoM while still accessible for audits. Every BoM version lives inside an ECO, which means organized testing and improvements without disrupting normal manufacturing operations. The ECO smart button on a BoM (visible only when PLM is installed) exposes the history, showing the responsible user and effective date, and supports reverting to a previous version and tracing which BoM version was active on a specific date for recalls or complaints.

Design files are versioned too. Users can attach CAD files, PDFs, images, or other design material to a BoM via the chatter; files can be added, modified, or removed inside an ECO, and only apply to the production BoM when the ECO is applied. Archived files remain accessible in prior ECOs.

When two ECOs touch the same BoM, PLM's 'Apply Rebase' feature simplifies merge-conflict resolution: if the production BoM was updated while another ECO still modifies the previous version, differences surface in a 'Previous Eco Bom Changes' tab, and Apply Rebase retains the changes already applied without losing the new ECO's edits.

From the shop floor: feedback that becomes an ECO

Odoo PLM is not only an engineering tool. Operators on the shop floor can suggest improvements directly from a Manufacturing Order, for example proposing a new quality-control step that checks for broken components. That suggestion generates an ECO, assigned to the operator who raised it, routed through the normal approval and apply pipeline.

The Quality app is required to configure the quality control points that can be used as operation steps on a BoM. This closes the loop between production execution and engineering change, so a real defect caught at a work center can become a controlled, approved revision rather than an informal email.

The Dynamics 365 equivalent: Engineering Change Management

For SMEs evaluating both platforms, the Microsoft counterpart is the Engineering Change Management (ECM) module inside Dynamics 365 Supply Chain Management. Originally an add-in and on by default since Supply Chain Management version 10.0.36, ECM is an ERP-native PLM layer rather than a standalone PLM product.

Its main capabilities are product versioning (with Version carried as an inventory dimension when the 'Product dimension - Version' configuration key is enabled), engineering change requests (ECRs) and engineering change orders (ECOs) routed through configurable approval workflows under Engineering change management > Engineering workflows, readiness checks that gate activation by validating required information, enhanced product release that maintains master data in one engineering company and publishes the fully configured released product to other legal entities, and fine-grained product lifecycle state control over where a released product can be used in specific business processes. A product structure can be released directly from within an engineering change order.

Microsoft does not market a dedicated CAD-level PLM product. For deep CAD/ECC integration and enterprise PLM-ERP workflows, partners typically layer third-party PLM solutions on top of D365 ECM.

When each fits an SME

Odoo PLM and D365 ECM solve the same problem, controlling engineering change, at different scales and with different centre of gravity.

Odoo PLM is BoM-centric and tightly coupled to the Manufacturing and Quality apps inside a single shared database. Its Kanban-driven ECO types, colour-coded BoM diffs, and versioned chatter attachments suit discrete-manufacturing SMEs that want simpler change control without a separate PLM licence or a complex workflow engine. Setup is lighter, and the data model is unified across engineering, planning, and shop-floor execution.

D365 ECM is enterprise-scale. Its strengths are stronger multi-company and multi-legal-entity release, a formal workflow engine, version-as-inventory-dimension, and process-manufacturing formula change support. The trade-off is heavier licensing and implementation effort, and deeper expertise to configure workflows, readiness checks, and release policies.

The decision rarely comes down to feature counts. It comes down to your legal-entity structure, your CAD integration needs, your existing ERP footprint, and whether a unified Odoo data model or a mature multi-entity ERP platform is the better foundation for the next five years of growth.