Skip to content
EDI X12 879

X12 transaction code

X12 879 Price Information

Stop Mapping. Start Trading.

Standard
X12
Code
879
Trading partners
2

Specification summary

X12 879 Price Information at the element level

The X12 879 specification defines 20 segments carrying 67 data elements, 38 of which are mandatory.

Segments
20
Data elements
67
Mandatory elements
38
Segments with mandatory elements
Segment Elements Mandatory
G91 1 1
N1 4 1
G61 4 2
NTE 2 1
G36 2 2
G69 1 1
G43 3 1
G46 5 2
G40 5 1
Key identifiers in 879
  • Change Type Code
  • Entity Identifier Code
  • Contact Function Code
  • Name
  • Description
  • Price List Number
  • Date
  • Free-form Description

Trading partners that support X12 879

2 partners, 2 channels. Click a channel for the full segment guideline.

Usage breakdown

Who trades X12 879 Price Information

879 is used most heavily in grocery & food.

The 879 carries item cost data between grocery trading partners: original prices for new items, changes to existing prices, and confirmations that pricing was received. Buyers load it into their cost files ahead of orders so later invoices match on price, which reduces deductions and invoice-matching disputes. It follows UCS grocery guidelines; general merchandise retailers typically carry the same data on an 832 Price/Sales Catalog. A supplier, manufacturer, or broker sends the 879 to a retailer, distributor, or buying organization, which confirms receipt with a 997 Functional Acknowledgment. A supplier creates a new item or approves a cost change in its ERP and must publish the price and its effective date to buyers before orders and invoices reference it.

By industry

  • grocery & food 2 channels

By network

  • SPS Commerce 1 channel
Largest 879 implementations

FAQ

X12 879 questions

What is X12 879 Price Information?

X12 879 (Price Information) is an EDI transaction set defined by ANSI ASC X12 for exchanging price information between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 2 Stacksync trading partners support this code across 2 channels.

Which trading partners use X12 879?

2 Stacksync partners accept X12 879: Harbor Foods, Thrive Market. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 879 with my ERP?

Stacksync handles the full X12 879 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.

Ready to automate your EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.