A grocery-specific invoice format that handles the complex billing structures common in CPG and food & beverage trading, including off-invoice allowances, promotional deductions, scan-based trading, and deal pricing.
The EDI 880 Grocery Products Invoice is the standard invoice transaction set for the grocery and consumer packaged goods industry. Unlike the general-purpose EDI 810 Invoice, the 880 is designed to accommodate the layered pricing, promotional programs, and allowance structures that define CPG commerce.
In grocery trading, invoices rarely reflect just a base price multiplied by quantity. CPG suppliers regularly apply off-invoice allowances, promotional scan-down payments, display allowances, early pay discounts, case deal pricing, and volume tiers. The 880 has dedicated structures (the G72 Allowance or Charge segment and the G83 Direct Store Delivery item loop) to carry all of this detail alongside the line-item charges.
The 880 also supports scan-based trading (SBT) arrangements, where the supplier retains ownership of goods on the shelf and is invoiced only when a product scans at the register. In these arrangements, the 880 carries both the quantity sold and the applicable promotional pricing at the time of sale. Retailers like Kroger, Albertsons, and Walmart Neighborhood Market frequently require 880 rather than 810 for their CPG vendor billing.
The 880 is specific to the grocery and consumer goods channel. Other industries use the 810 for invoicing.
National and regional grocery chains require 880 from CPG vendors. Retailers like Kroger, Safeway, and Publix mandate 880 to support their allowance deduction workflows and promotional matching systems. AP teams use the 880's allowance segments to auto-deduct against invoices without manual intervention.
Consumer packaged goods manufacturers supplying retailers and distributors send 880s to communicate multi-tier pricing. A single shipment may carry a base invoice price, a promotional allowance, a display fee, and a freight allowance - all in separate G72 loops within a single 880 transaction.
Specialty food distributors, club store distributors, and broadline foodservice distributors (Sysco, US Foods) use 880 when billing retail customers. Distributors also receive 880s from their supplier base when the distribution tier needs to pass allowance data downstream.
Costco, BJ's Wholesale, and similar club retailers have specific 880 requirements that often differ from traditional grocery. Club channels typically have larger case pack quantities, member-exclusive pricing, and limited-time promotional structures that the 880's flexibility can accommodate.
Natural channel distributors like UNFI and KeHE, and specialty retailers like Whole Foods and Sprouts, use 880 billing. The natural channel often has unique promotional structures (co-op, scan, bill-back) that require the allowance flexibility of the 880.
Direct store delivery suppliers - beverage companies, snack manufacturers, bakery suppliers - generate high volumes of 880s, often one per store per delivery route. DSD 880s typically reference the store's DEA number and must reconcile against a pre-sell order or route manifest.
The 880 extends the standard invoice structure with grocery-specific segments not found in the 810.
The beginning segment of the 880 carries the invoice number, invoice date, and the Purchase Order number being invoiced. The G21 also identifies whether the invoice is an original, duplicate, or credit memo, and optionally carries a deal number or promotional event code.
The G83 loop is the 880's equivalent of the IT1 in an 810. It carries UPC, item description, quantity invoiced, unit of measure, and the invoiced unit price. Each G83 loop can be followed by G72 allowance/charge segments that apply specifically to that line item.
The most critical grocery-specific segment. G72 carries allowance/charge code, the method of calculation (percent, per unit, per case), the dollar amount, and the applicable quantity. Multiple G72 loops can appear at both the header and line levels, documenting all promotional and billing adjustments in structured form.
Identifies the parties to the invoice: the supplier (SF - Ship From), the buyer (BY - Buying Party), the ship-to location (ST), and often the payer (PE - Payee). In DSD scenarios, the N1 ST identifies the individual store location rather than a DC.
Summarizes the invoice totals: total invoice amount, total allowance amount, and total charges. Trading partners use G76 to perform a header-level balancing check before processing individual line items. Mismatches between G76 totals and G83/G72 detail are a common rejection cause.
Carries multiple date qualifiers relevant to grocery billing: ship date (011), delivery date (035), deal effective date (007), and promotional period dates. Deal date alignment is critical - many retailers automatically reject invoice allowances when the DTM deal date falls outside the approved promotion window.
The 880 fits into a broader grocery trading partner document flow.
The grocery retailer's PO that initiated the shipment being invoiced. The 880 must reference the 850's PO number, and promotional pricing in the 880 must match deal codes from the 850.
The retailer's remittance back to the supplier after processing the 880. The 820 details which invoices were paid in full versus which were deducted against, and documents each allowance applied.
If the retailer disputes an allowance or charges back for compliance failures, they issue an 812 referencing the 880 invoice. Managing 812s effectively requires matching them back to specific G72 allowance segments.
In scan-based trading, the retailer sends 852 POS data to the supplier before the 880 is generated. The scan quantities in the 852 become the billable quantities in the subsequent 880 invoice.
Grocery EDI is among the most complex in any industry. Better EDI handles 880 mapping, allowance structure setup, trading partner certification, and ongoing compliance monitoring so your team can focus on selling, not reconciling deductions.
Talk to an EDI Expert