Skip to content

How to Configure PLM and Engineering Change Orders in Odoo 19

DeployMonkey Team · March 24, 2026 9 min read

Overview

The PLM module in Odoo 19 Enterprise manages product engineering changes through formal Engineering Change Orders (ECOs). It provides BOM versioning, multi-stage approval workflows, and complete revision history. ECOs ensure that product changes are reviewed, approved, and implemented in a controlled manner. Note: PLM is available in Odoo Enterprise only.

Prerequisites

  • Odoo 19 Enterprise with Manufacturing module
  • The mrp_plm module installed
  • BOMs configured for your products
  • PLM Manager access

Step 1: Install PLM

Navigate to Apps and search for PLM (technical name: mrp_plm). Install the module. This adds ECO management, BOM versioning, and approval workflows to Manufacturing.

Step 2: Configure ECO Stages

Navigate to PLM > Configuration > Stages. Set up your approval pipeline:

StagePurpose
NewECO just created, under initial review
In ProgressEngineering work being done on the change
ValidationRequires approval from stakeholders
ApprovedChange approved, ready to implement
DoneChange implemented in production BOM

Each stage can have approval requirements — specific users or groups who must sign off before the ECO advances.

Step 3: Configure ECO Types

Navigate to PLM > Configuration > ECO Types. Create types that match your change categories:

  • BOM Change — Component additions, removals, or substitutions
  • Routing Change — Operation modifications or resequencing
  • Product Specification — Non-BOM product attribute changes
  • Cost Reduction — Changes aimed at reducing manufacturing cost
  • Quality Improvement — Changes to address quality issues

Step 4: Create an Engineering Change Order

Navigate to PLM > ECOs and click New:

  • Description — Clear description of the proposed change
  • Type — Select the ECO type
  • Product — The product being changed
  • Bill of Materials — The specific BOM to modify
  • Responsible — The engineer handling the change
  • Effectivity — When the change takes effect (date or serial number)

Step 5: Make Changes in the ECO

Within the ECO, modify the BOM without affecting the current production version:

  • Add, remove, or replace components
  • Modify component quantities
  • Add or change routing operations
  • Update product specifications

All changes are staged within the ECO and only applied to the production BOM when the ECO is approved and implemented.

Step 6: Approval Workflow

As the ECO moves through pipeline stages:

  1. The engineer completes changes and advances to the Validation stage
  2. Designated approvers receive notifications
  3. Each approver reviews the proposed changes
  4. Approvers sign off or request revisions
  5. Once all required approvals are obtained, the ECO advances to Approved

Step 7: Implement the Change

When the ECO reaches the implementation stage:

  1. Click Apply Changes to update the production BOM
  2. The current BOM is versioned — the previous version is archived
  3. The new BOM becomes the active version
  4. All future manufacturing orders use the updated BOM

Step 8: Track Revision History

Each BOM maintains a version history:

  • View past versions of any BOM to see historical component lists
  • Each version links to the ECO that created it
  • Compare versions to identify what changed between revisions

Community Edition Alternative

Odoo Community does not include PLM. To manage engineering changes:

  • Manually version BOMs using naming conventions (e.g., "Product A - BOM v2.1")
  • Use chatter notes on BOMs to document changes
  • Archive old BOMs and create new ones for each revision
  • Track changes in external documentation

Best Practices

  • Require at least two approvers for safety-critical or high-cost changes
  • Include cost impact analysis in ECOs to inform approval decisions
  • Set effectivity dates to coordinate changes with production schedules
  • Review ECO throughput monthly to identify bottlenecks in your approval process
  • Use ECO types consistently for accurate change analysis and reporting