A build-to-order per-tenant AL extension that automates inbound 850 purchase orders, 855 acknowledgments, 856 ASNs and 810 invoices between Business Central and your retail trading partners, marketplaces and 3PLs — including drop-ship automation and GS1 UCC-128 compliant labeling. Built, installed and supported by ECOSIRE on your environment. One-time license from $799.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order per-tenant AL extension that automates inbound 850 purchase orders, 855 acknowledgments, 856 ASNs and 810 invoices between Business Central and your retail trading partners, marketplaces and 3PLs — including drop-ship automation and GS1 UCC-128 compliant labeling. Built, installed and supported by ECOSIRE on your environment.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Trading with big-box retailers and marketplaces means living by their EDI rules: a 997/855 functional acknowledgment within hours, an 856 Advance Ship Notice that exactly mirrors the physical carton hierarchy, a GS1-128 (UCC-128) label on every pallet, and a routing-compliant 810 invoice — or chargebacks follow. Business Central has no native EDI engine, so most suppliers stitch together spreadsheets, a third-party VAN portal and manual rekeying.
Inbound EDI 850 purchase orders auto-imported as draft or released Business Central Sales Orders, with line/item/UoM cross-reference mapping per trading partner
Outbound 855 Purchase Order Acknowledgment generated from order confirmation, including item-accept, item-reject and quantity-change logic
Outbound 856 Advance Ship Notice (ASN) built from Posted Sales Shipments, mirroring the pallet/carton/item hierarchy with SSCC numbers
Outbound 810 invoice triggered via event subscriber on Posted Sales Invoice, with partner-specific allowances, charges and remittance segments
GS1-128 / UCC-128 compliant shipping label generation with SSCC-18 serial shipping container codes to each partner's placement spec
Drop-ship order automation routing 850 lines directly to the supplier or 3PL and reconciling 856/810 back into Business Central
This is a build-to-order solution, not an instant AppSource download. ECOSIRE designs, builds, installs and supports a per-tenant AL extension directly on your Business Central environment (cloud SaaS or on-prem). We map each trading partner's EDI 850, 855, 856 and 810 specifications to your Sales Order, Purchase Order and Posted Sales Invoice tables using table and page extensions, event subscribers on document posting, and codeunits that translate X12 (or EDIFACT) segments to and from BC records.
Inbound 850 purchase orders land as draft Sales Orders for review or auto-release; 855 acknowledgments and 856 ASNs are generated from posted shipments; 810 invoices fire on posting. Drop-ship orders flow straight to your supplier or 3PL. Container and inbound receipts can be confirmed by EDI. SSCC/UCC-128 labels are generated to your partners' GS1 placement rules. Transport runs over your VAN, AS2 or SFTP gateway, scheduled through the BC Job Queue, with a monitoring page for failed documents and reprocessing.
We scope your partner list and specs, build against a sandbox tenant, run partner certification with you, then deploy to production with permission sets, a runbook and handover. Delivery is typically 3–5 weeks depending on partner count and spec complexity.
Owns retailer chargeback exposure and partner compliance. Needs ASNs and labels that pass every routing guide, functional acknowledgments returned in SLA, and a clear monitor of failed documents — without rekeying orders into Business Central by hand.
Wants 850 purchase orders to become Sales Orders and 810 invoices to fire automatically on posting, with a clean audit trail from each BC document to its EDI control numbers and no parallel spreadsheet process.
Responsible for the tenant, extensions and integrations. Prefers a properly scoped per-tenant AL extension with permission sets and Job Queue scheduling over brittle custom scripts or another portal login, and wants a vendor who supports it on the live environment.
Buy the license on ecosire.com and download the EDI Connector for Marketplaces & Retailers in Business Central 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 EDI Connector for Marketplaces & Retailers in Business Central, 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 |
|---|---|---|---|---|
| Inbound 850 → Business Central Sales/Purchase Order automation | ||||
| 856 ASN built from posted shipment with SSCC carton hierarchy | ||||
| GS1-128 / UCC-128 labels to each partner's exact routing-guide spec | ||||
| Drop-ship 850 routed to supplier/3PL and reconciled back into BC | ||||
| Per-partner mapping to your own item/UoM cross-references | ||||
| Built, installed and supported by vendor on your tenant | ||||
| Permission sets, Job Queue scheduling and failed-document monitor | ||||
| No per-document or per-partner SaaS subscription fee |
This is built to order, so there is no instant download. Typical delivery is 3–5 weeks from spec sign-off. We first scope your trading-partner list, transaction sets and routing guides, then build and test against a sandbox tenant, run certification interchanges with your retailers/marketplaces, and finally deploy to production. Lead time scales with the number of partners and how custom each partner's 850/856/810 spec is — a single retailer is faster than ten partners across X12 and EDIFACT.
ECOSIRE supports the extension on your live tenant. Because it is a versioned per-tenant AL extension, we ship fixes and enhancements as new builds you can install in your sandbox first. Onboarding a new trading partner, adding a transaction set, or adapting to a retailer's updated routing guide is handled as a support or change request. We also keep the extension compatible across Business Central's monthly and major (major-version) platform updates so it keeps working through Microsoft's release cadence.
No. It is a custom per-tenant extension that ECOSIRE builds specifically for your partner specifications and installs on your environment. That means we can map exact retailer routing guides and your own item/UoM cross-references rather than forcing your data into a generic published app. We do not provide an AppSource listing or a self-service download — installation and support are done by us on your tenant.
The core scope is X12 850 (PO), 855 (PO Acknowledgment), 856 (ASN) and 810 (Invoice), plus 997 functional acknowledgments. EDIFACT equivalents (ORDERS, ORDRSP, DESADV, INVOIC, CONTRL) can be added. Transport runs over your existing VAN, or direct AS2 / SFTP. GS1-128 (UCC-128) labels with SSCC-18 codes are generated to each partner's placement rules. Additional sets such as 860 PO change or 846 inventory advice can be added in scope.
Yes. The extension is written in AL using supported extension points — table/page extensions, event subscribers, codeunits and the Job Queue — so it runs on Business Central online (SaaS) and on-premises. For SaaS, outbound transport that needs AS2/SFTP is handled through a supported gateway or your VAN, since the cloud sandbox restricts certain outbound protocols; we confirm the right transport pattern for your deployment during scoping.
A build-to-order per-tenant AL extension that automates inbound 850 purchase orders, 855 acknowledgments, 856 ASNs and 810 invoices between Business Central and your retail trading partners, marketplaces and 3PLs — including drop-ship automation and GS1 UCC-128 compliant labeling. Built, installed and supported by ECOSIRE on your environment.