Direct store delivery generates paperwork at the speed of a delivery route: dozens of store drops a day, each with its own quantities, returns, and adjustments. Settling that trade delivery-by-delivery would drown both sides — so the industry rolls it up. The EDI 882 Direct Store Delivery Summary is the roll-up: a route-level summary of DSD activity that lets a supplier and its trading partner reconcile a settlement period without re-litigating every stop.
Where the 882 sits in the DSD chain
DSD trade runs on the grocery document family. Orders arrive on the 875 grocery purchase order, often daily per store. Individual deliveries get billed on the 880 grocery invoice. The 882 then aggregates: for a route and period, the summary of deliveries made, credits and adjustments applied, and the totals that settlement will be based on. Think of it as the statement to the 880's invoices — the document both sides check the math against before money moves.
Convenience-store distribution shows the pattern at full scale. McLane settles route-level DSD summaries against deliveries — and its suppliers are expected to map those summaries into AR rather than file them, because the summary is where discrepancies between delivered and settled first become visible.
What reconciliation actually catches
The value of a structured settlement summary is the mismatches it surfaces while they're small:
- Delivery-versus-settlement gaps — a stop recorded by your driver that the summary doesn't credit, or vice versa. Caught at period close, it's a correction; caught at quarter end, it's an investigation.
- Adjustment drift — returns, damages, and shortages applied at the store door accumulate across a route. The 882 itemizes them, which is how a supplier notices one store or one route consistently bleeding product.
- Pricing disagreements — settlement totals that don't tie to invoiced amounts point at a price-file mismatch upstream, the kind that otherwise repeats every period until someone reconciles by hand.
Suppliers who treat the 882 as a filing obligation absorb these quietly as margin erosion. Suppliers who post it into AR and auto-match against their own delivery records turn the same document into a control.
Cadence discipline helps on both sides. Settlement periods close on the partner's calendar, and corrections accepted in-period become far harder to place once the next cycle opens — so the summary needs to hit your reconciliation process the day it lands, with your own delivery records already posted and ready to match against.
Integrating settlement into AR
The working pattern: land each 882 against the period's delivery and invoice records in your accounting system, auto-tie the totals, and route only the deltas to a human. Store- and route-level cross-references do the heavy lifting — the partner's route and store identifiers must resolve to your customers and delivery records, the same discipline the rest of the grocery document set already demands. EDISQ maps 882s into your ERP or accounting platform alongside the 875/880 traffic, with the matching automated; the full DSD picture is covered in our food and beverage solution. Route-accounting detail feeds the sales side too — route-level velocity and adjustment patterns are the closest thing DSD suppliers get to store analytics.
Priced like the rest of the route
Settlement summaries arrive on a period cadence, so their document count stays modest even when the trade behind them is enormous — a favorable shape under EDISQ's per-document pricing. The month's first 25 documents are free; after that, each document runs from $0.50 down to $0.10 as your total volume climbs the tiers, billed marginally. No per-route charges, no mapping or setup fees, and the connectivity — VAN included, which matters in this channel — comes with it. The economics of DSD are fought at the store door; the documents that account for it should barely register, and here they don't.
FAQ
What does an EDI 882 summarize?
Direct store delivery activity at route level — the deliveries, adjustments, and totals behind a settlement period — so both sides can reconcile what was delivered against what gets paid.
How does the 882 relate to the 875 and 880?
The 875 orders, the 880 invoices individual deliveries, and the 882 rolls activity up for settlement. In DSD programs the three form the order-bill-settle chain.
Who uses the 882?
DSD-heavy trade: grocery and convenience channels, and distributors that settle with suppliers on route-level summaries rather than invoice by invoice.
How much does 882 processing cost?
Standard EDISQ metering: 25 documents free per month, then from $0.50 per document with volume tiers to $0.10 — settlement data included, no module fees.