Wakefern EDI requirements for a small supplier
Wakefern 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
Wakefern’s published requirements list 4 documents as required:
- 875 — Grocery purchase order; they send it to you.
- 880 — Grocery invoice; you send it to them.
- 856 — Advance ship notice; you send it to them.
- 997 — Functional acknowledgement; you send it to them.
02UCS, which is not quite X12
Wakefern trades on UCS, at 004010. UCS is the grocery variant of X12, and the difference that costs money is the pairing: 875 and 880 are the grocery purchase order and invoice, used where your trucks deliver to the stores, and 850 and 810 are the general pair used for warehouse deliveries.
They are not renamed versions of each other. Cross them (invoice a direct-store delivery on an 810) and the invoice bounces, and with most retailers a bounced invoice is a chargeable transaction.
We read both pairs. The full set list is on the home page, and the Kroger page covers the pairing in more detail if you are facing grocery for the first time.
03What catches people out
- Warehouse and direct-store-delivery orders are specified separately; check which one a supplier is set up for.
- Specifications are published openly rather than behind a supplier portal, which is rare and makes onboarding faster.
—Check we can read their file first
Before you give anybody an email address: take a file Wakefern 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 UCS
The same research, for the retailers people most often face alongside this one. All of them are listed here.
—Where these facts came from
- Wakefern’s own published supplier material: www2.wakefern.com/vendors/vendor-guidelines
Read on 5 October 2026. Wakefern 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.