EDI
Also known as: Electronic Data Interchange, X12, EDIFACT, AS2, trading partner integration
Electronic Data Interchange (EDI) is the electronic exchange of business documents between trading partners (purchase orders, invoices, shipping notices, and inventory reports) in standardized formats (ANSI X12 in North America, EDIFACT internationally).
EDI replaces paper-based or email-based document exchange with automated, system-to-system data transfer. It is the backbone of B2B commerce in retail, automotive, healthcare, and logistics: most major retailers (Walmart, Target, Amazon) require suppliers to be EDI-capable.
EDI, explained at three levels
At home
EDI is a way for businesses to automatically send and receive business documents like purchase orders and invoices between their computer systems: without email, without paper, without human re-entry. When a big retailer buys 500 units of a product from a supplier, the purchase order is sent automatically from the retailer's buying system directly into the supplier's order management system.
At work
If your company supplies products to major retailers or works in automotive or healthcare supply chains, EDI is likely a requirement. Large trading partners (Walmart, Home Depot, automotive OEMs) mandate that suppliers receive purchase orders and send invoices and shipping notices via EDI. A supplier that can't do EDI often can't do business with these partners.
At home
EDI documents have standardized transaction set numbers. The most common: 850 (Purchase Order), 855 (Purchase Order Acknowledgment), 856 (Advance Ship Notice: sent before a shipment arrives), 810 (Invoice), 846 (Inventory Inquiry/Advice). Each transaction set has a defined format specifying exactly what data goes where. Both trading partners must agree to exchange specific transaction sets and to follow each other's implementation guidelines.
At work
EDI implementation requires a translator (software that converts EDI format to/from your internal system's format), a communication method (AS2 is the most common internet EDI protocol; some partners still use FTP or VAN), and trading partner setup (exchanging partner IDs, agreeing on transaction sets, testing before going live). Third-party EDI service providers (SPS Commerce, DiCentral, TrueCommerce) handle the technical complexity for companies that don't want to run EDI infrastructure in-house.
At home
AS2 (Applicability Statement 2) is the most widely used EDI transmission protocol for internet-based exchange. It encrypts and digitally signs EDI documents, provides delivery receipts (MDNs), and runs over HTTP/HTTPS. Each AS2 connection requires exchanging digital certificates with each trading partner: a setup process that takes days to weeks per new partner. AS4 is the newer protocol used in European regulated industries (pharma, energy).
At work
Enterprise EDI programs manage hundreds of trading partner connections, each with their own implementation guidelines, testing requirements, and compliance mandates. Chargebacks (penalties retailers apply for EDI non-compliance: wrong label, wrong ASN timing) can total significant percentages of invoice value for suppliers who don't execute perfectly. EDI integration with ERP (SAP, Oracle) requires mapping from EDI transaction formats to ERP document types and handling error acknowledgments. Modern supply chain integration platforms (Boomi, MuleSoft) increasingly bridge EDI and API-based trading partner connections in a single integration layer.
Real-world examples
At home
Sophie worked at a small textile supplier that just landed a contract with a major department store chain. The retailer required all POs to be received and invoices sent via EDI 850 and 810 formats. She contracted an EDI managed service provider (SPS Commerce), which set up the connection, mapped the EDI documents to her accounting software, and completed the retailer's test requirements. She was EDI-capable within six weeks.
At work
Thomas managed supply chain integrations for a consumer goods manufacturer with 80 retail trading partners. His EDI platform handled 50,000 transactions per week automatically: POs flowing into their ERP as sales orders, ASNs generated from their WMS shipment data, invoices sent automatically after shipment confirmation. The EDI team spent their time on exception management (failed transmissions, rejected documents) rather than data entry.
Common confusions
- Some businesses assume email-based document exchange is the same as EDI — Emailing a PDF invoice is not EDI. EDI requires computer-to-computer exchange in standardized structured formats that your trading partner's system can automatically read without human involvement. An emailed PDF must be manually re-entered (or OCR-scanned) into the recipient's system: introducing delays and errors. Major retailers explicitly require EDI and will not accept emailed POs or invoices as EDI compliance.
- Many assume API integration will quickly replace EDI everywhere — APIs are replacing EDI for new integrations between modern cloud systems, and many emerging retail platforms (Shopify, Faire) use APIs rather than EDI. But established retail supply chains (especially grocery, mass market retail, and automotive) have decades of EDI investment and hundreds of legacy suppliers and systems. EDI will coexist with APIs for many years, and new supplier onboarding to established retailers still typically requires EDI capability.
For analysts
When a new supplier asks about EDI compliance with a major retailer, the first step is to get the retailer's Trading Partner Guide: this document specifies exactly which transaction sets are required, the implementation guidelines for each, testing requirements, and chargeback policies for non-compliance. The guide defines the requirements; only then can you assess which EDI solution fits the supplier's volume and technical capability.
History & origin
EDI developed in the 1960s from the need to exchange transportation documents (bills of lading, freight bills) electronically between companies. The US railroad and trucking industries developed early EDI standards. In the 1970s and 1980s, the grocery industry (through the Grocery Manufacturers of America) and retail chains (Sears, Kmart) standardized EDI for purchase orders and invoices using ANSI X12. Walmart made EDI mandatory for all its suppliers in the 1980s, driving widespread adoption across retail supply chains. EDI transmission moved from dedicated VAN (Value Added Network) lines to internet-based AS2 and SFTP protocols in the 2000s. API-based integration (REST APIs) is increasingly replacing EDI for modern B2B integrations, but EDI remains dominant in established retail and healthcare supply chains.