972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Ordering

EDI 876 Grocery Products Purchase Order Change

The X12 document grocery retailers and wholesalers use to change a grocery purchase order they have already sent to a supplier.

Sent by
Grocery retailer or wholesaler
Received by
Supplier, manufacturer or broker
Standard
ANSI ASC X12
EDIFACT equivalent
ORDCHG

What is an EDI 876?

The EDI 876 Grocery Products Purchase Order Change is the ANSI X12 transaction set grocery retailers and wholesalers use to request changes to a purchase order for finished goods that was already sent, usually as an 875. It follows grocery-industry practice and uses the grocery G-segments rather than the segments of the general 860.

Changes are made by restating the values that change, such as quantities, items, allowances or dates. Because grocery orders feed tightly scheduled warehouse and transport plans, suppliers need to apply each change to the original order quickly and accurately.

How the EDI 876 worksDiagram of the EDI 876 Grocery Products Purchase Order Change. Grocery retailer or wholesaler sends it to supplier, manufacturer or broker. It usually follows 875. It is usually followed by 997 and 856. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G92 (Purchase Order Change Type) and the required 0100 loop with N1 (Party Identification). 2 optional loops are listed by their first segment.How the EDI 876 worksGrocery Products Purchase Order Change: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS875Grocery ProductsPurchase OrderEDI 876SENDERGrocery retailer orwholesalerRECEIVERSupplier, manufactureror broker997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment856Advance Ship Notice2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code OGGS … GETransaction set 876ST … SEHEADINGG92Purchase Order Change TypeRequired loop 0100 · repeats many timesN1Party Identification+ 1 optional loop, starting with:G72DETAIL+ 1 optional loop, starting with:G68Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 876. Your trading partner's implementation guide adds its own requirements.
How the EDI 876 worksDiagram of the EDI 876 Grocery Products Purchase Order Change. Grocery retailer or wholesaler sends it to supplier, manufacturer or broker. It usually follows 875. It is usually followed by 997 and 856. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G92 (Purchase Order Change Type) and the required 0100 loop with N1 (Party Identification). 2 optional loops are listed by their first segment.How the EDI 876 worksGrocery Products Purchase Order Change: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS875Grocery Products Purchase OrderEDI 876SENDERGrocery retaileror wholesalerRECEIVERSupplier,manufacturer orbroker997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment856Advance Ship Notice2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code OG (GS … GE)Transaction set 876 (ST … SE)HEADINGG92Purchase Order Change TypeRequired loop 0100 · repeatsmany timesN1Party Identification+ 1 optional loop, starting with:G72DETAIL+ 1 optional loop, starting with:G68Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 876. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 876, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 876 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Changing quantities on an open grocery order
  • Adding or removing items before shipment
  • Updating allowances, charges or dates on an order

Where it fits in the document flow

Usually follows 875 Grocery Products Purchase Order
This document 876 Grocery Products Purchase Order Change
Usually followed by 997 Functional Acknowledgment856 Advance Ship Notice

Structure

Mandatory segments in the 876 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • G92
  • N1
  • G72
  • G68
  • SLN
  • SE

Practical example

The 876 in practice

A grocery wholesaler sent an 875 for 80 cases of two soup items. A day later, demand forecasts drop, so it sends an 876 restating the quantity of one item as 40 cases. The supplier's system matches the change to the original order number, reduces the quantity on its sales order and ships 40 cases, so the invoice and receipt agree.

Implementation

Implementation considerations for the 876

  • Match every change to the original order number and apply it as an update, never as a new order.
  • Read restated values carefully, because the 876 states the new value rather than the difference.
  • Route changes that arrive after picking has started to a person for review.

How ECOM helps

Automate the 876 with ECOM

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

Solution

Order-to-Cash Automation

Automate the flow from purchase order to payment across every customer channel.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related ordering documents

All 13 ordering documents

Need help with the EDI 876?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us