PLM / Engineering Change
BoM versioning, ECO workflow, where-used and full revision history
Manufacturing teams on Odoo Community have no controlled way to change a BoM — edits are silent and untracked. This module adds proper product-lifecycle management: Engineering Change Orders that move through draft, submission, approval and effectivity; BoM revisioning that bumps a revision letter and snapshots the prior line set into an immutable history record; and a where-used explorer that shows every BoM consuming a component. Changes are described as explicit lines and applied atomically to the target BoM only when the ECO becomes effective.
Key Features
Engineering Change Orders
ECOs flow draft → submitted → approval → approved → effective, with change type (add/remove/replace component, quantity change, document update), priority and a named approver matrix.
BoM Revisioning
Each manufacturing BoM carries a revision letter/number; an approved ECO bumps the revision and stores a copy of the prior lines as an immutable revision-history record.
Explicit Change Lines
Every change is captured as old-vs-new component and old-vs-new quantity, validated and applied atomically to the BoM the moment the ECO turns effective.
Where-Used Explorer
For any component, list every BoM and parent product that consumes it, with quantities — a one-click action straight from the product form.
Immutable Revision History
A per-BoM log records the ECO that produced each revision, the date, the user and a stored snapshot of the line set exactly as it was — full traceability.
Start-ECO Wizard
Launch an ECO against a chosen BoM pre-seeded with its current lines, so engineers start from reality rather than a blank form.
PLM Without Enterprise
Odoo's Enterprise PLM is billed per user; this delivers the core change-control loop for Community at a single price.
Audit-Grade Traceability
Every BoM change is approved, dated, attributed and snapshotted — the evidence quality and ISO audits expect.
Screenshots
Engineering Changes
Revision History
Start Engineering Change
Why Choose This Module
Discrete and process manufacturers, engineering and design teams, and quality managers who need controlled BoM changes, approval sign-off and complete revision traceability without upgrading to Enterprise.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: base, mail, mrp
- Support: support@pokutsoft.com
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Manufacturing (mrp) • Inventory (stock) |
| Lines of code | 867 |
| Technical Name |
gb_plm_engineering_change |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module