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.

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.