Skip to content
X12 EDI

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.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record delivery or return response

original delivery, response and affected item

  • Define which combination of original delivery, response and affected item identifies one business record, its lines and any later revision.
Update the receiving system Processing the delivery or return response

ID assigned by the receiving system and processing result

  • Apply an adjustment to the correct base-record line.
  • Test multiple responses without applying the same quantity correction twice.
Check the processing result Processing status for the delivery or return response

Original document reference and matching response

  • Reconcile the delivery or return response with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

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.

Implementation steps

  1. 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.

  2. 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.

  3. 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.

  4. 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
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
G87 6 5
LS 1 1
G89 7 1
G72 7 2
LE 1 1
G23 11 2
G85 1 1
Key identifiers in 895
  • 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
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

G87 Delivery/Return Adjustment Identification 6 elements

To transmit identifying numbers, dates, and other basic data relating to the transaction set

LS Loop Repeat: 1
LS Loop Header 1 element

To indicate that the next segment begins a loop

G89 Loop Repeat: 9,999
G89 Line-Item Detail Adjustment 7 elements

To transmit line-item detail adjustments

G72 Allowance or Charge 7 elements

To specify allowances, charges, or services

LE Loop Trailer 1 element

To indicate that the loop immediately preceding this segment is complete

G23 Terms of Sale 11 elements

To specify the terms of sale

G84 Delivery/Return Record of Totals 3 elements

To specify summary details of total items in terms of quantity or amount

G86 Signature 1 element

To transmit an electronic identity

G85 Record Integrity Check 1 element

To provide a secure method of identifying authenticity of record content

SE Transaction Set Trailer 2 elements

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.

Stater 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.