EDI requirements for Kroger suppliers running Odoo

What Kroger publishes, and where

Kroger's EDI portal sets out the envelope details: UCS and X12 version 5010, qualifier 08, with Kroger's ISA and GS identifiers. Guidelines are filed by group, and the group decides your document set: the Kroger and Peyton's food group, Fred Meyer, Harris Teeter, Health and Wellness, Ship To Home, imports, and a separate track Kroger labels its modernized systems. The food group alone spans banners from King Soopers and Ralphs to QFC and Smith's, so confirm which group your buyer sits in before you read anything else.

The portal also carries a New Partner Setup form, an AS2 service request form, and edi@kroger.com as the working mailbox. Your first step is the setup form, and your second is asking your buyer which group and which programmes apply to your category.

The documents behind a Kroger mandate

Kroger's published programme list is long, and the spine for a warehouse supplier reads like the grocery standard. Purchase orders arrive as the 850 or the 875 grocery purchase order, and both appear on the portal's requirements table. The 856 advance ship notice carries its own procedures, violation descriptions, logistics requirements and a food-traceability variant on the portal. Invoices run as the 810 or the 880, with published business standards for each. Payment comes back through the 820 remittance advice, and vendor-managed and scan-based programmes run on the 852 product activity feed.

The 997 is required, in Kroger's own words: "Functional acknowledgment (FA) is required for EDI data interchange." The portal is explicit that the 997 acknowledges transmission and implies no acceptance of the contents. Beyond the spine sit the 812, 824, 830, 832, 857, 867, 879, 889, 894, 895 and 940, each with its own programme page; our X12 catalog covers what each number does.

The compliance programme, in their words

Kroger's enforcement policy requires vendors shipping to a Kroger distribution centre to receive the purchase order and return the invoice by EDI. The policy gives a vendor ninety days to comply, and after that "an additional fee of 1% of total invoice amount or $250, whichever is greater, will be deducted by Kroger from payment to help offset the cost of manual processing."

A deduction on the remittance advice is where that fee, and every other chargeback, reaches you. How chargebacks land in Odoo covers counting and reconciling them, and the ASN violation descriptions on Kroger's own portal tell you which 856 mistakes their receiving systems flag.

Which route your files travel

Kroger states its position plainly on the compliance page: "We do not require you to use any specific EDI solution or software." The portal lists VANs and third-party providers its vendors use, names among them, and carries its own disclaimer that none is endorsed. It also takes direct AS2 connections through a self-service request form on the same site, which makes Kroger one of the retailers where trading directly is a documented, form-driven path rather than a negotiation.

The choice that remains is yours: a provider that translates and bills per document, or a direct link where the mapping work is yours. Read your volume and your team before your letter decides for you.

What changes inside your Odoo

There is no X12 in Odoo, so a Kroger programme is a connector sitting on top of it. Four Odoo-side mechanisms decide whether it holds. Packagings carry your casepack, configured per product with a Unit Name, Quantity and Reference Unit, and a casepack that disagrees with Kroger's produces a shortage on a load your warehouse picked correctly. The GS1 nomenclature maps the GTIN to the product Barcode field and the SSCC to the Package name, which is what your 856 and pallet labels are built from. The Kroger PO number belongs in Customer Reference, the field Odoo exposes as client_order_ref, because every document they send back quotes it. And the Delivery Date against Expected date decides what your warehouse is promising into their window.

Kroger's dual-order reality adds one more: a connector that reads the 850 and ignores the 875 covers half the programme, so confirm with your group which of the two your category receives, and map both when the answer is both.

Testing and setup, as the portal runs it

Setup starts with the New Partner form and your group's guideline. Grocery programmes generally test in three stages, connectivity first, then each document validated against the guideline, then a watched production window. Kroger's portal publishes startup documents and first-steps pages for the documents that need them, the 856 and 857 among them, which is more paper than most retailers hand a new vendor.

The item master is still what overruns: GTIN, casepack, price and item number agreeing across your Odoo, their system and anything in between. Clean it before the first test file moves.

The Canadian mirror of this page is Loblaw EDI requirements, and the wider US picture is on US retail EDI compliance. Mass-merchant mandates run a different document mix; see Walmart EDI requirements.