Skip to content
What Is EDI? A Plain-English Guide for Suppliers
Spring Systems
EDI Basics
Back to Blog

What Is EDI? A Plain-English Guide for Suppliers

May 28, 2025 6 min read EDI Basics

You’ve just landed a retail account. The buyer is excited, the product specs are locked, and then the onboarding packet arrives with a line that stops everything: you must be "EDI compliant" before the first purchase order can be processed. No EDI, no PO. No PO, no shipment. No shipment, no revenue from that account.

Electronic Data Interchange — EDI — is the standardized, computer-to-computer exchange of business documents between trading partners. Instead of emailing a purchase order as a PDF or faxing an invoice, your system and the retailer’s system exchange structured data in a format both sides can parse automatically. No one re-types anything. No one opens an attachment.

Why Retailers Require It

The requirement isn’t bureaucracy for its own sake. A modern retailer’s distribution center runs on automated receiving — conveyor systems, scanners, and warehouse management software that expect every inbound shipment to arrive with a matching electronic manifest already in the system. When a truck pulls up and the DC can match each carton to a pre-loaded Advance Ship Notice (ASN) by scanning its barcode, product moves from dock to shelf in minutes. When that electronic data is missing or wrong, the shipment gets pulled off the automated line and processed manually — someone has to open cartons, count items, and reconcile discrepancies by hand. That labor cost gets charged back to you.

This is the core mechanic behind chargebacks: the retailer has to spend real money fixing a problem you caused, and their compliance program is designed to recover that money from your invoice. A single late or inaccurate ASN, a wrong barcode, or an invoice that doesn’t match the PO can trigger deductions that eat directly into your margin. The EDI requirement exists to prevent that scenario before the truck even arrives.

The Core EDI Transaction Sets

Retailers don’t just require "EDI" generically — they require specific document types at specific points in the order cycle. Here are the five you’ll encounter with virtually every retailer:

  • EDI 850 — Purchase Order: The retailer sends you this to initiate an order. It exists so the order arrives in your system as structured data you can process automatically, not as an email you have to read and re-enter.
  • EDI 855 — Purchase Order Acknowledgment: You send this back to confirm receipt and flag any changes (quantity reduced, item discontinued, ship date adjusted). It exists so the retailer knows immediately whether you can fulfill the order as written, rather than discovering at ship time that something was off.
  • EDI 856 — Advance Ship Notice (ASN): You send this when product ships, detailing exactly what’s in each carton and how cartons are packed. It exists so the retailer’s DC can scan cartons on arrival and match them to expected contents without opening anything — the backbone of automated receiving.
  • EDI 810 — Invoice: You bill the retailer electronically. It exists so payment processing is automated and the invoice matches the PO and ASN exactly — discrepancies are what trigger invoice deduction disputes.
  • EDI 997 — Functional Acknowledgment: A technical receipt sent automatically when any EDI document arrives. It exists so both sides have proof of transmission — if a document was sent but the 997 never came back, you know something failed before it becomes a chargeback.

How It Flows in Practice

When a buyer at Target places a purchase order, their system generates an EDI 850 and sends it through a Value-Added Network (VAN) or a direct AS2 (Applicability Statement 2) connection to your EDI system. Your system processes it, generates an 855 acknowledgment confirming you can fulfill it, and — when you ship — creates an 856 ASN and an 810 invoice. All of this happens without a phone call or an email. The data moves system-to-system, and both sides have a complete, timestamped audit trail.

Self-Service vs. Managed EDI: How to Choose

Once you understand what EDI is, the practical question is how to handle it. There are three common approaches, and the right one depends on your order volume, your in-house IT capacity, and how many retail accounts you’re managing.

Web Self-Service (PortalApp) — You log into a browser, view incoming purchase orders, create ASNs, print compliant carton labels, and send invoices. No software to install, no IT team required. This fits suppliers with one or two retail accounts and moderate order volume — maybe a handful of POs per week — where the cost of full automation isn’t justified yet.

Full-Service EDI Bureau — A managed provider handles every EDI document on your behalf. You focus on fulfillment; they handle translation, transmission, retailer connections, spec updates, and error monitoring. This is the right call when you’re adding retail accounts faster than you can build internal capability, when chargebacks are already eating time and money, or when you simply don’t want to hire a dedicated EDI analyst.

Integrated Service — Your ERP or warehouse management system (WMS) connects directly to the EDI network. POs arrive and create sales orders automatically; ship confirmations generate and send ASNs at the moment of packing. This is for suppliers with meaningful order volume across multiple retailers — the kind where manual processing, even in a web portal, becomes a bottleneck and a liability.

Most suppliers start in one place and move along that spectrum as they grow. The key is matching your EDI approach to where your business actually is today.

Your Next Step

If you’ve just been told you need EDI, here’s what to do before anything else: ask your buyer’s onboarding contact for the vendor compliance guide (sometimes called a routing guide or supplier handbook). That document lists every EDI transaction set, labeling requirement, and timing window the retailer enforces. Once you have it in hand, you’ll know exactly what you’re building toward — and you can have an informed conversation with an EDI provider about which service model fits your volume and your timeline for going live — or contact our team directly for guidance.

Need Help with EDI Compliance?

Our team has been helping suppliers navigate retailer requirements since 2002. Whether you're onboarding with a new retailer, fighting chargebacks, or looking to automate your EDI process — we can help.

Spring Systems

Spring Systems EDI Team

EDI & Retail Compliance Experts Since 2002

Have Questions About EDI?

Our team is available by phone and email to help with any compliance challenge.