- ホーム
- Apps
- Specialized Solutions
- Manufacturing Order Merge & Split
イメージプレビューMerge same-product manufacturing orders into one batch run, or split a large MO into smaller lots
— with demand aggregation and traceability preserved.
Manufacturing Order Merge & Splitとは?
Merge same-product manufacturing orders into one batch run, or split a large MO into smaller lots — with demand aggregation and traceability preserved. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間(営業日ベース)で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise&Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
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.
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 one working week 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.
得られるもの
- Complete, version-matched Odoo addon source code (models, views, wizards, security, QWeb reports) delivered to your repository
- Deployment to your Odoo instance (staging first, then production) with the module installed and configured against your data
- Configuration of eligibility rules, planner security group, and record rules tuned to your work-center and BoM structure
- QWeb batch-label and merge/split summary report templates styled to your document layout
- Admin & planner user guide (PDF) plus an in-Odoo quick-reference for the merge and split workflows
- Live training session for your planning team, recorded for future onboarding
- Post-deployment support window with bug fixes and minor adjustments included (duration set in your engagement)
- XML-RPC/JSON-RPC integration notes and example calls if you connect an external scheduler or MES
これは誰のためのものですか
Production Planner batching similar orders
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.
Manufacturing / Operations Manager
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.
Quality & Compliance Lead in a regulated shop
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.
Manufacturing Order Merge & Split の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| 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 | 付属 | 付属 | 含まれていない | 付属 |
Manufacturing Order Merge & Split に関するよくある質問
How long until the module is delivered and live on our Odoo instance?
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 one working week. 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.
What support and updates do I get after delivery?
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.
Can I merge orders for different products, or must they be identical?
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.
Will merging or splitting break my lot/serial traceability or the link to the original sales orders?
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.
Does this work with Odoo Community, or do I need Enterprise?
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.
Can an external scheduler or MES trigger merges and splits automatically?
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.
関連モジュール

Manufacturing Gantt Native Web View
A build-to-order interactive Gantt timeline that plots your manufacturing work orders across work centers so planners can drag, drop, and reschedule production visually. ECOSIRE builds, installs, and supports it on your Odoo 17/18/19 instance after a scoping call.
Manufacturing Order Merge & Split
Merge same-product manufacturing orders into one batch run, or split a large MO into smaller lots — with demand aggregation and traceability preserved.
- 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


