To start and identify an interchange of zero or more functional groups and interchange-related control segments
Stater Bros. Markets X12 895 Delivery/Return Acknowledgment or Adjustment
Plan X12 895 Delivery/Return Acknowledgment or Adjustment 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 895
- Partner references ↗
Implementation guide
Stater Bros. Markets: 895 mapping and validation
X12 895 Delivery/Return Acknowledgment or Adjustment is used when delivery or return quantities are acknowledged or adjusted. Preserve original delivery, response and affected item so the delivery or return response 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 response original delivery, response and affected item |
|
| Update the receiving system | Processing the delivery or return response ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the delivery or return response 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 894 Delivery Return Base Record
delivery or return base record: delivery or return details establish a reconciliation baseline.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when delivery or return quantities are acknowledged or adjusted. Name the operational owner of the delivery or return response and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original delivery, response and affected 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 response 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 response processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 895 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic delivery or return response 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 response without processing it twice.
Transaction context
Where 895 Delivery/Return Acknowledgment or Adjustment fits on Stater Bros. Markets
- Stater Bros. Markets channels
- 1 of 1
1 of Stater Bros. Markets's 1 channel list 895
- Trading partners
- 1
partner references list 895
- Channels
- 1
channel entries list 895
Document structure
X12 895 Delivery/Return Acknowledgment or Adjustment at the element level
The X12 895 reference contains 15 segment entries and 65 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 15
- Data elements
- 65
- Mandatory elements
- 40
| Segment | Elements | Mandatory |
|---|---|---|
| G87 | 6 | 5 |
| LS | 1 | 1 |
| G89 | 7 | 1 |
| G72 | 7 | 2 |
| LE | 1 | 1 |
| G23 | 11 | 2 |
| G85 | 1 | 1 |
- Initiator Code
- Credit/Debit Flag Code
- Supplier's Delivery/Return Number
- Integrity Check Value
- Adjustment Number
- Loop Identifier Code
- Direct Store Delivery Sequence Number
- Allowance or Charge Code
Segment reference — 13 segments 2 loops · X12 895 Delivery/Return Acknowledgment or Adjustment
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
To indicate that the next segment begins a loop
To transmit line-item detail adjustments
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.
Showing 5 of 5 references
Browse the full directoryStater Bros. Markets EDI 895 questions
Common questions about 895 Delivery/Return Acknowledgment or Adjustment on the Stater Bros. Markets channel.
What is X12 895 Delivery/Return Acknowledgment or Adjustment used for?
895 is used when delivery or return quantities are acknowledged or adjusted. It carries information for the delivery or return response. Match it to your business system using original delivery, response and affected item.
Is 895 required for Stater Bros. Markets?
895 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 895?
Start with original delivery, response and affected item and the target delivery or return response. 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 895 error handling?
Apply an adjustment to the correct base-record line. Test multiple responses without applying the same quantity correction twice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 895 relate to other EDI messages?
X12 894 Delivery Return Base Record 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 895 and 894?
895 is used when delivery or return quantities are acknowledged or adjusted. 894 is used when delivery or return details establish a reconciliation baseline. 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.




