EDI failures look like document problems and are usually item problems. The 850 that won't cross-reference, the invoice that short-pays, the ASN the DC can't receive — trace them back and you find an identifier that two systems disagreed about. Retail compliance is roughly half item-data discipline; the documents just carry the consequences.
The identifier family, untangled
GTIN (Global Trade Item Number) is the umbrella standard. What most people call a UPC is a GTIN-12 — the 12 digits under the UPC-A barcode on a consumer unit. Europe's EAN is GTIN-13. The one retail EDI cares about most is GTIN-14: fourteen digits identifying a packaging level — an indicator digit (1–8) plus your item number, so the each, the inner pack, the case, and the pallet each carry distinct GTINs in one family.
This hierarchy is load-bearing. The retailer orders cases, your barcode scans eaches, the ASN describes cartons: three packaging levels, three GTINs, one item. Systems that store "the UPC" as a single flat field — common in small-business ERPs — lose the hierarchy, and the loss surfaces as ordered-versus-shipped unit confusion on every document downstream.
Alongside the GTIN, every retailer keeps its own internal number — Walmart item numbers, Target DPCIs, grocery PLUs — and your system has its SKU. A single order line can reference three identifier schemes at once.
The cross-reference: your most important table
The item cross-reference maps all of those to each other: retailer item number ↔ GTIN(s) by pack level ↔ your SKU ↔ unit of measure. Every inbound document resolves through it; every outbound document is populated from it. Its failure modes are mundane and expensive:
- The new-item gap. Merchandising sets up an item with the retailer; nobody updates the table; the first PO arrives unmappable. The fix is process, not software: cross-reference updates belong in the item-launch checklist.
- Pack-level confusion. The retailer's number means a case of 24; your table maps it to an each. Quantities inflate 24× on paper. Always store the unit relationship, not just the number pair.
- Silent revisions. Retailers renumber, packs change, GTINs roll on formula changes (GS1 rules dictate when a change forces a new GTIN). Yesterday's table is a slow leak.
A good EDI platform treats an unmapped identifier as a same-day exception — a queue item a human resolves before the order proceeds — never as a document that limps into the ERP wrong.
GDSN and item authorization
Before most major retailers order anything, the item must exist in their system with attributes they trust: dimensions, weights, case configuration, images, regulatory data. Two channels feed that:
- GDSN — the Global Data Synchronisation Network. You publish item data through a certified data pool; subscribing retailers (grocery and mass channels especially) pull it. Attribute completeness rules are strict and retailer-specific.
- Retailer portals and the 832 price/sales catalog — some programs take item and price data as an EDI catalog document; distributors in particular run 832-driven catalogs.
Either way, the sequencing rule is absolute: item authorization precedes the first PO. EDI testing can be perfect and go-live still fails if the item file was an afterthought.
The discipline, in five habits
- License a GS1 prefix and assign GTINs by rule — new GTIN when GS1's change rules say so, never reused, hierarchy explicit.
- Model pack levels natively: each/inner/case/pallet with their GTIN-14s and quantity relationships.
- Put cross-reference updates in the item-launch and item-change workflows, with the EDI table as a required sign-off.
- Reconcile against the retailer's file on a cadence — their authorized-item list versus your table, diffed quarterly at minimum.
- Surface unmapped identifiers as exceptions, and treat each one as a process miss to root-cause, not a lookup to hand-patch forever.
Get this layer right and the documents largely take care of themselves — which is the quiet reason experienced EDI teams spend onboarding week on spreadsheets, not maps. EDISQ builds the cross-reference into the platform: unmapped items surface immediately, one shared table serves all 2,200+ trading partners, and it's all included in per-document pricing that starts free.
FAQ
What's the difference between a GTIN and a UPC?
The UPC-A barcode on a package encodes a 12-digit GTIN-12. GTIN is the umbrella: GTIN-12 (UPC), GTIN-13 (EAN), and GTIN-14 for case and pallet packaging levels. Retail EDI increasingly speaks GTIN-14 at the case level.
Why do EDI documents fail on item data?
Because documents pass syntax with wrong identifiers in them. An 850 with an item you can't cross-reference, or an invoice with a GTIN the retailer didn't authorize, fails business validation — often weeks later as a deduction.
What is GDSN?
The Global Data Synchronisation Network: certified data pools that publish your item attributes — dimensions, weights, packaging hierarchy — to subscribing retailers. Grocery and mass retailers commonly require it before item authorization.
Who assigns GTINs?
You do, under a GS1 company prefix you license from GS1. Never invent numbers or reuse a prefix from a barcode vendor — retail item validation checks prefix ownership.