Kroger EDI Requirements: How to Become Compliant

Kroger is the biggest pure grocer in the US, and its EDI program reflects grocery's split personality: warehouse programs that look like classic retail EDI, and direct-store-delivery programs that run on the grocery-specific document set. Compliant suppliers speak both dialects. Here's the map for Kroger.

Two programs, two document sets

Warehouse (DC) programs trade the standard chain: 850 purchase order in, 855 acknowledgment, 856 ASN, and 810 invoice out, with 997s both directions.

DSD programs — where your trucks deliver to stores — run on the grocery documents: the 875 Grocery Products Purchase Order in and the 880 Grocery Products Invoice out. The 875 was built for grocery's rhythm: orders cut daily, sometimes intra-day, per store, with delivery expected on your next route.

The pairing rule trips up new suppliers constantly: the 880 pairs with the 875, and the 810 pairs with the 850. Cross the streams — invoicing a DSD delivery on an 810 — and the invoice bounces. Which document set you trade is decided per program by your Kroger category team, and many suppliers run both simultaneously. EDISQ loads both map sets when you enable Kroger, so the right document answers the right order automatically.

The rules that carry deductions

Kroger's compliance deductions center on the ASN and on item data:

1. ASN before appointment. For DC deliveries, the 856 must post before the scheduled appointment time. Kroger's receiving operation plans against it; late or missing ASNs draw deductions.
2. Pallet-level hierarchy. Kroger prefers pallet-level HL structures on DC freight — shipment → order → tare (pallet) → item — mirroring how grocery DCs actually receive.
3. Item cross-referencing, both ways. Kroger item codes and UPCs both appear on orders; your map must translate in both directions, on every document. Most rejected documents trace to items, not syntax.
4. DSD cadence. At store-level order frequency, manual processing physically can't keep up. Same-day turnaround on 875s is the operating assumption — automation is mandatory at volume, not an upgrade.

Connectivity and setup

Kroger trades X12 4010 over AS2 direct — EDISQ maintains the connection and certificates as part of the service. The setup path:

1. Vendor setup with Kroger — vendor number, item setup through Kroger's item management process, program assignment (warehouse, DSD, or both).
2. Connect your system — NetSuite, Cin7, QuickBooks, or whatever runs your operation; grocery attributes like case packs and catch weights ride the item cross-reference.
3. Sandbox the flows — replay Kroger 875 and 850 scenarios, generate the ASNs and invoices, validate end to end.
4. Go live with the ack trail watching — 997 tracking plus ASN timing tied to your ship confirmations.

The EDI side typically takes one to three days. And if your grocery footprint extends past Kroger — Publix, Meijer, Albertsons — the same 875/880 machinery covers them; each partner's page in the directory lists its program specifics.

Cost follows the per-document ladder: first 25 documents monthly free, then from $0.50 each, decreasing with volume. High-frequency DSD volume is exactly what the ladder was built for — the more 875s that flow, the less each one costs.

FAQ