Transaction explainers · October 28, 2026

EDI 895 Delivery/Return Acknowledgment: The DSD Adjustment Guide

How the EDI 895 works in direct store delivery — the store's response to your 894, adjustment codes, and the reconciliation discipline that protects settlement.

Direct store delivery settles at the store door, and the 895 is the document where the store talks back. Your driver delivers against an 894 delivery record; the retailer answers with an 895 saying what the store actually agrees it received. When the two match, settlement is clean. When they don't, the 895 is telling you exactly where your money went — if you're reconciling it.

The 894/895 pair

DSD flips the normal retail flow. There's often no warehouse PO, no ASN, no DC receiving. The delivery is the transaction, so the documents mirror the doorstep:

  • 894 Delivery/Return Base Record — outbound from you: route, stop, items, quantities, prices for one store delivery (or pickup of returns).
  • 895 Delivery/Return Acknowledgment — inbound from the retailer: the store's line-by-line response, confirming or adjusting each item.

The pair is the electronic version of the driver and the receiver signing the same delivery ticket. DEX/UCS — the store-door handheld exchange — is the same idea running locally over a physical connection at check-in; many programs run DEX at the door and X12 894/895 with the corporate office, and grocery chains like Publix anchor their supplier DSD programs on this document family. Which combination applies to you is program-specific: confirm it in the retailer's current DSD guide.

What an adjustment actually looks like

The 895 responds at line level. For each item on your 894, the store can confirm the quantity, adjust it, or reject the line, with reason codes: shorted cases, damage refused at the door, an unauthorized substitution, a price or item-code mismatch against the retailer's authorization file. The adjusted quantities — not your originals — are what flow into the retailer's payable and eventually into route settlement summaries like the 882.

That last sentence is the whole game. The 895 is the retailer editing your invoice, one delivery at a time. Ignore it and you'll discover the edits weeks later as unexplained short-pays on the 820 remittance.

The reconciliation discipline

DSD operations that stay solvent treat the 895 as a daily ledger, not an FYI:

  1. Match every 895 to its 894 same-day. Unanswered deliveries after the program's acknowledgment window are their own exception to chase.
  2. Auto-clear the agreements. Lines where the store confirmed your quantity need no human. That should be the vast majority — get them out of the way so people only see exceptions.
  3. Work adjustments by reason code. Shorts and damage are operations problems (route, truck, handling). Item and price mismatches are data problems — your item file versus the retailer's authorization list. The two need different owners.
  4. Feed patterns back to the route. A store that adjusts every Tuesday delivery, a driver whose shorts cluster, an item that's always "not authorized" at one banner — the 895 stream surfaces all of it if anyone aggregates it.
  5. Dispute with the document. When an adjustment is wrong, the 894 with driver capture data is your evidence. Suppliers who reconcile daily dispute from records; suppliers who don't, negotiate from memory.

The broader DSD context — 894 details, DEX at the door, grocery invoice flows — is covered in our grocery DSD guide and the 882 settlement summary explainer.

Common failure modes

  • Treating the 997 as the answer. The 997 only means the 894 parsed. The business verdict arrives in the 895, sometimes days later.
  • No adjustment tolerance policy. Chasing every one-case adjustment costs more than it recovers; auto-accepting everything trains stores to be careless. Set a threshold and enforce it consistently.
  • Item file drift. Half of DSD adjustments trace to your item and price data disagreeing with the retailer's authorization file. Reconcile the files on the program's cadence, not just at onboarding.

EDISQ handles the 894/895 pair like everything else in the network — certified maps, automatic acknowledgments, and each document metered on the same per-document ladder with the first 25 each month free. For the full grocery document set by retailer, start at the partner directory.

FAQ

What is the EDI 895?

The Delivery/Return Acknowledgment — the store's electronic response to your 894 delivery record. It confirms what the receiver agrees was delivered or returned, including any line-level adjustments to quantity or item.

How is the 895 different from a 997?

The 997 says the file arrived and parsed. The 895 is a business answer: the store looked at your delivery record and agreed or adjusted it. A clean 997 with an adjusted 895 is common — and the 895 is the one that moves money.

What causes 895 adjustments?

Shorted cases, damaged product refused at the door, item substitutions the store didn't accept, and scan mismatches between the driver's handheld and the store's receiving system. Each adjustment changes what you'll be paid.

Do all DSD retailers send an 895?

No. Programs vary — some acknowledge every 894, some only send adjustments, and some run DEX/UCS at the store door instead. Confirm the acknowledgment model in each retailer's current DSD program guide.