Most EDI documents describe freight moving between distribution centers. The 894 describes something more intimate: what a driver actually hands over at the back door of a store. It is the backbone document of direct store delivery — the model where bread, soda, chips, beer, and dairy skip the retailer's DC entirely and arrive on the supplier's own truck, on the supplier's own route.
Where the 894 sits in the DSD loop
DSD runs on a different rhythm than warehouse supply. Orders are frequent and small, deliveries are daily or near-daily, and the moment of truth is the store door, not the DC dock. The document loop reflects that:
- An order exists — sometimes an 875 grocery PO, sometimes a standing route plan the driver works from.
- The supplier sends the 894 Delivery/Return Base Record: the delivery's line-item contents — items, quantities, unit prices, allowances, and any returns or pickups — identified by UPC or GTIN.
- The store responds with an 895 Delivery/Return Acknowledgment: confirmation as delivered, or an adjusted record where the receiver counted something different.
- Settlement follows from the agreed record — an 880 grocery invoice where the program bills separately, and often an 882 DSD summary rolling up a route's deliveries for reconciliation.
The 894/895 pair is the DSD world's answer to the ASN-and-receipt handshake: a machine-readable statement of delivery, and a machine-readable answer, so that pricing and quantity disputes get settled per delivery instead of festering until the invoice fight.
DEX handhelds vs the network 894
There are two transports for the same idea, and suppliers regularly confuse them.
DEX/UCS is the store-door variant. The driver's handheld connects directly to the store's receiving system — historically through a physical DEX jack at the back door — and exchanges the delivery record on the spot. The receiver checks the delivery against the transmission, adjustments happen at the door, and the driver leaves with a settled record. DEX is driver hardware, store-by-store connectivity, and real-time reconciliation.
The network 894 travels over ordinary EDI connectivity — AS2 or VAN — from the supplier's system to the retailer's, ahead of or alongside the physical delivery. The store still verifies at the door, and the 895 comes back over the network. No jack, no handheld dependency, and the supplier's back office sees everything centrally.
Which one you run is the retailer's call, and programs vary — some accept network 894s across the board, some require DEX at the door, some mix by category. Confirm in the current DSD program guide before building anything.
The item-level detail that matters
The 894's G83 line items carry more commercial payload than most documents: quantity, unit of measure, UPC/GTIN, unit price, and item-level allowances and charges. Two details deserve engineering attention:
- Price agreement. The store-side system validates your delivered price against its authorized cost. A price mismatch at the door becomes an adjustment on the 895 and a deduction in settlement. Keeping item and price data synchronized with each retailer — before the truck rolls — is most of the game.
- Returns on the same document. The 894 handles both directions: delivery lines and pickup/return lines (stales, damages, buybacks) in one record. Your reconciliation has to net them correctly or route accounting drifts from store receipts.
Get those two right and DSD settlement becomes arithmetic. Get them wrong and every route generates paperwork.
Grocery context, and where Publix fits
Grocery is where DSD lives, and Publix is a prominent example of a retailer trading the 894/895 pair as part of its supplier program, alongside the 875 and 880. The broader landscape — which categories run DSD, how warehouse and DSD programs coexist at the same chain — is covered in our grocery DSD overview, and the retailer-specific picture is in the Publix requirements guide.
For a supplier standing up DSD EDI, the practical checklist is short: item and price sync per retailer, 894 generation from route accounting data, 895 capture feeding adjustments back into settlement, and acknowledgment tracking on the whole flow. EDISQ supports the DSD document set — 894, 895, 875, 880, 882 — on the same per-document meter as everything else: first 25 documents monthly free, then a published ladder on the pricing page, with connectivity operated as part of the service.
FAQ
What is the EDI 894?
The Delivery/Return Base Record — the DSD document a supplier sends to tell a store what the driver is delivering or picking up at the store door: items, quantities, prices, and any returns, at line-item level.
What is the difference between the 894 and the 895?
They are a pair. The 894 states what the supplier delivered; the 895 Delivery/Return Acknowledgment is the store's response, confirming the delivery or adjusting quantities the receiver disputes. Together they settle what actually crossed the threshold.
What is DEX and how does it relate to the 894?
DEX/UCS is the store-door variant: the driver's handheld exchanges the same delivery record with the store's system over a direct connection at the receiving door. Network 894s travel over normal EDI connectivity ahead of or alongside the delivery.
Which retailers use the 894?
Grocery DSD generally. Publix is a prominent example, trading the 894/895 pair alongside the 875 and 880. Confirm the exact document set and version in each retailer's current DSD program guide.