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 · Catalogs and pricing

EDI 879 Price Information

The X12 document a manufacturer, supplier, broker or agent uses to give a trading partner pricing information, mainly in grocery and consumer goods.

Sent by
Manufacturer, supplier, broker or agent
Received by
Retailer, wholesaler or distributor
Standard
ANSI ASC X12
EDIFACT equivalent
PRICAT

What is an EDI 879?

The EDI 879 Price Information is the ANSI X12 transaction set that lets a manufacturer, supplier, broker or agent provide a trading partner with pricing information. It belongs to the grocery and consumer goods family of transaction sets, alongside the 888 item maintenance and 889 promotion announcement, and uses grocery-style G-segments.

Pricing sent by 879 typically includes list costs, the dates they take effect and the items they apply to. Buyers load it so that their orders carry the correct cost and supplier invoices match without deductions.

How the EDI 879 worksDiagram of the EDI 879 Price Information. Manufacturer, supplier, broker or agent sends it to retailer, wholesaler or distributor. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G91 (Price Change Status), the required 0100 loop with N1 (Party Identification) and G62 (Date/Time) and detail: the required 0200 loop with G28 (Line Item Numbers). 2 optional loops are listed by their first segment.How the EDI 879 worksPrice Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 879SENDERManufacturer,supplier, broker oragentRECEIVERRetailer, wholesaler ordistributor997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code QGGS … GETransaction set 879ST … SEHEADINGG91Price Change StatusRequired loop 0100 · repeats up to 999N1Party IdentificationG62Date/Time+ 1 optional loop, starting with:G93DETAILRequired loop 0200 · repeats many timesG28Line Item Numbers+ 1 optional loop, starting with:G40Blue 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 879. Your trading partner's implementation guide adds its own requirements.
How the EDI 879 worksDiagram of the EDI 879 Price Information. Manufacturer, supplier, broker or agent sends it to retailer, wholesaler or distributor. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G91 (Price Change Status), the required 0100 loop with N1 (Party Identification) and G62 (Date/Time) and detail: the required 0200 loop with G28 (Line Item Numbers). 2 optional loops are listed by their first segment.How the EDI 879 worksPrice Information: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 879SENDERManufacturer,supplier, brokeror agentRECEIVERRetailer,wholesaler ordistributor997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code QG (GS … GE)Transaction set 879 (ST … SE)HEADINGG91Price Change StatusRequired loop 0100 · repeats upto 999N1Party IdentificationG62Date/Time+ 1 optional loop, starting with:G93DETAILRequired loop 0200 · repeatsmany timesG28Line Item Numbers+ 1 optional loop, starting with:G40Blue 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 879. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 879, 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 879 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

  • Announcing new list costs and effective dates
  • Sending price changes for existing items
  • Keeping a broker's or distributor's pricing current

Where it fits in the document flow

This document 879 Price Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 879 (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
  • G91
  • N1
  • G62
  • G93
  • G28
  • G40
  • SE

Practical example

The 879 in practice

A snack manufacturer raises list costs on a product line from the first of next month. It sends an 879 to each wholesale customer with the affected items, the new costs and the effective date. The wholesalers load the costs into their purchasing systems, so orders placed after that date carry the new cost and invoices match.

Implementation

Implementation considerations for the 879

  • Send price information well before the effective date so partners can load and approve it.
  • Use the same item identifiers and units of measure that orders and invoices use.
  • Agree with each partner whether pricing travels in the 879, the 832 or both.

How ECOM helps

Automate the 879 with ECOM

Industry

Food and Beverage

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

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

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 catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 879?

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

Request a Demo Contact us