EDI basics · October 23, 2026

What Is EDI? The Plain-English Guide

EDI explained without jargon: what X12 documents are, how the 850-to-810 chain works, what AS2 and VANs do, and how modern self-serve EDI works.

EDI — Electronic Data Interchange — is how companies trade business documents machine-to-machine. When Walmart orders from a supplier, no human sends an email. Walmart's system emits a purchase order in a standardized format, it travels over a secured connection, and it lands in the supplier's system as structured data. The response documents travel back the same way. That's the whole idea. Everything else is detail — but the detail is where compliance lives.

The standard: X12

In North America, the dominant EDI standard is ANSI X12. It defines a document type for nearly every business event — a purchase order is an 850, a ship notice is an 856, an invoice is an 810 — and specifies exactly how each is structured: segments, elements, qualifiers, in a defined order.

An X12 file looks hostile to human eyes — ISA*00*...~GS*PO*...~ST*850*0001~ — but the structure is rigorously logical. Documents travel inside envelopes: the ISA/IEA interchange envelope identifies sender and receiver, the GS/GE group envelope batches documents of one type, and each ST/SE transaction set is one business document. Trading partners commonly run version 4010 or 5010 of the standard; both are decades old and both are everywhere.

The catch: the standard defines what's possible, and each trading partner defines what's required. Every retailer publishes a companion guide saying which segments it uses, which reference numbers must round-trip, and what gets rejected. Two partners can both be "standard X12 5010" and still need completely different maps.

The core document chain

Retail EDI runs on a four-document loop, with a fifth riding along:

  • 850 Purchase Order in — the order: items, quantities, prices, ship-to locations, dates.
  • 855 Acknowledgment out — your confirmation of what you can actually ship.
  • 856 Advance Ship Notice out — the carton-level mirror of the physical shipment, transmitted before the freight arrives. This is the document retailers enforce hardest.
  • 810 Invoice out — your bill, which the buyer's system matches against the PO and ASN automatically.
  • 997 Functional Acknowledgment — the receipt for every document, both directions, automatic. Not agreement, just "received and readable."

Around that core, industries add their own documents: the 846 inventory feed that drives dropship programs, the 852 sales data retailers share back, grocery's 875/880 pair, the 940/945 warehouse loop for 3PLs. There are hundreds of X12 document types; most suppliers use fewer than ten.

How documents actually travel

Three transport methods cover nearly all of it:

  • AS2 — encrypted, signed document exchange over HTTPS, with cryptographic delivery receipts. Walmart made it the retail default; most large retailers trade AS2 direct. See our AS2 explainer for how it works.
  • SFTP — plain file drop over a secure connection. Simple, common, effective.
  • VANs — Value-Added Networks, the postal service of legacy EDI. Your documents go to the network; the network routes them to the partner's mailbox. Some partners still require one.

Which one you use is the partner's call, not yours — which is why a provider that operates all three matters. EDISQ runs AS2, SFTP, and VAN connectivity as part of the service, so the transport question disappears into configuration.

What "doing EDI" used to mean — and what it means now

The traditional path: buy translation software or a managed service, pay a subscription plus per-partner fees, commission mapping projects for each document type, wait weeks for onboarding, and hope the quote survives contact with reality. That model priced small suppliers out of retail for decades.

The modern self-serve model works like any other SaaS: sign up, pick your trading partner from a directory, use certified maps that already exist, test in a sandbox, go live. EDISQ's partner directory covers 2,200+ retailers, distributors, and carriers with the document specs preloaded, 997s handled automatically both directions, and CSV import/export live from day one — ERP connectors activate on request.

What it costs

Pricing is the clearest difference between EDI generations. EDISQ publishes its model openly: the first 25 documents each month are free on the self-serve plan with no monthly fee, then per-document pricing from $0.50, tapering to $0.10 at volume. Going live on the Production plan is a $100/month minimum that applies as usage credit and includes your first live trading partner, with $50/month per additional live partner. The full ladder is on the pricing page — no quote required, which is rather the point.

If a retailer just handed you an EDI requirements packet, start with the product overview and the partner's page in the directory. The acronyms are survivable; most suppliers are live within days, not months.

FAQ

What does EDI stand for?

Electronic Data Interchange — the exchange of standardized business documents between companies' systems. A purchase order leaves the retailer's system and lands in yours as structured data, with no email, PDF, or re-keying in between.

Is EDI still used in 2026?

Heavily. Nearly every major retailer, distributor, and carrier in North America requires it from suppliers. APIs exist alongside it, but the X12 document chain remains the backbone of retail and logistics commerce.

Do I need special software to do EDI?

You need something that translates X12 into data your systems understand and back, plus a connection (AS2, SFTP, or VAN) to each partner. Modern EDI SaaS bundles both — you don't buy a translator, maps, and a network separately.

How much does EDI cost to start?

With EDISQ, nothing: signup is self-serve and the first 25 documents each month are free, with per-document pricing from $0.50 after that. Traditional setups involve subscriptions, per-partner fees, and mapping projects.