To start and identify an interchange of zero or more functional groups and interchange-related control segments
Piggly Wiggly X12 875 Grocery Products Purchase Order
Plan X12 875 Grocery Products Purchase Order for Piggly Wiggly Midwest (via Edict Systems). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 16
- Loops
- 3
- X12 875
- Partner references ↗
Implementation guide
Piggly Wiggly Midwest (via Edict Systems): 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.
This document is listed for Piggly Wiggly Midwest (via Edict Systems). Confirm the version, required fields and responses that apply to your account.
| 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 |
|
The document reference includes 16 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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.
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 Piggly Wiggly 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.
Transaction context
Where 875 Grocery Products Purchase Order fits on Piggly Wiggly Midwest (via Edict Systems)
On Piggly Wiggly Midwest (via Edict Systems), the X12 875 Grocery Products Purchase Order can precede the 880 Grocery Products Invoice in an example Grocery replenishment cycle. Confirm the required sequence for your trading agreement.
- Piggly Wiggly channels
- 2 of 2
2 of Piggly Wiggly's 2 channels list 875
- Trading partners
- 34
partner references list 875
- Channels
- 38
channel entries list 875
Frequently listed alongside 875
The directory associates Edict Systems and 875 with 5 channels.
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 |
Key identifiers in 875
- Order Status Code
- Date
- Purchase Order Number
- Reference Identification Qualifier
- Contact Function Code
- Name
- Description
- Terms Type Code
Segment reference — 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 identify a person or office to whom communications should be directed
To specify pertinent dates and times
To specify transportation instructions relating to the shipment
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 describe the allowance or charge in free-form format
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)
Related references
875 Grocery Products Purchase Order on other Piggly Wiggly channels
Compare the listed channel references and confirm their current implementation guides.
Related references
Other transactions in Piggly Wiggly Midwest (via Edict Systems)
Other EDI documents listed on this channel.
Piggly Wiggly Midwest (via Edict Systems) EDI 875 questions
Common questions about 875 Grocery Products Purchase Order on the Piggly Wiggly Midwest (via Edict Systems) channel.
What is X12 875 Grocery Products Purchase Order used for?
875 is used when a grocery buyer places an order. It carries information for the grocery purchase order. Match it to your business system using purchase order, item and pack or unit basis.
Is 875 required for Piggly Wiggly Midwest (via Edict Systems)?
875 is listed for Piggly Wiggly Midwest (via Edict Systems). Confirm the required version and direction for your business unit and account with the partner.
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.
How does 875 relate to other EDI messages?
X12 880 Grocery Products Invoice is a related document also listed on Piggly Wiggly Midwest (via Edict Systems). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 875 and 880?
875 is used when a grocery buyer places an order. 880 is used when grocery goods are ready for detail billing. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Piggly Wiggly 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.
