Odoo Manufacturing · intermediate · 11 min read
Planning an Odoo Manufacturing Project
Phases, scope, pilot products, data migration, training, and go-live criteria for Odoo manufacturing implementations — greenfield and upgrade.
Last reviewed 2026-07-30 · Estimated effort: 2–6 weeks typical implementation slice
Table of contents
Planning an Odoo manufacturing project starts with architecture choices (MTS, MTO, subcontract, configurators) and scopes pilot product families before enterprise-wide BoM load.
Parallel workstreams cover products and BoMs, locations and routes, purchase lead times, sales-to-MO rules, shop-floor execution, and reporting — with integration points tested on one end-to-end build.
Migration projects add cutover rules for open MOs, BoM revisions, and custom shop-floor modules. Development supports bespoke configurators; Migration owns version jump validation.
Manufacturing scope often arrives late in ERP projects — after warehouses and finance are configured for a generic distributor. Refitting routes and BoMs under go-live pressure causes expensive rework.
This article outlines phases and deliverables so manufacturing is a first-class workstream, not a phase two promise.
Document product mix, build models, subcontract use, configurator needs, and traceability requirements. Sign off MTS/MTO/ETO per family before configuring routes globally.
Identify custom modules or external CPQ integrations early — they affect timeline more than standard MO training.
- ▸Product family inventory and build complexity
- ▸Subcontract and vendor component flows
- ▸Configurator versus variant decision
- ▸Regulatory traceability (lots/serials)
Choose one pilot family representing your hardest BoM, not your simplest kit. Load BoMs, routings, work centers, vendors, and lead times for pilot scope only first.
Validate UoM, product categories, and costing method on pilot before mass import from legacy ERP.
Schedule location mapping, orderpoints, and buy routes before MO pilot. Purchase must receive components into manufacturing-reservable locations during pilot window.
Sales-to-MO testing belongs in the same sprint as MO pilot — not a separate sales phase.
Operators execute real MOs on pilot SKUs using the intended device (barcode, tablet, desktop). Supervisors sign checklist: pick, produce, scrap, backorder, FG putaway.
Train on exception paths — shortages, partial build, rework — not only happy path demo.
Go-live when pilot metrics hold: MO confirm without manual spreadsheet, component shortages visible, FG deliverable on SO test order. Define hypercare coverage for first production month peak.
Migration cutover requires open MO policy, BoM effective dates, and staged module upgrade testing per Migration guide.
- ✓Publish manufacturing workstream plan parallel to inventory and finance — not nested underneath.
- ✓Assign named owners for BoM data, routes, purchase lead times, and shop-floor UAT.
- ✓Time-box pilot to six to eight weeks with explicit exit criteria.
- ✓Run cutover rehearsal for migration with subset of real BoMs and one open MO.
- ✓Budget hypercare MO and shortage review daily for first two weeks live.
- ✓Cross-link Development for configurator modules; Migration for version upgrades.
- !Enterprise-wide BoM import before pilot proves structure.
- !Go-live date driven by finance while purchase lead times are dummy values.
- !Shop-floor training on sandbox products operators never build.
- !No rollback plan for manufacturing cutover weekend.
- !Configurator customizations untested on staging MO volume.
- !Hypercare ends before first seasonal production peak.
Manufacturing project planning is pilot-first master data plus shop-floor proof — architecture, purchase, and sales handoffs on one timeline.
Next, draft your pilot SKU list and go-live checklist using the architecture and common mistakes articles as gates.
- 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
How long should manufacturing pilot take?
Typically six to eight weeks for one product family including two full build cycles and SO-linked MTO test if applicable. Complex subcontract or configurator adds time.
Can we go live with partial catalog?
Yes — scope go-live families explicitly. Non-manufactured lines can live in Odoo while remaining BoMs load in waves with change control.
What about open MOs on migration weekend?
Decide finish-in-legacy vs migrate-open vs recreate — document per MO state. Migration guide covers transactional cutover patterns.
Do we need a dedicated manufacturing PM?
At least a named operations lead with time allocated. ERP PM coordinates; plant lead validates BoM and floor readiness.
Related articles
Choosing the Right Manufacturing Architecture
Decision framework for MTS, MTO, ETO, subcontracting, variants, and configurators in Odoo — matching product mix to routes, apps, and custom scope.
View →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.
View →What Is Odoo Manufacturing?
A practical definition of Odoo Manufacturing (MRP): BoMs, manufacturing orders, work centers, subcontracting, and how production connects to sales, stock, and purchasing.
View →Sales-to-Manufacturing Workflow
How confirmed sales orders trigger manufacturing orders, procurement, and delivery in Odoo for MTO, MTS, and configurable product lines.
View →Related services
Odoo Manufacturing Services
Implementation and optimization of BoM, MO, subcontracting, and shop-floor flows.
View →Odoo Migration
Version upgrades that preserve manufacturing data, BoMs, and custom shop-floor logic.
View →Dedicated Odoo Developer
Reserved capacity for manufacturing modules, reports, and backlog.
View →Building a manufacturing implementation plan?
Share greenfield or migration context and pilot scope — we will outline phases and readiness gates.
