The EDI 875 · Grocery Products Purchase Order is how grocery buyers order product from grocery suppliers in data instead of phone calls and fax sheets. It does the job the 850 · Purchase Order does everywhere else, but it was built for an industry where an order is thousands of UPCs, quantities are cases and eaches at the same time, and half the lines carry a promotional allowance that decides whether the order makes money.
If you sell into grocery — or build software for anyone who does — the 875 is the document your whole replenishment cycle turns on. It arrives from the retailer or distributor, it states what they want, in what pack, at what price, with what deals attached, and everything downstream (the pick, the 856 · Advance Ship Notice, the 880 · Grocery Products Invoice) is graded against it.
What is the EDI 875?
The 875 · Grocery Products Purchase Order is sent by the buyer (a grocery retailer, wholesaler, or distributor) to the supplier. It descends from UCS, the Uniform Communication Standard the grocery industry adopted for electronic ordering long before general retail settled on the 850 — which is why grocery still runs its own document family today.
Three ideas define it:
- The UPC is the item identity. Where a general 850 line might carry a buyer's internal part number, an 875 line is anchored on the product's UPC/GTIN. There is no translation table to argue about: the code on the case is the code on the order.
- Quantity is two numbers, not one. Grocery orders think in cases ordered and eaches inside them. A line that says "10" without saying 10 of what — cases, pallets, consumer units — is a receiving dispute scheduled in advance.
- The allowance is part of the order. Promotional deals, new-item allowances, and bill-back terms ride on the order itself, because in grocery the deal is often the reason the order exists at all. An 875 that drops the allowance has not transmitted the order — it has transmitted a more expensive misunderstanding.
How is the 875 different from the 850?
The two documents are cousins, not twins:
- The 850 · Purchase Order is the general-purpose order used across retail, manufacturing, and distribution, with flexible item identification (buyer part numbers, vendor part numbers, UPCs).
- The 875 · Grocery Products Purchase Order is the grocery specialization: UPC-centric lines, case/each quantity conventions, and first-class handling of allowances and grocery pricing.
- The invoice pair splits the same way. A general supplier answers an 850 with an 810 · Invoice; a grocery supplier answers an 875 with an 880 · Grocery Products Invoice, which carries the grocery allowance and deduction conventions the 810 was never shaped for.
Teams moving from general retail into grocery get bitten by assuming the 850 map will stretch. The envelope looks familiar; the grading rules — how the buyer checks price, pack, and allowance — are grocery's own.
What breaks on the 875?
Pack size drift. The buyer orders by the case pack that was current when the item was set up; the supplier has since moved from a 12-pack to a 24-pack. The UPC matches, the case count matches, and the store receives twice the product it can shelve. The order was "accurate" and wrong at the same time.
Allowances that live in email instead. The deal was agreed with the buyer, the order arrives without it, and the supplier invoices full price. The deduction that follows is not a payment error — it is the order and the invoice telling two different stories, and the 880 gets graded against the buyer's version.
Eaches read as cases. A quantity field interpreted in the wrong unit of measure multiplies or divides a line by the pack size. This is the single most expensive reading error in grocery ordering, and it survives testing whenever test orders use a quantity of 1.
Price that moved between setup and order. Grocery pricing changes on deal cycles. An 875 priced from last cycle's file invites the invoice to be short-paid to this cycle's price — with the supplier holding paperwork that proves nothing except that the two systems disagreed.
How should you run grocery ordering cleanly?
- Treat UPC + pack as one key. Never validate the item code without the pack configuration it was ordered in; a correct UPC in a retired pack is a wrong shipment.
- Carry the allowance on the order, and echo it on the invoice. If a deal exists anywhere except the 875 and the 880, it exists nowhere when deductions are reviewed.
- Test with real quantities. A test line of "1 case" cannot catch a unit-of-measure error. Test with the quantities and pack sizes the buyer actually orders.
- Grade your own ASN against the 875, not the pick ticket. The 856 should report what the 875 asked for, translated into what physically shipped — discrepancies named, not smoothed over.
- Watch the deal calendar. When a promotion starts or ends, expect order patterns to change that week, and check the first orders of the cycle by hand.
Frequently asked questions
Who sends the 875 — the buyer or the supplier?
The buyer sends it. The supplier acknowledges, ships against it, and invoices with the 880 · Grocery Products Invoice.
Is the 875 only for big grocery chains?
No. Regional chains, distributors, and food cooperatives use it too, and it is often the first EDI document a small food or beverage brand meets when it wins its first grocery placement.
Can a supplier use an 850 instead if the buyer asks for an 875?
Not safely. The buyer's system is set up to receive, validate, and grade the grocery document family; substituting an 850 drops the grocery conventions the buyer's checks depend on.
What acknowledges an 875?
The 997 · Functional Acknowledgment confirms the file was structurally readable, as with any X12 set. The business conversation continues with the shipment (856) and the grocery invoice (880).
Grocery runs on thin margins and thick order files, and the 875 is where both are decided — item by UPC, quantity by pack, price with the deal attached. Get that one document right and the rest of the cycle has something solid to be graded against.
I build SignalEDI to help SMB teams handle exactly this layer — grocery orders read with their pack and allowance context intact, so the notice and the invoice agree with what the buyer actually ordered.
— Chris, founder of SignalEDI
Top comments (1)
The point about UPC + pack is especially useful: I’d treat the pack configuration as versioned master data, with an effective date, rather than letting the UPC alone drive validation. A good test fixture should include a retired pack and a promotion boundary, then assert that the 875’s case/each quantities and allowance survive through the 856 and 880. That catches the “valid item, wrong shipment” case before it becomes a deduction, and makes the test suite a little less optimistic than a single-case demo.