Glossary
/
electronic-data-interchange-edi
B2B EDI e-commerce: electronic data interchange, EDIFACT X12 order and invoice messages, differences with API and Shopify integration.
Updated on
June 4, 2026
EDI (Electronic Data Interchange) is an automated exchange standard for commercial documents between two computer systems: orders, confirmations, shipping notices, invoices. In B2B e-commerce and retail, EDI replaces manual entry or PDF emails when a key account, a distributor, or a marketplace requires structured flows with its ERP or its warehouse.
Summary
Definition: EDI, messages, standards, APIs
EDI transmits standardized messages from one system to another, without human re-entry. Each message has a defined type and structure.
Common EDI documents in commerce:
Purchase Order (ORDERS / 850): the client sends their order.
Acknowledgement (ORDRSP / 855): the supplier confirms or modifies.
Dispatch Advice (DESADV / 856): shipped package, tracking, quantities.
Invoice (INVOIC / 810): structured payment request.
Catalog (PRICAT): price and reference update.
Main standards:
EDIFACT: common in Europe (GS1, retail, industry).
ANSI X12: dominant in the United States.
XML / UBL / cXML: modern variants depending on partners.
Useful distinctions:
EDI vs API: EDI follows B2B formats imposed by the client; API is a flexible proprietary or REST protocol.
EDI vs CSV export: CSV is an ad hoc file; EDI is a contract of standardized messages.
EDI vs PDF email: EDI is machine-to-machine; PDF requires reading or manual entry.
EDI vs web B2B portal: the portal (B2B e-commerce) often serves SMEs; EDI is for automated high volumes.
EDI vs webhook: the webhook notifies of an e-commerce event; EDI transports standardized business documents between ERPs.
VAN (Value Added Network) vs direct AS2: intermediate network (SPS Commerce…) or secure point-to-point connection.
Why EDI matters in B2B e-commerce
EDI mainly concerns merchants who sell to retailers, wholesalers, or B2B marketplaces requiring automated streams. It is not very relevant for a classic DTC Shopify store; however, it is critical for scaling retail or industrial contracts.
Automation: customer order received directly into ERP or WMS.
Error reduction: ends manual re-entry (references, quantities).
Lead times: faster processing, SLAs respected by major accounts.
Partner compliance: condition of access for certain distributors.
Traceability: documentary chain from order → shipping → invoice.
Volume: hundreds or thousands of lines per day without an entry team.
Without EDI when the client requires it, the supplier remains on manual processes (email, Excel): risk of penalties, payment delays, or loss of the contract. EDI is often part of an architecture including ERP, WMS, and sometimes the online store as an additional channel.
How does an EDI flow work in B2B e-commerce
E-commerce / retail supplier type flow:
First, the distributor sends an ORDERS (purchase order) message.
Then, the EDI middleware translates the message into an order in the ERP or Shopify.
Next, the supplier confirms via ORDRSP (acceptance or quantity changes).
Then, upon shipment: DESADV message with SSCC, packages, tracking (fulfillment).
Finally, after delivery: INVOIC (invoice) to trigger net 30/60 payment.
Flow actors:
Issuer: Customer's ERP or platform (retailer, wholesaler).
Receiver: Supplier's ERP, WMS, or middleware.
Translator / EDI provider: maps the fields (GTIN, GLN, quantities, dates).
For example: a sports equipment brand on Shopify Plus also sells to a national retailer under a retail contract. Every night, the retailer sends EDIFACT ORDERS to the SPS Commerce middleware. Orders are automatically created in the ERP; the logistics team prepares the pallets. Upon shipment, DESADV is sent to the retailer's central warehouse with SSCC numbers. INVOIC follows for the customer's accounting department. The DTC Shopify store remains on a classic API flow; only the retail channel goes through EDI.
The role of EDI in a Shopify environment
Shopify does not offer native EDI. Merchants connect a technical intermediary.
EDI Middleware: SPS Commerce, TrueCommerce, eBridge, Comarch, Generix.
iPaaS: Celigo, Boomi, Make (custom mapping, moderate volumes).
ERP hub: Shopify orders → ERP → EDI to B2B clients (frequent architecture).
Shopify Plus: complex B2B projects, advanced APIs, dev resources.
Marketplace apps: connectors depending on the partner (Amazon Vendor, European retail).
Shopify merchant checklist when faced with an EDI request:
First, obtain the EDI specifications from the client (messages, versions, GLN identifiers).
Next, choose a middleware or use the existing ERP.
Then, map product references (SKU ↔ GTIN/EAN).
Next, test in a sandbox environment before production.
Finally, align inventory and lead times (inventory management).
Finally, document the after-sales process (returns, EDI credit notes if applicable).
For a purely DTC SME, EDI is rarely a priority. It becomes relevant when a B2B client or a marketplace contractually imposes it.
The key takeaways about EDI
EDI = automated exchange of standardized B2B documents (orders, shipments, invoices).
EDIFACT, X12 standards; often via VAN or AS2.
Typical for major retail/industrial accounts, not standard DTC shops.
Distinct from API, CSV, B2B web portal.
Shopify: middleware, ERP hub, no native EDI module.
In brief
EDI = automated exchange of standardized B2B documents (orders, shipments, invoices).
EDIFACT, X12 standards; often via VAN or AS2.
Typical of major retail/industry accounts, not standard DTC shops.
Distinct from API, CSV, B2B web portal.
Shopify: middleware, ERP hub, no native EDI module.
Associated terms, FAQ, and useful resources
Associated terms
B2B E-commerce: main context of EDI.
ERP: pivotal system for EDI flows.
Order: object created from an ORDERS.
Shopify API: alternative or complementary integration.
Catalog export: product flows to partners.
FAQ
Does a Shopify store need EDI?
Rarely if you only sell directly in B2C. EDI becomes necessary when a B2B client, a major retailer, or a marketplace requires it to automate orders and invoices.
EDI or API: which to choose?
If the partner imposes an EDI format (EDIFACT, X12), you must comply. The REST API is suitable for modern, flexible integrations (Shopify, SaaS). Both often coexist: EDI on the major retail side, API on the online store side.
How much does an EDI setup cost?
Variable depending on volume, number of partners, and middleware: monthly provider subscription + setup and initial mapping fees. Ask an EDI integrator for a quote; it is a project budget rather than a free tool.
What are the most common EDI messages?
In retail: ORDERS (order), DESADV (dispatch advice), INVOIC (invoice). The client's specifications detail the variants and mandatory fields.
Going further
Connect your e-commerce tools.
Shopify integrations explained.
Back to the Qstomy e-commerce glossary.
Sources: GS1 (EDI standards), EDI middleware documentation (SPS Commerce, TrueCommerce). Formats and requirements vary according to each trading partner.
Enzo
June 4, 2026
