The sales team closes the account everyone wanted – a national retailer, a major distributor – and the onboarding packet arrives. Page one: congratulations. Page two: EDI compliance requirements, label specs, ship-window rules, and a chargeback schedule for getting any of it wrong. The deal that was supposed to grow revenue now has a tax on every mistake.
EDI is forty-year-old technology that still runs B2B trade because it works at volumes and formality levels that APIs have not displaced. This guide covers what EDI actually is, the documents that matter, where EDI belongs in your architecture, and how to scope a partner onboarding so the win stays a win.
What EDI is, and why partners still mandate it
EDI is a set of standardized document formats (ANSI X12 in North America, EDIFACT internationally) that let trading partners exchange orders, acknowledgments, ship notices, and invoices machine-to-machine, with no human re-keying. Retailers mandate it because their receiving operations run on it: the ASN tells the warehouse what is arriving before the truck does, and the barcode on the carton matches the document. When suppliers get it right, goods flow without anyone touching a keyboard. When suppliers get it wrong, the partner’s operation absorbs the cost – which is why they bill it back as chargebacks.
The documents that matter
| Document | What it is | Direction | Where it bites |
|---|---|---|---|
| 850 | Purchase order | Partner to you | Item / UOM mapping against your catalog |
| 855 | PO acknowledgment | You to partner | Acknowledging quantities you cannot actually ship |
| 856 | Advance Ship Notice (ASN) | You to partner | The chargeback machine: must describe the real cartons, on time |
| 810 | Invoice | You to partner | Mismatches against PO and receipt trigger payment delays |
| 997 | Functional acknowledgment | Both | Silence reads as failure; partners monitor these |
The 856 deserves special respect. It must be generated from what was physically packed – carton by carton, with the right labels – and arrive before the shipment does. ASNs generated from the order (instead of the actual pack-out) are the single most common source of compliance failures we see.
Where EDI fits in your architecture
The architecture question is the one most EDI vendor content skips: which of your systems speaks EDI? The answer should follow order ownership. If your ERP owns orders and fulfillment – the pattern we recommend in our ERP integration guide – then EDI documents translate at the edge and flow through the ERP like any other order source. Your ecommerce-to-ERP integration carries webstore orders; the EDI translator carries partner orders; fulfillment treats them identically downstream.
The mistake we keep rescuing: wiring EDI into the ecommerce platform because that is where the integration budget lived. Storefronts do not know about cartons, pallets, or pack-outs, so the 856 ends up fabricated from order data, and the chargebacks start. If a 3PL or WMS does your fulfillment, the ASN must come from their pack-out data – which makes EDI an integration architecture problem first and a document-format problem second.
Transport and tooling: VAN, AS2, managed, or custom
- VAN. A third-party network moves documents for a per-document fee. Fast to start, costs scale with volume.
- AS2. Direct encrypted connection to the partner. No per-document fee, more setup and certificate management. Walmart-style partners often mandate it.
- Managed EDI service. A provider (SPS Commerce, TrueCommerce, Cleo and peers) handles translation, partner specs, and monitoring. The right answer for most mid-market sellers – with the caveat that the integration INTO your ERP and fulfillment is still your project, and it is the part that determines whether ASNs are real.
- Custom translation. Worth it at high document volume or when your stack is unusual. Total control, total ownership.
Scoping a partner onboarding so the win stays a win
- 1. Read the compliance manual before quoting the timeline. Label specs, ship windows, ASN timing, and the chargeback schedule define the project.
- 2. Map the document set to your systems. Who produces the 855? Where does pack-out data for the 856 come from? Which system invoices?
- 3. Decide UOM and item mapping once. Their item numbers, your SKUs, GTINs, and pack hierarchies (each / inner / case / pallet) – the mapping table is the project’s real deliverable.
- 4. Test with their certification process, then load-test your side. Partners certify the formats; only you can verify your fulfillment actually produces accurate ASNs at volume.
- 5. Monitor 997s and chargebacks from day one. Both are feedback loops; silence in either direction means something is already wrong.
For manufacturers and distributors, EDI is usually the third leg of the same stool as the webstore and the ERP – one architecture, three order sources, identical fulfillment. Built that way, the next partner mandate is configuration, not a project.
EDI for distributors: where it meets your ERP
For wholesale distributors the EDI conversation is really an ERP conversation. Distribution ERPs like Epicor P21, NetSuite, and Microsoft Dynamics carry the objects your trading partners transact against – items, UOM definitions, contract pricing, branch inventory – so the EDI layer should read from and write to the ERP, with the storefront as a peer channel rather than the hub. The same queue-and-reconciliation discipline we apply to ERP integration for B2B platforms applies verbatim to EDI: per-document failure isolation, idempotent processing (partners re-send), and acknowledgment tracking, because an unacknowledged 850 is a chargeback with a delay on it.
EDI also rarely travels alone. The same large accounts that mandate EDI for replenishment often buy through procurement systems for spot purchases – which is a different protocol with the same architecture, covered in our guide to PunchOut catalogs. Build the document-translation and queue layer once and both ride on it.
Frequently asked questions
EDI (Electronic Data Interchange) is the standardized document format large retailers, distributors, and trading partners use to exchange business documents – purchase orders, invoices, ship notices – machine-to-machine. When a big-box retailer or major distributor becomes your customer, EDI compliance is usually a condition of doing business, not a suggestion.
The core order cycle: the 850 is the purchase order your partner sends you; the 855 is your acknowledgment accepting (or adjusting) it; the 856 is the Advance Ship Notice (ASN) describing exactly what is in each carton and shipment; the 810 is your invoice. Most chargebacks trace back to the 856 being late, wrong, or mismatched with the physical shipment.
EDI documents should flow through whichever system owns orders and fulfillment – usually the ERP, with the ecommerce platform untouched. The common architecture mistake is wiring EDI directly into the storefront, which was never designed to generate ASNs or track carton-level packing.
Two transport options. A VAN (Value-Added Network) is a third-party mailbox network that moves documents between partners for a per-document fee. AS2 is a direct, encrypted point-to-point connection – no per-document cost, more setup. Large partners often mandate one or the other; many suppliers run both.
Late or inaccurate 856 ASNs, label spec violations, and shipping-window misses are the big three. Avoidance is architectural: the ASN must be generated from what was actually packed (WMS or 3PL data), not from what was ordered, and the compliance specs need to live in your testing checklist before the first live order.
Got an EDI mandate with a deadline attached? Talk to us – we will map the documents to your systems and scope the onboarding honestly, chargeback schedule included.