Odoo PLM: Engineering Changes, Versions, and Controlled Updates

Introduction

Picture the classic scene: sales confirms delivery Friday, the planner finds out Thursday night, and Odoo PLM was never part of the conversation. That is the gap this guide addresses.

We ranked ten scenarios from creating a BOM for a simple table to running a deliberately exaggerated level-10 production puzzle, each with a click-by-click Odoo checklist.

Odoo PLM is where physical reality (stock, batches, pickings, production) meets what customers and finance expect. When it works, nobody retypes quantities. When it does not, everyone blames the ERP.

Plenty of factories and warehouses run on experience, WhatsApp, and Excel tabs called FINAL_v3. It holds until you scale, add a second site, or audit traceability.

PLM is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo PLM: Engineering Changes, Versions, and Controlled Updates states the storyline for stakeholders approving budgets.

With PLM, you model how goods actually move: receive, store, pick, manufacture, ship, scrap, replenish. Each step leaves a record your future self will thank you for.

You will read ten use cases with concrete company examples, from first BOM to barcode on the shop floor.

Operations directors, warehouse leads, and production planners are the primary audience. Developers can join later; this is business language first.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo PLM.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo PLM is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Sales promises delivery Friday. The planner learns Thursday evening because the order lived in email, not in Odoo PLM. Expedite fees eat the margin, and finance discovers the stock gap at month-end, not on Tuesday.

Warehouses and factories run on experience, yet stock and production data often live outside Odoo. That gap creates stockouts, urgent purchases, and month-end surprises.

Sound familiar? Teams usually hit these walls:

• Stock files that do not match what sales promises
• Production or purchasing plans made without live quantities
• Traceability gaps when customers or auditors ask questions

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo PLM, and measure what changes.

Top 8 PLM Use Cases

8 use cases for Odoo PLM, ranked from Level 1 (easy, do it this afternoon) to Level 8 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Submit your first Engineering Change Order on a Bill of Materials Level 1 — Easy

Level 1 is the simplest possible PLM action: one engineer, one BOM edit, one tracked ECO. No workflow, no automation, just a documented engineering change that production can read.

Here's how you'd do it in Odoo:

1. Install the PLM app, then go to PLM, Engineering Change Orders, New, and pick the impacted product.
2. Link the current Bill of Materials and describe the change in plain text: what changes from, what changes to.
3. Add the reason (cost reduction, quality issue, supplier change) and an effective date for the new revision.
4. Save the ECO; the BOM stays locked on the current version until the change is approved.
5. Approve the ECO; Odoo creates a new BOM version, archives the previous one, and logs the edit on the product chatter.

What you get: Engineering changes stop happening in private spreadsheets and start living on the product record, with one owner, one reason, and one audit trail anyone can open.

2. Activate BOM versioning and compare two revisions side by side Level 2 — Easy

Level 2 turns each ECO into a real version-controlled history. You can compare Revision A and Revision B line by line, like a code diff, but for components and quantities.

Here's how you'd do it in Odoo:

1. Go to PLM, Configuration, Settings, and tick Engineering Versioning on Bills of Materials.
2. Every approved ECO now creates a new BOM version automatically; the previous one is archived but still readable.
3. Open the product, click the BOM Versions smart button, and select two revisions you want to compare.
4. Click Compare; Odoo highlights added, removed, and modified components, with quantity deltas in color.
5. Export the comparison as PDF and attach it to the ECO so any future audit reads the exact same diff.

What you get: The 'who changed what on this BOM, and when' question is answered in thirty seconds instead of one afternoon of digging through emails and shared drives.

3. Attach CAD drawings and revision notes to every ECO via Documents Level 3 — Easy

Level 3 connects PLM to the Documents app. Every ECO becomes the single source of truth for drawings, STEP files, and the technical notes the shop floor actually reads.

Here's how you'd do it in Odoo:

1. Open an active ECO and switch to the Documents tab on the form.
2. Drag the new PDF drawing into the upload zone; Odoo auto-tags it with the ECO reference, product, and revision.
3. Pin the latest CAD export (STEP or IGES) so operators always read from one approved file.
4. Write a revision note in the chatter describing what physically changes on the part and how to spot it.
5. Generate a QR code that points to the document folder, print it, and stick it next to the workstation.

What you get: Operators stop building from the old drawing pinned on the wall and start working from the live revision the engineer just approved this morning.

4. Configure a multi-stage approval workflow for engineering changes Level 4 — Medium

Level 4 introduces governance. The ECO no longer moves on one approval, it runs through Engineering, Production, Quality, and Finance, with one named approver per stage.

Here's how you'd do it in Odoo:

1. Go to PLM, Configuration, Approval Workflows, New, and name it Standard ECO Approval.
2. Add stages in order: Engineering Review, Production Sign-off, Quality, and Finance (only when cost impact exceeds 500 euros).
3. Assign one approver or one group per stage; require a comment on every refuse decision so reasons stay traceable.
4. Enable Notify by Activity so every approver gets a task in their inbox the day an ECO lands at their stage.
5. Build a pipeline view grouped by stage so the engineering lead spots stuck ECOs at a glance every Monday.

What you get: Change governance becomes a defined process instead of a chain of personal escalations, and the engineering lead finally knows which ECOs are stuck and why.

5. Propagate an approved revision to running Manufacturing Orders Level 5 — Medium

Level 5 is where PLM meets the shop floor. Once an ECO is approved, you decide whether the change applies to new MOs only or also to MOs already confirmed in production.

Here's how you'd do it in Odoo:

1. Open an approved ECO and check the Apply To field: New MOs only, Confirmed MOs, or All Open MOs.
2. Pick All Open MOs to push the new BOM version onto every active manufacturing order in one click.
3. Confirm; Odoo flags the affected MOs in red so the planner knows the recipe just changed mid-run.
4. Open one impacted MO and check that the new component appears in the consumption list with the right quantity.
5. Post a Discuss message in the production channel with the ECO link and the cutover date.

What you get: Mid-flight engineering changes reach the right MOs at the right moment, so the next finished batch matches the new specification instead of the old one.

6. Block the new revision until a Quality gate passes a pilot run Level 6 — Hard

Level 6 connects PLM to Quality. The new BOM version cannot go live until a pilot batch passes a real quality control point with measurements logged on the shop floor.

Here's how you'd do it in Odoo:

1. Quality, Configuration, Control Points, New, and link the point to the impacted product and BOM operation.
2. Define the test (dimensional measurement, visual check, instructions) and mark failure as a blocker for the workflow.
3. On the ECO form add a Quality Gate stage that triggers the control point on a pilot MO of three units.
4. An inspector runs the pilot MO, validates the test on tablet, and uploads photos directly from the workstation.
5. If the test fails, Odoo refuses to advance the ECO and auto-creates a Quality Alert with the failed measurement.
6. If the test passes, the ECO moves to the next stage and the new BOM version goes live for production.

What you get: Defective revisions are caught on three pilot units instead of three hundred customer returns, and the link between engineering change and quality outcome is finally measurable.

7. Sync revisions with external CAD via the Odoo API Level 7 — Hard

Level 7 connects PLM to the design world. Engineers stay in their CAD tool of choice; Odoo receives every release as a draft ECO with the new BOM, the drawing, and the part list pre-filled.

Here's how you'd do it in Odoo:

1. Generate an API key in Settings, Technical, API Keys with scope read and write on the PLM module.
2. Connect a CAD bridge (SolidWorks, Inventor, Fusion 360, Onshape) to that key via a webhook or a connector.
3. Configure the bridge: every CAD release pushes a draft ECO with new BOM lines, drawing PDF, and STEP attached.
4. Map CAD revision letters (A, B, C) to Odoo BOM version numbers so naming stays consistent both ways.
5. Enable bidirectional updates: a component swap inside Odoo flags the CAD part as Needs Review the next time an engineer opens it.
6. Pilot one product family for one week, monitor the sync log, and only roll out to the full catalog when error count is zero.

What you get: Engineering data flows once from design to production; nobody retypes BOM lines, and a CAD revision letter and an Odoo BOM version always tell the same story.

Designing the CAD-to-Odoo sync, the field mapping, the conflict resolution, and the rollout cadence is the kind of integration Dasolo runs as a partner-led PLM engagement.

8. Run a full Design-to-Retire lifecycle across PLM, Quality, AI and live dashboards Level 8 — Expert

Level 8 is the ceiling. PLM orchestrates Project, Quality, Manufacturing, Field Service, and AI so every revision flows from a design idea to an end-of-life notification with one audit trail.

Here's how you'd do it in Odoo:

1. Build a Project board Design to Retire with R&D tasks linked to draft products; every prototype lives there before the first ECO.
2. Configure Odoo AI to read each ECO description and predict cost impact, risk score, and the most likely approver path before submission.
3. Wire PLM to Quality, Maintenance, and Field Service so every approved revision auto-creates QC plans, equipment alerts, and spare-part updates.
4. Push every approved ECO to the Knowledge base for distributors and to Field Service technicians on mobile, with offline access on site.
5. Sync the BOM version stream with external systems (CAD, MES, customer portals) via signed webhooks, with retry queues and a dead-letter view.
6. Build a Spreadsheet dashboard Product Lifecycle Live: average ECO cycle time, cost impact per quarter, blocked changes, top failure reasons.
7. End-of-life automation: when a product is archived, notify affected customers, and propose a replacement part on every open quotation in CRM.

What you get: Engineering changes stop being a private spreadsheet and become the connective tissue between design, production, service, and finance, with one number per quarter on the executive dashboard.

Wiring PLM with Project, Quality, Field Service, AI, Knowledge, Spreadsheet, and external CAD or MES sync is the cross-app architecture Dasolo assembles as a partner-led PLM program. Most teams need an outside team to get the routing rules and the failure handling right the first time.

When Expert Help Makes Sense

If levels 1 to 5 fit your world, you can often succeed with standard Odoo PLM, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 6 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for PLM includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo