To start and identify an interchange of zero or more functional groups and interchange-related control segments
HEB (Here Everything's Better) X12 876 Grocery Products Purchase Order Change
X12 876 (Grocery Products Purchase Order Change) is the EDI transaction exchanged between HEB (Here Everything's Better) (HEB (Here Everything's Better) (Standard)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 15
- Loops
- 3
- X12 876
- All partners ↗
Transaction context
Where 876 Grocery Products Purchase Order Change fits on HEB (Here Everything's Better) (Standard)
- HEB (Here Everything's Better) channels
- 1 of 1
- Trading partners
- 3
- Channels
- 4
1 of HEB (Here Everything's Better)'s 1 channel carries 876
partners across the Stacksync network trade 876
channels network-wide carry 876
Most common alongside 876
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.
When it fires: 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.
Common 876 rejection causes
- Sending delta or negative quantities instead of restating full new values, which conflicts with how the 876 defines changes and corrupts the order state.
- Change transactions referencing a purchase order number the supplier has no record of, or one already released to picking and shipping.
- Line items in the change that do not match the item identifiers on the original 875, so changes attach to the wrong lines or fail entirely.
- Missing or invalid purchase order change type codes, leaving the supplier unable to determine the nature of the requested change.
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 |
Key identifiers in 876
- Change or Response Type Code
- Date
- Purchase Order Number
- Reference Identification Qualifier
- Contact Function Code
- Name
- Description
- Terms Type Code
Full segment guideline — 15 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 specify pertinent dates and times
To transmit information in a free-form format, if necessary, for comment or special instruction
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify additional names or those longer than 35 characters in length
To specify the geographic place of the named party
G68 Loop Repeat: 9,999
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
G72 Loop Repeat: 100
To specify allowances, charges, or services
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)
Trading partners
8+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
HEB (Here Everything's Better) HEB (Here Everything's Better) (Standard) EDI 876 FAQ
Common questions about 876 Grocery Products Purchase Order Change on the HEB (Here Everything's Better) (Standard) channel.
What is X12 876 Grocery Products Purchase Order Change?
X12 876 (Grocery Products Purchase Order Change) is the EDI transaction set used to exchange grocery products purchase order change data. HEB (Here Everything's Better)'s HEB (Here Everything's Better) (Standard) channel requires it from trading partners.
Does HEB (Here Everything's Better) HEB (Here Everything's Better) (Standard) require 876 for trading partners?
Yes, HEB (Here Everything's Better) (HEB (Here Everything's Better) (Standard)) supports X12 876 Grocery Products Purchase Order Change. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate HEB (Here Everything's Better) 876 with Stacksync?
Most companies go live with HEB (Here Everything's Better) 876 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 876 on HEB (Here Everything's Better) (Standard)?
On HEB (Here Everything's Better) (Standard), X12 876 is typically exchanged alongside 850 Purchase Order, 856 Ship Notice Manifest, 810 Invoice, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your HEB (Here Everything's Better) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
