Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $499.00 USD
- dynamics_365_business_central versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
ایک بار کی خریداری
Subcontracting & Outsourced Production Manager
A build-to-order Business Central extension that manages outsourced production end-to-end: ship components to subcontractors, track off-site WIP, receive finished routing steps back, and reconcile subcontract costs against the production order.
$499.00USD
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
اہم خصوصیات
Subcontract purchase orders linked directly to the routing operation on a released production order via a table extension on Prod. Order Routing Line, so each outsourced step has its own PO and traceable cost
Components shipped-to-vendor tracking using a dedicated off-site WIP location, with item ledger entries that move components out of your warehouse without consuming them prematurely
Off-site WIP aging visibility — a Job Queue task computes how long components and in-process units have been at each subcontractor, flagging overdue work
Receipt of the subcontracted operation back into routing: posting the vendor PO advances the production order operation and brings the completed quantity back to the next routing step
Vendor-supplied vs manufacturer-supplied material scenarios handled explicitly, so consumption and cost are attributed correctly whether you ship the metal or the vendor sources it
Subcontract cost reconciliation page comparing components sent, scrap reported, and units received against the PO value rolled into the production order's actual cost
Event subscribers on the manufacturing and purchasing posting routines (no core modification) keep the link between PO receipt and routing progress automatic
Permission sets scoped for production planners and outsourcing buyers, installed alongside the extension
OData v4 / REST API endpoints exposing off-site WIP and aging data for Power BI dashboards and Power Automate vendor reminder flows
Subcontractor-facing print/email layout (PO plus components-to-supply list) so the vendor knows exactly what to expect and return
Role Centre cues for 'Overdue at Subcontractor' and 'Awaiting Subcontract Receipt' surfaced to the production planner
Optional Dataverse / Power Platform sync so a vendor portal or canvas app can read off-site WIP status
اس مصنوع کے بارے میں
If you outsource significant routing steps — plating, heat-treat, machining, coating, assembly — standard Business Central manufacturing leaves gaps. Subcontract purchase orders aren't natively linked to the routing operation they fulfil, components shipped to a vendor disappear from your WIP visibility, and reconciling what the subcontractor actually consumed against what you sent becomes a spreadsheet exercise.
Subcontracting & Outsourced Production Manager کیوں منتخب کریں
Subcontract purchase orders linked directly to the routing operation on a released production order via a table extension on Prod. Order Routing Line, so each outsourced step has its own PO and traceable cost
Components shipped-to-vendor tracking using a dedicated off-site WIP location, with item ledger entries that move components out of your warehouse without consuming them prematurely
Off-site WIP aging visibility — a Job Queue task computes how long components and in-process units have been at each subcontractor, flagging overdue work
Receipt of the subcontracted operation back into routing: posting the vendor PO advances the production order operation and brings the completed quantity back to the next routing step
Vendor-supplied vs manufacturer-supplied material scenarios handled explicitly, so consumption and cost are attributed correctly whether you ship the metal or the vendor sources it
Subcontract cost reconciliation page comparing components sent, scrap reported, and units received against the PO value rolled into the production order's actual cost
Subcontracting & Outsourced Production Manager is a per-tenant AL extension that closes these gaps. It ties a subcontract purchase order to the specific routing operation on the released production order, tracks components shipped to the vendor against an off-site WIP location, surfaces aging of parts sitting at subcontractors, receives the completed operation back into routing, and reconciles vendor-supplied versus manufacturer-supplied material so your production order cost is accurate.
This is honest build-to-order, not an instant AppSource download. ECOSIRE builds the extension to your routing structure, subcontract workflow, and costing model; installs it as a per-tenant extension on your Business Central environment (cloud SaaS or on-prem); configures permission sets and a Job Queue entry for WIP aging; and supports it after go-live. Delivery is typically 2–4 weeks depending on scope.
Built with table and page extensions over Production Order, Purchasing, and Item Ledger; event subscribers on the manufacturing posting routines so nothing is bolted on; and OData/REST API exposure for Power BI WIP dashboards or Power Automate vendor alerts. Your data stays in your tenant. You own the extension. We hand over source and documentation, and you can choose a support retainer for updates as Microsoft ships new Business Central releases.
What you get
- A per-tenant Business Central AL extension (.app) built to your routing and subcontract workflow, installed on your sandbox then production environment
- Table and page extensions over Production Order Routing Line, Purchasing, and the off-site WIP location, plus the subcontract reconciliation page
- Event-subscriber codeunits linking PO receipt to routing operation completion with no modification of Microsoft base objects
- Configured permission sets for production planners and outsourcing buyers
- A Job Queue entry for nightly off-site WIP aging computation
- OData/REST API pages for WIP and aging data, with a sample Power BI dashboard and a sample Power Automate vendor-reminder flow
- Source code, the AL project, and technical documentation handed over to your team
- Admin and planner user guide plus a configuration walkthrough session
Who this is for
Production Planner
Schedules and releases production orders and needs to see, in real time, which outsourced operations are out at a vendor, what has aged past its expected return, and what is blocking the next routing step — without leaving the production order.
Outsourcing / Procurement Buyer
Raises subcontract purchase orders for plating, machining, or coating and needs each PO tied to the exact routing operation and to the components shipped, so receipts reconcile cleanly and supplier performance is measurable.
Cost Accountant / Controller
Owns the accuracy of production order costs and wants subcontract charges, components sent, and vendor-supplied material attributed correctly so off-site WIP is properly valued on the balance sheet.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Subcontracting & Outsourced Production Manager module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Subcontracting & Outsourced Production Manager, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Subcontracting & Outsourced Production Manager Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Subcontract PO linked to the specific routing operation | ||||
| Off-site WIP location with aging visibility | ||||
| Receive subcontracted operation back into routing automatically | ||||
| Vendor-supplied vs manufacturer-supplied material costing | ||||
| Built to your exact routing and workflow (not a fixed template) | ||||
| Installed and supported on your environment by the builder | ||||
| Source code and AL project handed to you | ||||
| OData/REST API + Power BI / Power Automate ready | ||||
| Upgrade-safe (no base-object modification) |
Frequently Asked Questions about Subcontracting & Outsourced Production Manager
+How long does delivery take, and what does the process look like?
Typical delivery is 2–4 weeks from a scoping call, depending on the complexity of your routings, costing model, and vendor-supplied material scenarios. We start by mapping your current subcontract flow, build the extension against your Business Central sandbox, validate it with your planners and buyers on real production orders, then install it on production and configure permission sets and the Job Queue aging task. This is build-to-order: there is no instant AppSource download — the extension is tailored to your environment.
+Is this an official Microsoft AppSource app I can just install?
No. It is a per-tenant Business Central extension that ECOSIRE builds, installs, and supports directly on your environment — cloud SaaS or on-prem. Because it is a per-tenant extension rather than a public AppSource listing, it can fit your exact routing structure and subcontract workflow instead of forcing you into a generic template. We hand over the source code and the AL project, so you own it.
+Will this conflict with future Business Central updates?
The extension uses table extensions, page extensions, and event subscribers — it does not modify Microsoft base objects, which is the supported extension model and the same approach AppSource apps follow. That keeps upgrade risk low. Microsoft ships major Business Central releases twice a year; an optional support retainer covers recompiling and validating the extension against each new release plus any enhancements you need.
+How does it handle material the subcontractor supplies versus material we ship?
Both scenarios are modelled explicitly. When you ship components, they move to a dedicated off-site WIP location via item ledger entries and stay valued in your inventory until the operation is received back. When the vendor supplies the material, that consumption is attributed to the subcontract cost on the PO rather than to your inventory, so the production order's actual cost stays correct either way.
+Can we report on off-site WIP in Power BI or alert vendors automatically?
Yes. The extension exposes off-site WIP and aging data through OData v4 / REST API pages, and we provide a sample Power BI dashboard you can point at it. We also include a sample Power Automate flow that reads aging data and emails subcontractors when work is overdue. If you use Dataverse, an optional sync lets a Power Apps vendor portal read the same status.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
قیمت کا تخمینہ طلب کریں
Subcontracting & Outsourced Production Manager
A build-to-order Business Central extension that manages outsourced production end-to-end: ship components to subcontractors, track off-site WIP, receive finished routing steps back, and reconcile subcontract costs against the production order.
- Subcontract purchase orders linked directly to the routing operation on a released production order via a table extension on Prod. Order Routing Line, so each outsourced step has its own PO and traceable cost
- Components shipped-to-vendor tracking using a dedicated off-site WIP location, with item ledger entries that move components out of your warehouse without consuming them prematurely
- Off-site WIP aging visibility — a Job Queue task computes how long components and in-process units have been at each subcontractor, flagging overdue work
- Receipt of the subcontracted operation back into routing: posting the vendor PO advances the production order operation and brings the completed quantity back to the next routing step