EDI, Routing Guides, and Chargebacks: The Compliance Stack Behind Every PO

Big-box compliance · Read time about ten minutes

Retail compliance is usually described as a checklist. It's more accurate to describe it as a metering system: a set of automated checkpoints that measure your operational precision and bill you for the variance.

That distinction matters because checklists get completed once. Metering systems run continuously — on every carton, every ASN, every appointment window, for the life of the account.

Here's the stack, layer by layer, and what each layer costs when it fails.

Layer 1: EDI — The Transaction Backbone

Electronic Data Interchange is how retailers and suppliers exchange commercial documents without human handling. The core set for most mass retailers:

• 850 — Purchase Order (retailer to you)
• 855 — PO Acknowledgment (you to retailer)
• 856 — Advance Ship Notice, the ASN (you to retailer)
• 810 — Invoice (you to retailer)
• 997 — Functional Acknowledgment (both directions)

Walmart requires EDI capability with no manual alternative for ongoing business. Target requires the same core documents over AS2 or an approved VAN. Costco requires four X12 documents: 850, 810, 856, and 997.

What it costs to get wrong: the failure mode isn't usually a rejected document — it's a delayed one. Late 855s and 856s cascade into receiving problems, which become chargebacks attributed to fulfillment rather than integration.

The timeline reality: setup with a legacy provider typically runs 7–14 weeks from signed contract to go-live. A provider with prebuilt mappings for your specific retailer can compress that dramatically — Costco integrations in particular can complete in as little as one to nine business days with the right prebuilt path. That spread, days versus months, is almost entirely a vendor selection decision made before you have a PO.

Provider selection: the practical evaluation criteria are prebuilt mappings for your target retailers, integration with your actual ERP or 3PL system, whether they support AS2 directly or route through a VAN, per-document versus subscription pricing at your volume, and how they handle retailer spec changes. Legacy full-service providers and newer API-first platforms both have valid use cases; the wrong choice is the one selected on price alone after the PO lands.

Layer 2: GS1 Labeling — The Physical Identity Layer

Every case shipped to a major retailer carries a GS1-128 label with an SSCC-18 serial shipping container code that uniquely identifies that carton. The label also encodes PO number, item identifiers, quantities, and destination in defined zones.

Retailers use these for automated receiving: the scan cross-references the physical carton against the ASN. If the label and the ASN disagree, the system flags a discrepancy without a human ever looking at it.

Requirements are specific — print quality, size, position, white space — and all barcodes must scan reliably. Labels must match item setup exactly, including description, quantity, and UPC.

What it costs to get wrong: roughly $25–200 per labeling violation. Individually small. Multiplied across a truckload, structural.

Layer 3: ASN Accuracy — The Reconciliation Layer

The Advance Ship Notice tells the retailer what's arriving, in what cartons, on what pallets, before it arrives. It's the document that lets automated receiving work at all.

What it costs to get wrong: approximately $50–500 per ASN error incident. This is the single highest-frequency chargeback category for new suppliers, because ASN accuracy depends on warehouse execution matching system data perfectly — and most DTC-native fulfillment operations have never had to hold that standard.

Layer 4: Routing Guide — The Logistics Rulebook

The routing guide governs how product physically moves: approved carriers, appointment windows, pallet configuration (typically GMA standard 48x40, stacked to spec), carton-level labeling, bill-of-lading formatting, carrier selection rules for prepaid shipments, and delivery appointment procedures.

Routing guides change. A supplier operating from a version six months out of date is generating chargebacks against rules they don't know exist.

What it costs to get wrong: varies by violation type, but routing non-compliance also causes appointment rejection — which converts a logistics error into an OTIF failure, which is the expensive layer.

Layer 5: OTIF — The Aggregate Scorecard

On-time, in-full. Walmart's standard is 98%, and penalties run roughly 3% of PO value for failures. For a brand shipping $50,000 per week, a 10% OTIF miss runs about $1,500 weekly — roughly $78,000 annually on business already won.

OTIF is the aggregate output of every layer beneath it. You don't fix OTIF directly; you fix the EDI timing, labeling accuracy, ASN precision, and routing adherence that produce it.

What Changed in 2026

The meaningful shift is enforcement automation. Retailers have moved from human-reviewed disputes to system-triggered enforcement, with rule-based engines and AI-driven platforms flagging non-compliance directly — Walmart's SQEP program and Amazon's 1P vendor model both now operate with algorithmic precision.

Two consequences follow. First, errors are caught at essentially 100% detection rather than sampled. Second, disputing requires documentation formatted for a system rather than a persuasive email to a person. Suppliers who built their compliance response around relationships are finding the relationship is no longer in the loop.

The Practical Sequence

1. Select an EDI provider before you need one. Evaluate on retailer-specific prebuilt mappings, ERP/3PL integration, and change management — not on monthly cost.
2. Get GS1 company prefix and GTIN assignment right at the item level. Errors here propagate into every downstream document.
3. Test labeling against the actual retailer spec, including scan verification, before first shipment.
4. Assign routing guide ownership to a named person, with a recurring review for spec updates.
5. Instrument OTIF internally so you're measuring against retailer definitions before the retailer does.
6. Build a deduction dispute workflow with document retention, formatted for automated submission.

The Bottom Line

Compliance infrastructure is not overhead — it's a margin variable. Two brands with identical products, identical wholesale prices, and identical velocity can run five to ten points apart in net contribution purely on chargeback rate. That gap is invisible in the pitch and permanent in the P&L.

The brands that clear onboarding in days rather than months made these decisions before they had a purchase order forcing them.