X12 transaction code
X12 876 Grocery Products Purchase Order Change
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 876
- Trading partners
- 3
Specification summary
X12 876 Grocery Products Purchase Order Change at the element level
The X12 876 specification defines 24 segments carrying 80 data elements, 46 of which are mandatory.
- 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
Trading partners that support X12 876
3 partners, 4 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 876 Grocery Products Purchase Order Change
876 is used most heavily in grocery & food.
The 876 communicates changes to a grocery purchase order previously sent as an 875, covering quantity adjustments, item additions and deletions, and date changes. Changes are made by restating the new full value of each affected element rather than sending a delta, and deleting an item is done by restating its ordered quantity to zero. Partners require it so the supplier picks and ships against the current version of the order. The grocery retailer or wholesaler that placed the original 875 sends the 876 to the supplier to modify that order. A buyer revises a submitted grocery purchase order before fulfillment, for example a demand shift, an item cut, or a delivery date move, and transmits the revision as an 876.
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?
X12 876 (Grocery Products Purchase Order Change) is an EDI transaction set defined by ANSI ASC X12 for exchanging grocery products purchase order change between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 3 Stacksync trading partners support this code across 4 channels.
Which trading partners use X12 876?
3 Stacksync partners accept X12 876: HEB (Here Everything's Better), Kroger Modernized Systems, Sprouts Farmers Market. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 876 with my ERP?
Stacksync handles the full X12 876 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
