Skip to main content

EDI — Electronic Data Interchange

EDI (Electronic Data Interchange) describes the structured, machine-to-machine exchange of business documents between trading partners using standardized message formats. EDI predates the internet, dates back to the 1970s, and remains the backbone of B2B supply-chain communication — particularly in the US automotive industry, grocery and mass retail (Walmart, Target, Kroger, Costco) and pharmaceutical distribution. Modern ERP systems either ship with EDI integration or connect to specialized EDI service providers.

Relevant EDI standards

  • ANSI ASC X12 — the dominant EDI standard in the United States and the rest of North America. Industry subsets include VICS (general merchandise retail), UCS (grocery) and the AIAG transaction sets (automotive).
  • EDIFACT (UN standard) — dominant in Europe and Asia, occasionally relevant for US companies trading with overseas partners.
  • AIAG recommendations — Automotive Industry Action Group implementation guidelines layered on X12 (for example the 830 planning schedule, 862 shipping schedule and 856 ASN).
  • AS2 — the dominant transport protocol in North America. Walmart and many other large buyers require AS2 for EDI communications; SFTP and value-added networks (VANs) are also common.

How ERP-EDI integration works

An incoming order arrives as an EDI message (X12 850 purchase order). The EDI converter maps the message structure to the ERP's sales-order data model. The order is created automatically, with stock availability and pricing applied per the customer master data. Outgoing advance ship notices (X12 856 ASN) and invoices (X12 810) are generated by the ERP and sent back through the converter. Errors trigger manual review in an exception queue.

ERP vendor EDI capabilities

Strong native EDI: SAP S/4HANA, Microsoft Dynamics 365 Finance & Operations, Oracle NetSuite, Infor CloudSuite, Epicor Kinetic. Cloud-native ERP often connects to external EDI service providers (SPS Commerce, TrueCommerce, Cleo, Boomi) via REST API — typical for Acumatica, Sage Intacct, Odoo and similar platforms. For most US mid-market companies, a managed EDI service costs roughly $250–$2,500 per month depending on transaction volume.

EDI message types in daily US operations

A typical US supplier-to-customer EDI flow uses 6–10 message types. 850 (purchase order): the incoming order. 855: purchase order acknowledgment, confirming acceptance and committed ship date. 830 / 862: rolling planning schedule and just-in-time shipping schedules, dominant in US automotive supply (Ford, General Motors, Stellantis and Tier-1 suppliers such as Magna, BorgWarner and Aptiv). 856 (Advance Ship Notice / ASN): sent when goods leave the dock, often required to be transmitted before the truck arrives, with a compliant UCC-128 / GS1-128 shipping label. 861: receiving advice / acknowledgment from the customer. 810: the electronic invoice. 820: payment order / remittance advice. 852 / 846: product activity and inventory inquiry/advice, common in vendor-managed inventory arrangements with mass retailers like Walmart, Target and Kroger. Translation between these standards and the ERP's internal data structures is the EDI converter's core job. Modern EDI service providers (SPS Commerce, TrueCommerce, Cleo) handle thousands of these mappings as preconfigured retailer and trading-partner templates — a significant cost saving versus building each mapping from scratch.

EDI vs API-first ERP — the strategic question

For new B2B trading relationships in 2026, the legitimate question is whether to roll out EDI at all or to start with modern REST/GraphQL API integration. EDI remains the right answer when (1) the customer mandates X12, which large US retailers and the automotive supply chain still do for most established suppliers; (2) the trading partner uses asynchronous batch processing through a VAN; (3) industry conventions prescribe specific transaction sets and labeling (for example UCC-128 ASN compliance for retail). API-first integration (REST/GraphQL via iPaaS platforms like Boomi, MuleSoft, Workato or Cleo Integration Cloud) is preferable when (1) both parties have modern ERPs with proper API coverage, (2) the integration needs to be real-time, (3) the data model is richer than legacy EDI standards can carry. In practice, many US mid-market companies operate hybrid landscapes: EDI for the historic customer base, API integration for new partners, with the EDI service provider acting as a translation layer that converts API calls into EDI messages where needed. Peppol-based e-invoicing through the DBNAlliance network is an emerging structured standard that fits between classic EDI and pure API integration, especially for invoicing — though, unlike in many countries, the US has no federal B2B e-invoicing mandate, so adoption remains voluntary and market-driven.

Operating an EDI environment in practice

Beyond initial setup, daily EDI operations involve a recurring pattern of exception handling that any procurement team should understand. Mapping changes: trading partners revise their EDI specifications (new fields, changed segments, version upgrades from one X12 release to the next) typically once or twice a year. Each change requires testing and a coordinated cutover. Reject monitoring: incoming messages that fail validation queue in an exception list for manual review. Common causes: unknown item numbers, customer-specific part codes not mapped, missing master data, expired pricing. Mature operations clear the queue daily; below that cadence, reject volume accumulates and trading-partner relationships suffer — with large retailers, missed ASNs or late acknowledgments can also trigger chargebacks. Acknowledgment tracking: X12 997 functional acknowledgments or AS2 MDN messages confirm receipt — missing acknowledgments within the SLA window must trigger an investigation. Performance under peak load: order bursts during retail promotion periods or just-in-time automotive end-of-quarter typically spike volume 3–5x normal — the EDI infrastructure must scale or queue gracefully. Onboarding new partners: each new customer or supplier adds 1–6 weeks of mapping and certification work. Managed-EDI providers maintain libraries of pre-built mappings that compress this. Audit trail: every inbound and outbound message should be archived because order and shipment data feeds into invoicing and tax records — the IRS generally expects supporting records to be kept for at least three to seven years, and public companies subject to SOX retain financial records for seven years. The volume can be substantial — mid-market companies in automotive supply routinely store 50–200 GB per year of EDI messages.

Related Topics

erp-software.org · the independent ERP comparison for the mid-market in Germany, Switzerland and Austria
All mentioned brand, product and company names are property of their respective owners. References are made solely for identification and comparison purposes (no indication of commercial or partnership relationships). Note pursuant to §5b German UWG (Unfair Competition Act): user reviews are manually plausibility-checked before publication – we cannot, however, determine with absolute certainty whether reviews originate exclusively from actual users. Some links on erp-software.org may lead to advertising partnerships or lead-referrals; editorial assessments are made independently of these.