X12 transaction code
EDI 875 Grocery Products Purchase Order (X12 875)
EDI 875 is the X12 Grocery Products Purchase Order transaction set, used when a grocery buyer places an order. A grocery retailer, wholesaler, or distributor sends the 875 to a food and beverage supplier, manufacturer, or broker to request delivery of finished goods.
- Standard
- X12
- Code
- 875
- Partner references
- 34
At a glance
EDI 875 at a glance
What the 875 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 875 Grocery Products Purchase Order |
|---|---|
| Business record | Grocery purchase order |
| Who sends it to whom | 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 is sent | 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. |
| Match on | Purchase order, item and pack or unit basis |
| Partner references | 34 trading partners in this directory |
| Related documents | X12 880 Grocery Products Invoice, X12 876 Grocery Products Purchase Order Change |
Key segments in an EDI 875
The business segments that appear in at least half of the 38 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| G50 | Purchase Order Identification | To transmit identifying dates and numbers for this transaction set. | 38 of 38 |
| G62 | Date/Time | To specify pertinent dates and times. | 38 of 38 |
| G66 | Transportation Instructions | To specify transportation instructions relating to the shipment. | 38 of 38 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 38 of 38 |
| G68 | Line Item Detail - Product | To specify basic and most frequently used purchase order line item data. | 38 of 38 |
| G76 | Total Purchase Order | To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method. | 38 of 38 |
| G69 | Line Item Detail - Description | To describe an item in free-form format. | 37 of 38 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 36 of 38 |
| N3 | Party Location | To specify the location of the named party. | 35 of 38 |
| G72 | Allowance or Charge | To specify allowances, charges, or services. | 34 of 38 |
Stacksync connects EDI documents such as the X12 875 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 875 mapping and validation
X12 875 Grocery Products Purchase Order is used when a grocery buyer places an order. Preserve purchase order, item and pack or unit basis so the grocery purchase order in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | grocery purchase order purchase order, item and pack or unit basis |
|
| Update the receiving system | Processing the grocery purchase order ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the grocery purchase order Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 880 Grocery Products Invoice
grocery invoice: grocery goods are ready for detail billing.
- X12 876 Grocery Products Purchase Order Change
grocery order change: a grocery buyer revises an order.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a grocery buyer places an order. Name the operational owner of the grocery purchase order and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map purchase order, item and pack or unit basis. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic grocery purchase order data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful grocery purchase order processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 875 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic grocery purchase order data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out grocery purchase order without processing it twice.
Document structure
X12 875 Grocery Products Purchase Order at the element level
The X12 875 reference contains 36 segment entries and 210 data elements; 60 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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 |
- Order Status Code
- Date
- Purchase Order Number
- Reference Identification Qualifier
- Contact Function Code
- Name
- Description
- Terms Type Code
Find your trading partner for X12 875
34 partners, 38 channels. Choose a channel to inspect its listed document reference and implementation context.
- 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
- Certco Inc.
- Core-Mark (via SPS Commerce)
- DeMoulas Super Markets, Inc
- Harris Teeter
- HEB (Here Everything's Better)
- Heinens
- Ingles Markets Inc
- Kroger
- Kroger Modernized Systems
- Labatt Food Service
- McLane Company, Inc.
- Meijer
- Merchant Distributors
- Piggly Wiggly
- Publix
- Schnucks
- Spartan Nash (dba Nash Finch)
- SpartanNash
- Sprouts Farmers Market
- Stater Bros. Markets
- Super Store Industries
- United Supermarkets
- URM Stores
- Wakefern
- Wegmans Food Markets, Inc.
- WinCo
Catalog breakdown
Where X12 875 Grocery Products Purchase Order appears in this catalog
The largest groups of classified 875 catalog entries are in grocery & food and consumer goods.
By industry
- grocery & food 37 channels
- consumer goods 1 channel
By network
- Edict Systems 5 channels
- SPS Commerce 3 channels
FAQ
EDI 875 questions
What is an EDI 875?
EDI 875 is the X12 Grocery Products Purchase Order transaction set. Trading partners use it when a grocery buyer places an order. It carries the data for the grocery purchase order, and your system matches it on purchase order, item and pack or unit basis.
Who sends an EDI 875 and who receives it?
A grocery retailer, wholesaler, or distributor sends the 875 to a food and beverage supplier, manufacturer, or broker to request delivery of finished goods. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 875 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 875?
Across 38 partner document references listed here, the business segments that appear most often include G50 (Purchase Order Identification), G62 (Date/Time), G66 (Transportation Instructions), N1 (Party Identification), G68 (Line Item Detail - Product), G76 (Total Purchase Order). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 875 and EDI 880?
The 875 carries the grocery purchase order and is used when a grocery buyer places an order. The 880 carries the grocery invoice and is used when grocery goods are ready for detail billing.
What should I map for X12 875?
Start with purchase order, item and pack or unit basis and the target grocery purchase order. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 875 error handling?
Test catch-weight or variable-quantity items using the units agreed in the partner guide. Separate case quantities from each quantities during sales-order creation. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 875?
The directory on this page links 34 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
