X12 transaction code
EDI 876 Grocery Products Purchase Order Change (X12 876)
EDI 876 is the X12 Grocery Products Purchase Order Change transaction set, used when a grocery buyer revises an order. The grocery retailer or wholesaler that placed the original 875 sends the 876 to the supplier to modify that order.
- Standard
- X12
- Code
- 876
- Partner references
- 3
At a glance
EDI 876 at a glance
What the 876 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 876 Grocery Products Purchase Order Change |
|---|---|
| Business record | Grocery order change |
| Who sends it to whom | The grocery retailer or wholesaler that placed the original 875 sends the 876 to the supplier to modify that order. |
| When it is sent | 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. |
| Match on | Original grocery order, revision and item |
| Partner references | 3 trading partners in this directory |
| Related documents | X12 875 Grocery Products Purchase Order, X12 880 Grocery Products Invoice |
Key segments in an EDI 876
The business segments that appear in at least half of the 4 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| G92 | Purchase Order Change Type | To identify the reason for a change to a previously transmitted purchase order. | 4 of 4 |
| G62 | Date/Time | To specify pertinent dates and times. | 4 of 4 |
| NTE | Note/Special Instruction | To transmit information in a free-form format, if necessary, for comment or special instruction. | 4 of 4 |
| N1 | Name | To identify a party by type of organization, name, and code. | 4 of 4 |
| G68 | Line Item Detail - Product | To specify basic and most frequently used purchase order line item data. | 4 of 4 |
| G69 | Line Item Detail - Description | To describe an item in free-form format. | 4 of 4 |
| G70 | Line Item Detail - Miscellaneous | To provide for miscellaneous information relative to a line item. | 4 of 4 |
| G72 | Allowance or Charge | To specify allowances, charges, or services. | 4 of 4 |
| G76 | Total Purchase Order | To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method. | 4 of 4 |
| N9 | Extended Reference Information | To transmit identifying information as specified by the Reference Identification Qualifier. | 3 of 4 |
Stacksync connects EDI documents such as the X12 876 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
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
EDI 876 questions
What is an EDI 876?
EDI 876 is the X12 Grocery Products Purchase Order Change transaction set. Trading partners use it when a grocery buyer revises an order. It carries the data for the grocery order change, and your system matches it on original grocery order, revision and item.
Who sends an EDI 876 and who receives it?
The grocery retailer or wholesaler that placed the original 875 sends the 876 to the supplier to modify that order. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 876 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 876?
Across 4 partner document references listed here, the business segments that appear most often include G92 (Purchase Order Change Type), G62 (Date/Time), NTE (Note/Special Instruction), N1 (Name), G68 (Line Item Detail - Product), G69 (Line Item Detail - Description). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 876 and EDI 875?
The 876 carries the grocery order change and is used when a grocery buyer revises an order. The 875 carries the grocery purchase order and is used when a grocery buyer places an order.
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.
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.
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.
