Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 transaction set reference
X12 880 — Grocery Products Invoice
The 880 grocery products invoice is the UCS-standard invoice a supplier sends to a grocery buyer, carrying invoice identification, parties, line items, and allowance/charge detail.
EDI 880 facts
- GS01 functional ID for 880 groups is IB — the UCS grocery invoice family is acknowledged separately from retail invoice (IN) groups.
- 880 invoices pair with 875 orders; mismatched UPC/GTIN or totals drive grocery-program deductions.
- SignalEDI validates 880 line and allowance/charge math against the order before partner send.
Where EDI 880 fits
- Direction
- Supplier → grocery buyer / distributor
- GS functional ID
- IB
- Workflow position
- 880 closes the grocery order-to-cash flow after the 875 order and shipment; invoice references must reconcile with the order and shipped quantities.
Related sets: 875, 856, 997 · Document guide
Key segments in EDI 880
Sample EDI 880
ST*880*0001~ G01*20260609*INV5521~ N1*SU*FOODS SUPPLIER*92*SUP01~ LIN*1*UP*012345678905~ G69*CASE GOODS~ SE*6*0001~
Validate samples with the free EDI validator.
Send EDI 880 with SignalEDI
POST /api/v1/documents/outbound
{
"partnerId": "grocery-demo",
"documentTypeCode": "880",
"payload": { "invoiceNumber": "INV5521", "purchaseOrderNumber": "GP1001" }
}Your side can reach partner-ready setup in days, not weeks — partner certification calendars may still take longer. See the API quickstart.
Common EDI 880 errors
- Invoice line UPC/GTIN not matching the originating 875 order
- Allowance/charge values that do not reconcile with invoice totals
- Duplicate G01 invoice number for the same grocery partner
- Using the retail 810 envelope where the partner mandates UCS 880
Related reference
FAQ
EDI 880 FAQ
Both are invoices, but the 880 is the UCS grocery-industry variant paired with the 875 order; some grocery partners require it instead of the retail 810.
Yes — for clean reconciliation the 880 should reference the originating 875 order and the shipped quantities.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees on core plans, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
Supports HIPAA complianceBAA path documentedSecure API + webhooksNo per-document fees on core plans
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with handling that supports HIPAA compliance and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”