Splittable Manufacturing Orders in Odoo 20

Production plans are written before the day starts; production problems arrive after it has. A component delivery lands short, a work center goes down, a customer pulls half an order forward and pushes the rest back, or a long run simply needs to free the line for something more urgent. Until recently, changing the quantity story of a manufacturing order that was already under way meant awkward workarounds — cancel, recreate, and explain the paper trail later. Odoo 20 lists the cleaner answer in its release notes under Manufacturing: split ongoing manufacturing orders to produce the remaining amount later.

Splitting is not about producing faster. It is about making the order in the system match the decision on the floor: this much now, the rest later, each part with its own schedule, status, and record. This article explains what splitting an ongoing order means in Odoo 20, how it differs from backorders, partial completion, and the older pre-planned split, when to use it, and what to check before and after you split.

What splitting an ongoing order means

A manufacturing order (MO) normally carries one product, one bill of materials (BoM), and one quantity to produce, executed through its work orders. Splitting takes an order that is already in progress and separates it so that the quantity still to be made becomes a distinct order to be produced later, while the part already under way continues to its own completion.

The emphasis on ongoing is the point. Splitting a draft order before anything starts is ordinary planning. Splitting mid-run is a replanning act: some components may already be consumed, some operations may be partly done, time may already be recorded, and a provisional cost already exists. Odoo 20's Manufacturing changes support that moment in several connected ways: manufacturing orders are planned as soon as possible by default, backorders of planned productions are now also planned automatically upon their creation, the MO Cost field shows a provisional cost while an order is in progress and the real cost when it is complete, and the separate Produce and Produce All buttons have been replaced by a single Produce button across Manufacturing, Shop Floor, and Barcode.

Four similar ideas, kept separate

Odoo's vocabulary around partial production is easy to blur. The distinctions matter because each option leaves a different record:

Option	What happens	Best used when
Split an ongoing MO (Odoo 20)	The order in progress is split so the remaining amount is produced later as a separate order.	The plan itself has changed mid-run and the remainder needs its own schedule.
Manufacturing backorder	You produce a partial quantity, close that part, and create a backorder for the rest. The documentation shows the original reference splitting into suffixed orders such as `-001` for the produced part and `-002` for the open remainder.	You can finish some units now and the rest must wait, typically for components.
Partially complete and close	You enter a smaller quantity, click Produce, handle any consumption warning, and choose to close production. The MO is marked Done for the quantity actually made, with no remainder carried forward.	The shortfall is permanent — the order is genuinely reduced, not deferred.
Pre-planned split	An MO is split into multiple orders up front, with each new order assigned its own quantity to produce and references carrying suffixed tags.	You already know a large quantity should run as several smaller orders.

In practice the backorder flow is the most common way a split remainder appears: produce what you can, and let the system carry the rest into an open order rather than leaving one half-finished MO hanging.

Why shops split an order mid-run

Component shortage. The classic case in Odoo's own backorder documentation: an order for ten units, components on hand for five. Produce five properly now; carry five as a clearly identified remainder instead of stalling the whole order.
Capacity interruption. A machine breakdown, a missing operator, or maintenance on a work center can make the second half of a run unschedulable today. Splitting lets the completed portion close cleanly while the remainder takes a realistic new date.
Priority changes. A rush order needs the line. Splitting the current run frees capacity without cancelling work already done, and the deferred part remains visible in planning instead of living in someone's memory.
Staged customer demand. The customer still wants the full quantity, but in two deliveries. Two orders map naturally onto two deliveries, two packings, and two completion records.
Quality containment. If a suspect batch of components or a process concern affects part of a run, separating the remainder allows the unaffected quantity to proceed while the rest waits for a decision — with a record of exactly which quantity was held.
Very long runs. A multi-day run split at a sensible boundary gives supervisors closable milestones, cleaner cost snapshots, and less risk concentrated in a single order.

What happens to the pieces after a split

Schedule

Odoo 20 plans manufacturing orders as soon as possible by default, with the sequence of orders in the list determining priority when several are planned, and backorders of planned productions are planned automatically when they are created. A split remainder therefore enters planning as a real order with a real place in the queue — not as a note on a closed one. Planners can then resequence it deliberately using the new work order Kanban and Gantt views rather than discovering it later.

Components and consumption

All manufacturing orders in Odoo 20 use flexible consumption by default — the old BoM setting has been removed. That flexibility helps at split time, because actual consumption on a part-completed run rarely matches the theoretical BoM quantities exactly. When you produce a partial quantity, Odoo may raise a Consumption Warning: you can confirm to keep the recorded consumption, or update quantities so consumption matches the quantity produced. Treat that choice as an accounting decision, not a dialog to dismiss — it determines what the finished units actually cost.

Cost

While either part is still in progress, its MO Cost is provisional; once an order is complete, the field shows the real cost. Splitting therefore gives finance two clean cost records — one for each production run — instead of a single order whose cost blends two runs separated by days, different component prices, or different labour conditions.

Traceability

Each resulting order keeps its own reference, with suffixed tags identifying the parts of a split or backorder family, and lots and serial numbers are automatically generated when manufacturing orders are closed. For regulated or warranty-sensitive goods, that separation is valuable: the units produced before the interruption and the units produced after it are distinguishable in the record, not merged into one ambiguous batch.

A practical workflow

Stop and state the decision. How many units are being completed under the current run, and how many are being deferred? Get the numbers from the floor, not from the original plan.
Record reality first. Register produced quantities and actual component consumption on the work in progress before splitting, so the split divides a truthful order.
Produce the immediate quantity. On the MO, set the quantity being produced now and use the single Produce button. Handle the consumption warning deliberately.
Carry the remainder forward explicitly. When prompted that you produced less than the initial demand, create the backorder — or use the split so the remaining amount stands as its own ongoing order to produce later. Confirm the new order exists, carries the deferred quantity, and shows in planning.
Reschedule the remainder honestly. Give the deferred order the date driven by the real constraint — component arrival, work center availability, customer need — and check it in the Gantt or Kanban planning views.
Close the loop in the chatter. Note why the order was split. The next planner, and anyone auditing costs later, should not have to guess.

When not to split

The order will finish today anyway. A short pause is not a replanning event; splitting adds records without adding clarity.
The shortfall is permanent. If the deferred quantity will never be made, partially complete and close the order instead of parking a remainder nobody intends to produce.
Nobody owns the remainder. A split order without a rescheduled date and an owner is just a tidier form of forgetting. If the team cannot say when the rest will run, fix that first.
As a substitute for fixing supply. If the same component shortage splits orders every week, the split is a symptom. The reordering and replenishment problem upstream needs the attention.

The bottom line

Splittable manufacturing orders in Odoo 20 acknowledge something every production manager knows: the plan will change while work is under way, and the system should absorb that change gracefully. Split the ongoing order, close what is genuinely done at its real cost, plan the remainder as a first-class order with its own date and reference, and the MO list stays an honest picture of the floor — which is the entire point of running manufacturing in an ERP.