EDI (Electronic Data Interchange)

The structured, machine-readable exchange of business documents between companies — purchase orders, acknowledgements, delivery notices, invoices, inventory data — formalized into defined formats that two systems can process without human intervention. EDI sits at the intersection of three distinct problems: standards (what format is the data?), transport (how does it move from A to B?), and mapping (how does the received format map onto each party's internal ERP or WMS?). ^[1]

EDI replaces paper, PDFs, and manual re-keying with system-to-system document flows that load directly into the retailer's software. Major retailers cannot manually process thousands of supplier invoices or delivery notices — a single typo on a SKU, size, or price can trigger chargebacks, delays, or order cancellation. ^[2]

In 2026, B2B ecommerce and EDI are converging: companies are bringing B2B ecommerce platforms and EDI networks into tight alignment with ERP systems, warehouse operations, and supplier connectivity, with the goal of re-engineering order flows from the moment a customer clicks "buy" to the instant inventory, shipping notices, and invoices update across trading partners. ^[3]

Standards (formats)

ANSI X12

The dominant standard in North America, governed by the Accredited Standards Committee (ASC X12). Used by US retail (Walmart, Target, Amazon Vendor), healthcare (HIPAA mandates X12 837/835), and logistics. ANSI X12 and EDIFACT are not compatible — a manufacturer with trading partners on both standards must maintain separate mapping configurations. (Gerloff, 2026-03-19)

EDIFACT and EANCOM

EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport) is an ISO standard (ISO 9735) managed by the UN, dominant in Europe across manufacturing, automotive, retail, and logistics. Most real-world EDIFACT implementations are not pure EDIFACT but subsets that define stricter rules for which segments are mandatory and what values are acceptable — "We use EDIFACT ORDERS D96A" discloses roughly 30% of the actual specification. (Gerloff, 2026-03-19)

EANCOM is the GS1 subset of EDIFACT, originally developed for the retail sector and now the most widely used UN/EDIFACT subset, implemented by approximately 126,000 companies across retail/FMCG, healthcare, construction, and publishing. GS1 recommends GS1 XML for new implementations but commits to maintaining EANCOM for the existing user base. ^[4]

GS1 EDI covers the entire retail supply chain scope: master data alignment, order and delivery management, financial settlement, transport, and warehouse management, with main partners being retailers, manufacturers, material suppliers, and logistics service providers. ^[5]

Tradacoms is one of the earliest EDI standards and remains in use in UK retail despite being formally succeeded by EDIFACT EANCOM. ^[6] — 2025 source; included as no 2026 update found.

GS1 ^[7] explicitly recommends GS1 XML to new EDI users as the forward path while committing to maintain EANCOM for the existing user base. SPS Commerce and Körber position EDI (including EANCOM) as fully current and expanding in 2026 without flagging XML migration. commercetools and Manhattan Associates frame the integration picture as primarily API-first, with EDI treated as one compatible protocol among several. The market is not converging on a single answer — platform vendors are adding API wrappers around EDI rather than replacing it, while the standards body signals a slow XML migration for new implementations.

Other standards

Tradacoms: UK retail legacy standard, still in active use despite EDIFACT succession (EDI Basics/OpenText, 2025-09-11)
ODETTE: European automotive supply chains; OFTP2 (ODETTE File Transfer Protocol 2) is its modern transport protocol, providing encryption, signing, and end-to-end delivery acknowledgements comparable to AS2. (Gerloff, 2026-03-19)
cXML (Commerce XML, SAP Ariba): widely used for procurement and e-procurement platforms; connects suppliers to large buyers through SAP Ariba ecosystems (Gerloff, 2026-03-19)
UBL (Universal Business Language): underlies most EU e-invoicing formats including Peppol (EN-16931) (Gerloff, 2026-03-19)
GS1 XML: GS1's recommended standard for new implementations; JSON representations of GS1 XML schemas are emerging for modern API-based integrations (Gerloff, 2026-03-19)

Core retail transaction sets (ANSI X12)

The full retail transaction set in X12 for fashion/apparel and general retail (AIMS360, 2025-08-29):

Transaction Set	Name	Purpose
850	Purchase Order	Retailer → Supplier: the order
855	PO Acknowledgment	Supplier → Retailer: confirm or reject the PO
856	Advance Ship Notice (ASN)	Supplier → Retailer: carton-level shipment detail with GS1-128 label data
810	Invoice	Supplier → Retailer: billing
820	Payment/Remittance Advice	Retailer → Supplier: payment confirmation
997	Functional Acknowledgment	Syntactic receipt confirmation for any EDI file
832	Price/Sales Catalog	Publish product data to catalog networks (OpenText GXS, Intertrade)
846	Inventory Inquiry/Advice	Share available-to-sell quantities — central to drop-ship programs
852	Product Activity Data	Retailer shares store/site sales and on-hand data for CPFR/VMI
753/754	Routing Request/Instruction	Carrier selection, approved SCAC codes, DC address
864	Text Message	Free-form compliance notes
865	PO Change Acknowledgment	Seller-initiated PO changes
870	Order Status Report	Backorder or partial shipment status

The EDIFACT equivalents for the core retail flows: ORDERS (850), ORDRSP (855), DESADV/IFTMIN (856), INVOIC (810), REMADV (820), CONTRL (997), and PRICAT (832). (Gerloff, 2026-03-19)

Transport layer

AS2

AS2 (Applicability Statement 2, RFC 4130) is the most widely used EDI transmission protocol for direct B2B connections. It is HTTP/S-based and provides encryption (PKCS#7), digital signatures (non-repudiation), and Message Disposition Notifications (MDNs) — confirming the partner received and decrypted the file. Required by major retailers including Walmart and Marks & Spencer. AS2 requires managing X.509 certificates that expire; certificate-related failures are a common source of outages and calendaring certificate renewals is non-optional operational hygiene. (Gerloff, 2026-03-19)

SFTP

Operationally simpler than AS2 — no certificates, no MDN, authenticated file transfer to/from a shared directory. No built-in delivery acknowledgement, meaning a file dropped in a directory provides no confirmation whether the partner picked it up and processed it. SFTP-based EDI tends to have more manual monitoring overhead than AS2. (Gerloff, 2026-03-19)

Value Added Networks (VANs)

A Value Added Network (VAN) is a third-party network intermediary: the sender transmits EDI messages to the VAN, which routes them to trading partners. VANs predate the internet and were the original EDI infrastructure in the 1980s–1990s. They still exist because they provide indirect connections to hundreds of trading partners without managing individual AS2 connections. VANs typically charge per-document or per-character fees. Major European VANs include GXS (now OpenText), Sterling Commerce (now IBM), and Inovis. Many EDI platforms offer VAN-like managed networks (ecosio, Seeburger's network). (Gerloff, 2026-03-19; volatile)

Rough heuristic: 10,000+ documents/month per partner is the crossover where direct AS2 overhead becomes economical compared to per-document VAN fees — though specific VAN pricing matters more than the heuristic. (Gerloff, 2026-03-19; practitioner estimate, not survey data)

Retailer compliance and chargebacks

Major retailers enforce strict routing guides — the retailer's rulebook covering cartonization, UCC-128/GS1-128 label specifications, SCAC codes (Standard Carrier Alpha Codes), ship windows, packing slips, DC addresses, and compliance checks. Suppliers that cannot integrate seamlessly risk exclusion from preferred vendor lists regardless of price or product quality. (Digital Commerce 360, 2026-02-02)

Chargebacks (financial penalties for non-compliance — distinct from payment Chargeback disputes) are triggered by late ASNs, label errors, wrong quantities, and missed cancel dates. Generating the EDI 856 from actual pick/pack data so ASNs match physical cartons, and printing UCC-128 labels from the same data, avoids the most common label/content mismatches. (AIMS360, 2025-08-29)

Carton and pallet labelling requirements:

UCC-128 / GS1-128 shipping label required on every carton or pallet at most major retailers
Label must include barcode, PO number, carton ID (SSCC — Serialized Shipping Container Code), destination DC, and SCAC code — all must match the 856 ASN
Every style-color-size combination requires a unique UPC/GTIN assigned through a GS1 Company Prefix; these must be in item masters and included in 850, 810, 856, and 832 documents (AIMS360, 2025-08-29)
Some retailers additionally mandate RFID (EPC) tickets and encoded swing tags alongside barcode labelling (AIMS360, 2025-08-29; as-of 2025-08-29)

Partner onboarding and mapping complexity

For a typical EDIFACT ORDERS/ORDRSP/DESADV/INVOIC setup with an established partner via AS2, six to eight weeks is not slow — it is normal. The bottleneck is rarely technical capability but coordination overhead: the technical EDI work might represent 2–3 weeks of actual effort in an 8-week project. (Gerloff, 2026-03-19)

Typical onboarding timeline:

Weeks 1–2: scoping and information exchange (partner provides their EDI specification document, often a 30–100 page PDF)
Weeks 2–4: mapping development
Weeks 3–5: certificate and connection setup
Weeks 4–6: testing
Week 6+: go-live and stabilization — first 30–90 days produce the most support tickets

A company with 50 active EDI partners typically maintains 200–400 individual mapping rules — accumulated per partner per message type and held in the EDI middleware's proprietary mapping language (XSLT, SAP message mapping, Seeburger BIS scripts, etc.). (Gerloff, 2026-03-19)

EDI in fashion and apparel

Two distinct EDI flows exist in fashion (AIMS360, 2025-08-29):

Bulk EDI: dated POs to DCs or stores (850/856/810 cycle) — the traditional wholesale model
Drop-ship EDI: retailer's ecommerce site forwards consumer orders to the supplier for DTC fulfillment; requires on-time 856 ASN with tracking, clean 810 invoicing, and typically the EDI 846 (Inventory Inquiry/Advice) so the retailer can display live availability

The five largest US multi-brand apparel retailers all run strict EDI programs: Walmart US Apparel (~~$39.0B), Target Apparel (~~$17.0B), Macy's (~~$15.1B), TJX (~~$14.9B), Kohl's (~$10.5B) — 2024 actuals. (AIMS360, 2025-08-29; as-of 2024; sourcing methodology not disclosed)

Major US product data catalog networks for apparel: OpenText GXS and Intertrade — trading partners typically require brands to host product lines (styles, UPCs, pricing) in these networks before they can place orders; the EDI 832 is the catalog transaction set. (AIMS360, 2025-08-29; as-of 2025-08)

EDI vs API in 2026

The framing in 2026 is not EDI vs API but hybrid architecture: EDI provides the structured, reliable document exchange required by large trading partners; APIs enable the real-time data access needed for dynamic pricing, shipment visibility, and live inventory updates inside ecommerce experiences. (Digital Commerce 360, 2026-02-02)

The deeper issue identified by Stacksync (2026-02-12) is synchronization: when EDI systems extract outdated ERP data during batch windows, documents become misaligned with real inventory or pricing; when APIs update systems instantly but EDI runs on a delay, timing mismatches create chargebacks and compliance penalties. ^[8]

Amazon, Zalando, and REWE Digital use REST APIs rather than AS2 for their vendor connections; the boundary between "EDI" and "API integration" is blurring as EDI middleware platforms begin to include API management capabilities. (Gerloff, 2026-03-19; volatile as-of 2026-03)

Home Depot, CVS Health, and Walgreens continue to require structured EDI documents (X12) for compliance and receiving automation, regardless of how their internal systems communicate. (Stacksync, 2026-02-12)

Shopify Winter '26 EDI integration (2026)

Shopify's Winter '26 Edition natively integrated EDI workflows into the platform for the first time via SPS Commerce and Crstl: "Previously, big box retailers and enterprise customers relied on EDI for purchase orders, but those workflows lived completely outside the Shopify platform." Draft orders from EDI purchase orders now sync directly into Shopify admin, with label printing included. ^[9]

CPFR and VMI integration

CPFR (Collaborative Planning, Forecasting and Replenishment) was developed by VICS (Voluntary Inter-industry Commerce Solutions), now part of GS1 US. The EDI 852 (Product Activity Data) is central to CPFR — it transmits store sales and on-hand data from retailer to supplier. (EDI Basics/OpenText, 2025-09-11)

Vendor-Managed Inventory (VMI), pioneered by Walmart and P&G, uses a combination of 852 (sales/inventory data), 846 (inventory levels), and 855/856 (acknowledgement and fulfillment) transaction sets to shift replenishment decisions from retailer buyers to suppliers. The EDI 846 is also described as enabling ASN use to reduce receiving times. (EDI Basics/OpenText, 2025-09-11)

EDI Basics/OpenText (2025-09-11, vendor source) states using ASNs can reduce receiving times by up to 60%, saving large retailers thousands of hours annually — no primary study cited; vendor conflict of interest applies.

AI in EDI (as-of 2026)

Integration platforms are applying AI to automate data mapping, detect transaction errors, and analyse order patterns for forecasting and planning. (Digital Commerce 360, 2026-02-02)

SPS Commerce MAX (launched February 2026) is an AI layer embedded into SPS Commerce's EDI network, drawing on 300,000 trading connections and billions of transactions. Initial features: MAX Chat, MAX Monitor (continuous monitoring of transactions, workflow requirements, and exceptions across the network), and MAX Connect (supports Agentic Commerce Protocol (ACP)|Model Context Protocol / MCP — built to collaborate with other agents across ERPs, CRMs, and data platforms). Described as embedded into existing supply chain workflows rather than a standalone dashboard. ^[10]

From SPS Commerce 2026 Demand Report (as-of 2026-01): 41% of SPS customers face integration challenges with ERP and WMS systems; only 40% of companies report optimal inventory levels while 45% say inventory is too high. (SPS Commerce, 2026-01; volatile)

AI-assisted mapping: Gerloff (2026-03-19) estimates LLMs can propose field mappings covering 60–80% of straightforward structural mappings automatically, with the remaining 20–40% requiring human input for business logic (routing rules, tax determination, pricing conditions) — a 50–70% effort reduction for straightforward cases, not to zero. Vendors active in this space: Seeburger ("Intelligentes Daten-Mapping") and Orderful ("AI-powered automated mappings"). (Gerloff, 2026-03-19; practitioner estimate, not survey data)

AI monitoring: Log analysis, error pattern recognition, and predictive failure detection are identified as the most mature AI application in EDI. Anomaly detection ("Partner X normally sends 50 ORDRSP per day; today they sent 3 — flag for investigation") is described as the clearest value proposition with the least controversy. (Gerloff, 2026-03-19)

Regulatory context: e-invoicing mandates

Germany (Wachstumschancengesetz, 2025): Since January 2025, all German companies must be able to receive structured B2B e-invoices (XRechnung, ZUGFeRD formats). Mandatory sending phases: 2027 for most companies, 2028 for small companies. Companies already running EDI must add this additional format requirement. (Gerloff, 2026-03-19; as-of 2026-03; volatile)

EU VAT in the Digital Age (ViDA): All intra-EU B2B invoices must use the Peppol standard (EN-16931) by July 1, 2030, with country-level mandatory sending rolling out earlier — Belgium (January 2026), France (September 2026), Poland (February–April 2026), Germany (January 2027), Spain (January 2027). (Gerloff, 2026-03-19, citing BMF Schreiben vom 15.10.2024 and §14 UStG n.F.; as-of 2026-03; volatile)

OMS/WMS and carrier integration patterns

EDI operates as a co-equal integration path alongside REST APIs in leading Order Management System (OMS)|OMS and Warehouse Management System (WMS)|WMS platforms:

Körber Enspire Commerce: B2B file management (EDI) is native to the platform — "eliminating the need for a third-party service resulting in reduced points of failure, complexity and costs." Managed EDI services available for retailers where EDI is outside core competency; dropship-EDI integration on the same platform. ^[11]
Manhattan Active Platform: publishes "thousands of integration-ready REST API endpoints" alongside EDI standards; carrier shipping management covers "certified carrier labels and EDI, track and trace, and delivery KPIs." ^[12]
Fluent Commerce: B2B order management positioned as requiring intake from "EDI, online portals, marketplaces, field sales reps, and DTC ecommerce" as co-equal channels — not positioning EDI as legacy. (Fluent Commerce, undated)
ParcelLab / carriers: Gebrüder Weiss provides shipment status via "the BORD512 interface via EDI, including parcel numbers in RFF+CW"; Kühne+Nagel provides status data "according to the EDIFACT IFTSTA specification via SFTP" — confirming EDIFACT is in active use for carrier-to-retailer status messaging in 2026. ^[13]

Key terms

Term	Meaning
850/ORDERS	Purchase Order — the core buying document from retailer to supplier
856/DESADV	Advance Ship Notice — carton-level shipment data transmitted before delivery
SSCC	Serialized Shipping Container Code — unique identifier for each carton/pallet
SCAC	Standard Carrier Alpha Code — 2–4 letter code identifying each carrier
ASN	Advance Ship Notice (same as 856/DESADV)
VAN	Value Added Network — intermediary routing hub for EDI messages
AS2	Applicability Statement 2 — the dominant HTTP-based EDI transport protocol
Routing guide	Retailer's compliance rulebook for suppliers — cartonization, labels, ship windows
Chargeback	Financial penalty imposed by retailer on supplier for EDI/logistics compliance failures
Mapping	Translation rules converting source EDI format to destination ERP fields
GTIN	Global Trade Item Number — unique product identifier (includes UPCs)
GS1-128 / UCC-128	Barcode standard for shipping labels; encodes SSCC, PO, destination
EANCOM	GS1 subset of EDIFACT; most widely used EDI standard in EU retail (~126,000 companies)
Peppol	Pan-European procurement network; mandatory for EU B2B e-invoicing (ViDA)
GDSN	GDSN (Global Data Synchronization Network) — GS1-managed network for synchronizing product master data between trading partners

Next frontier

Value Added Network (VAN) · ANSI X12 · EDIFACT · GDSN (Global Data Synchronization Network) · Peppol · Drop-ship Program · GS1 Company Prefix

References

Gerloff, 2026-03-19; — www.gerloff.dev/writing/edi-deep-dive-standards-protocols-2026
AIMS360, 2025-08-29; — www.aims360.com/fashion-business-resources/edi-software-apparel-industry-erp-edi-certified-guide
Digital Commerce 360, 2026-02-02; — www.digitalcommerce360.com/2026/02/02/b2b-sellers-operations-ecommerce-edi
GS1 Standards, undated; — www.gs1.org/standards/eancom
GS1 Standards, undated; — www.gs1.org/standards/edi
EDI Basics/OpenText, 2025-09-11; — www.edibasics.com/edi-by-industry/the-retail-industry
www.gs1.org/standards/edi/implementation
Stacksync, 2026-02-12; — www.stacksync.com/blog/edi-vs-api-integration-supply-chain-data-guide
Shopify, 2026; volatile as-of 2026 — www.shopify.com/enterprise/blog/shopify-winter-26-edition-b2b-roundup
SPS Commerce, 2026-02; — www.spscommerce.com/blog/meet-max
Körber, undated; — koerber-supplychain.com/supply-chain-solutions/supply-chain-software/order-management-system/edi
Manhattan Associates, undated; — www.manh.com/solutions/manhattan-active-platform
ParcelLab Docs, undated; — docs.parcellab.com/docs/platform/carrier-integrations