To start and identify an interchange of zero or more functional groups and interchange-related control segments
Sprouts Farmers Market X12 876 Grocery Products Purchase Order Change
Plan X12 876 Grocery Products Purchase Order Change for Sprouts Farmers Market (Produce) (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 20
- Loops
- 3
- X12 876
- Partner references ↗
Implementation guide
Sprouts Farmers Market (Produce) (via SPS Commerce): 876 mapping and validation
X12 876 Grocery Products Purchase Order Change is used when a grocery buyer revises an order. Preserve original grocery order, revision and item so the grocery order change in your business system stays connected to the original document.
This document is listed for Sprouts Farmers Market (Produce) (via SPS Commerce). 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 | grocery order change original grocery order, revision and item |
|
| Update the receiving system | Processing the grocery order change ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the grocery order change Original document reference and matching response |
|
The document reference includes 20 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 875 Grocery Products Purchase Order
grocery purchase order: a grocery buyer places an order.
- X12 880 Grocery Products Invoice
grocery invoice: grocery goods are ready for detail billing.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a grocery buyer revises an order. Name the operational owner of the grocery order change and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original grocery order, revision and item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Sprouts Farmers Market guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic grocery order change 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 grocery order change processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 876 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic grocery order change 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 grocery order change without processing it twice.
Transaction context
Where 876 Grocery Products Purchase Order Change fits on Sprouts Farmers Market (Produce) (via SPS Commerce)
- Sprouts Farmers Market channels
- 2 of 2
2 of Sprouts Farmers Market's 2 channels list 876
- Trading partners
- 3
partner references list 876
- Channels
- 4
channel entries list 876
The directory associates SPS Commerce and 876 with 2 channels.
Document structure
X12 876 Grocery Products Purchase Order Change at the element level
The X12 876 reference contains 24 segment entries and 80 data elements; 46 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 24
- Data elements
- 80
- Mandatory elements
- 46
| Segment | Elements | Mandatory |
|---|---|---|
| G92 | 3 | 3 |
| N9 | 2 | 1 |
| G61 | 4 | 2 |
| NTE | 2 | 1 |
| G23 | 6 | 2 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| G68 | 9 | 2 |
| G69 | 1 | 1 |
| G72 | 3 | 2 |
| G73 | 1 | 1 |
- Change or Response Type Code
- Date
- Purchase Order Number
- Reference Identification Qualifier
- Contact Function Code
- Name
- Description
- Terms Type Code
Segment reference — 20 segments 3 loops · X12 876 Grocery Products Purchase Order Change
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 identify the reason for a change to a previously transmitted purchase order
To transmit identifying information as specified by the Reference Identification Qualifier
To identify a person or office to whom communications should be directed
To specify pertinent dates and times
To transmit information in a free-form format, if necessary, for comment or special instruction
To specify transportation instructions relating to the shipment
To specify the terms of sale
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To specify basic and most frequently used purchase order line item data
To describe an item in free-form format
To provide for miscellaneous information relative to a line item
To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify allowances, charges, or services
To describe the allowance or charge in free-form format
Related references
876 Grocery Products Purchase Order Change on other Sprouts Farmers Market channels
Compare the listed channel references and confirm their current implementation guides.
Related references
Other transactions in Sprouts Farmers Market (Produce) (via SPS Commerce)
Other EDI documents listed on this channel.
Showing 8 of 8 references
Browse the full directorySprouts Farmers Market (Produce) (via SPS Commerce) EDI 876 questions
Common questions about 876 Grocery Products Purchase Order Change on the Sprouts Farmers Market (Produce) (via SPS Commerce) channel.
What is X12 876 Grocery Products Purchase Order Change used for?
876 is used when a grocery buyer revises an order. It carries information for the grocery order change. Match it to your business system using original grocery order, revision and item.
Is 876 required for Sprouts Farmers Market (Produce) (via SPS Commerce)?
876 is listed for Sprouts Farmers Market (Produce) (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 876?
Start with original grocery order, revision and item and the target grocery order change. 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 876 error handling?
Apply a pack-quantity change to the original order line. Test a late reduction after warehouse picking and require operational review. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 876 relate to other EDI messages?
X12 875 Grocery Products Purchase Order; X12 880 Grocery Products Invoice are related documents also listed on Sprouts Farmers Market (Produce) (via SPS Commerce). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 876 and 875?
876 is used when a grocery buyer revises an order. 875 is used when a grocery buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Sprouts Farmers Market 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.




