Product Lifecycle Management: From Design to End-of-Life in Odoo

The average manufactured product goes through 15-20 engineering changes during its production lifetime. Each change touches the bill of materials, manufacturing instructions, quality specifications, supplier agreements, inventory, and potentially customer documentation. Without a system to manage these changes, engineering revisions become a source of costly errors: production builds the wrong version, purchasing orders obsolete components, and quality inspects against outdated specifications.

Product Lifecycle Management (PLM) provides the framework to control how products evolve from initial concept through design, production, service, and eventual end-of-life. When integrated with manufacturing ERP, PLM ensures that every department works from the same revision and that engineering changes flow through the organization in a controlled, traceable manner.

This article is part of our Manufacturing in the AI Era series.

Key Takeaways

• BOM versioning in Odoo ensures manufacturing always builds from the approved revision while engineering works on the next version without disrupting production
• Engineering Change Orders (ECOs) provide auditable control over product modifications, preventing unauthorized changes and ensuring proper review
• Phase-gate processes structure product development into stages with defined deliverables and approval gates, reducing development risk
• PLM-manufacturing integration eliminates the gap between "what engineering designed" and "what the factory builds"

---

Product Lifecycle Stages

Every product passes through distinct lifecycle stages, each with different priorities, activities, and data requirements.

| Stage | Primary Activity | Key Deliverables | Odoo Support | |-------|-----------------|------------------|--------------| | Concept | Market research, feasibility | Business case, initial specs | CRM (opportunity), Documents | | Design | Engineering development | CAD models, prototype BOM | PLM (ECO), Manufacturing (BOM) | | Prototype | Build and test samples | Test results, design validation | Manufacturing (pilot orders), Quality | | Pre-Production | Process validation, tooling | Production BOM, work instructions | Manufacturing (routing), Quality (PPAP) | | Production | Volume manufacturing | Finished products, quality records | Manufacturing, Inventory, Quality | | Service | Warranty, spare parts, updates | Service records, spare parts BOMs | Helpdesk, Inventory, Field Service | | End-of-Life | Phase-out, discontinuation | Last-buy notifications, replacements | Sales (notifications), Inventory (phase-out) |

Managing Stage Transitions

Each stage transition represents a decision point where stakeholders evaluate whether the product should proceed, require modification, or be cancelled. Odoo supports these transitions through:

• Approval workflows on ECOs that require sign-off from defined reviewers
• Quality checklists that document stage-gate deliverables
• Dashboard visibility showing all products by lifecycle stage
• Automated notifications to stakeholders when products move between stages

---

Bill of Materials Versioning

The Version Control Problem

A bill of materials is the DNA of a manufactured product. It defines every component, quantity, and assembly relationship. When engineering changes a BOM, several scenarios can coexist:

• Current production runs build from revision B
• Engineering is developing revision C with component changes
• Customer service supports products built on revisions A and B
• Purchasing has orders in flight for revision B components

Without version control, these overlapping realities create confusion. Manufacturing might accidentally build revision C before it is approved. Purchasing might order revision A components that are no longer needed.

Odoo BOM Versioning Features

Odoo's PLM module supports BOM versioning through:

Active/Inactive BOMs: Only one BOM version is active for manufacturing at any time. Previous versions are retained for reference and service support but are not available for new manufacturing orders.

ECO-Driven Changes: BOM modifications are always made through Engineering Change Orders, never directly on the active BOM. This ensures every change is reviewed, approved, and documented.

Effectivity Dates: BOM versions can be scheduled with start and end dates. This enables seamless transitions where the new BOM takes effect on a specific date and the old BOM automatically deactivates.

Where-Used Analysis: Before modifying a component, engineers can see every BOM that uses it. This prevents unintended consequences where a change to a common component affects products the engineer did not consider.

BOM Structure Best Practices

| Practice | Description | Benefit | |----------|-------------|---------| | Multi-level BOMs | Separate sub-assemblies from final assembly | Independent versioning of sub-assemblies | | Phantom BOMs | Sub-assemblies that are not stocked | Simplified inventory without losing BOM structure | | Kit BOMs | Products assembled at shipping | Clear picking lists, no separate manufacturing step | | Configurable BOMs | Variants managed through product configurator | Single BOM serves multiple product variants | | Reference Designators | Position identifiers for components | Clear assembly instructions, easier troubleshooting |

---

Engineering Change Orders

The ECO Workflow

Engineering Change Orders provide a controlled process for modifying products. A properly implemented ECO workflow ensures that changes are justified, reviewed, approved, and implemented systematically.

Step 1: Change Request An ECO originates from various sources: engineering improvement, customer feedback, quality issue, cost reduction opportunity, or supplier notification. The requester documents:

• What needs to change and why
• Affected products and BOM levels
• Proposed effective date
• Impact assessment (cost, lead time, inventory, tooling)

Step 2: Impact Analysis Before approval, the change is analyzed for cross-functional impact:

• Manufacturing: Does the change require new tooling, different equipment, or modified work instructions?
• Inventory: Is there existing stock of obsolete components that must be used, scrapped, or returned?
• Purchasing: Are there open purchase orders for affected components?
• Quality: Do inspection plans, control limits, or test procedures need updating?
• Cost: How does the change affect product cost?

Step 3: Review and Approval Odoo's ECO approval workflow routes the change to designated reviewers based on the type and scope of the change:

• Minor changes (documentation, non-functional): Engineering manager approval
• Moderate changes (component substitution, same form/fit/function): Engineering + quality approval
• Major changes (design change, new tooling): Full cross-functional review board

Step 4: Implementation After approval, the ECO triggers coordinated actions:

• BOM updated with new revision
• Work instructions revised in manufacturing routing
• Quality inspection plans updated
• Purchasing notified of component changes
• Existing inventory dispositioned (use-up, scrap, or return)
• Customer documentation updated if externally visible

Step 5: Verification The ECO remains open until implementation is verified:

• First articles from the new revision pass inspection
• Updated documentation is in place
• Old revision materials are dispositioned
• All affected systems reflect the change

---

Phase-Gate Product Development

Structuring Development with Gates

Phase-gate processes divide product development into phases separated by decision gates. Each gate requires specific deliverables and stakeholder approval before the project proceeds to the next phase.

Gate 0: Idea Screening

• Deliverables: Market opportunity description, preliminary business case, strategic fit assessment
• Decision: Investigate further or decline
• Odoo: CRM opportunity created, initial documentation in Documents module

Gate 1: Concept Approval

• Deliverables: Detailed market analysis, technical feasibility study, preliminary cost estimate, project plan
• Decision: Proceed to design or decline
• Odoo: Project created in Projects module, budget approved in Accounting

Gate 2: Design Approval

• Deliverables: Completed design, prototype BOM, risk assessment (DFMEA), initial test plan
• Decision: Build prototypes or redesign
• Odoo: BOM created in Manufacturing, ECO initiated for design freeze

Gate 3: Prototype Validation

• Deliverables: Prototype test results, design validation report, updated BOM, process plan (PFMEA)
• Decision: Proceed to pre-production or redesign
• Odoo: Quality records from prototype testing, Manufacturing pilot orders

Gate 4: Production Readiness

• Deliverables: Production BOM validated, work instructions finalized, quality plan approved, PPAP complete
• Decision: Launch production or correct deficiencies
• Odoo: Final BOM revision activated, routings configured, quality control points set

Gate 5: Post-Launch Review

• Deliverables: Production performance data, initial quality data, customer feedback, financial performance
• Decision: Continue, modify, or discontinue
• Odoo: Manufacturing KPIs, Quality dashboards, Sales data analysis

---

PLM Integration with Manufacturing

Closing the Design-to-Production Gap

The gap between what engineering designs and what the factory builds is one of the most expensive problems in manufacturing. PLM-manufacturing integration closes this gap through:

Automatic BOM Transfer: When an ECO is approved, the new BOM revision becomes available to manufacturing without manual re-entry. Component changes, quantity updates, and routing modifications flow directly from engineering to the shop floor.

Work Instruction Synchronization: Updated assembly instructions, quality inspection criteria, and process parameters propagate to manufacturing work orders. Operators see the current revision's instructions, not a printed copy that may be outdated.

Change Effectivity Management: The system manages the transition between old and new revisions, ensuring that work orders started before the change use the old BOM while new orders use the updated revision. No mixed-revision products leave the factory.

Deviation Control: When manufacturing encounters a situation where they cannot build exactly to the BOM (component substitution, process deviation), the system captures the deviation with documentation and approval, maintaining traceability.

Document Management for Product Data

| Document Type | Purpose | Odoo Location | |---------------|---------|---------------| | CAD Files/Drawings | Define product geometry | Documents, linked to BOM | | Assembly Instructions | Guide manufacturing | Manufacturing routing operations | | Inspection Plans | Define quality checks | Quality control points | | Material Specifications | Define material requirements | BOM component notes, linked documents | | Test Procedures | Validate product performance | Quality procedures, linked to gate deliverables | | Customer Specifications | Capture requirements | Sales order specifications, Documents |

---

End-of-Life Management

Products eventually reach end-of-life (EOL). Managing EOL systematically prevents two common problems: continuing to sell and support products that are no longer viable, and cutting off customers abruptly without alternatives.

EOL Process in Odoo

Phase 1: EOL Decision (6-12 months before EOL)

• Analyze declining sales trends, increasing support costs, component obsolescence risks
• Identify replacement products or upgrade paths for customers
• Set the planned EOL date

Phase 2: Last-Buy Notification (3-6 months before EOL)

• Notify customers of upcoming EOL through CRM and email marketing
• Open final ordering window for spare parts and replacement units
• Calculate final production quantities based on last-buy orders and service requirements

Phase 3: Final Production

• Execute last manufacturing run
• Build service spare parts inventory based on installed base analysis
• Update product status in Odoo (mark as not for sale, but available for service)

Phase 4: Service Continuation (1-5 years after EOL)

• Continue spare parts supply from reserved inventory
• Maintain service documentation
• Track remaining spare parts inventory and notify when supplies are running low
• Guide customers toward replacement products

---

Frequently Asked Questions

How does Odoo's PLM compare to dedicated PLM software like Siemens Teamcenter or PTC Windchill?

Dedicated PLM software offers deeper capabilities for complex product development, particularly in CAD integration, simulation management, and multi-site engineering collaboration. Odoo's PLM module provides 80% of the functionality that most small and mid-size manufacturers need: BOM versioning, ECO management, approval workflows, and manufacturing integration. The advantage of Odoo PLM is that it shares the same database as manufacturing, inventory, and quality, eliminating the integration challenges that plague standalone PLM implementations. For manufacturers without complex CAD integration requirements, Odoo PLM is typically sufficient and significantly more cost-effective.

What is the difference between a BOM revision and a product variant?

A BOM revision changes the design of the same product. The revision C of a circuit board replaces a capacitor with a different value to fix a reliability issue. All units going forward use the new BOM. A product variant is a planned option within the same product family. A laptop might have variants for different processors, memory sizes, and storage capacities. Variants use product configurators with optional BOM components. In Odoo, variants are managed through product attributes and configurable BOMs, while revisions are managed through ECOs and BOM versioning.

How many approval levels should an ECO workflow have?

The number of approval levels should match the risk of the change. Over-engineering the approval process slows innovation and frustrates engineers. Under-engineering it allows changes that cause production problems. A practical approach uses three tiers: engineering-only approval for documentation and non-functional changes, engineering plus quality for component changes that maintain form-fit-function, and full cross-functional review for changes that affect product performance, cost, or manufacturing process. Most ECOs (60-70%) should fall into the first two tiers and be approved within 2-3 days.

---

What Is Next

Product lifecycle management is the discipline that ensures your products evolve systematically from concept through end-of-life. Odoo provides the integrated platform to manage BOMs, control engineering changes, enforce phase-gate development processes, and maintain the connection between engineering intent and manufacturing reality.

ECOSIRE implements Odoo PLM and manufacturing systems that give manufacturers full control over their product lifecycles. From BOM versioning configuration through ECO workflow design, our team helps establish PLM practices that reduce errors and accelerate time-to-market.

Explore our related guides on quality management and ISO 9001 and lean manufacturing with Odoo, or contact us to discuss your PLM requirements.

---

Published by ECOSIRE — helping businesses scale with AI-powered solutions across Odoo ERP, Shopify eCommerce, and OpenClaw AI.