X12 transaction code
EDI 880 Grocery Products Invoice (X12 880)
EDI 880 is the X12 Grocery Products Invoice transaction set, used when grocery goods are ready for detail billing. The supplier, manufacturer, or distributor sends the 880 to the grocery retailer or wholesaler after goods ship; the receiver returns a 997 Functional Acknowledgment.
- Standard
- X12
- Code
- 880
- Partner references
- 33
At a glance
EDI 880 at a glance
What the 880 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 880 Grocery Products Invoice |
|---|---|
| Business record | Grocery invoice |
| Who sends it to whom | 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 is sent | Goods ship against a grocery purchase order and the supplier issues its payment request for the delivered products. |
| Match on | Invoice, grocery order and item |
| Partner references | 33 trading partners in this directory |
| Related documents | X12 875 Grocery Products Purchase Order, X12 879 Price Information, X12 820 Payment Order/Remittance Advice |
Key segments in an EDI 880
The business segments that appear in at least half of the 36 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 |
|---|---|---|---|
| G01 | Invoice Identification | To transmit identifying dates and numbers for this transaction set. | 36 of 36 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 36 of 36 |
| G72 | Allowance or Charge | To specify allowances, charges, or services. | 36 of 36 |
| G17 | Item Detail - Invoice | To specify the basic and most frequently used line item data for the invoice and related transactions. | 36 of 36 |
| G31 | Total Invoice Quantity | To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method. | 36 of 36 |
| G33 | Total Dollars Summary | To specify the total invoice amount, including charges less allowances, before terms discount. | 36 of 36 |
| G23 | Terms of Sale | To specify the terms of sale. | 35 of 36 |
| G69 | Line Item Detail - Description | To describe an item in free-form format. | 35 of 36 |
| N3 | Party Location | To specify the location of the named party. | 32 of 36 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 32 of 36 |
Stacksync connects EDI documents such as the X12 880 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 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.
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 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 |
|
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 879 Price Information
price information: grocery or product pricing is distributed.
- 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 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 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.
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 |
- Date
- Invoice Number
- Reference Identification Qualifier
- Contact Function Code
- Name
- Description
- Transportation Method/Type Code
- Terms Type Code
Find your trading partner for X12 880
33 partners, 36 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
- 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 880 Grocery Products Invoice appears in this catalog
The largest groups of classified 880 catalog entries are in grocery & food.
By industry
- grocery & food 36 channels
By network
- Edict Systems 5 channels
- SPS Commerce 3 channels
FAQ
EDI 880 questions
What is an EDI 880?
EDI 880 is the X12 Grocery Products Invoice transaction set. Trading partners use it when grocery goods are ready for detail billing. It carries the data for the grocery invoice, and your system matches it on invoice, grocery order and item.
Who sends an EDI 880 and who receives it?
The supplier, manufacturer, or distributor sends the 880 to the grocery retailer or wholesaler after goods ship; the receiver returns a 997 Functional Acknowledgment. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 880 sent?
Goods ship against a grocery purchase order and the supplier issues its payment request for the delivered products. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 880?
Across 36 partner document references listed here, the business segments that appear most often include G01 (Invoice Identification), N1 (Party Identification), G72 (Allowance or Charge), G17 (Item Detail - Invoice), G31 (Total Invoice Quantity), G33 (Total Dollars Summary). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 880 and EDI 875?
The 880 carries the grocery invoice and is used when grocery goods are ready for detail billing. The 875 carries the grocery purchase order and is used when a grocery buyer places an order.
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.
Which partners list X12 880?
The directory on this page links 33 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.
