If you have ever received a vendor compliance guide from a retailer, distributor, or logistics partner, you have almost certainly seen the acronym EDI followed by document numbers like 850, 856, and 810. For many businesses encountering it for the first time, EDI feels like an opaque technical requirement imposed from outside. This guide cuts through the jargon and explains what EDI actually is, how it works, and why it matters for your business.
The Plain-English Definition
EDI stands for Electronic Data Interchange. At its core, it is simply a standardised way for two computer systems to exchange business documents with each other — automatically, without human input.
Instead of a buyer emailing a PDF purchase order to a supplier, who then manually keys the order into their system, EDI lets the buyer's system send a structured electronic file that the supplier's system reads and acts on directly. No email. No printing. No data entry. No delay.
The "standardised" part is what makes it work across thousands of different companies and software systems. In North America, the dominant standard is ANSI X12, maintained by the Accredited Standards Committee. Each document type has a number: 850 for Purchase Orders, 810 for Invoices, 856 for Ship Notices, and so on.
What EDI Documents Are Exchanged?
A typical supplier-retailer relationship involves a handful of core transaction sets:
- 850 — Purchase Order: The buyer sends this to place an order
- 855 — PO Acknowledgment: The supplier confirms they received and can fulfil it
- 856 — Advance Ship Notice: The supplier notifies the buyer when goods ship
- 810 — Invoice: The supplier requests payment
- 997 — Functional Acknowledgment: A technical receipt confirming any EDI document was received and validated
- 820 — Payment Order: The buyer confirms payment details
These six documents handle the vast majority of B2B commerce transactions. More specialised industries use additional sets — healthcare uses 837 for claims, logistics uses 204 for load tenders — but the core six are where almost every EDI implementation starts.
How EDI Is Transmitted
EDI documents travel between trading partners via one of three main transport methods:
- AS2 — a secure, real-time internet protocol favoured by major retailers. Documents are encrypted, signed, and delivered with a digital receipt (MDN).
- SFTP — secure file transfer. Documents are deposited in an agreed folder and picked up on a schedule. Simpler to set up, slightly less real-time.
- VAN (Value Added Network) — a third-party mailbox service that routes documents between trading partners. Common in older implementations and some industries.
Why EDI Is Required (Not Optional)
Major retailers, grocery chains, automotive manufacturers, and 3PLs require EDI from their suppliers because manual document handling does not scale. A retailer processing 10,000 orders a day from 500 suppliers cannot afford to have humans reading emails and keying data. EDI makes that volume manageable — and it makes errors rare, trackable, and automatically flagged.
For suppliers, EDI compliance is the price of entry to working with significant buyers. The good news: with modern cloud platforms, getting set up no longer requires consultants, six-month projects, or enterprise software budgets.