A build-to-order AL extension that automates trading-partner EDI inside Business Central — translating 850/855/856/810/940/945 and more directly into BC sales orders, purchase orders, warehouse shipments and posted invoices, with AS2/SFTP/VAN transport and SSCC-18 carton labels. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A build-to-order AL extension that automates trading-partner EDI inside Business Central — translating 850/855/856/810/940/945 and more directly into BC sales orders, purchase orders, warehouse shipments and posted invoices, with AS2/SFTP/VAN transport and SSCC-18 carton labels.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
You go live in about 2–4 weeks, with a post-launch support window.
Selling into Walmart, Target, Amazon, Kroger or any big-box retailer means EDI compliance is non-negotiable — and Business Central has no native EDI engine. This is a build-to-order per-tenant AL extension that ECOSIRE designs, builds, installs and supports directly on your Business Central environment (online or on-premises). It is not an instant AppSource download; we scope your trading-partner specs first, then deliver a working integration tuned to your documents.
The extension adds EDI mapping, transaction logging and transport orchestration as table extensions, page extensions and event subscribers that hook into the standard sales, purchase and warehouse document lifecycle. An inbound 850 Purchase Order lands as a BC sales order; we generate the 855 Acknowledgment and 856 ASN from the warehouse shipment, and the 810 Invoice from the posted sales invoice — all reconciled against the originating PO. For 3PL and cross-dock flows we map 940 Warehouse Shipping Order, 945 Shipping Advice and 947 Inventory Adjustment against your warehouse entries.
Transport runs through your choice of AS2, SFTP or a VAN, with the 997 Functional Acknowledgment handled automatically. Translation, document numbering and partner onboarding are configured per trading partner so each retailer's qualifier, segment and label rules are honored. Outbound batches run on the BC Job Queue; every transaction is logged with raw payload, parsed values and error detail for audit and reprocessing.
SSCC-18 carton and pallet labels are generated to each partner's GS1 spec. Because it is a proper extension built on the BC object model and exposed through the standard permission-set framework, it upgrades cleanly and integrates with Power Platform via the BC API where you need dashboards or approvals. ECOSIRE delivers, validates against real partner test data, and supports it.
Owns the retailer relationship and is on the hook for chargebacks. Needs 850s acknowledged on time, accurate 856 ASNs with valid SSCC labels, and a clear audit trail when a partner disputes a document.
Wants EDI handled inside BC as a clean per-tenant extension rather than a brittle middleware bolt-on — proper permission sets, Job Queue automation and no changes to base Microsoft objects so upgrades stay safe.
Lives in warehouse shipments and pick/pack. Needs the ASN and carton labels to flow straight from the BC warehouse shipment, and 940/945 cross-dock flows to reconcile against actual inventory movements.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| 850/855/856/810 mapped directly to native BC sales/purchase/warehouse documents | Included | Partial support | Included | |
| 3PL / cross-dock 940/945/947 against BC warehouse entries | Included | Partial support | Partial support | |
| SSCC-18 carton/pallet label generation to retailer GS1 spec | Included | Partial support | Partial support | |
| AS2 / SFTP / VAN transport with 997 acknowledgment handling | Included | Partial support | Included | |
| Per-tenant AL extension — no base-object changes, upgrade-safe | Included | Partial support | Included | |
| Built, installed and supported on your environment by the vendor | Included | Not included | Partial support | |
| Mapping tailored to your exact trading-partner specs at delivery | Included | Included | Not included | |
| EDI status exposed via BC REST/OData API for Power BI / Power Automate | Included | Partial support | Partial support |
This is built to order, so lead time depends on how many trading partners and document types you need. After purchase we run a short scoping call to collect your partner specs (qualifiers, document set, transport, label requirements). A single retailer with the core 850/855/856/810/997 set is typically delivered and validated against partner test data in a few weeks; multi-partner or 3PL/cross-dock 940/945/947 scopes take longer. We install to your sandbox first, test against real partner data, then promote to production with you. We give you an honest date during scoping, not before.
ECOSIRE supports the extension on your environment. Because it is a per-tenant AL extension built on event subscribers and table/page extensions — not modifications to base Microsoft objects — it survives Business Central's automatic update cycle; we validate it against major BC releases. Onboarding a new trading partner is a configuration task using the partner mapping workspace, which we can do for you or hand off via the admin runbook. Ongoing support, partner additions and new document types are covered by a support arrangement we agree with you.
Yes. The extension targets the AL object model that is common to both, so it installs on Business Central online (cloud) and on-premises. Transport differs slightly — AS2/SFTP/VAN connectivity is configured to suit your hosting — and we confirm the right approach during scoping.
No. It adds table extensions, page extensions and event subscribers alongside the standard documents and never edits base Microsoft objects. EDI fields, the transaction log and partner configuration live in extension objects, so your Business Central stays upgrade-safe and Microsoft's update cadence is honored.
Yes. EDI documents and their status are exposed through the Business Central REST/OData API, so you can build Power BI dashboards over interchange volumes and errors, or drive Power Automate / Dataverse approval flows — for example routing 855 change responses for sign-off before they send.
Every inbound interchange is written to the EDI transaction log with its raw payload, parsed values and status before it touches a BC document, so nothing is silently lost. Unmapped or failing documents are flagged rather than posted, and you (or ECOSIRE) can adjust the partner mapping and reprocess the document from the log with one action.
A build-to-order AL extension that automates trading-partner EDI inside Business Central — translating 850/855/856/810/940/945 and more directly into BC sales orders, purchase orders, warehouse shipments and posted invoices, with AS2/SFTP/VAN transport and SSCC-18 carton labels.