商品詳細は英語で表示されます。翻訳は近日公開予定です。
簡単な事実
- 価格
- $99.00 USD
- Odoo のバージョン
- 17, 18, 19
- セットアップ時間
- 20160分
- ライセンス
- ワンタイム永続
- 言語
- 11 言語
一回購入
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.
$99.00USD
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
主な機能
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
Batch labeling: QWeb-rendered batch labels and a printable merge/split summary report for shop-floor packets
Group-based security via ir.model.access.csv and record rules — only the Planner/Manufacturing group can merge or split
Merge/split wizards implemented as TransientModel with a clear preview step showing the resulting order(s) before confirmation
Automatic recompute of scheduled dates, component reservations, and work-order sequencing on the resulting order(s)
Reversible design — merged/split orders retain back-links so planners can audit or unwind before production starts
Chatter and mail.thread logging on every merge/split so the change history is visible on each affected MO
Optional automated action to auto-suggest merge candidates (same product, overlapping schedule window) for planner review
XML-RPC / JSON-RPC endpoints so an external scheduler, MES, or custom app can trigger merges/splits programmatically
Compatible with Odoo 17, 18, and 19 on both Community and Enterprise editions
この製品について
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を選ぶ理由
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.
得られるもの
- 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.
インストールの概要
ECOSIREからダウンロード
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Manufacturing Order Merge & Split モジュールの ZIP をダウンロードします。
Odoo にアップロードする
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
モジュールをインストールする
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Manufacturing Order Merge & Split」を検索し、「インストール」を押します。
設定を構成する
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
検証して公開する
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
Manufacturing Order Merge & Split の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| 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 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.
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 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