Merge same-product manufacturing orders into one batch run, or split a large MO into smaller lots — with demand aggregation and traceability preserved. One-time license from $99.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Merge same-product manufacturing orders into one batch run, or split a large MO into smaller lots — with demand aggregation and traceability preserved.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Your planners know the pain: five separate manufacturing orders for the same finished product, each spinning up its own work orders, its own setup time, and its own line changeover — when they could all run as a single batch. Or the opposite: one enormous MO for 5,000 units that has to be broken into shift-sized lots so the shop floor can actually schedule it. Odoo core (mrp.production) gives you no first-class way to do either. Planners resort to manually cancelling and re-keying orders, which destroys the link back to the originating sales orders and blows up component reservations.
Merge multiple confirmed manufacturing orders of the same finished product into one consolidated batch MO
Split a large MO into multiple child sub-orders by target quantity, lot count, or work-center capacity
Auto-aggregate component demand on merge — sums each raw-material stock.move so reservations roll up into a single requirement
Proportionally divide component consumption and stock moves across child orders on split, keeping BoM math exact
Preserve full traceability: source MO references, originating sales/purchase links, and lot/serial genealogy survive both operations
Eligibility guardrails — configurable rules enforce same product, same Bill of Materials, and same unit of measure before a merge is allowed
Manufacturing Order Merge & Split is a build-to-order Odoo module that ECOSIRE designs, builds, installs, and supports specifically for your MRP workflow. It adds two governed operations directly onto the Manufacturing app: Merge — select multiple confirmed MOs of the same product (and, where you require it, the same Bill of Materials and unit of measure) and combine them into one consolidated batch order; and Split — take a large MO and divide it into several sub-orders by quantity, work-center capacity, or a lot count you specify. Component demand is auto-aggregated on merge so stock.move reservations roll up correctly, and traceability links — source MOs, originating sales/purchase documents, and lot/serial genealogy — are preserved on both operations so your audit trail never breaks.
This is not an off-the-shelf apps.odoo.com download. There is no instant ZIP. ECOSIRE writes the module against your exact Odoo version (17, 18, or 19), your BoM structure, your work-center topology, and your traceability policy, then deploys it to your instance and hands over the source. Typical delivery is 2–4 weeks depending on scope and integration surface.
How it's built (for the technically inclined): A clean addon with its own __manifest__.py declaring the mrp dependency. New models (mrp.production.merge.wizard, mrp.production.split.wizard) drive the operations as TransientModel wizards launched from server actions on mrp.production. Merge logic groups eligible orders, sums quantities and component stock.move demand, and writes a new consolidated mrp.production with @api.depends computed roll-ups; split logic proportionally divides quantity and moves across N children while linking each back to the parent via a relational field. Access is locked down through ir.model.access.csv plus record rules so only users in the Manufacturing / Planner group can merge or split, and only within their allowed operation types. Batch labels and a merge/split summary are rendered as QWeb reports, and every merge or split can be triggered programmatically over XML-RPC / JSON-RPC for integration with an external scheduler or MES. Works on both Community and Enterprise editions of Odoo.
Runs the daily/weekly production schedule and constantly sees several small MOs for the same product that would be far cheaper to run as one batch. Uses Merge to consolidate setups and cut changeovers, and Split to break oversized MOs into shift-sized lots the line can actually execute.
Owns line efficiency, OEE, and on-time delivery. Wants fewer changeovers, better work-center utilization, and a defensible audit trail. Values the guardrails and record-rule security so only authorized planners can restructure orders, and the preserved traceability for quality and compliance.
Responsible for lot/serial genealogy and audit readiness (food, pharma, aerospace, automotive). Needs certainty that merging or splitting an MO never severs the traceability chain back to source orders and lots — which this module preserves and logs on every operation.
Buy the license on ecosire.com and download the Manufacturing Order Merge & Split module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Manufacturing Order Merge & Split, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Merge same-product MOs into one batch run | ||||
| Split a large MO into smaller lots/sub-orders | ||||
| Auto-aggregate component demand on merge | ||||
| Preserves lot/serial traceability & source links | ||||
| Built for your exact Odoo version (17/18/19) & BoM structure | ||||
| Group-based security via record rules & ir.model.access.csv | ||||
| XML-RPC/JSON-RPC trigger for external scheduler/MES | ||||
| Installed, tested on staging, and supported for you | ||||
| Full source code handed over — you own it |
This is a build-to-order module, not an instant download. After a short scoping call to confirm your Odoo version, BoM structure, work-center setup, and traceability rules, typical delivery is 2–4 weeks. We build against your exact version (17, 18, or 19), test on a staging copy of your database, then deploy to production and hand over the source. Timelines flex with scope — a straightforward same-product merge/split ships faster than one wired into an external MES.
Every engagement includes a post-deployment support window (duration set in your quote) covering bug fixes and minor adjustments. Because we hand over the full source, you own the code outright — no per-seat SaaS fee. When you upgrade Odoo (e.g. 18 to 19), we offer a paid compatibility update to re-target and re-test the module against the new release. Extended support and enhancement retainers are available if you want us on call long-term.
By default a merge requires the same finished product, and we can enforce the same Bill of Materials and unit of measure as guardrails so batch math stays correct. If your process legitimately needs to group different variants of one product template, or mixed-BoM batches, we configure the eligibility rules for that during the build. Split has no such constraint — any single large MO can be divided into smaller lots.
No — preserving traceability is a core design goal. On merge, the consolidated MO carries back-references to every source order and their originating documents; on split, each child links to the parent. Lot/serial genealogy and component stock.move history are retained, and every operation is logged in the chatter. This is exactly what a manual cancel-and-re-key approach destroys, and the reason regulated shops need a proper module.
It works with both. The module depends only on the standard Manufacturing (mrp) app, which ships in Community and Enterprise alike, so there's no Enterprise-only dependency. We build and test against whichever edition and version (17/18/19) you run.
Yes. The merge and split operations are exposed over Odoo's XML-RPC / JSON-RPC API, so an external scheduling engine, MES, or custom application can call them programmatically. We can also configure an automated action that surfaces suggested merge candidates (same product, overlapping schedule window) for a planner to approve, keeping a human in the loop where you want one.
Merge same-product manufacturing orders into one batch run, or split a large MO into smaller lots — with demand aggregation and traceability preserved.