DEX/UCS File Explorer

What Is DEX/UCS?

DEX (Direct Exchange) is how direct-store-delivery vendors hand delivery data to a retailer at the receiving dock, traditionally over a handheld connected to the store controller. DEX wraps the UCS 894/895 delivery and return transaction sets in an application envelope: a DXS header that names the sender, receiver, and version, and a DXE trailer that closes the session with a matching control number. Inside that envelope are the same 894/895 records exchanged over EDI, so DEX is really a transport layer around familiar delivery documents.

Reading a DEX Transmission

This explorer parses the DXS/DXE envelope, checks that the trailer control number matches the header, and decodes each embedded 894/895 into a readable delivery: direction, parties, a line-item table, and totals. A raw labeled-segment view shows every segment exactly as received, which matters because element positions vary by vendor and version. The structured view is best-effort; the raw view is always exact, so receiving teams can confirm a discrepancy at the segment level.

From the Dock to Your Back Office

Capturing DEX is one thing; posting it to your item file, reconciling it to the purchase order, and feeding accounts payable without rekeying is the integration I build. See integration services or get in touch. For 894/895 received over EDI rather than DEX, use the EDI 894/895 Explorer; for any X12 document, the EDI File Parser. New to DSD data? Read Reading DSD Deliveries: DEX, EDI 894, and 895. Have questions? Ask James.