Contact

KeHE EDI requirements for a small supplier

KeHE has asked you to trade documents electronically. This page is what they publish that they want, which parts are genuinely hard, and where every fact came from, so you can check it rather than take our word for it.

01What they ask a supplier for

KeHE’s published requirements list 9 documents as required:

  • 850 — Purchase order; they send it to you.
  • 860 — Purchase order change; they send it to you.
  • 855 — Order acknowledgement; you send it to them.
  • 753 — Ready to ship — routing request; you send it to them.
  • 754 — Routing instructions; they send it to you.
  • 856 — Advance ship notice; you send it to them.
  • 810 — Invoice; you send it to them.
  • 812 — Credit / debit adjustment; you send it to them.
  • 997 — Functional acknowledgement; you send it to them.

02The standard, and the version

KeHE trades on X12, at 004010. That is the ordinary North American standard rather than the grocery variant, which makes it the more straightforward of the two to set up: there is no 875/880 pairing to get wrong.

The version matters more than people expect. A segment that is optional in 004010 can be required in 005010, and a file built to the wrong version parses and then fails validation at the retailer. The sets we read are listed here.

03What catches people out

  • From 1 July 2026 every supplier must handle the full set, including the 753 routing request and the 812 adjustment. This is the longest required list of any partner here.
  • The 855 acknowledgement has a deadline rather than merely being required: within 48 hours of the order. A supplier who sends it eventually is still non-compliant.
  • An invoice that does not arrive by EDI carries a $150 processing fee, which makes this one of the few partners where the cost of getting EDI wrong is published rather than discovered.
  • The 753 and 754 are a routing conversation: you say the shipment is ready, they tell you which carrier to use. A supplier who books their own freight is doing it wrong and will be charged for it.
  • A distributor rather than a retailer, and often a small supplier’s first EDI relationship.

—Check we can read their file first

Before you give anybody an email address: take a file KeHE has sent you and run it through the validator. It works in your browser and uploads nothing (the file never leaves your machine), and it will tell you what is in it and whether it can be read.

Then tell us the retailer and the date on the letter. We are in Florence, Kentucky, and we would rather have the conversation than the form.

—What it costs

Published rather than quoted: the plans and the per-document prices are on the home page, including what a retailer connection costs when one is needed. There is no implementation fee and no per-retailer setup charge.

—Others on plain X12

The same research, for the retailers people most often face alongside this one. All of them are listed here.

—Where these facts came from

Read on 6 October 2026. KeHE can change what they require without telling us, and their own implementation guide wins over anything on this page. Check it before you rely on a version number or a required document here.