X12 transaction code
X12 876 Grocery Products Purchase Order Change
X12 876 Grocery Products Purchase Order Change: explore its business purpose, mapping identifiers, validation tests and 3 partner references across 4 listed channels.
- Standard
- X12
- Code
- 876
- Partner references
- 3
Implementation guide
X12 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.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| 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 |
|
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 partner 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.
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
Find your trading partner for X12 876
3 partners, 4 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 876 Grocery Products Purchase Order Change appears in this catalog
The largest groups of classified 876 catalog entries are in grocery & food.
By industry
- grocery & food 4 channels
By network
- SPS Commerce 2 channels
FAQ
X12 876 questions
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.
Which partners list X12 876?
The directory on this page links 3 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
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 linked from this page. 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 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.
