Skip to content

James Allman | JA Technology Solutions LLC

EDI 894/895 DSD Delivery/Return Explorer

Decode X12 EDI 894 and 895 DSD delivery/return documents into a readable summary: header, parties, line items, totals, plus raw segments and CSV export.

EDI 894/895 DSD Delivery/Return Explorer

Upload or paste an X12 EDI 894 (Delivery/Return Base Record) or 895 (Delivery/Return Acknowledgment) and read it as a structured delivery: the G82 header (delivery vs return, store, document number, date), N1 trading parties, G83 line items with UPC, quantity, and cost, and G84 totals. A raw labeled-segment view shows every segment exactly as transmitted, and you can export line items to CSV or Excel. These UCS transaction sets are how direct-store-delivery vendors report what they delivered or picked up at a store.
Learn more ↓

Loading interactive explorer...

Before you use this output: Segment IDs, transaction-set detection, party loops, and the raw segment breakdown are exact. The named element mappings (which G83 element is the UPC, the unit cost, and so on) follow the common UCS 894/895 layout but vary by trading partner and version, so verify against your partner's implementation guide.

What the 894 and 895 Are

The UCS 894 Delivery/Return Base Record reports the goods a vendor delivered to a store, or the goods returned from it. The 895 Delivery/Return Acknowledgment closes the loop, confirming or adjusting what the 894 reported. These are the backbone of direct-store-delivery (DSD): bread, beverages, snacks, and dairy vendors who deliver straight to the store and settle at the door. The G82 header carries the credit/debit direction, store, and document number; G83 segments carry the line items; G84 carries the totals.

Reading One by Hand Is Slow

A raw 894 is a wall of asterisk-delimited segments. This explorer turns it into a delivery you can read: direction, parties, a line-item table with UPC, quantity, and cost, and the document totals, alongside a raw segment view that labels every segment exactly as transmitted. Because element positions vary by trading partner and version, the structured view is best-effort and the raw view is always exact, so you can cross-check anything that matters before you trust it.

From Delivery Record to Posted Data

Reading a delivery is the start; matching it to the purchase order, validating it against the item file, and posting it to accounts payable without rekeying is the work I build. See integration services or get in touch. For DSD captured at the dock, see the DEX/UCS File Explorer; for other X12 documents, the EDI File Parser and X12 Segment Reference. New to these documents? Read Reading DSD Deliveries: DEX, EDI 894, and 895. Have questions? Ask James.

All tools run entirely in your browser. Your data never leaves your machine. Need help? Ask James.