X12 882 — Direct Store Delivery Summary Information
The 882 summarizes Direct Store Deliveries — bread, snack, beverage routes — from a DSD supplier to a retailer, for visibility and payment reconciliation.
Purpose
The 882 documents a DSD route summary: for each store visited, delivered items, retrieved items (stales), credits issued, payment collected (cash, check, account). It feeds the retailer financial system and avoids duplicate billing with the 810.
It is widely used in US and CA mass distribution for bread, snacks, beverage segments. Acknowledged by 997.
Envelope structure
The 882 travels within the three X12 envelope levels (ISA/IEA,
GS/GE with functional group DD, and ST/SE).
Didactic example in release 004010:
ISA*00* *00* *ZZ*DSDSUPPLIER *ZZ*RETAILER *260515*1030*U*00401*000000882*0*P*>~
GS*DD*DSDSUPPLIER*RETAILER*20260515*1030*1*X*004010~
ST*882*0001~
BAU*00*DD*RTE-2026-7711*20260515~
N1*ST*ACME RETAIL STORE 042*92*042~
LX*1~
LIN*1*UP*012345678905~
QTY*38*48~
AMT*ZZ*144.00~
LX*2~
LIN*2*UP*012345678905~
QTY*39*6~
AMT*ZZ*18.00~
SE*11*0001~
GE*1*1~
IEA*1*000000882~ Common segments
- Header —
ST,BAU(Beginning Segment for Application Update). - Store —
N1*ST. - Items —
LXloop:LIN*UP,QTY*38(Delivered),QTY*39(Stales / picked up),AMT*ZZ. - Summary —
SE.
Common pitfalls
- Stales reconciliation: forgetting the stales QTY in a 882 underbills the retailer; stales are essential to net billing.
- Route signature: a DSD must carry a digital route signature from the driver; a 882 without signature is contested during audits.
- Same-day cutover: if the 882 is late vs. store close, retailer financial close breaks; negotiate a strict SLA.
Related transactions
Documentation
The code 882 and the name Direct Store Delivery Summary Information are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.