1. What Does EDI Stand For?
EDI stands for Electronic Data Interchange. The name describes exactly what it does: it is a standardized method for exchanging business data electronically between two organizations — typically a supplier and a retailer.
Before EDI, companies exchanged purchase orders, invoices, and shipping documents by mail, fax, or phone. EDI replaced all of that with a secure, automated, machine-readable format that both parties' systems can process instantly — no human re-entry required.
The EDI standards most commonly used in North American retail are defined by ANSI X12, a committee that maintains the document formats used across industries. In Europe and globally, the EDIFACT standard is more common. Both accomplish the same goal: a universal language that allows different companies' systems to communicate without custom programming.
2. How EDI Works: The Order Lifecycle
Understanding EDI is easiest when you follow a typical order from start to finish.
- The retailer sends a Purchase Order (EDI 850) — The process begins when a retailer's buyer creates a purchase order in their system. That order is automatically formatted as an EDI 850 document and transmitted to the supplier. In the grocery category, this document is called an EDI 875.
- The supplier acknowledges the order (EDI 855) — The supplier reviews the order and sends back a Purchase Order Acknowledgment (EDI 855) confirming they can fulfill it — in full, partially, or with changes.
- The supplier ships and sends an Advance Ship Notice (EDI 856) — Before the shipment leaves the warehouse, the supplier sends an Advance Ship Notice (EDI 856). This is one of the most compliance-sensitive documents in the process — retailers depend on it to plan receiving. A late or inaccurate ASN is one of the most common causes of retailer chargebacks.
- The supplier invoices (EDI 810) — After shipment, the supplier sends a digital invoice using the EDI 810 document. This is processed automatically by the retailer's accounts payable system.
- The retailer acknowledges receipt (EDI 997) — The retailer sends a Functional Acknowledgment (EDI 997) to confirm they received the EDI transaction. This is a system-level confirmation, not a confirmation of the shipment itself.
This five-step loop repeats with every order. Depending on the retailer, additional documents may be required — routing requests (EDI 753/754), payment remittances (EDI 820), inventory updates (EDI 846), and more.
3. EDI Document Types: The Most Common Transactions
There are hundreds of EDI document types, but most suppliers will work with a core set. Here are the ones you are most likely to encounter:
| EDI Document | Name | When It Is Used |
|---|---|---|
| EDI 850 | Purchase Order | Retailer places an order with a supplier |
| EDI 855 | Purchase Order Acknowledgment | Supplier confirms they received and can fill the order |
| EDI 856 | Advance Ship Notice (ASN) | Supplier notifies retailer a shipment is on its way |
| EDI 810 | Invoice | Supplier bills the retailer for goods shipped |
| EDI 997 | Functional Acknowledgment | System-level receipt confirmation |
| EDI 846 | Inventory Inquiry/Advice | Supplier shares inventory levels with retailer |
| EDI 820 | Payment Order / Remittance | Retailer sends payment details to supplier |
| EDI 852 | Product Activity Data | Retailer shares point-of-sale and sell-through data |
| EDI 860 | Purchase Order Change | Retailer modifies an existing purchase order |
| EDI 875 | Grocery Purchase Order | Grocery-specific version of the EDI 850 |
4. EDI vs. API vs. Manual Processing: A Comparison
Companies sometimes ask whether they need EDI, an API, or whether manual order management is sufficient. Here is a straightforward comparison:
| EDI | API | Manual Processing | |
|---|---|---|---|
| Best for | Retailer compliance, high-volume orders | Real-time integrations, ecommerce | Very low-volume, one-off transactions |
| Speed | Near real-time to batch | Real-time | Hours to days |
| Accuracy | High — automated, standardized | High — automated | Low — human error risk |
| Required by retailers? | Yes — most major retailers mandate EDI | Sometimes, as a supplement | Rarely accepted at scale |
| Scales with volume? | Yes | Yes | No |
| Chargeback risk | Low when managed correctly | Low | High |
The short answer: If a major retailer requires EDI, there is no substitute. EDI and API integrations are increasingly used together — EDI for retailer compliance documents, APIs to connect your internal systems (ERP, WMS, accounting) to your EDI platform.
5. EDI Transmission Types: How Documents Are Sent
Not all EDI connections work the same way. The transmission type refers to the technical method used to send EDI documents between trading partners. The four most common are:
AS2 (Applicability Statement 2)
The most widely used transmission protocol for retail EDI. AS2 is a direct, encrypted, point-to-point connection between your system and your trading partner's system. It confirms delivery with a Message Disposition Notification (MDN). Most major retailers — including Walmart, Target, and Amazon — prefer or require AS2.
VAN (Value-Added Network)
A VAN is a third-party network that acts as a mailbox system. You send your EDI documents to the VAN, and the VAN routes them to your trading partner. VANs are older technology but still widely used, particularly for smaller retailers and distributors. Most EDI providers can connect via VAN on your behalf.
FTP / SFTP (File Transfer Protocol)
Some trading partners use FTP or its secure version, SFTP, to exchange EDI files. Documents are placed in a designated folder and retrieved by the trading partner on a scheduled basis. Less common for large retailers but still used in specific industries and supply chains.
API-Based EDI
A newer approach where EDI data is exchanged via RESTful APIs rather than traditional flat-file formats. Some modern retailers and platforms are moving in this direction, but traditional ANSI X12 EDI remains the dominant standard in North American retail.
6. The Real Cost of EDI: Benefits and Drawbacks
The Benefits of EDI
- Eliminates manual data entry. Every purchase order that arrives electronically is automatically formatted and ready to process — no one has to type it in. At high order volumes, this alone saves dozens of hours per week.
- Reduces costly errors. When data is re-keyed manually, errors happen. Wrong quantities, wrong addresses, mismatched item numbers — each one creates friction with retail partners and risks a compliance fine. EDI eliminates that layer of human error.
- Speeds up the order cycle. Orders that arrive at 11pm are processed before your team comes in the next morning. ASNs go out automatically when shipments are scanned. Invoices transmit without waiting for someone to prepare them.
- Improves retailer scorecards. Major retailers grade their suppliers on compliance — on-time ASNs, accurate invoices, correct label formats. Strong EDI execution directly improves your scorecard, which affects shelf placement, reorder frequency, and your relationship with the buyer.
- Scales with your business. Whether you are shipping 10 orders a week or 10,000, EDI handles the volume without additional headcount.
The Drawbacks of Poorly Managed EDI
- Chargebacks accumulate quickly. When EDI documents are late, incorrect, or missing, retailers issue compliance fines. These can range from a small flat fee to a percentage of the invoice value. Suppliers who manage EDI manually or with a weak provider often face chargeback totals that erode their margins significantly.
- Each retailer has different requirements. Walmart's EDI spec is not the same as Target's. What works for one trading partner may not work for another. Managing these differences in-house requires ongoing technical attention.
- In-house EDI is expensive. Building and maintaining your own EDI infrastructure — servers, software licenses, staff to manage mapping and compliance updates — is a significant investment that rarely makes sense for suppliers below enterprise scale.
This is exactly why most suppliers choose a managed EDI service provider rather than building in-house. A managed provider handles all mapping, compliance updates, and technical maintenance — you process orders in a clean interface without worrying about what is happening in the background.
7. Choosing an EDI Solution: In-House vs. Managed Service
| In-House EDI | Managed EDI Service (eZCom) | |
|---|---|---|
| Who manages mapping | Your IT team | The provider's team |
| Who handles compliance updates | Your IT team | The provider's team |
| Upfront cost | High | Low to moderate |
| Ongoing technical burden | High | Low |
| Best for | Large enterprises with IT resources | Brands and suppliers of any size |
| Scalability | Requires investment to scale | Scales automatically |
| Support when things break | Internal team | Dedicated provider support |
8. EDI Compliance and Chargebacks: What You Need to Know
Every retailer publishes an EDI compliance guide — a document that specifies exactly which EDI transactions are required, in what format, and by when. Deviating from these requirements triggers chargebacks.
The most common compliance failures that lead to chargebacks:
- Late or missing ASN (EDI 856) — The advance ship notice must arrive before the shipment, typically within a tight window after the order ships. Missing this deadline is the single most common chargeback trigger.
- Incorrect label format — GS1-128 shipping labels must be formatted exactly to the retailer's specification. Wrong barcode, wrong placement, or wrong data structure all generate fines.
- Inaccurate invoice (EDI 810) — Quantity, pricing, or item number mismatches between the PO and the invoice create disputes and payment delays.
- Wrong packing configuration — Some retailers require specific pack quantities, inner pack ratios, or carton configurations. Deviating generates chargebacks even if the product itself is correct.
A good EDI provider monitors compliance requirements across all your trading partners and flags potential issues before they become fines.
9. EDI Glossary: Key Terms You Will Encounter
- ANSI X12
- The committee that defines and maintains EDI document standards used in North American retail and supply chains. Most EDI transaction sets (850, 856, 810, etc.) are ANSI X12 formats.
- ASN (Advance Ship Notice)
- The EDI 856 document. Sent by the supplier to the retailer before a shipment arrives. Contains carton, item, and shipping details. One of the most compliance-critical documents in retail EDI.
- Chargeback
- A financial penalty issued by a retailer when a supplier fails to meet EDI or compliance requirements. Can range from a flat fee to a percentage of the invoice value.
- EDIFACT
- The EDI standard most commonly used outside North America, particularly in Europe and Asia. Functionally similar to ANSI X12 but uses different document formats.
- GS1-128
- A barcode standard used on shipping cartons and pallets. Required by most major retailers as part of EDI compliance. Contains shipment information encoded in a scannable format.
- ISA/GS Header
- The envelope structure that wraps every EDI transmission. Contains sender and receiver identification, date, time, and interchange control numbers.
- Mapping
- The process of translating data from your internal system (ERP, WMS, order management) into the correct EDI format for each trading partner. Different retailers require different mappings for the same document type.
- Trading Partner
- Any company you exchange EDI documents with. In retail, your primary trading partners are the retailers you sell to.
- Transaction Set
- A single EDI document type (e.g., the EDI 850 is a transaction set). Each transaction set has a defined structure specified by the relevant standard.
- VAN (Value-Added Network)
- A third-party network that routes EDI documents between trading partners, acting as a digital mailbox.
- X12
- Shorthand for the ANSI X12 EDI standard. When someone says "X12 EDI," they mean the standard used in North American commerce.
10. Who Uses EDI?
EDI is used across virtually every industry that involves supply chains, but it is most deeply embedded in:
- Consumer goods and retail — The dominant use case in North America. Every major retailer requires EDI from their suppliers.
- Grocery and food distribution — EDI is essential for managing the speed and compliance requirements of perishable supply chains.
- Healthcare — EDI is used for insurance claims, remittances, and eligibility verification (under the HIPAA transaction sets).
- Automotive — Manufacturers and suppliers use EDI for production scheduling, shipping, and invoicing.
- 3PL and logistics — Warehouses and logistics providers use EDI to exchange shipment instructions, receipts, and inventory data with their clients.
11. EDI and Your ERP or Accounting System
EDI does not replace your ERP, accounting software, or inventory management system — it connects them. When your EDI platform integrates with your internal systems, purchase orders flow in automatically and are converted into sales orders. Advance ship notices and invoices are generated and transmitted without manual steps.
eZCom's Lingo integrates with leading ERP and accounting platforms including NetSuite, Acumatica, QuickBooks, Microsoft Dynamics, SAP, and many others.
12. Why the EDI Provider You Choose Matters
Not all EDI providers work the same way. The technical function — transmitting documents between trading partners — is table stakes. What separates providers is everything around that function:
- Mapping and setup. When you add a new retailer, someone has to build the mapping from your system's data to that retailer's specific EDI requirements. With a managed provider like eZCom, their team handles this. With a self-service platform, your team does.
- Support when something breaks. EDI issues do not wait for business hours. A missed ASN at 11pm can generate a chargeback by morning. The quality and responsiveness of your provider's support team directly affects your compliance scores.
- Staying current with retailer requirements. Retailer compliance guides change. Format updates, new document requirements, changed label specifications — a managed provider monitors these and updates your mapping before they affect your orders.
- Ease of use. Your operations team should be able to see every order, every document, and every status at a glance — without needing to understand the underlying EDI technology.
13. Frequently Asked Questions About EDI
What does EDI stand for?
EDI stands for Electronic Data Interchange. It is the standardized, computer-to-computer exchange of business documents — purchase orders, invoices, shipping notices, and more — between trading partners.
Do I need EDI to sell to major retailers?
Yes. Virtually every major retailer in North America — including Walmart, Target, Amazon, Costco, Home Depot, and hundreds of others — requires their suppliers to use EDI. If a retailer has asked you to "get set up on EDI," it is a requirement, not a suggestion.
What is the difference between EDI and an API?
EDI uses standardized document formats (ANSI X12 or EDIFACT) to exchange business transactions between companies. APIs are more flexible, real-time connections between software systems. In retail, EDI is typically required for retailer compliance documents, while APIs are often used to connect your EDI platform to your internal systems.
What is an EDI 850?
The EDI 850 is the Purchase Order transaction set. It is the document a retailer sends to a supplier to place an order. It contains item numbers, quantities, prices, delivery dates, and ship-to locations. The grocery equivalent is the EDI 875.
What is an EDI 856?
The EDI 856 is the Advance Ship Notice (ASN). It is sent by the supplier to the retailer before a shipment arrives and contains carton-level detail about what is in the shipment. A late or inaccurate ASN is the most common cause of retailer chargebacks.
What causes EDI chargebacks?
The most common causes are: a late or missing Advance Ship Notice (EDI 856), incorrect or missing GS1-128 shipping labels, invoice discrepancies (EDI 810), and incorrect pack configurations. A good EDI provider helps you avoid these by automating document transmission and monitoring compliance requirements.
Can a small business use EDI?
Yes. Cloud-based managed EDI services have made EDI accessible to businesses of any size. You do not need IT staff or servers — your provider handles all the technical infrastructure. You process orders through a web-based interface.
What is the difference between EDI software and managed EDI?
Standard EDI software gives you the tools to manage EDI yourself — your team handles mapping, compliance updates, and troubleshooting. Managed EDI means your provider handles all of that for you. eZCom's Lingo is a managed EDI platform.
How long does it take to get set up on EDI with a new retailer?
With an experienced managed EDI provider, the setup process for a new trading partner typically takes days to a few weeks — not months. The timeline depends on the retailer's testing requirements and the complexity of their EDI specification.
What EDI standard is used in the US?
The dominant EDI standard in North American retail is ANSI X12. In Europe and internationally, EDIFACT is more common. Both define structured document formats for exchanging business transactions electronically.
14. Ready to Simplify Your EDI?
EDI does not have to be complicated. With the right managed provider, your team processes orders in an intuitive interface while your provider handles everything technical in the background — mapping, compliance, trading partner communication, and support.
Let's talk EDI, online order processing, and system integrations.
Schedule a Discovery Call