Grocery runs on a different rhythm than the rest of retail. Orders are cut per store, often per day, for product that may be on the shelf tomorrow — and the industry built its own EDI vocabulary to match. The EDI 875 Grocery Products Purchase Order is the centerpiece: a purchase order shaped for the cadence of food, beverage, and direct-store-delivery trade rather than the slower DC-replenishment world the 850 grew up in.
Why grocery has its own PO
The 875 comes from the UCS (Uniform Communication Standard) family, developed for the grocery channel. Functionally it does what any PO does — who's buying, what, how much, delivered where and when — but its structure and conventions assume grocery realities: store-level ordering, tight delivery windows tied to appointments, item identification by UPC alongside the grocer's internal code, and volumes measured in orders per day rather than per week.
Inside the document, a G50 segment opens with the order number and date, N1 loops identify the store or DC, G62 carries delivery dates, and G68 detail lines list items and quantities. The syntax differs from an 850, but the operational questions are identical — which is why a good EDI layer presents both formats to your team as, simply, orders.
The DSD cadence problem
Direct store delivery is where the 875 earns its reputation. In DSD programs your trucks deliver to individual stores, and the orders arrive at matching granularity: Kroger cuts DSD orders daily or even intra-day, and at that frequency manual processing is not a staffing question — it's mathematically off the table. An order file that lands at 6 a.m. for same-day or next-morning delivery has to flow straight to routing and picking. Grocery wholesalers and regional chains run the same pattern by category, some pairing warehouse programs on the 850 with DSD programs on the 875 simultaneously.
The good news: 875s are repetitive in the best way. The same stores order the same assortment on a steady drumbeat, so once item and store cross-references are mapped, automation handles the flood indefinitely.
Two data disciplines keep it that way. Store cross-references have to track the grocer's network as stores open and close, because an unrecognized store code strands an order the morning it was needed. And item alignment matters doubly in grocery: pack sizes, catch-weight flags, and deposit items all change the arithmetic between what a store orders and what a truck delivers.
The paper trail after the order
The 875 anchors its own document family. Deliveries get billed with the 880 Grocery Products Invoice — the grocery counterpart of the 810, matched against the 875 and what the store received. Route-level settlement in DSD programs is summarized on the 882. And where a grocer runs warehouse replenishment alongside, ship notices and standard documents flow in parallel. Mapping only the order and skipping its companions leaves the billing half of the relationship manual — the half where disputes live.
Keeping up without hiring for it
EDISQ treats grocery as a first-class flow, detailed in our food and beverage solution: 875s land in your ERP as orders with store and item codes already translated, order acknowledgment and invoicing generate from the same records, and the daily cadence becomes a background process instead of a morning scramble.
Volume is the whole story in grocery, so pricing built on volume fits it naturally. With EDISQ the first 25 documents each month cost nothing; past that, each document starts at $0.50 and the per-document rate declines through the tiers to $0.10, charged marginally as you cross each threshold. No per-store charges, no mapping or setup fees, and the connectivity — AS2, SFTP, or VAN, whichever your grocer requires — is bundled. A thousand store-level orders a month is precisely the shape of traffic the ladder was designed for.
FAQ
What is the difference between an 875 and an 850?
Both are purchase orders. The 875 is the UCS grocery-industry variant, built for high-frequency store-level ordering and DSD programs; the 850 is the general retail PO. Many grocers trade both, split by program.
Which invoice pairs with the 875?
The 880 Grocery Products Invoice. Orders that arrive as an 875 are generally billed with an 880 rather than an 810 — the documents are designed as a pair.
Can I handle daily 875 volume manually?
Rarely for long. DSD orders arrive per store, often daily, with same-day turnaround expectations — the volume and cadence are exactly what EDI automation exists to absorb.
How does EDISQ charge for 875s?
Per document: 25 free monthly, then from $0.50 each, stepping down to $0.10 at high volume. Daily store-level ordering is where the volume tiers do their work.