To start and identify an interchange of zero or more functional groups and interchange-related control segments
Wakefern X12 875 Grocery Products Purchase Order
X12 875 (Grocery Products Purchase Order) is the EDI transaction exchanged between Wakefern (Wakefern Warehouse & DSD) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 3
- X12 875
- All partners ↗
Transaction context
Where 875 Grocery Products Purchase Order fits on Wakefern Warehouse & DSD
On Wakefern Warehouse & DSD, the X12 875 Grocery Products Purchase Order precedes the 880 Grocery Products Invoice in the Grocery replenishment cycle.
- Wakefern channels
- 2 of 2
- Trading partners
- 34
- Channels
- 38
2 of Wakefern's 2 channels carry 875
partners across the Stacksync network trade 875
channels network-wide carry 875
Most common alongside 875
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.
When it fires: 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.
Common 875 rejection causes
- Item identifiers (UPC or case codes) not on the supplier's item master, causing rejected or manually reworked order lines.
- Mapping the 875 with general-merchandise 850 conventions instead of grocery UCS segments such as G50 (order header) and G68 (line item detail).
- Ordered quantities expressed in the wrong pack or case unit of measure, so the supplier ships a different total than the buyer intended.
- Missing or late 997 Functional Acknowledgment, leaving the retailer unsure the order was received.
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
| 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
Full segment guideline — 16 segments 3 loops · X12 875 Grocery Products Purchase Order
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying dates and numbers for this transaction set
To specify pertinent dates and times
To transmit information in a free-form format, if necessary, for comment or special instruction
To specify transportation instructions relating to the shipment
To specify the terms of sale
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
G68 Loop Repeat: 9,999
To specify basic and most frequently used purchase order line item data
To describe an item in free-form format
G72 Loop Repeat: 100
To specify allowances, charges, or services
To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
1+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
Trading partners
6+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order TE Text Message PU Purchase Order Acknowledgment IN Invoice GR Grocery Products Invoice SH Ship Notice Manifest
No trading partner matches your search.
Browse the full directory
Wakefern Wakefern Warehouse & DSD EDI 875 FAQ
Common questions about 875 Grocery Products Purchase Order on the Wakefern Warehouse & DSD channel.
What is X12 875 Grocery Products Purchase Order?
X12 875 (Grocery Products Purchase Order) is the EDI transaction set used to exchange grocery products purchase order data. Wakefern's Wakefern Warehouse & DSD channel requires it from trading partners.
Does Wakefern Wakefern Warehouse & DSD require 875 for trading partners?
Yes, Wakefern (Wakefern Warehouse & DSD) supports X12 875 Grocery Products Purchase Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Wakefern 875 with Stacksync?
Most companies go live with Wakefern 875 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Wakefern channels accept 875?
X12 875 runs on 2 of Wakefern's 2 channels. Besides Wakefern Warehouse & DSD, it is accepted on Wakefern Warehouse & DSD (UCS). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your Wakefern EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
