Most Odoo implementations follow a playbook designed for make-to-stock or repetitive manufacturing environments. For engineer-to-order manufacturers, this standard approach creates more problems than it solves. Instead of gaining operational control, ETO companies end up managing engineering variations in spreadsheets, running production from outdated drawings, and discovering cost overruns months after delivery. The culprit isn’t Odoo itself—it’s the configuration strategy that ignores the fundamental realities of project-based, engineering-driven manufacturing.
Five specific mistakes account for the majority of ETO implementation failures. Each one directly erodes margins and schedule reliability by forcing the organization to work around the system rather than through it. These mistakes fall into predictable categories: data structure, process flow, version control, system integration, and financial visibility. Understanding them helps ETO manufacturers design Odoo implementations that support how their business operates.
Mistake 1: Treating ETO Like Standard BOM + Simple MO
The most common mistake is treating Odoo as if every order uses fixed bills of materials and standard routings. This approach works well for companies that manufacture the same product repeatedly, but it breaks down immediately in ETO environments where each job requires engineered variations, optional features, and order-specific component selections.
The consequences appear quickly. Engineers maintain the actual product structure in CAD or spreadsheets while Odoo holds generic placeholder BOMs labeled “Custom Valve” or “Special Assembly.” Planners cannot see actual component demand because the system shows only high-level items. Manufacturing orders lack the detail needed for execution, forcing shop floor supervisors to work from separate engineering documentation that may or may not match what’s in Odoo. The ERP becomes a reporting tool rather than an operational control system.
The solution requires configuring Odoo to support order-specific BOMs and routings. This means using BOM variants, configurable products, or project-linked structures that capture the actual engineered design for each order, not just a template. The goal is to make Odoo the single source for what gets built, eliminating parallel documentation systems that create confusion and errors.
Mistake 2: No Robust Quote → Project → MO Flow
ETO manufacturers often configure Odoo to automatically create manufacturing orders from sales orders, bypassing the critical engineering and approval phase that defines what will actually be manufactured. This shortcut treats custom engineering as just another step in production rather than a distinct phase with its own dependencies and approvals.
The damage compounds throughout the project lifecycle. Production starts from provisional or incomplete designs. Engineering changes hit live manufacturing orders that have already triggered purchasing and work center scheduling. Customer approval cycles have no formal home in the system, so sales and engineering coordinate through email while Odoo shows orders as “in production.” Delivery dates become fictional because the system assumes the design is complete when it’s still in review. Change orders cascade through purchasing, production, and quality without traceability or proper impact analysis.
The correct approach structures the workflow so that sales quotes create projects with engineering tasks, design reviews, and BOM-freeze milestones. Manufacturing orders and purchase requisitions should be released only after engineering signs off on the final design. This configuration reflects the reality that ETO orders are projects first and production jobs second, ensuring the system reflects actual workflow rather than fighting against it.
Mistake 3: Weak BOM Versioning and Engineering Change Control
In ETO manufacturing, nearly every job involves a unique or modified product configuration. Without formal revision management and engineering change order processes, BOM integrity collapses under the weight of project-specific variations.
The typical pattern is both common and dangerous. Engineers and planners duplicate and tweak BOMs for each project without revision tracking. Changes are made to live manufacturing orders after purchasing has started, with no record of what changed or why. Documentation diverges among engineering, purchasing, and the shop floor. When a customer calls six months after delivery asking for replacement parts, no one can definitively say which revision was shipped. For regulated industries, this lack of traceability isn’t just inconvenient—it’s a compliance failure that puts the entire business at risk.
Addressing this mistake requires implementing formal ECO workflows with approval gates and automatic versioning. Each manufacturing order must link to a specific BOM revision, creating an auditable trail from quote to delivery. The organization needs clear rules for when a change creates a new revision versus an inline correction. This isn’t bureaucracy for its own sake—it’s treating BOM versioning as a compliance and risk-management requirement that protects both the company and its customers.
Mistake 4: Misaligned CAD/PLM and Odoo Structures
For ETO manufacturers, the engineering design in CAD or PLM is the source of truth for product definition. Without a disciplined process to translate engineering structures into ERP-readable BOMs and routings, the disconnect leads to cascading failures across operations.
The misalignment manifests in several ways. Planners work from oversimplified structures that hide component-level lead times and supplier alternatives. Purchasing buys incomplete or incorrect parts because CAD updates don’t reliably propagate to Odoo. The shop floor receives work orders that reference Odoo data, but works from drawings that no longer match. Engineering changes loop endlessly because there’s no clear handoff protocol between systems. Each disconnect multiplies errors and delays, forcing people to spend more time reconciling data than actually building products.
The solution requires establishing formal integration or a structured data handoff process that maps CAD/PLM assemblies to Odoo products and BOMs at the appropriate level of detail. This means clearly defining ownership: which system is the source of truth for what, and how changes flow between them. The goal is structural alignment that ensures Odoo accurately reflects the engineering design, not just collecting file attachments that sit unused in a document repository.
Mistake 5: Inadequate Job-Level Costing and Margin Visibility
ETO profitability is fundamentally job-specific. Each project has unique engineering hours, custom components, and subcontractor steps that must be measured against the original quote. Relying on standard product costs and generic cost centers without tying these project-specific elements back to individual jobs destroys financial visibility.
The consequences hit the bottom line directly. Management cannot see which types of custom projects are profitable and which quietly lose money. Quoting assumptions never improves because actual labor and material variances aren’t visible at the job level. Engineering hours spiral on complex designs, with no red flags until quarterly reviews reveal the damage. Chronic underpricing of engineering-intensive work erodes margins invisibly. The finance team sees aggregate results but cannot diagnose which ETO characteristics—product complexity, customer change patterns, or engineering scope—actually drive profitability.
The fix requires structuring projects, manufacturing orders, purchasing, timesheets, and subcontracting so every ETO order has clear cost accumulation and margin analysis. Use project-based accounting to capture both direct production costs and indirect engineering and management time against the original quote. This transforms job-level profitability from a forensic exercise conducted months after delivery into a real-time operational metric that guides both execution and future quoting.
Designing Odoo Around the ETO Reality
These five mistakes share a common root: treating ETO manufacturing as standard, repetitive production with some custom options rather than designing Odoo to reflect the project-based, engineering-driven reality of how these companies operate. The objective of an ETO Odoo implementation isn’t to automate a factory—it’s to encode your engineering governance, project workflow, version control discipline, system integration strategy, and job costing model into a system that enforces consistency and captures data for continuous improvement.
Companies that get ETO implementations right stop fighting their ERP and start using it to scale their engineering-driven business model. Addressing these five areas lays the foundation for reliable delivery dates and defensible margins. The difference between a successful and failed ETO implementation isn’t Odoo’s capability—it’s whether the configuration reflects how engineer-to-order businesses actually work.
When costing, engineering, and production are not fully aligned, profitability becomes harder to measure and manage. Book a consultation with our team to explore how your Odoo environment can better support accurate job costing and real-time operational insight.
DISCLAIMER: The information in this article reflects the views and opinions of Novobi, based on publicly available information, and is intended for informational purposes only. It is not legal or financial advice. All trademarks are the property of their respective owners.
