---
title: "EDI 876 Grocery Products Purchase Order Change | Stacksync"
description: "EDI 876 is the X12 Grocery Products Purchase Order Change, used when a grocery buyer revises an order. See key segments (G92, G62, NTE) and mapping checks."
canonical: https://www.stacksync.com/edi/x12/876-grocery-products-purchase-order-change
last_modified: 2026-09-29
---

X12 transaction code

# EDI 876 Grocery Products Purchase Order Change (X12 876)

> For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md

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

[Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi)

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.

**X12 876 Grocery Products Purchase Order Change summary**

|  |  |
| --- | --- |
| 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](https://www.stacksync.com/edi/x12/875-grocery-products-purchase-order), [X12 880 Grocery Products Invoice](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/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.

**Map records and test the business result**

| Document or decision | Record and matching IDs | What to test |
| --- | --- | --- |
| Match the business record | **grocery order change** original grocery order, revision and item | Define which combination of original grocery order, revision and item identifies one business record, its lines and any later revision. |
| Update the receiving system | **Processing the grocery order change** ID assigned by the receiving system and processing result | Apply a pack-quantity change to the original order line. Test a late reduction after warehouse picking and require operational review. |
| Check the processing result | **Processing status for the grocery order change** Original document reference and matching response | Reconcile the grocery order change with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. |

### 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](https://www.stacksync.com/edi/x12/875-grocery-products-purchase-order)

  **grocery purchase order:** a grocery buyer places an order.
- [X12 880 Grocery Products Invoice](https://www.stacksync.com/edi/x12/880-grocery-products-invoice)

  **grocery invoice:** grocery goods are ready for detail billing.

### Implementation steps

1. #### 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.
2. #### 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.
3. #### 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.
4. #### 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.

### Related documents and resources

- [X12 875 Grocery Products Purchase Order](https://www.stacksync.com/edi/x12/875-grocery-products-purchase-order)
- [X12 880 Grocery Products Invoice](https://www.stacksync.com/edi/x12/880-grocery-products-invoice)
- [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook)
- [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist)

**Sources.** Sources reviewed 2026-09-15.

- [X12 transaction-set directory](https://x12.org/products/transaction-sets)
- [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/)

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

**Segments with elements marked mandatory in this reference**

| 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

## Find your trading partner for X12 876

3 partners, 4 channels. Choose a channel to inspect its listed document reference and implementation context.

- [HEB (Here Everything's Better)](https://www.stacksync.com/edi/heb-here-everythings-better)

  [HEB (Here Everything's Better) (Standard)](https://www.stacksync.com/edi/heb-here-everythings-better/heb-here-everything-s-better-standard/x12-876-grocery-products-purchase-order-change)
- [Kroger Modernized Systems](https://www.stacksync.com/edi/kroger-modernized-systems)

  [Kroger Modernized Systems](https://www.stacksync.com/edi/kroger-modernized-systems/kroger-modernized-systems/x12-876-grocery-products-purchase-order-change)
- [Sprouts Farmers Market](https://www.stacksync.com/edi/sprouts-farmers-market)

  [Sprouts Farmers Market (Produce) (via SPS Commerce)](https://www.stacksync.com/edi/sprouts-farmers-market/sprouts-farmers-market-produce-via-sps-commerce/x12-876-grocery-products-purchase-order-change) [Sprouts Farmers Market (via SPS Commerce)](https://www.stacksync.com/edi/sprouts-farmers-market/sprouts-farmers-market-via-sps-commerce/x12-876-grocery-products-purchase-order-change)

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

Partner entries with the most listed channels

- [Sprouts Farmers Market](https://www.stacksync.com/edi/sprouts-farmers-market)
- [HEB (Here Everything's Better)](https://www.stacksync.com/edi/heb-here-everythings-better)
- [Kroger Modernized Systems](https://www.stacksync.com/edi/kroger-modernized-systems)

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.

[Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)