Skip to content
EDI X12 875

X12 transaction code

X12 875 Grocery Products Purchase Order

Stop Mapping. Start Trading.

Standard
X12
Code
875
Trading partners
34

Specification summary

X12 875 Grocery Products Purchase Order at the element level

The X12 875 specification defines 36 segments carrying 210 data elements, 60 of which are mandatory.

Segments
36
Data elements
210
Mandatory elements
60
Segments with mandatory elements
Segment Elements Mandatory
G50 5 3
N9 5 1
G61 5 2
NTE 2 1
G23 13 2
N1 4 1
N2 2 1
N3 2 1
G72 11 2
G73 1 1
G68 15 2
G69 1 1
Key identifiers in 875
  • Order Status Code
  • Date
  • Purchase Order Number
  • Reference Identification Qualifier
  • Contact Function Code
  • Name
  • Description
  • Terms Type Code

Trading partners that support X12 875

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

Usage breakdown

Who trades X12 875 Grocery Products Purchase Order

875 is used most heavily in grocery & food and consumer goods.

The 875 is the grocery industry's purchase order, defined under Uniform Communication Standard (UCS) conventions as a simpler alternative to the general-purpose 850, which carries more complexity than most grocery orders need. A retailer or wholesaler uses it to order finished grocery goods from a supplier or broker. The transaction is for order placement only; changes and acknowledgments travel on separate documents. A grocery retailer, wholesaler, or distributor sends the 875 to a food and beverage supplier, manufacturer, or broker to request delivery of finished goods. A grocery retailer's or wholesaler's replenishment system cuts a purchase order for finished goods for a store or distribution center and transmits it as an 875.

By industry

  • grocery & food 37 channels
  • consumer goods 1 channel

By network

  • Edict Systems 5 channels
  • SPS Commerce 3 channels

FAQ

X12 875 questions

What is X12 875 Grocery Products Purchase Order?

X12 875 (Grocery Products Purchase Order) is an EDI transaction set defined by ANSI ASC X12 for exchanging grocery products purchase order between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 34 Stacksync trading partners support this code across 38 channels.

Which trading partners use X12 875?

34 Stacksync partners accept X12 875: Affiliated Foods Inc., Albertsons (Safeway), Associated Food Stores (AFS), Associated Wholesale Grocers (AWG), Bashas' Supermarkets, Bozzuto’s Inc., C&S Wholesale Grocers Inc, CA Carlin, and more. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 875 with my ERP?

Stacksync handles the full X12 875 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.