Industry guides · October 13, 2026

Grocery DSD EDI: The 875 and 880 Behind Store-Door Delivery

How direct-store-delivery EDI works — daily 875 grocery orders, the 880 invoice that answers them, and 882 settlement summaries.

Direct-store-delivery skips the distribution center entirely. Your driver pulls up behind the store, wheels product to the shelf, and the transaction lives or dies on data moving as fast as the truck. Grocery built a document set specifically for that rhythm, and suppliers who arrive knowing only the 850/810 world find the dialect unfamiliar. Here's how the store-door flow actually works.

Orders at store speed

The workhorse is the 875 Grocery Products Purchase Order. Structurally it's a cousin of the 850, but it was designed for grocery cadence: an order per store, cut daily. At Kroger, DSD orders arrive daily and sometimes intra-day — a frequency at which manual processing physically cannot keep up, which is why automation is the entry ticket rather than an optimization. Grocers running DSD programs, from Kroger to Publix, cut store-level orders daily against tight delivery windows, so an 875 that waits overnight in a portal is already late.

Item identification is its own discipline. Kroger orders carry both the retailer's item codes and UPCs, and your map must translate in both directions on every document; most bounced grocery documents trace back to item cross-references rather than syntax. Grocery majors are equally demanding on the warehouse side of the house — H-E-B expects same-day acknowledgment on its replenishment orders — so speed is the common denominator across both flows.

The 880 answers the 875

Getting paid in DSD runs through the 880 Grocery Products Invoice. The pairing is strict: grocery orders settle on grocery invoices. A supplier who bills a store-door delivery with an 810 discovers the mismatch at accounts payable, after the product is long since sold. The 880 mirrors the delivery — items, quantities, and pricing as delivered — and the retailer reconciles it against what the store received at the back door.

Because DSD deliveries get adjusted at the door (shorts, damages, returns pulled from the shelf), the invoice has to reflect the driver's final delivered quantities, not what the order requested. Wiring the handheld or route-accounting system into the 880 flow is what keeps deductions off the ledger.

Settlement and the 882

Above the individual invoices sits the 882 Direct Store Delivery Summary, a route-level roll-up that summarizes deliveries and adjustments for settlement. Where a retailer or distributor uses it, the 882 is how both parties reconcile a week of store drops against one payment — mapping it into your AR process turns a pile of per-store paperwork into a single match. Not every grocery program trades the 882, but where it appears, treating it as filing-cabinet material instead of AR input is a common and expensive mistake.

Warehouse and DSD, side by side

Most grocery suppliers of any size end up running both flows: warehouse replenishment on the 850/856/810 chain into the DCs, and DSD on the 875/880 pair into stores — often with the same retailer, decided category by category. The practical requirement is that your EDI layer routes each order type into the right workflow automatically, so the grocery documents and the retail documents never cross. Our food and beverage solutions page covers the combined picture, and the 875 deep-dive unpacks the order document segment by segment.

DSD's economics reward the pricing model that matches its shape: hundreds of small documents rather than a few large ones. With EDISQ you pay for exactly that flow — nothing for the first 25 documents in a month, then a per-document rate that opens at $0.50 and falls to $0.10 as monthly volume climbs, applied marginally the way tax brackets work. There are no mapping or setup fees, AS2, SFTP, and VAN connectivity come standard, and live trading runs on a $100/month Production minimum applied entirely to usage — first live retailer included, each additional one a flat $50/month. The pricing page has the complete tier ladder.

FAQ

What is the EDI 875?

The Grocery Products Purchase Order — a PO format built for grocery's direct-store-delivery rhythm: orders cut daily per store, delivered on your next route, with grocery-specific item and pricing conventions.

Can I answer an 875 with a regular 810 invoice?

No. DSD deliveries invoice on the 880 Grocery Products Invoice, which is the 875's companion document. Sending an 810 against a grocery PO gets rejected at the retailer's accounts payable.

What is the 882 used for?

Direct Store Delivery Summary — a route-level settlement document that rolls up deliveries and adjustments so both sides can reconcile what was delivered against what gets paid.