Kroger EDI Requirements: A Supplier’s Guide

Kroger runs one of the largest grocery supply chains in the country, and its vendor requirements reflect that scale: high transaction volume, tight delivery windows tied to perishable and center-store replenishment, and a compliance program that treats data accuracy as inseparable from on-shelf availability. For CPG and food suppliers, Kroger is frequently the largest single account on the books, and the largest source of chargeback exposure if EDI isn’t running cleanly.

Kroger’s Core Document Requirements

• 850 (Purchase Order) inbound orders across Kroger’s divisional structure; the same item can order differently depending on which division and distribution center is issuing the PO
• 855 (PO Acknowledgment) confirmation with accurate quantities and delivery dates
• 856 (Advance Ship Notice) carton and pallet-level detail matching GS1-128 labels, critical for cross-docked and perishable freight moving on tight windows
• 810 (Invoice) matched against PO and receipt; mismatches surface as deductions
• 820 (Remittance Advice) outbound from Kroger, the record of what was actually paid against what was invoiced
• 852 (Product Activity Data) common in Kroger’s replenishment programs, sharing point-of-sale and inventory data back to the supplier to support forecast-driven ordering

What Sets Kroger Apart

Divisional complexity. Kroger operates through regional divisions (each with its own distribution centers and, historically, some banner-specific requirements), which means item setup, pricing, and even document routing can vary by division for the same national account relationship. A mapping built against one division’s pattern doesn’t automatically work for another.

Perishable and DSD timing pressure. For fresh and direct-store-delivery categories, ASN and routing accuracy has a much tighter tolerance than dry grocery. A late or inaccurate ASN on a perishable load doesn’t just cost a deduction, it risks the delivery window entirely.

852-driven replenishment. Suppliers in Kroger’s collaborative replenishment programs receive product activity and inventory data specifically to drive forecast accuracy. Ignoring or mishandling that data undercuts the whole point of the program and shows up as poor fill rates.

Where Kroger Suppliers Trip Up

Treating Kroger as one account. Divisional variation means what worked for the first DC doesn’t automatically work for the fifth. Each new division relationship deserves its own verification pass, not an assumption of uniformity.

ASN timing on perishable lanes. Suppliers who batch ASN generation at end-of-day routinely miss the window perishable and DSD categories actually need.

Ignoring 852 data. Suppliers who receive product activity data but don’t act on it are paying for a replenishment program without getting its benefit, and often see it reflected in fill-rate scorecards.

How We Run Kroger EDI

Foundational supports clients actively trading with Kroger today. We account for divisional variation at setup rather than assuming a single national template, keep ASN timing aligned with the realities of perishable and DSD freight, and build the 852 replenishment data into the operational flow rather than treating it as a document to archive. Ongoing monitoring and spec-change management run under our managed EDI service.

Key Takeaways

• Kroger’s divisional structure means document routing and item setup can vary by division, not just by trading partner.
• Perishable and DSD categories carry tighter ASN timing tolerance than dry grocery.
• 852 product activity data is meant to drive replenishment, not sit unused.
• Treat each division relationship as its own verification point, not an assumption of uniformity.

Onboarding with Kroger, or working through fill-rate or chargeback issues on an existing account? Talk to our team. For how your ERP connects into all of this, see EDI Integration by ERP Platform.