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 875 — Grocery Products Purchase Order
The 875 grocery products purchase order is the UCS-standard order a grocery buyer sends to a supplier, carrying order identification, parties, and line items for food and grocery distribution.
EDI 875 facts
- GS01 functional ID for 875 groups is OG — the UCS grocery purchase-order family is distinct from retail PO (PO) groups.
- Grocery partners that standardize on UCS expect the 875/880 pair rather than the retail 850/810 documents.
- SignalEDI maps G50/LIN grocery order data into structured JSON aligned with item-master UPC/GTIN references.
Where EDI 875 fits
- Direction
- Grocery buyer / distributor → supplier
- GS functional ID
- OG
- Workflow position
- 875 opens the grocery order-to-cash flow; suppliers ship and acknowledge, then invoice with the paired 880 grocery products invoice.
Related sets: 880, 856, 810, 997 · Document guide
Key segments in EDI 875
Sample EDI 875
ST*875*0001~ G50*PO*GP1001*20260609~ N1*BY*GROCERY CHAIN*92*BUYER01~ LIN*1*UP*012345678905~ G69*CASE GOODS~ SE*6*0001~
Validate samples with the free EDI validator.
Send EDI 875 with SignalEDI
POST /api/v1/documents/outbound
{
"partnerId": "grocery-demo",
"documentTypeCode": "875",
"payload": { "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 875 errors
- UPC/GTIN in LIN not matching the grocery buyer's item master
- G50 order number missing or duplicated for the same partner
- Pack/size data inconsistent with the buyer catalog
- Using the retail 850 envelope where the partner mandates UCS 875
Related reference
FAQ
EDI 875 FAQ
Both are purchase orders, but the 875 is the UCS grocery-industry variant; some grocery partners require 875/880 instead of the retail 850/810 pair.
The 880 grocery products invoice is the standard companion document to the 875 in UCS grocery programs.
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.”