EDI Knowledge Center
EDI 101: a plain-English guide to electronic data interchange
EDI is how retailers, manufacturers, distributors and 3PLs exchange orders, shipping notices and invoices automatically — no email attachments, no re-keying. Use this guide to get comfortable with the terms your trading partners use every day.
What is EDI? · X12 vs EDIFACT · Common transactions · EDI glossary
What is EDI?
Electronic data interchange (EDI) is the computer-to-computer exchange of business documents in a standard format. Instead of a buyer emailing a PDF purchase order that someone types into an ERP, the buyer’s system sends a structured EDI purchase order that your system can read and process automatically.
Faster
Orders, shipping notices and invoices move in minutes instead of days, so you ship sooner and get paid sooner.
More accurate
No re-keying means fewer typos, fewer short shipments and fewer costly retailer chargebacks.
Often required
Most large retailers, distributors and logistics providers require suppliers to trade via EDI as a condition of doing business.
X12 vs EDIFACT
Two standards cover most of the EDI traded around the world. They do the same job with different names, structures and syntax — and which one you use usually depends on where your trading partner is based.
| ANSI X12 | UN/EDIFACT | |
|---|---|---|
| Maintained by | Accredited Standards Committee X12 (ASC X12), under ANSI | United Nations, through UN/CEFACT |
| Where it’s used | Primarily North America | Primarily Europe and international trade |
| Document names | Numbered “transaction sets” — e.g. 850 Purchase Order | Six-letter “messages” — e.g. ORDERS |
| Building blocks | Transaction set → segments → data elements | Message → segments → data elements (simple and composite) |
| Envelopes | ISA/IEA (interchange), GS/GE (functional group), ST/SE (transaction set) | UNB/UNZ (interchange), optional UNG/UNE (group), UNH/UNT (message); optional UNA sets the delimiters |
| Typical delimiters | Defined in the ISA segment; commonly * between elements and ~ ending each segment | Defaults of + between elements, : between components and ' ending each segment, with ? as the release character |
| Versions | Numbered releases, e.g. 004010 or 005010 | Directory releases, e.g. D.96A or D.01B |
| Acknowledgment | 997 Functional Acknowledgment (999 in healthcare) | CONTRL message |
| Industry subsets | Retail (VICS), grocery (UCS), healthcare (HIPAA), automotive (AIAG) | Retail and consumer goods (EANCOM), automotive (Odette), transport and customs |
Common EDI transactions
These are the documents we see most often across retail, manufacturing and 3PL relationships. A typical retail order flows 850 → 855 → 856 → 810, with a 997 acknowledging each step.
Order to cash
| X12 | EDIFACT | Name | What it does |
|---|---|---|---|
| 850 | ORDERS | Purchase Order | The buyer orders goods — items, quantities, prices, ship-to and requested dates. |
| 855 | ORDRSP | Purchase Order Acknowledgment | The supplier confirms, changes or rejects the order lines. |
| 860 | ORDCHG | Purchase Order Change (buyer-initiated) | The buyer changes an order already sent — quantities, dates or items. |
| 865 | ORDRSP | Purchase Order Change Acknowledgment | The supplier responds to a change, or initiates one of its own. |
| 856 | DESADV | Ship Notice/Manifest (ASN) | Tells the buyer exactly what shipped, how it’s packed and when it will arrive — often tied to GS1-128 carton labels. |
| 810 | INVOIC | Invoice | Bills the buyer for what was shipped. |
| 820 | REMADV | Payment Order/Remittance Advice | Details a payment and which invoices it covers. |
| 812 | — | Credit/Debit Adjustment | Notifies a credit or debit, such as a deduction or chargeback. |
Inventory and product data
| X12 | EDIFACT | Name | What it does |
|---|---|---|---|
| 846 | INVRPT | Inventory Inquiry/Advice | Shares available inventory, often used for drop-ship and replenishment. |
| 852 | SLSRPT | Product Activity Data | Retailer shares sell-through and on-hand data by item and store. |
| 832 | PRICAT | Price/Sales Catalog | Shares item details, UPCs and pricing with the buyer. |
Warehousing and transportation (3PL)
| X12 | EDIFACT | Name | What it does |
|---|---|---|---|
| 940 | — | Warehouse Shipping Order | The owner of the goods tells the 3PL warehouse what to ship. |
| 945 | — | Warehouse Shipping Advice | The 3PL confirms what was actually shipped. |
| 943 | — | Warehouse Stock Transfer Shipment Advice | Tells the warehouse an inbound shipment is on its way. |
| 944 | — | Warehouse Stock Transfer Receipt Advice | The warehouse confirms what it received. |
| 947 | — | Warehouse Inventory Adjustment Advice | Reports inventory adjustments such as damages or cycle-count changes. |
| 204 | IFTMIN | Motor Carrier Load Tender | Offers a shipment to a carrier. |
| 990 | — | Response to a Load Tender | The carrier accepts or declines the load. |
| 214 | IFTSTA | Transportation Carrier Shipment Status | Pickup, in-transit and delivery status updates. |
| 210 | — | Motor Carrier Freight Details and Invoice | The carrier bills for freight. |
Acknowledgments
| X12 | EDIFACT | Name | What it does |
|---|---|---|---|
| 997 | CONTRL | Functional Acknowledgment | Confirms a document was received and passed syntax checks — not that the order was accepted. |
| 999 | — | Implementation Acknowledgment | A more detailed acknowledgment, used mainly in healthcare (HIPAA). |
EDI 101 glossary
EDI terms and definitions
Trading partner — Any company you exchange EDI documents with — a retailer, supplier, 3PL or carrier.
Transaction set / message — A single EDI document, such as an 850 purchase order (X12) or ORDERS message (EDIFACT).
Segment — One line of an EDI document holding related data, such as the ship-to address (N1 in X12, NAD in EDIFACT).
Data element — A single piece of data inside a segment, such as a quantity or a date.
Delimiter — The character that separates elements and segments so systems can read the file.
Envelope — The header and trailer segments that wrap documents for delivery, identifying the sender, receiver and control numbers.
Control number — A unique, sequential number in each envelope used to track documents and spot duplicates or gaps.
Implementation guide — A trading partner’s rulebook for which documents, versions, segments and codes they require.
Mapping — Defining how fields in your ERP translate to and from EDI segments and elements.
Translator — Software that converts EDI files into data your ERP can use, and back again.
VAN (value-added network) — A secure, third-party mailbox service that routes EDI documents between trading partners.
AS2 — A secure internet protocol for sending EDI directly between partners, with encryption and signed receipts (MDNs).
SFTP — Secure file transfer, another common way to exchange EDI files directly.
ASN — Advance ship notice — the 856 or DESADV that tells a buyer what is on its way before it arrives.
GS1-128 / SSCC label — A standard barcode carton label whose unique serial shipping container code links each carton to the ASN.
Chargeback — A deduction a retailer takes for compliance misses, such as a late or inaccurate ASN.
Drop ship — The supplier ships directly to the retailer’s end customer, usually coordinated through EDI.
Functional acknowledgment — The 997 or CONTRL that confirms a file was received and could be read.
Need help with EDI?
From onboarding a new retail partner to fixing chargebacks and failed documents, our managed EDI service handles the full lifecycle so you can focus on running your business.
