EDI 875 and 880: how grocery orders and invoices move

Your first grocery distributor just sent a vendor packet, and in it are two document codes you have never seen. They do two jobs you know well: the order coming in, and your invoice going out.

What the 875 and 880 are, in plain English

The 875 and 880 are grocery industry documents that let grocery stores and their suppliers order products and handle invoices electronically. Think of them as the grocery version of placing an order and getting a bill.

The 875 is the purchase order: the items a grocery buyer wants, by UPC, with quantities, prices and the delivery date. The 880 is the invoice going back the other way: what actually shipped, at what price, referencing the exact order it answers. If you already know the 850 purchase order and the 810 invoice, these are their grocery counterparts. New to EDI altogether? Start with what EDI is and come back.

How the EDI 875 travelsThe 875 Grocery Products Purchase Order goes from Grocery buyer to Supplier. In sequence with: 850, 856, 810, 875.Grocery buyerSupplier875Grocery Products Purchase OrderIn sequence850Purchase order856Ship notice810Invoice875875
How the EDI 875 travelsThe 875 Grocery Products Purchase Order goes from Grocery buyer to Supplier. In sequence with: 850, 856, 810, 875.Grocery buyerSupplier875Grocery Products Purchase OrderIn sequence850Purchase order856Ship notice810Invoice875875
Which way the 875 travels, and the documents it is usually traded alongside. Partner implementation guides can add or drop documents from this set.

Why grocery has its own documents

The grocery industry standardized early, on UCS, a streamlined subset of the X12 standard built for the way grocery actually trades: high volumes, short lead times, weekly or daily ordering, and items identified by UPC. The 875 and 880 are leaner than their general-purpose cousins, and the industry kept them because they fit the tempo.

In practice that means a supplier entering grocery distribution supports the pair together: orders arrive as 875s, invoices go back as 880s, and most partners expect a 997 acknowledgment for every document in both directions, often with an advance ship notice in between. Chains publish their own requirements on top; see our Kroger EDI guide for one example, and our food industry page for the wider picture.

Where grocery invoicing goes wrong

The pattern in grocery is deductions: when the invoice and the order disagree, the buyer pays what their system thinks is right, short-pays the rest, and the supplier spends weeks getting it back.

  • Price variances: the 880 bills a price the 875 did not carry, and the difference becomes a deduction the moment the buyer matches documents
  • Missing order references: an invoice that does not cleanly reference its order falls out of the automatic match and into a manual queue, where it ages
  • UPC and unit mismatches: a case billed where an each was ordered, or an item number the buyer does not recognize, and the line is disputed
  • Silence: no 997 comes back, nobody notices, and the order or invoice was simply never received

What you get when it is set up right

  • Orders land ready to pick: 875s flow into your system with items and quantities already translated to your catalog
  • Invoices go out same-day: each 880 references its order, carries matching prices and units, and bills what actually shipped
  • Fewer deductions: clean matches mean the buyer pays the invoice instead of their own version of it
  • Every document accounted for: acknowledgments are reconciled both ways, so nothing disappears quietly

Why set it up with Effective Data

We map the pair completely with you: items cross-referenced to the catalog, prices carried through from order to invoice, and every document tested against each partner specification before go-live rather than on live orders. Prebuilt alerts and human support monitor the flow, so errors get caught quickly. And when a partner question comes up, a named specialist works it with you the same business day.

For the technical team

If you are the one doing the mapping, these are the segments that matter most in practice across the pair. The partner implementation guide governs the exact requirements.

Set Document Direction Notes
G50 Purchase Order Identification 875 header The order number and date that the 880 invoice must reference back
G62 Date/Time 875 header Requested delivery or pickup date for the order
G68 Line Item Detail 875 detail One ordered line: quantity, unit, and the item by UPC or vendor number
G69 Line Item Description 875 detail Free-form description of the line item
G76 Total Purchase Order 875 summary Order totals the receiver checks against the detail lines
G01 Invoice Identification 880 header Invoice number and date, plus the purchase order it answers
G23 Terms of Sale 880 header Payment terms, discounts and due dates
G17 Item Detail 880 detail One invoiced line: quantity shipped, price, and the item identifier
G33 Total Dollars Summary 880 summary The invoice total the buyer matches against the lines and the order

Common 875 and 880 segments, UCS. Which are mandatory varies by trading partner. Their specification governs.

Frequently asked

+ What is an EDI 875?

The Grocery Products Purchase Order. It does the same job as the standard 850 purchase order, in the leaner UCS format the grocery industry standardized on: the items, quantities, prices and delivery date a grocery buyer wants.

+ What is an EDI 880?

The Grocery Products Invoice, the grocery version of the standard 810 invoice. It bills for what shipped, references the 875 order it answers, and carries the terms and totals the buyer matches before paying.

+ Why does grocery use the 875 and 880 instead of the 850 and 810?

History and speed. The grocery industry standardized early on UCS, a streamlined subset of the X12 standard built for high-volume, fast-turn ordering. The documents are leaner than their general-purpose cousins, and the industry has kept them because they work.

+ Which trading partners require them?

Grocery distributors, wholesalers and many grocery retail chains. If a grocery partner has handed you a vendor packet, the 875 and 880 are usually in it, often alongside a 997 acknowledgment requirement and an advance ship notice.

+ What is DEX, and how is it different?

DEX, direct exchange, is for direct-store-delivery: the driver transmits the invoice at the back door of the store using the 894 and 895 documents. The 875 and 880 travel between systems over a network connection instead. Suppliers who deliver both to warehouses and direct to stores often end up running both.

A grocery partner just handed you the 875 and 880?

Tell us which distributor or chain, and what the packet asks for. We will map out the setup, including the acknowledgments and ship notices that usually ride along, and tell you exactly what it takes to go live.

Answered the same business day. No charge, no mailing list.