To start and identify an interchange of zero or more functional groups and interchange-related control segments
Meijer X12 880 Grocery Products Invoice
X12 880 (Grocery Products Invoice) is the EDI transaction exchanged between Meijer (Meijer (Grocery)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 19
- Loops
- 3
- X12 880
- All partners ↗
Transaction context
Where 880 Grocery Products Invoice fits on Meijer (Grocery)
On Meijer (Grocery), the X12 880 Grocery Products Invoice follows the 875 Grocery Products Purchase Order in the Grocery replenishment cycle.
- Meijer channels
- 1 of 2
- Trading partners
- 33
- Channels
- 36
1 of Meijer's 2 channels carries 880
partners across the Stacksync network trade 880
channels network-wide carry 880
Most common alongside 880
The 880 is the UCS grocery-industry invoice, the grocery counterpart to the general-purpose 810. A supplier bills the retailer for a shipped order using grocery segments: G01 invoice identification, G17 item detail, G72 allowances and charges, and mandatory G31/G33 totals. Retailers match it against the purchase order and receiving records before payment, so pricing, item identifiers, and allowance data must line up with the PO. The supplier, manufacturer, or distributor sends the 880 to the grocery retailer or wholesaler after goods ship; the receiver returns a 997 Functional Acknowledgment.
When it fires: Goods ship against a grocery purchase order and the supplier issues its payment request for the delivered products.
Common 880 rejection causes
- Duplicate allowance codes: Kroger fails an invoice that carries more than one G72 segment with the same allowance/charge code under an item or invoice; values must be combined into a single G72 per code.
- Allowance sign and basis errors: allowance amounts must be negative (positive amounts are treated as charges) and the G72 rate must match the item's unit of measure, per-case for CA items and per-each for EA items (Kroger 880 guideline).
- Item format mismatches: the G17 item identifier must match an item format from the purchase order, and catch-weight lines need total weight invoiced in LB plus a separate case count in G1710 (Kroger 880 guideline).
- Header rejections: an invoice issue date in the future is not accepted, and the ship-to N1 must carry the retailer's location DUNS+4 from the purchase order being invoiced (Kroger 880 guideline).
Specification summary
X12 880 Grocery Products Invoice at the element level
The X12 880 specification defines 33 segments carrying 180 data elements, 58 of which are mandatory.
- 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
Full segment guideline — 19 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 specify pertinent dates and times
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 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)
Trading partners
2+ 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.
No trading partner matches your search.
Browse the full directory
Meijer Meijer (Grocery) EDI 880 FAQ
Common questions about 880 Grocery Products Invoice on the Meijer (Grocery) channel.
What is X12 880 Grocery Products Invoice?
X12 880 (Grocery Products Invoice) is the EDI transaction set used to exchange grocery products invoice data. Meijer's Meijer (Grocery) channel requires it from trading partners.
Does Meijer Meijer (Grocery) require 880 for trading partners?
Yes, Meijer (Meijer (Grocery)) supports X12 880 Grocery Products Invoice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Meijer 880 with Stacksync?
Most companies go live with Meijer 880 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 880 on Meijer (Grocery)?
On Meijer (Grocery), X12 880 is typically exchanged alongside 875 Grocery Products Purchase Order, 894 Delivery Return Base Record. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Meijer EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
