To start and identify an interchange of zero or more functional groups and interchange-related control segments
Stater Bros. Markets X12 894 Delivery/Return Base Record
Plan X12 894 Delivery/Return Base Record for Stater Bros. Markets. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 13
- Loops
- 2
- X12 894
- Partner references ↗
Implementation guide
Stater Bros. Markets: 894 mapping and validation
X12 894 Delivery/Return Base Record is used when delivery or return details establish a reconciliation baseline. Preserve delivery reference, store and item so the delivery or return base record in your business system stays connected to the original document.
This document is listed for Stater Bros. Markets. Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | delivery or return base record delivery reference, store and item |
|
| Update the receiving system | Processing the delivery or return base record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the delivery or return base record Original document reference and matching response |
|
The document reference includes 13 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 895 Delivery Return Acknowledgment Or Adjustment
delivery or return response: delivery or return quantities are acknowledged or adjusted.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when delivery or return details establish a reconciliation baseline. Name the operational owner of the delivery or return base record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map delivery reference, store and item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Stater Bros. Markets guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic delivery or return base record data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful delivery or return base record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 894 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic delivery or return base record data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out delivery or return base record without processing it twice.
Transaction context
Where 894 Delivery/Return Base Record fits on Stater Bros. Markets
- Stater Bros. Markets channels
- 1 of 1
1 of Stater Bros. Markets's 1 channel list 894
- Trading partners
- 8
partner references list 894
- Channels
- 8
channel entries list 894
Frequently listed alongside 894
Document structure
X12 894 Delivery/Return Base Record at the element level
The X12 894 reference contains 17 segment entries and 72 data elements; 45 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Segment reference — 13 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 the terms of sale
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)
Related references
Other transactions in Stater Bros. Markets
Other EDI documents listed on this channel.
Grocery Products Invoice X12 880 Grocery Products Purchase Order X12 875 Shipment And Billing Notice X12 857 Delivery Return Acknowledgment Or Adjustment X12 895 Product Activity Data X12 852
No references match your search.
Showing 5 of 5 references
Browse the full directoryStater Bros. Markets EDI 894 questions
Common questions about 894 Delivery/Return Base Record on the Stater Bros. Markets channel.
What is X12 894 Delivery/Return Base Record used for?
894 is used when delivery or return details establish a reconciliation baseline. It carries information for the delivery or return base record. Match it to your business system using delivery reference, store and item.
Is 894 required for Stater Bros. Markets?
894 is listed for Stater Bros. Markets. Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 894?
Start with delivery reference, store and item and the target delivery or return base record. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 894 error handling?
Separate returned units from delivered units when calculating the net quantity. Retain the original delivery record when a receiving party later disputes a quantity. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 894 relate to other EDI messages?
X12 895 Delivery Return Acknowledgment Or Adjustment is a related document also listed on Stater Bros. Markets. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 894 and 895?
894 is used when delivery or return details establish a reconciliation baseline. 895 is used when delivery or return quantities are acknowledged or adjusted. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Stater Bros. Markets EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
