Retail integration

Kroger EDI integration for grocery suppliers

A guide for suppliers connecting with Kroger and its divisions, covering X12 and grocery documents, ship notice structure, labeling and payments.

Overview

Understanding Kroger integration

Who this is for: Food, beverage and consumer goods suppliers shipping to Kroger distribution centers and stores, including suppliers to Kroger divisions.

Kroger publishes EDI program requirements for its suppliers through its EDI portal. For a typical supplier, the flow starts with a purchase order, continues with a ship notice for every shipment, and closes with an invoice, functional acknowledgments and payment information. Kroger also uses adjustment and application advice documents, which suppliers need to process to keep accounts reconciled.

Grocery adds its own conventions. Kroger accepts standard X12 purchase orders and invoices in some programs and grocery-specific documents in others, so suppliers should confirm which format applies to each division and program. Kroger's own program pages require ship notices in a shipment, order, pack and item structure, accompanied by GS1-128 carton labels, which ties EDI accuracy directly to warehouse operations.

Kroger operates several divisions and banners, and third-party sources note that some divisions maintain separate EDI connections. Suppliers serving more than one division should plan for division-specific setup and testing.

Workflows

Typical Kroger business workflows

Grocery order-to-cash

  1. 1Receive purchase order
  2. 2Acknowledge the order
  3. 3Ship with GS1-128 labels
  4. 4Send 856 ship notice
  5. 5Send invoice
  6. 6Reconcile 812 and 820

Documents and APIs

Common Kroger transactions

Documents commonly exchanged with Kroger, based on the public sources listed below. Exact requirements depend on your program, so always confirm against Kroger's current implementation guide.

DocumentNameDirectionPurpose
850 / 875Purchase Order (X12 or grocery)From KrogerKroger orders product. The format depends on division and program.
855Purchase Order AcknowledgmentTo KrogerConfirms the order where required.
856Advance Ship NoticeTo KrogerDescribes each shipment in shipment, order, pack and item structure.
810 / 880Invoice (X12 or grocery)To KrogerRequests payment. The format depends on division and program.
812Credit/Debit AdjustmentFrom KrogerCommunicates adjustments to invoices.
820Payment Order/Remittance AdviceFrom KrogerExplains payments.
824Application AdviceFrom KrogerReports errors in documents the supplier sent.
997Functional AcknowledgmentBoth directionsConfirms documents were received.

Connectivity

How companies connect

  • Direct EDI or EDI provider

    Suppliers connect to Kroger directly or through an EDI provider that manages the connection.

  • Kroger EDI portal

    Kroger publishes program requirements and guidance for suppliers through its EDI portal.

Challenges

Common integration challenges

  • Format by division

    Some divisions and programs use grocery documents while others use standard X12, so maps must match each one.

  • Ship notice structure

    The 856 must follow the required hierarchy and match GS1-128 carton labels.

  • Adjustments and remittance

    Adjustment and remittance documents must be reconciled to keep receivables accurate.

How ECOM helps

How ECOM can support your Kroger integration

ERP integration options

ECOM integrates Kroger orders, ship notices, invoices, adjustments and remittances with your ERP, handling X12 and grocery formats per division.

Visibility and exception management

PRISM-SCV, ECOM's supply chain visibility product, is designed to follow each Kroger document from receipt to response and flag late or missing documents and mismatches, so your team can resolve exceptions before they affect the relationship.

Explore PRISM-SCV

Kroger integration FAQs

Does Kroger use grocery-specific EDI documents?

Kroger accepts standard X12 purchase orders and invoices in some programs and grocery-specific documents in others. Confirm which applies to your division and program.

What does Kroger require for ship notices?

Kroger's program pages require the 856 in a shipment, order, pack and item hierarchy, sent with GS1-128 carton labels.

Do Kroger divisions need separate EDI setup?

Third-party sources note that some divisions maintain separate connections. Suppliers serving multiple divisions should confirm setup for each one.

Is ECOM a Kroger-approved provider?

This page is an integration guide and does not indicate an approval or partnership with Kroger. ECOM builds integrations to Kroger's published requirements.

Sources and accuracy

This guide summarizes publicly available information as of October 2026. Kroger sets its own requirements and can change them at any time; your Kroger implementation guide, supplier portal or account contact is the authoritative source for your program.

Request Kroger integration assistance

Tell us about your Kroger program, documents and ERP. We will outline the connection, mapping and testing plan.