To start and identify an interchange of zero or more functional groups and interchange-related control segments
Core-Mark (via SPS Commerce) X12 880 Grocery Products Invoice
Plan X12 880 Grocery Products Invoice for Core-Mark (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 23
- Loops
- 3
- X12 880
- Partner references ↗
Implementation guide
Core-Mark (via SPS Commerce): 880 mapping and validation
X12 880 Grocery Products Invoice is used when grocery goods are ready for detail billing. Preserve invoice, grocery order and item so the grocery invoice in your business system stays connected to the original document.
This document is listed for Core-Mark (via SPS Commerce). 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 invoice invoice, grocery order and item |
|
| Update the receiving system | Processing the grocery invoice ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the grocery invoice Original document reference and matching response |
|
The document reference includes 23 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 875 Grocery Products Purchase Order
grocery purchase order: a grocery buyer places an order.
- X12 820 Payment Order Remittance Advice
payment or remittance record: payment instructions or allocation details are ready.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when grocery goods are ready for detail billing. Name the operational owner of the grocery invoice and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map invoice, grocery order and item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Core-Mark (via SPS Commerce) 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 invoice 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 invoice processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 880 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic grocery invoice 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 invoice without processing it twice.
Transaction context
Where 880 Grocery Products Invoice fits on Core-Mark (via SPS Commerce)
On Core-Mark (via SPS Commerce), the X12 880 Grocery Products Invoice can follow the 875 Grocery Products Purchase Order in an example Grocery replenishment cycle. Confirm the required sequence for your trading agreement.
- Core-Mark (via SPS Commerce) channels
- 1 of 1
1 of Core-Mark (via SPS Commerce)'s 1 channel list 880
- Trading partners
- 33
partner references list 880
- Channels
- 36
channel entries list 880
Frequently listed alongside 880
The directory associates SPS Commerce and 880 with 3 channels.
Document structure
X12 880 Grocery Products Invoice at the element level
The X12 880 reference contains 33 segment entries and 180 data elements; 58 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 33
- Data elements
- 180
- Mandatory elements
- 58
| Segment | Elements | Mandatory |
|---|---|---|
| G01 | 6 | 2 |
| N9 | 5 | 1 |
| G61 | 5 | 2 |
| NTE | 2 | 1 |
| G27 | 6 | 1 |
| G23 | 16 | 2 |
| G25 | 3 | 2 |
| N1 | 4 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| G72 | 11 | 2 |
| G73 | 1 | 1 |
Key identifiers in 880
- Date
- Invoice Number
- Reference Identification Qualifier
- Contact Function Code
- Name
- Description
- Transportation Method/Type Code
- Terms Type Code
Segment reference — 23 segments 3 loops · X12 880 Grocery Products Invoice
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 transmit identifying information as specified by the Reference Identification Qualifier
To identify a person or office to whom communications should be directed
To specify pertinent dates and times
To transmit information in a free-form format, if necessary, for comment or special instruction
To specify the terms of sale
To transmit information pertaining to method of freight payment and transfer of title
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
G72 Loop Repeat: 100
To specify allowances, charges, or services
To describe the allowance or charge in free-form format
G17 Loop Repeat: 9,999
To specify the basic and most frequently used line item data for the invoice and related transactions
To describe an item in free-form format
To specify details when differences exist between 1) Quantities ordered/quantities shipped 2) Units of measurement 3) Pricing 4) Coupons redeemed/validated
To specify packing details of the items shipped
To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method
To specify the total invoice amount, including charges less allowances, before terms discount
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
Other transactions in Core-Mark (via SPS Commerce)
Other EDI documents listed on this channel.
Purchase Order X12 850 Grocery Products Purchase Order X12 875 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Invoice X12 810 Product Activity Data X12 852 Payment Order Remittance Advice X12 820 Credit Debit Adjustment X12 812
No references match your search.
Showing 8 of 8 references
Browse the full directoryCore-Mark (via SPS Commerce) EDI 880 questions
Common questions about 880 Grocery Products Invoice on the Core-Mark (via SPS Commerce) channel.
What is X12 880 Grocery Products Invoice used for?
880 is used when grocery goods are ready for detail billing. It carries information for the grocery invoice. Match it to your business system using invoice, grocery order and item.
Is 880 required for Core-Mark (via SPS Commerce)?
880 is listed for Core-Mark (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 880?
Start with invoice, grocery order and item and the target grocery invoice. 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 880 error handling?
Reconcile quantity units and allowances before posting the invoice. Test a duplicate invoice while keeping an authorized correction traceable. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 880 relate to other EDI messages?
X12 875 Grocery Products Purchase Order; X12 820 Payment Order Remittance Advice are related documents also listed on Core-Mark (via SPS Commerce). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 880 and 875?
880 is used when grocery goods are ready for detail billing. 875 is used when a grocery buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Core-Mark (via SPS Commerce) 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.
