Retailer Routing Guides vs. EDI Mapping Guides: Why Suppliers Need Both
Ask most suppliers what “EDI compliant” means, and you’ll hear about transaction sets: the 850, the 856, the 810, maybe a 997. Map those correctly, pass a few tests, and you’re done — right?
Not quite. Every one of those documents sits inside a bigger set of rules that has nothing to do with X12 segments: the retailer’s Routing Guide. Master only one of these documents, and you’ll eventually get hit with chargebacks, rejected shipments, or both.
Two Guides, Two Different Jobs
The EDI Mapping Guide tells your systems how to structure the data — segments, qualifiers, valid values, how the retailer’s translator parses an 856 or 810.
The Routing Guide tells your operations team how to ship the product — carrier selection, appointment scheduling, transportation mode, freight terms, label placement, delivery windows, and the chargeback program tied to logistics failures.
These two documents can (and do) override each other in ways that aren’t obvious until you’re already being charged.
The Retailers Make This Explicit
buybuy BABY states it directly. Their EDI 856 ASN Mapping Guidelines make clear the current Vendor Routing Guide always supersedes the EDI Mapping Standards, and vendors must follow the Routing Guide first. A technically perfect ASN that ignores its carrier or ship-from rules is still out of compliance.
Kroger treats the ASN as part of a full operational program, not just a data feed. Vendor certification depends on correct container marking and on the ASN transmitting at least 90 minutes before the truck arrives — timing and labeling detail that lives in shipping requirements, not the X12 spec.
Lowe’s builds routing logic into its ASN rules directly. Whether a shipment needs a Detail ASN with GS1-128 pallet labeling or a Summary ASN depends on how it’s physically shipped — pallets, cartons, or a mix. Get the packaging decision wrong, and the “correct” EDI structure becomes the wrong one.
Macy’s may be the clearest case: its Vendor Standards list Vendor Standards, EDI Mapping Guides, and the Routing Guide as three separate documents, and specify that all transportation requirements — when to ship, how to route, carrier appointments — live in the Routing Guide, not the mapping guide. A perfectly mapped 856 sent under wrong routing instructions still fails.
Home Depot follows the same pattern common across big-box retail: a separate vendor compliance manual governs packaging, labeling, and routing, layered on top of the EDI specs used for orders, ASNs, and invoices.
Why This Trips Suppliers Up
EDI projects are usually run by IT or an EDI provider, focused on getting transactions to validate. That’s necessary, but only half the picture — the other half sits with logistics or compliance teams who own the Routing Guide, and the two groups don’t always talk during onboarding.
The result: a supplier who is technically “EDI compliant” — clean 850s, validating 856s, balanced 810s — still racks up chargebacks because the ASN’s structure doesn’t match the shipping method, a routing request was never obtained, or an appointment window was missed. None of these are mapping failures; they’re routing failures surfacing as EDI-adjacent deductions.
The Takeaway
- Read both documents before go-live — the Routing Guide typically takes precedence on shipping decisions.
- Get logistics and EDI/IT talking, since routing requirements often dictate ASN structure.
- Re-check both when they update — they’re maintained on separate schedules.
- Watch for chargebacks that look like EDI issues but aren’t — check the Routing Guide first.
The suppliers who avoid chargebacks aren’t the ones with the fanciest EDI systems — they’re the ones who treat compliance as two rulebooks working together.
To learn more about EDI and become a CEDIAP® (Certified EDI Academy Professional), please visit our course schedule page.