To start and identify an interchange of zero or more functional groups and interchange-related control segments
Kroger X12 894 Delivery/Return Base Record
X12 894 (Delivery/Return Base Record) is the EDI transaction exchanged between Kroger (Peyton's Group (a Kroger Division)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 2
- X12 894
- All partners ↗
Transaction context
Where 894 Delivery/Return Base Record fits on Peyton's Group (a Kroger Division)
- Kroger channels
- 1 of 2
- Trading partners
- 8
- Channels
- 8
1 of Kroger's 2 channels carries 894
partners across the Stacksync network trade 894
channels network-wide carry 894
Most common alongside 894
The 894 is the direct store delivery (DSD) equivalent of an invoice: a delivery or return record transmitted for check-in at the store, carrying the credit/debit flag, supplier delivery/return number, both parties' DUNS and location numbers, line items, costs, and off-invoice allowances. Retailers require it so store personnel can verify the delivery at the back door and reconcile it against the invoice before settlement. The DSD supplier or distributor sends the 894 to the retailer's store or headquarters system; the retailer responds with an 895 Delivery/Return Acknowledgment or Adjustment, or a 997.
When it fires: A route driver delivers product to, or collects returns from, a store on a DSD route and the delivery record must reach the retailer for check-in; some retailers expect it within 4 hours of delivery.
Common 894 rejection causes
- Invalid identifiers in the G82 header: Winn-Dixie rejects invoices with an invalid store number, and requires unique, numeric-only invoice numbers regardless of debit or credit.
- Negative values: costs and quantities must always be positive; the G82 credit/debit flag alone dictates whether the record is handled as a debit or a credit.
- Duplicate lines and identifiers: an item may appear only once per 894 (quantities rolled up into one line per UPC or SKU), and duplicate ISA control numbers are rejected.
- Line items without a UPC are rejected unless they are random-weight items, and commingling disallowed unit types on one invoice (for example case and each items together) fails the invoice at Winn-Dixie.
Specification summary
X12 894 Delivery/Return Base Record at the element level
The X12 894 specification defines 17 segments carrying 72 data elements, 45 of which are mandatory.
- Segments
- 17
- Data elements
- 72
- Mandatory elements
- 45
| Segment | Elements | Mandatory |
|---|---|---|
| G82 | 7 | 5 |
| N9 | 2 | 1 |
| LS | 1 | 1 |
| G83 | 11 | 3 |
| G72 | 8 | 2 |
| LE | 1 | 1 |
| G23 | 3 | 2 |
| G85 | 1 | 1 |
Key identifiers in 894
- Credit/Debit Flag Code
- Supplier's Delivery/Return Number
- D-U-N-S Number
- Supplier's Location Number
- Physical Delivery or Return Date
- Reference Identification Qualifier
- Loop Identifier Code
- Direct Store Delivery Sequence Number
Full segment guideline — 12 segments 2 loops · X12 894 Delivery/Return Base Record
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying numbers, dates, and other basic data relating to the transaction set
LS Loop Repeat: 1
To indicate that the next segment begins a loop
G83 Loop Repeat: 9,999
To specify the basic, and most frequently used line item data for the delivery record transaction
To specify allowances, charges, or services
To indicate that the loop immediately preceding this segment is complete
To specify summary details of total items in terms of quantity or amount
To transmit an electronic identity
To provide a secure method of identifying authenticity of record content
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
8+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
Kroger Peyton's Group (a Kroger Division) EDI 894 FAQ
Common questions about 894 Delivery/Return Base Record on the Peyton's Group (a Kroger Division) channel.
What is X12 894 Delivery/Return Base Record?
X12 894 (Delivery/Return Base Record) is the EDI transaction set used to exchange delivery/return base record data. Kroger's Peyton's Group (a Kroger Division) channel requires it from trading partners.
Does Kroger Peyton's Group (a Kroger Division) require 894 for trading partners?
Yes, Kroger (Peyton's Group (a Kroger Division)) supports X12 894 Delivery/Return Base Record. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Kroger 894 with Stacksync?
Most companies go live with Kroger 894 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 894 on Peyton's Group (a Kroger Division)?
On Peyton's Group (a Kroger Division), X12 894 is typically exchanged alongside 880 Grocery Products Invoice, 875 Grocery Products Purchase Order, 810 Invoice, 850 Purchase Order. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Kroger EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
