PLM stands for product lifecycle management, and Odoo has a PLM capability. For manufacturers whose products change and who need control over those changes, it is worth understanding what Odoo PLM does and, importantly, which edition of Odoo provides it. This piece explains Odoo PLM.
The problem PLM addresses
Products change. A component is revised, a design is improved, a supplier issue forces a substitution. Each change means a change to the bill of materials, and BOM changes are consequential, because the BOM feeds planning, purchasing, production, and costing. An uncontrolled BOM change, made directly with no record of who changed what, why, when, and with no review, is a real risk: the factory may build the wrong revision, purchasing may order the wrong parts, and nobody can reconstruct what happened. PLM is the discipline, and the software capability, that brings change under control.
What Odoo PLM provides
Odoo's PLM capability is built around the engineering change order, usually called an ECO. An ECO is a controlled, tracked record of a proposed change to a product or its bill of materials. Rather than editing a production BOM directly, a change is raised as an ECO, and the ECO carries the change through a controlled path.
The core things Odoo PLM provides are:
- Engineering change orders, so every BOM change is a deliberate, recorded event rather than a silent edit.
- BOM versioning, so a manufacturer has a controlled history of BOM revisions and always knows which version is current.
- Approval workflow, so a change is reviewed and approved before it becomes the production BOM, rather than taking effect the moment someone makes it.
- Change visibility, so the impact of a proposed change can be considered before it is applied.
Together these turn BOM change from a risk into a managed process.
Who needs Odoo PLM
Not every manufacturer needs formal PLM. A manufacturer with stable products that rarely change can manage with care. PLM earns its place where products change often enough, or where the consequences of an uncontrolled change are serious enough, that change must be formal and traceable. That includes manufacturers in fast-moving product areas, manufacturers in regulated industries where controlled, documented change is a requirement, and manufacturers whose products are complex enough that the impact of a change needs review before it is applied. For those, Odoo PLM is the difference between controlled and uncontrolled engineering change.
The important edition point
Here is the point a manufacturer must know when planning. The PLM capability, with engineering change orders and the formal versioning and approval workflow, is part of Odoo Enterprise. It is not included in Odoo Community. The core Manufacturing application, bills of materials, manufacturing orders, work centers, routing, is available in Community, but formal PLM is an Enterprise capability.
This matters for the decision. A manufacturer that genuinely needs formal engineering change control should plan on Odoo Enterprise. A manufacturer on Odoo Community that needs some change discipline can manage BOM changes more manually, using naming conventions for versions, recording change reasons in the record's history, and using activities for review steps, but that is a workaround, not the controlled ECO process that PLM provides. A manufacturer should decide honestly whether its change-control needs require Enterprise.
The takeaway
Odoo PLM brings product change under control through engineering change orders, BOM versioning, and an approval workflow, turning a risky silent edit into a managed, traceable process. It is needed by manufacturers whose products change often or whose industry demands controlled change, and it is an Odoo Enterprise capability, not part of Community. A manufacturer that needs formal change control should factor that into its edition decision. For how we approach Odoo for manufacturers, see our ERP practice.