Quick facts
- Price
- $499.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 20160 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Engineering Change Management (PLM/ECO)
Build-to-order Odoo ECO workflow: BOM versioning, revision diff, approval routing, e-sign & effectivity dates for controlled PLM changes.
$499.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Stage-driven Engineering Change Order (ECO) pipeline — Draft, Under Review, In Approval, Approved, Effective, Rejected — modeled as a Kanban stage_id workflow you can rename and extend
BOM versioning that snapshots the released Bill of Materials into a working revision on ECO creation, so the original is never overwritten
Line-by-line BOM revision diff computed server-side (added/removed components, quantity deltas, operation and routing changes) via @api.depends compute methods
Configurable approval routing per change type — sequential or parallel approvers — with role-based approval gates before a change can be released
E-signature capture on each approval step with immutable audit trail written to the record's chatter (who, when, against which revision)
Document and drawing version control that promotes the correct drawing revision together with the approved BOM
Effectivity dates that control the exact date an approved change becomes the active/released revision
One-click rollback to a prior released revision for recalled or reverted changes, preserving full history
Change impact linkage from an ECO to the affected product, BOM, routing, and attached documents in a single view
Role-based security via ir.model.access.csv plus record rules so engineers, approvers, and manufacturing each see only their permitted scope
QWeb PDF ECO release sheet and BOM revision-history report for quality and audit records
Automated actions/notifications (server actions) to alert approvers when an ECO enters their queue and flag overdue reviews
Full revision history log per product and per BOM — every released revision timestamped and traceable
XML-RPC / JSON-RPC API access so external PLM/CAD systems can create change requests or read revision history programmatically
Built and validated for Odoo 17, 18 and 19 (Community and Enterprise), designed to coexist with the standard MRP/Manufacturing app
About this Product
Uncontrolled engineering changes are how the wrong revision ends up on the shop floor. A verbal "just swap the resistor" turns into scrapped batches, mismatched drawings, and a warehouse full of obsolete stock — because there was no single, auditable place where the change was proposed, reviewed, approved, and released with a defined effectivity date.
Why Choose Engineering Change Management (PLM/ECO)
Stage-driven Engineering Change Order (ECO) pipeline — Draft, Under Review, In Approval, Approved, Effective, Rejected — modeled as a Kanban stage_id workflow you can rename and extend
BOM versioning that snapshots the released Bill of Materials into a working revision on ECO creation, so the original is never overwritten
Line-by-line BOM revision diff computed server-side (added/removed components, quantity deltas, operation and routing changes) via @api.depends compute methods
Configurable approval routing per change type — sequential or parallel approvers — with role-based approval gates before a change can be released
E-signature capture on each approval step with immutable audit trail written to the record's chatter (who, when, against which revision)
Document and drawing version control that promotes the correct drawing revision together with the approved BOM
ECOSIRE builds a purpose-fit Engineering Change Management (PLM/ECO) module for your Odoo instance that gives every design change a controlled lifecycle. This is not a generic apps.odoo.com download — it is a net-new module we design, develop, install, and support around your actual products, your BOM structure, and your approval hierarchy. We deliver it as clean, upgradeable Odoo code (a proper __manifest__.py package with models/, views/, security/ and report/ directories), tuned to the way your engineers and manufacturing team really work.
At the core is a stage-driven Engineering Change Order object (an mrp.eco-style models.Model with a state/stage_id Selection field driving a Kanban pipeline: Draft, Under Review, In Approval, Approved, Effective, Rejected). Each ECO links to the affected product, the Bill of Materials, and any attached drawings or documents. When an engineer proposes a change, the module snapshots the current BOM into a working revision so the original release is never overwritten — you can always see exactly what shipped before the change.
The revision comparison engine renders a line-by-line diff between the released BOM and the proposed BOM: components added, removed, quantity changes, operation and routing edits, and attribute changes, all computed server-side (compute methods with @api.depends on the BOM lines) so reviewers see a clean "what actually changed" summary instead of eyeballing two nearly identical BOMs. Document and drawing revisions are versioned the same way, so approving an ECO promotes both the BOM and the correct drawing revision together.
Approval routing is configurable per change type and can require multiple approvers in sequence or in parallel, with an e-signature capture and a full audit trail written to the chatter (mail.thread) — who approved, when, and against which revision. Effectivity dates control exactly when an approved change becomes the active revision, and a rollback path lets you revert to a prior released revision if a change is recalled. Security is enforced with proper ir.model.access.csv grants plus record rules so engineers, approvers, and manufacturing see only what their role allows.
Everything is exposed over Odoo's standard XML-RPC / JSON-RPC API so your PLM data isn't locked in — you can push CAD-driven change requests in, or pull revision history out to a data warehouse. QWeb reports produce a printable/PDF ECO release sheet and BOM revision history for your quality and audit records. Built and tested for Odoo 17, 18 and 19, Community or Enterprise, and designed to sit cleanly alongside the standard Manufacturing (MRP) app rather than fight it.
What you get
- Complete, installable Odoo module package (a proper __manifest__.py addon with models/, views/, security/, report/ and data/ directories) delivered as source you own
- Configuration tailored to your products, BOM structure, change types, and approval hierarchy — set up in your Odoo 17/18/19 environment
- ir.model.access.csv access rights and record rules mapped to your engineering, approval, and manufacturing roles
- QWeb ECO release-sheet and BOM revision-history report templates configured to your branding
- Deployment onto your instance (staging then production) with a smoke-test pass and a short migration/rollback note
- Admin and end-user documentation plus a recorded walkthrough of the ECO workflow, diff view, and approval routing
- Live training session for engineers and approvers, including how to raise, review, approve, and roll back a change
- Post-launch support window with defect fixes and minor adjustments, and a version-compatibility check for your Odoo edition
Who this is for
Product / Design Engineer
Owns design changes and needs a controlled way to propose a revision, attach updated drawings, and see exactly what changed on the BOM without overwriting the released version or losing history.
Engineering / Change Manager
Approves or rejects ECOs and enforces process. Needs sequential or parallel approval routing, e-sign accountability, and a full audit trail showing who approved which revision and when.
Manufacturing / Production Lead
Needs certainty that the shop floor is building the current released revision. Relies on effectivity dates and rollback so a change only reaches production when it is officially effective.
Quality & Compliance Officer
Requires printable, timestamped revision history and ECO release sheets (QWeb PDF) to satisfy audits and traceability requirements across every design change.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Engineering Change Management (PLM/ECO) module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Engineering Change Management (PLM/ECO), and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Engineering Change Management (PLM/ECO) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fit to your change types, BOM structure & approval hierarchy | Built to your exact process from a scoping call | Possible but you design and maintain it | Fixed to the app author's assumptions | |
| Line-by-line BOM revision diff (added/removed/qty/routing) | Server-side computed diff view included | Must be built from scratch | ||
| Configurable approval routing with e-sign & audit trail | Sequential/parallel routing + chatter audit | Build and test the whole workflow yourself | ||
| Effectivity dates & one-click rollback to prior revision | Included and tuned to your production flow | Significant engineering to get right | ||
| Runs on Odoo Community (not just Enterprise) | Yes — Community or Enterprise, 17/18/19 | Depends on your build | ||
| Role-based security (ir.model.access.csv + record rules) | Mapped to your engineering/approval/mfg roles | You must define and maintain every rule | ||
| XML-RPC / JSON-RPC API for CAD/PLM integration | Exposed and documented, connector optional | You wire up and document it | ||
| Ownership, source code & upgrade support | Full source + support window + version checks | You own it and all maintenance | Author-controlled, per-license updates |
Frequently Asked Questions about Engineering Change Management (PLM/ECO)
+How long until the module is delivered and live?
This is a build-to-order module, not an instant download. Typical lead time is 2 to 4 weeks depending on complexity — the number of change types, how intricate your approval routing is, and any CAD/PLM integration. After you order, we run a short scoping call to confirm your BOM structure, change types, approval hierarchy, and Odoo version (17, 18 or 19). We then build, deliver to a staging instance for your review, and deploy to production once you sign off.
+What support and updates are included after go-live?
Every build includes a post-launch support window covering defect fixes and minor adjustments to what we delivered. Because you receive the full module source, you own it outright. We also perform a version-compatibility check so the module runs cleanly on your Odoo edition, and we offer an optional ongoing support/maintenance retainer for future enhancements or migrations to a newer Odoo release (e.g. 18 to 19).
+Is this the same as Odoo Enterprise PLM?
No. Odoo's Enterprise PLM app is a strong general product, but it is a fixed feature set. This is a net-new module we tailor to your exact change types, approval routing, diff behavior, and reporting — and it runs on Community as well as Enterprise. If you already run Enterprise PLM, we can complement or extend it rather than replace it; we scope that during the discovery call.
+Does it work with our existing BOMs and Manufacturing setup?
Yes. The module is designed to sit alongside the standard Odoo Manufacturing (MRP) app and your existing products, BOMs, and routings — it references them rather than duplicating them. On ECO creation it snapshots the released BOM into a working revision so your current production data is never disturbed until a change is approved and effective.
+Can it integrate with our CAD or external PLM system?
Yes. The module exposes its data through Odoo's standard XML-RPC and JSON-RPC APIs, so an external CAD or PLM tool can create change requests, attach drawing revisions, and read back revision history programmatically. We scope the specific integration points (fields, authentication, sync direction) during discovery and can build a connector as part of the engagement.
+Which Odoo versions and editions are supported?
We build and validate for Odoo 17, 18 and 19, on both Community and Enterprise. Tell us your exact version and edition at scoping and we target that build; the delivered code follows current Odoo ORM, security (ir.model.access.csv plus record rules), and view conventions so it stays upgradeable.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
Engineering Change Management (PLM/ECO)
Build-to-order Odoo ECO workflow: BOM versioning, revision diff, approval routing, e-sign & effectivity dates for controlled PLM changes.
- Stage-driven Engineering Change Order (ECO) pipeline — Draft, Under Review, In Approval, Approved, Effective, Rejected — modeled as a Kanban stage_id workflow you can rename and extend
- BOM versioning that snapshots the released Bill of Materials into a working revision on ECO creation, so the original is never overwritten
- Line-by-line BOM revision diff computed server-side (added/removed components, quantity deltas, operation and routing changes) via @api.depends compute methods
- Configurable approval routing per change type — sequential or parallel approvers — with role-based approval gates before a change can be released