ECO Approvals & Stages in Odoo 18 PLM
By Braincuber Team
Published on December 26, 2025
Engineering teams making product changes via email threads create chaos: design changes to circuit boards go straight to production without safety review, material substitutions happen without cost analysis approval, BoM revisions lack version control causing assembly line confusion when workers don't know which revision to follow, and critical changes bypass quality checks because there's no formal approval process—leading to recalls when flawed designs ship.
Odoo 18's ECO (Engineering Change Order) Approvals system transforms ad-hoc design changes into controlled, traceable workflows. Define multi-stage approval processes where design changes require engineering manager sign-off, cost impacts need finance approval, and safety modifications must pass quality review before implementation. Each ECO tracks version history, impact analysis, and approval signatures—preventing unauthorized changes while maintaining complete audit trails for compliance and warranty claims.
ECO Approval Features:
- Multi-stage approval workflows
- Role-based approval assignment
- Three approval types (Optional, Required, Comment-only)
- BoM version control and tracking
- Impact analysis on components and operations
- Component change tracking
- Kanban visual workflow
- Complete audit trail with signatures
Understanding ECO (Engineering Change Orders)
ECOs formalize the process of modifying product designs, Bills of Materials (BoM), or manufacturing routings.
Why ECO Management Matters
Controlled Changes
Prevent rogue design changes—all modifications follow structured approval process before reaching production
Version Control
Track BoM evolution over time—easily reference previous revisions or rollback changes if needed
Team Collaboration
Engineering, manufacturing, quality, and finance teams coordinate on changes—everyone sees impact before approval
Compliance
Complete audit trail with approval signatures—prove changes followed proper procedures for regulatory compliance
Step 1: Install PLM Module
Installation
- Go to
Apps - Search for "PLM" (Product Lifecycle Management)
- Click
Install - Wait for installation to complete
Note: PLM module requires Manufacturing module as prerequisite.
Step 2: Configure ECO Stages
Access Stage Configuration
- Open
PLMmodule - Navigate to
Configuration→ECO Stages - View existing stages or click
Newto create custom stage
Stage Configuration Fields
| Field | Purpose | Example |
|---|---|---|
| Stage Name | Descriptive name for workflow stage | New, In Progress, Validated, Effective |
| ECO Type | Category of change order | BoM Updates, New Product Introduction |
| Folded in Kanban | Hide stage in Kanban board initially | Enable for "Effective" (final stage) |
| Allow Apply Changes | Enable component/operation modifications | Enable for "In Progress" stage |
| Final Stage | Mark as workflow completion stage | Enable for "Effective" stage |
Step 3: Configure Approval Rules
Approval Types
Optional Approval
Type: "Approval, but the approval is optional"
User CAN approve, but approval not mandatory—ECO can proceed to next stage without waiting
Required Approval
Type: "Is required to approve"
Approval MANDATORY—ECO blocked from advancing until designated user approves
Comment Only
Type: "Comments only"
User comment treated as approval—lightweight review without formal approve/reject
Adding Approvals to Stage
- In stage configuration, scroll to "Approvals" section
- Click
Add a Line - Configure:
- Role: Approver's role (Engineering Manager, Quality Lead, etc.)
- User: Specific person responsible for approval
- Approval Type: Select Optional, Required, or Comment-only
- Save stage configuration
Example: BoM Update Workflow
4-Stage Approval Process:
New
Initial submission stage
Approval: Optional (Engineering Reviewer)
Can Apply Changes: No
Purpose: Initial review without blocking
In Progress
Engineering makes changes
Approval: None
Can Apply Changes: Yes ✓
Purpose: Add components, modify operations, update BoM
Validated
Quality review
Approval: Comment-only (Quality Manager)
Can Apply Changes: No
Purpose: Quality feedback before final approval
Effective
Final sign-off
Approval: Required (Engineering Director)
Can Apply Changes: No
Purpose: Formal approval to release to production
Step 4: Create ECO for BoM
ECO Creation
- Access BoM: Go to BoM you want to modify
- Open Changes: Click
Changesmenu button - Create ECO: Click
New - Configure ECO:
- Description: What are you changing (e.g., "Upgrade Packaging Material")
- Type: Select ECO type (BoM Updates)
- Applies To: Bill of Materials
- Bill of Materials: Select specific BoM
- Update Version: Enable to increment BoM version number
- Start Revision: Click
Start Revisionbutton
Step 5: Apply Changes
Making Modifications
- ECO advances to "In Progress" stage (or stage with "Allow Apply Changes" enabled)
- Click "Revision" smart button to view BoM revision
- Add/remove components:
- Add new components to Components tab
- Remove obsolete components
- Adjust quantities
- Modify operations if needed in Operations tab
- Return to ECO view
- Review changes in "Component Changes" tab
- Click
Apply Changesbutton
Note: Changes are staged but not final until ECO completes all approval stages.
Step 6: Navigate Approval Workflow
Approval Actions by Type
Optional Approval
Assigned user can approve OR skip without blocking progression:
- Click "Approve" to formally sign off
- OR advance to next stage without approval
Required Approval
ECO BLOCKED until approval received:
- Assigned user MUST click "Approve" button
- Cannot advance to next stage until approved
- Can reject if changes need rework
Comment-Only Approval
Adding comment serves as approval:
- Add comment in comment field
- Click "Done" button
- Comment logged as approval signature
Version Control
BoM Versioning
Automatic Version Increment
When ECO completes with "Update Version" enabled, BoM version increases (1 → 2 → 3...)
Historical Tracking
View version history in BoM's Miscellaneous tab—see all previous revisions
Rollback Capability
If new version has issues, reference previous version to restore known-good configuration
Best Practices
Match Approvals to Risk
Use Required approvals for safety-critical or high-cost changes. Use Optional for minor cosmetic updates. Match rigor to impact.
Cross-Functional Approvers
Include approvers from Engineering, Quality, Manufacturing, and Finance—each sees impact from their perspective before release.
Document Changes Clearly
Write detailed ECO descriptions explaining WHY change is needed, WHAT is changing, and IMPACT on cost/performance/compliance.
Version All Changes
Always enable "Update Version" for ECOs—even minor changes deserve version increment for complete historical tracking.
Frequently Asked Questions
Conclusion
Odoo 18's ECO Approvals system transforms engineering changes from risky ad-hoc modifications into controlled, traceable workflows. By defining multi-stage approval processes with optional, required, and comment-based sign-offs, you ensure every design change receives appropriate scrutiny—lightweight review for minor tweaks, multi-department approval for critical modifications—before reaching production.
Version control maintains complete BoM history for regulatory compliance and warranty claims, while impact analysis shows exactly what changed between revisions. Whether you're managing simple BoM updates or complex new product introductions across engineering, quality, and finance teams, PLM's approval workflow ensures changes follow proper procedures, preventing costly production errors while maintaining the agility to implement improvements quickly when all stakeholders align.
Need Help with Product Lifecycle Management?
Our PLM experts can help you design approval workflows, configure ECO types and stages, implement version control strategies, train engineering teams, integrate with PDM systems, and build complete product change management processes that balance control with agility.