Odoo Manufacturing · intermediate · 10 min read
Sales-to-Manufacturing Workflow
How confirmed sales orders trigger manufacturing orders, procurement, and delivery in Odoo for MTO, MTS, and configurable product lines.
Last reviewed 2026-07-30 · Estimated effort: 2–6 weeks typical implementation slice
Table of contents
Sales-to-manufacturing connects customer demand to production: product routes (MTO, manufacture, buy) decide whether SO confirmation creates an MO, triggers procurement, or reserves finished stock.
Promise dates on sales lines only hold if component lead times, MO duration, and subcontract steps are modeled — otherwise customer service commits dates the plant cannot hit.
Configurable and engineer-to-order lines need BoM snapshots on the order so MOs match the quote. Retail-driven replenishment may feed MTS MOs separately from direct SO links.
The break between sales and production is where Odoo projects succeed or fail. Sales confirms an order; manufacturing sees no MO. Or an MO appears for the wrong variant because routes were copied from a demo database.
This article maps the operational path from quotation through SO confirmation to MO and delivery.
Each product carries routes such as Manufacture, Buy, and Make To Order. MTO on a manufactured product typically creates procurement that explodes to an MO when stock is insufficient.
Delivered quantities on SO lines should align with how you ship finished goods — partial shipments, dropship, or make-to-order single delivery each need explicit policy.
- ▸MTO: demand pulls MO or PO at confirmation
- ▸MTS: SO consumes FG stock; replenishment MOs run separately
- ▸Kit or phantom lines: understand explosion at delivery versus MO
- ▸Multi-company: routes and warehouses per company
On confirmation, procurement rules evaluate need per line. Manufacturing app creates MOs linked to origin documents where configured — planners use these links to prioritize by customer date.
Delays often come from missing BoM on the ordered variant or components on backorder. Surface shortages on the SO or MO list rather than after the promised ship date.
Option-driven quotes must freeze BoM structure at confirmation. Custom modules often copy configured components to the MO or create a one-off BoM revision.
Cross-link Customization when sales uses configurators that standard MTO cannot interpret without extension.
Delivery orders reserve finished goods when MO completes. If production posts to a WIP location, ensure pick rules move FG to outbound locations before delivery validation.
Logistics operations with barcode shipping benefit from aligned location naming so pickers see the same bins manufacturing uses.
- ✓Document route per product family before sales go-live.
- ✓Show procurement/MO status on SO for customer service visibility.
- ✓Align promised date with cumulative lead time including subcontract.
- ✓Test partial ship scenarios for long-running MOs.
- ✓Use retail replenishment patterns only when ecommerce drives MTS — not mixed blindly with MTO SO lines.
- ✓Train sales not to swap variants after SO confirmation without planner review.
- !MTO route on products without BoM — MO creation fails silently or blocks.
- !Confirming SO before configurator finishes BoM explosion.
- !Same product both MTS and MTO on different warehouses without rules.
- !Delivery promised from FG location manufacturing never posts to.
- !Ignoring subcontract lead time in customer-facing promise dates.
- !Duplicate MOs from reconfirming or duplicating SO lines.
Sales-to-manufacturing is route discipline plus visible procurement — SO confirmation should never be a surprise for the plant.
Next, trace your highest-volume MTO SKU from quote to delivery with sales and production in one session.
Quote / order
Sales confirms demand.
Engineer / BoM
Configurable or standard.
MO create
Manufacturing order.
Deliver
FG to customer or stock.
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
Can one SO line spawn multiple MOs?
Multi-level BoMs or separate procurements can create child MOs and POs from one line. Planners should trace the procurement tree from the SO.
How do I link MO back to the customer order?
Origin and destination links on MOs and pickings tie to SO lines when routes are standard. Custom flows may need extra fields via Customization.
What if we build ahead of sales for stock?
That is MTS — SO consumes stock and reorder rules or planners create MOs independently. Do not use MTO on those SKUs unless every order should trigger fresh production.
Does ecommerce change the workflow?
Online orders confirm like inside sales but may need automated MO priority and stricter ATP rules. Retail portfolio cases show demand-driven replenishment beside manufacturing.
Related articles
Configurable Products vs Standard Variants
When to use Odoo product variants versus configurators and custom BoM explosion for made-to-order manufacturing — without SKU explosion or broken MOs.
View →Procurement for Manufacturing
How Odoo purchase and replenishment rules supply manufacturing: reordering rules, MTO buy, vendor lead times, and MO-driven component demand.
View →Manufacturing Orders Explained
How Odoo manufacturing orders move from draft to done: reservation, work orders, production posting, backorders, scrap, and shop-floor execution patterns.
View →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 →Related services
Connecting sales promises to the plant?
Share your MTO/MTS mix and configurator use — we will map SO-to-MO routes and visibility.
