How to Set Up EDI with Kroger (Step by Step)

Before you map a single segment for Kroger, get one question answered by your category team: which program are you shipping into? Warehouse replenishment trades the standard retail chain; direct-store-delivery trades the grocery document set; plenty of suppliers run both at once. Everything downstream of that answer — maps, testing, even invoice pairing — depends on it. With the answer in hand, a Kroger setup runs 1–3 days on the EDI side, in five stages.

Stage one: vendor setup and item groundwork

Kroger's side of the project covers your vendor number, program assignment, and item setup through its item management process. Your side is the cross-reference: Kroger item codes and UPCs travel together on every document, and the table must translate both directions. Grocery items add attributes retail items don't carry — case packs and catch weights ride the item data — so capture them now rather than during testing.

Stage two: connect the pipe and the ERP

EDISQ maintains the network connection to Kroger as part of the service; your work is attaching the business system. Orders should land in NetSuite, Cin7, QuickBooks, or whichever of the 30+ supported platforms runs your operation, arriving as ready-to-fulfill sales orders with items and ship-tos already resolved.

Stage three: load both map sets

Enabling Kroger loads two families of maps. The retail set handles the 850 inbound with 855, 856, and 810 outbound. The grocery set handles the 875 inbound and 880 outbound. The critical configuration is the pairing logic: the 880 invoice answers the 875 and the 810 answers the 850, and the platform should enforce that automatically so a DSD delivery can never be billed on the wrong document.

Stage four: rehearse grocery reality in the sandbox

Kroger testing earns its keep when it simulates the operating tempo, not just the syntax. Replay a burst of store-level 875s and confirm your system turns them around same-day without a human in the loop — at daily and intra-day order frequency, automation is the baseline, not a luxury. Generate a pallet-level ASN from a mock DC shipment and verify the hierarchy describes pallets as loaded, since that structure is what Kroger receiving reconciles against. Then run both invoice pairings end to end.

Stage five: go live with the timing monitors on

Two production monitors matter from the first order. Acknowledgment tracking on the 997 stream catches transmission failures while they are still retransmissions rather than late documents. And ASN timing against the delivery appointment guards the exact behavior Kroger's compliance deductions measure — the failure modes are cataloged in How to Avoid Kroger EDI Chargebacks, but the short version is: late and inaccurate ASNs are the whole game.

The first live week

Expect the opening days of production to be a tuning exercise rather than a fire drill. Watch how the order tempo actually lands — DSD flows in particular reveal their real frequency only in production — and review every exception the validators raise, because week-one exceptions are almost always cross-reference gaps you can close permanently in minutes. Keep your Kroger merchandising contact informed of go-live timing; a heads-up on both sides makes the first appointment-driven deliveries smoother. By the second week, the goal state is boring: orders in, documents out, dashboards green, nobody touching anything.

What it costs to operate

Kroger's order frequency is the argument for per-document pricing: the meter reads 25 free documents monthly, then from $0.50 per document sliding to $0.10 at the top tier, billed marginally so each threshold discounts only the documents above it. Grocery volume pushes you down the ladder instead of into a bigger subscription — the Production plan's $100/month minimum applies entirely to usage, and there are no mapping or setup charges. Full tiers at pricing.

FAQ