972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Shipping and logistics

EDI 894 Delivery/Return Base Record

The X12 document a direct store delivery vendor uses to communicate the details of a delivery during the store's check-in procedure.

Sent by
Direct store delivery (DSD) vendor
Received by
Retail store
Standard
ANSI ASC X12

What is an EDI 894?

The EDI 894 Delivery/Return Base Record is the ANSI X12 transaction set a direct store delivery (DSD) vendor uses to communicate the details of a DSD delivery during the check-in procedure.

DSD vendors, such as bakeries, beverage and snack companies, deliver directly to stores rather than through the retailer's warehouse. At the back door, the driver's handheld transmits the delivery and any returns to the store's receiving system, which checks them before the store accepts the goods. The store responds with the 895.

How the EDI 894 worksDiagram of the EDI 894 Delivery/Return Base Record. Direct store delivery (DSD) vendor sends it to retail store. It usually starts the exchange. It is usually followed by 895 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G82 (Delivery/Return Base Record Identifier) and summary: G84 (Delivery/Return Record of Totals), G86 (Signature Identification) and G85 (Record Integrity Check). 1 optional loops are listed by their first segment.How the EDI 894 worksDelivery/Return Base Record: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 894SENDERDirect store delivery(DSD) vendorRECEIVERRetail store997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY895Delivery/ReturnAcknowledgment orAdjustment997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code DXGS … GETransaction set 894ST … SEHEADINGG82Delivery/Return Base RecordIdentifierDETAIL+ 1 optional loop, starting with:G83SUMMARYG84Delivery/Return Record ofTotalsG86Signature IdentificationG85Record Integrity CheckBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 894. Your trading partner's implementation guide adds its own requirements.
How the EDI 894 worksDiagram of the EDI 894 Delivery/Return Base Record. Direct store delivery (DSD) vendor sends it to retail store. It usually starts the exchange. It is usually followed by 895 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G82 (Delivery/Return Base Record Identifier) and summary: G84 (Delivery/Return Record of Totals), G86 (Signature Identification) and G85 (Record Integrity Check). 1 optional loops are listed by their first segment.How the EDI 894 worksDelivery/Return Base Record: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 894SENDERDirect storedelivery (DSD)vendorRECEIVERRetail store997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY895Delivery/Return Acknowledgment orAdjustment997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code DX (GS … GE)Transaction set 894 (ST … SE)HEADINGG82Delivery/Return Base RecordIdentifierDETAIL+ 1 optional loop, starting with:G83SUMMARYG84Delivery/Return Record ofTotalsG86Signature IdentificationG85Record Integrity CheckBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 894. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 894, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 894 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Transmitting delivery details at store check-in
  • Recording returns picked up from the store
  • Supporting receiving without paper tickets

Where it fits in the document flow

This document 894 Delivery/Return Base Record
Usually followed by 895 Delivery/Return Acknowledgment or Adjustment997 Functional Acknowledgment

Structure

Mandatory segments in the 894 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • G82
  • G83
  • G84
  • G86
  • G85
  • SE

Practical example

The 894 in practice

A beverage company's driver arrives at a supermarket's back door. The handheld sends the store's receiving system an 894 with the items, quantities and prices delivered and the empty crates and outdated product being returned. The receiver checks the goods and the system responds with an 895.

Implementation

Implementation considerations for the 894

  • Use item and price data synchronized with the store's files.
  • Make the exchange work quickly at the back door.
  • Record returns separately from deliveries.
  • Reconcile receipts with the vendor's summary billing (882).

How ECOM helps

Automate the 894 with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related shipping and logistics documents

All 15 shipping and logistics documents

Need help with the EDI 894?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us