Aperçu illustratifA 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.
Qu'est-ce que EDI Connector for Business Central ?
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 $999.00 USD; request a quote for a scoped proposal.
Fonctionnalités clés
Fait sur commande, clé en main
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
- 1
Vous commandez
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
- 2
Nous développons et installons
ECOSIRE la développe, la configure et l'installe sur votre Dynamics 365 Business Central.
- 3
Mise en ligne + assistance
Vous êtes en ligne en une semaine ouvrée environ, avec deux semaines d’assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.
À propos de ce produit
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.
Ce que vous obtenez
- A per-tenant AL extension (.app) built for your Business Central version, installed on your sandbox then promoted to production
- Trading-partner mapping configuration for the partners scoped at purchase (qualifiers, segments, item/ship-to cross-references)
- Transport setup for your chosen channel — AS2 certificate exchange, SFTP credentials, or VAN mailbox connection
- Dedicated EDI permission sets and Job Queue entries for inbound polling and outbound batching
- SSCC-18 label layout configured to each partner's GS1 / retailer specification
- Source AL project, configuration export and an admin runbook covering onboarding new partners and reprocessing failed documents
Pour qui c'est
Supply-chain / EDI compliance manager
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.
Business Central functional consultant / IT lead
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.
Operations / warehouse manager at a retail supplier
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.
Comment EDI Connector for Business Central se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Natif Dynamics 365 Business Central |
|---|---|---|---|---|
| 850/855/856/810 mapped directly to native BC sales/purchase/warehouse documents | Inclus | Prise en charge partielle | Inclus | Non inclus |
| 3PL / cross-dock 940/945/947 against BC warehouse entries | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| SSCC-18 carton/pallet label generation to retailer GS1 spec | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| AS2 / SFTP / VAN transport with 997 acknowledgment handling | Inclus | Prise en charge partielle | Inclus | Non inclus |
| Per-tenant AL extension — no base-object changes, upgrade-safe | Inclus | Prise en charge partielle | Inclus | Inclus |
| Built, installed and supported on your environment by the vendor | Inclus | Non inclus | Prise en charge partielle | Non inclus |
| Mapping tailored to your exact trading-partner specs at delivery | Inclus | Inclus | Non inclus | Non inclus |
| EDI status exposed via BC REST/OData API for Power BI / Power Automate | Inclus | Prise en charge partielle | Prise en charge partielle | Prise en charge partielle |
Foire aux questions sur EDI Connector for Business Central
How long until the EDI Connector is live in our environment?
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.
Who maintains it after go-live, and what happens when we add a new retailer or Microsoft ships a BC update?
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.
Does this work on Business Central online (SaaS) and on-premises?
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.
Will it modify our standard sales, purchase and warehouse documents or break upgrades?
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.
Can we see EDI status in Power BI or trigger Power Automate flows?
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.
What if a trading partner sends a document our mapping doesn't expect?
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.
Modules associés
eBay Connector for Business Central
A build-to-order AL extension that syncs eBay listings, orders, inventory and shipment tracking with Dynamics 365 Business Central in near real time. Built, installed per-tenant and supported by ECOSIRE.
eBay Connector for Dynamics 365 Finance & Operations
A bi-directional eBay integration for Dynamics 365, custom-built by ECOSIRE as a per-tenant AL extension, installed on your environment, and supported after go-live. Orders, listings, inventory, shipments and returns sync automatically across legal entities and warehouses.
Egypt E-Invoicing & E-Receipt Connector for Business Central
A per-tenant Business Central AL extension that submits ETA-compliant e-invoices and e-receipts, handles digital signatures and UUIDs, maps GS1/EGS item codes, and tracks real-time clearance — built, installed, and supported by ECOSIRE on your tenant.
eMAG Marketplace Connector for Business Central
A custom-built, per-tenant AL extension that links the eMAG Marketplace (Romania, Bulgaria, Hungary) to Dynamics 365 Business Central — automating order import, offer and price/stock sync, eMAG Fulfilment (FBE) reconciliation, and invoice, VAT and AWB write-back. Built, installed and supported by ECOSIRE on your environment.
EDI Connector for Business Central
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.
- Inbound 850 Purchase Order translated directly into a Business Central sales order, with line, pricing and ship-to mapping per trading partner
- Outbound 855 Purchase Order Acknowledgment generated from the BC sales order, including line-level accept/reject/change responses
- 856 Advance Ship Notice (ASN) built from the warehouse shipment with hierarchical shipment/order/tare/item loop and SSCC references
- 810 Invoice generated from the posted BC sales invoice and reconciled against the originating 850