Odoo guides · SALUT TECH SRL
Odoo servicesMerging manufacturing orders over-orders sub-assemblies: why, and a workaround without code
A company on Odoo Online 19.3 reported this on GitHub (issue 302664). Two make-to-order manufacturing orders for the same product, 20 and 10, merged into one MO of 30. The sub-assembly MOs created by 0/0/1 reordering rules jumped from 30 to 60 in total, leaving +30 forecasted stock nobody needs.
Why it happens (Odoo 19.0 code): action_merge() creates and confirms the merged MO before it cancels the originals. Confirming runs every reordering rule with Trigger = Auto for the components. At that moment the sub-assembly demand is counted twice (the new 30 plus the old 20 + 10), so the rule orders 30 more. Then the old demand is cancelled, and the extra stays. We read this in the 19.0 code; we couldn't read 19.3, but the reported numbers match it exactly.
Workarounds (test on a duplicate database first):
- Before merging: set the sub-assemblies' reordering rules to Trigger = Manual (Inventory > Operations > Procurement > Replenishment). Merge, check the forecast shows no surplus, then set them back to Auto straight away. While they're on Manual, the daily scheduler won't order those products.
- If you've already merged: open each inflated sub-assembly MO, click its quantity to open Change Quantity, and set it back. Then check the product's forecast.
Merging the sub-assembly MOs themselves doesn't show the problem; only the finished-product merge does.
Sources: Odoo 19.0 source, addons/mrp/models/mrp_production.py (action_merge, action_confirm) and addons/stock/models/stock_move.py (_trigger_scheduler), read 17 Nov 2026; github.com/odoo/odoo/issues/302664.
Questions about your own Odoo setup? Ask for a free review and a written fixed price.