A build-to-order Business Central AL extension that maps your 3PL warehouses into native sales and purchase flows — sending fulfillment orders, ingesting ASN and shipment confirmations, and reconciling on-hand quantities against each 3PL's stock balances. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order Business Central AL extension that maps your 3PL warehouses into native sales and purchase flows — sending fulfillment orders, ingesting ASN and shipment confirmations, and reconciling on-hand quantities against each 3PL's stock balances.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
If you outsource fulfillment to one or more third-party logistics (3PL) providers, your real inventory lives in someone else's warehouse — but Business Central still has to quote, sell, reserve, ship and invoice against it. This extension closes that gap inside BC itself, not in a spreadsheet or a separate portal.
3PL locations mapped into standard BC Locations so availability, reservations and warehouse handling work natively across sales and purchase documents
Outbound fulfillment orders pushed to the 3PL automatically on sales order release via AL event subscribers
Inbound ASN (Advance Shipment Notice) ingestion that creates and helps post warehouse/purchase receipts for stock arriving at the 3PL
Outbound shipment-confirmation messaging that posts sales shipments and writes back carrier and tracking numbers
Scheduled inventory reconciliation comparing BC on-hand against each 3PL's reported stock balances, with a variance worklist
Pluggable per-provider connector interface — each 3PL implemented behind one AL contract (API, REST/OData, or file/EDI)
ECOSIRE builds, installs and supports this as a per-tenant AL extension on your own Business Central environment (cloud SaaS or on-prem). It is not an instant AppSource download — we scope your 3PL providers and message formats, develop against the real BC objects, and deploy to your sandbox before production.
What it does. It introduces 3PL locations and maps them into standard BC Locations so item availability, reservations and warehouse handling behave natively. Sales-order release pushes outbound fulfillment orders to the 3PL; inbound ASNs and outbound shipment confirmations flow back to post receipts and shipments and update tracking. A scheduled reconciliation job compares BC on-hand against each provider's reported balances and surfaces variances for review.
How it's built. Table and page extensions on Location, Item Ledger and the sales/purchase documents; event subscribers (e.g. on release and post) to trigger messaging; a pluggable connector interface so each 3PL provider has its own implementation behind one contract; the BC job queue for polling and reconciliation; and outbound/inbound exchange over the provider's API, the BC REST/OData surface, or file/EDI where that's all a provider offers. Dedicated permission sets scope who can configure connectors and resolve variances; optional Dataverse / Power Platform surfacing for approvals or dashboards.
The result is honest, auditable 3PL inventory — owned by your team, maintained by ours.
Owns the relationship with one or more 3PLs and needs BC to reflect what those warehouses actually hold and ship — without chasing portals or spreadsheets to confirm stock and dispatch.
Wants a clean per-tenant extension with proper permission sets, job queue and an auditable message log, installed without destabilizing the production tenant or blocking BC upgrades.
Relies on accurate on-hand and cost postings; values the scheduled reconciliation and variance worklist that catch discrepancies between BC and 3PL balances before they hit the books.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des 3PL / Outsourced-Warehouse Manager-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „3PL / Outsourced-Warehouse Manager“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| 3PL locations behave as native BC locations in sales/purchase flows | ||||
| Outbound fulfillment orders + inbound ASN / shipment-confirmation messaging | ||||
| Scheduled BC-vs-3PL inventory reconciliation with variance worklist | ||||
| Pluggable per-provider connector for multiple 3PLs | ||||
| Tailored to your exact 3PL providers and message formats | ||||
| Installed, supported and BC-upgrade-maintained by the vendor | ||||
| Source-code ownership handed to your team | ||||
| Available without a custom build project or in-house AL team |
No — this is build-to-order. ECOSIRE develops it as a per-tenant AL extension for your specific 3PL providers and message formats, then installs it to your sandbox for validation before production. Typical delivery is roughly 3–6 weeks depending on how many 3PLs you connect and whether each exposes a modern API or only file/EDI exchange. We confirm a firm timeline after a short scoping call.
ECOSIRE supports it. The included warranty/support window covers bug fixes and keeping the extension compatible across Business Central's monthly and major releases — we test against your sandbox ahead of upgrades. Because it's a clean per-tenant extension using event subscribers and table/page extensions (no base-app modification), it upgrades like any well-behaved AL app. You also receive the source, so you're never locked in.
Yes. The connector is a pluggable AL interface, so each provider has its own implementation behind one contract. You can run several 3PLs concurrently, each mapped to its own BC location with independent messaging, SKU mapping and reconciliation schedule.
That's common. The connector contract supports API/REST/OData where available and falls back to scheduled file or EDI exchange (e.g. CSV/XML drops or SFTP) where a provider only offers batch integration. Either way the job queue handles polling, retry and reconciliation so the integration behaves consistently.
Minimally and intentionally. Sales and purchase documents stay native — 3PL locations behave like standard BC locations, and fulfillment is triggered on the actions you already use (like order release). The new surfaces are mostly for admins: connector setup, the message log, and the variance worklist, all gated behind dedicated permission sets.
A build-to-order Business Central AL extension that maps your 3PL warehouses into native sales and purchase flows — sending fulfillment orders, ingesting ASN and shipment confirmations, and reconciling on-hand quantities against each 3PL's stock balances.