Odoo Manufacturing · intro · 8 min read
Common Manufacturing Mistakes in Odoo
Frequent Odoo manufacturing failures: bad BoMs, dual spreadsheets, ignored subcontract stock, weak shop-floor UAT, and go-live without procurement alignment.
Last reviewed 2026-07-30 · Estimated effort: 1–2 weeks typical discovery
Table of contents
Common manufacturing mistakes in Odoo cluster around master data (BoMs, routes, UoM), parallel systems (Excel still authoritative), and weak handoffs (sales configurator to MO, subcontract resupply).
Go-live without shop-floor user acceptance on the actual MO screen creates shadow processes that erode inventory accuracy within weeks.
Migration projects repeat the same errors when BoMs are bulk-loaded without open MO cutover rules or when custom shop-floor modules are untested on the new version.
Teams often know Odoo can manufacture but discover too late that their implementation treated MRP as a checkbox after accounting go-live.
This article lists mistakes we see repeatedly — use it as a pre-go-live audit, not as blame assignment.
Incomplete BoMs, wrong quantities, missing phantom flags, and variant BoM gaps produce MOs that do not match engineering. Costing and picks diverge immediately.
Dual maintenance — engineering truth in Excel, operational truth in Odoo — guarantees drift. Pick one system of record and migration path for legacy sheets.
MTO on products you stock, MTS without reorder rules, and buy routes on assemblies you build in-house each create opposite pain: surprise MOs or chronic stockouts.
Promise dates set in sales without component lead times train customers to distrust Odoo before manufacturing stabilizes.
Shipping components to vendors without resupply moves makes subcontract MOs impossible to close. Finance sees missing inventory; purchase sees service POs only.
FG posted to wrong locations blocks delivery even when production celebrates finishing the job.
Training on demo data instead of real BoMs means operators learn clicks not exceptions. Shop-floor supervisors must sign off on one full build in Odoo before cutover.
Ignoring barcode or tablet workflow when operators will not use desktop forms guarantees workarounds.
Bulk BoM import without UoM validation breaks every MO after upgrade. Custom work order modules may need retesting when core MRP changes between Odoo versions.
Link Migration guidance when manufacturing customizations must survive version jump.
- ✓Run a manufacturing mistake audit using this list four weeks before go-live.
- ✓Retire parallel planning spreadsheets with a named cutover date.
- ✓Require shop-floor sign-off on pilot MO for top three SKUs.
- ✓Reconcile subcontract locations before first vendor shipment in Odoo.
- ✓Align sales promise date policy with planner lead time data.
- ✓Test custom manufacturing modules on staging with production-volume data.
- !Treating manufacturing as phase two that never gets funded.
- !Letting sales add unstructured line notes instead of configured options.
- !Zero scrap recording — yields look perfect while costs bleed.
- !Work centers added for demo load charts with no operator adoption.
- !Assuming purchase go-live is independent of MO component need.
- !Skipping hypercare first month when MO volume spikes.
Manufacturing mistakes in Odoo are predictable — master data, routes, subcontract stock, and shop-floor adoption — and preventable with disciplined pilot builds.
Next, score your project against this list and assign owners to every red item before go-live.
- Owners named
- UAT scripts signed
- Rollback documented
- Hypercare roster ready
Trigger
Business event starts the flow.
Execute
Operate in the system of record.
Validate
Check outcomes and exceptions.
Close
Reconcile and hand off.
Frequently asked questions
What is the single fastest warning sign?
MOs confirmed with repeated component shortages on the same parts — usually BoM, route, or procurement timing issues, not operator error.
Can we fix BoMs after go-live?
Yes, but open MOs may need adjustment. Plan revision cutover rules and communicate with production before mass BoM edits.
How do mistakes differ on migration versus greenfield?
Migration repeats bad legacy BoM structure at scale; greenfield skips shop-floor UAT because team is small. Both need pilot MO discipline.
When should we pause go-live?
When pilot MO cannot complete pick-produce-deliver for a representative order and leadership has not accepted documented workaround scope.
Related articles
Planning an Odoo Manufacturing Project
Phases, scope, pilot products, data migration, training, and go-live criteria for Odoo manufacturing implementations — greenfield and upgrade.
View →Understanding Bills of Materials in Odoo
How to structure Odoo BoMs for single-level, multi-level, phantom, and subcontracting builds — with quantities, UoM, revisions, and costing implications.
View →Inventory Control in Manufacturing
Locations, routes, lots, reservation, and WIP handling in Odoo so manufacturing can find components and post finished goods where sales and shipping expect them.
View →Manufacturing Performance Metrics
KPIs and reporting in Odoo for on-time delivery, scrap, WIP aging, component shortages, and work center load — with owners and actionable thresholds.
View →Related services
Worried about manufacturing go-live risk?
Share your timeline and current blockers — we will prioritize a pre-go-live audit focused on MO path integrity.
