Grocery EDI: What Suppliers Need to Know

Grocery suppliers must be EDI-capable to sell to major chains: the U.S. food retail industry generates over $800 billion in annual sales, nearly all of it flowing through EDI-connected supply chains. High SKU counts, perishable goods, and tight delivery windows make manual document handling operationally impossible at scale. If you are supplying products to grocery chains or distributing food products to retail, you need to understand the specific EDI transactions, compliance models, and data flows that make this industry different from general retail.

This guide covers the grocery-specific EDI landscape: the transaction sets unique to grocery, how scan-based trading changes the standard EDI flow, DSD delivery requirements, cold chain and FSMA traceability, and what major grocery retailers actually expect from their food suppliers.

How EDI Works in the Grocery Industry

The basic EDI flow in grocery follows the same pattern as other retail sectors. A retailer sends an EDI 850 purchase order, the supplier acknowledges it, ships the product with an EDI 856 ship notice, and sends an invoice. But grocery adds layers of complexity that other industries do not deal with.

Perishable inventory timing. A 48-hour delivery window on fresh produce means the EDI transaction cycle compresses dramatically. There is no buffer for manual re-keying or delayed acknowledgments. When a retailer sends you a purchase order for 2,000 cases of fresh chicken with a 48-hour window, your warehouse needs to be picking within hours.

High transaction volume. A single grocery distribution center might process thousands of purchase orders per week across hundreds of suppliers. According to FMI - The Food Industry Association, the U.S. food retail industry generates over $800 billion in sales, nearly all of it flowing through EDI-connected supply chains.

Store-level ordering. Unlike general merchandise where orders route through a central DC, many grocery categories involve direct store delivery (DSD) or store-level replenishment. Your EDI system needs to handle orders at the individual store level, not just the retailer level.

Regulatory pressure. The FDA's Food Safety Modernization Act (FSMA) requires traceability records across the supply chain. EDI gives you a structured, auditable trail of every lot, batch, and shipment, which matters when the FDA asks you to trace a contaminated product back to its source within 24 hours.

If you are new to EDI fundamentals, start with our essential guide to EDI before diving into grocery specifics.

Key Grocery EDI Transactions

Grocery suppliers need to support the standard retail EDI transaction sets plus several that are specific to (or heavily used in) the grocery and food distribution industry.

Standard Transactions

These are non-negotiable for any grocery trading partnership:

| Transaction | Name | Direction | |---|---|---| | EDI 850 | Purchase Order | Retailer to Supplier | | EDI 855 | Purchase Order Acknowledgment | Supplier to Retailer | | EDI 856 | Advance Ship Notice (ASN) | Supplier to Retailer | | EDI 810 | Invoice | Supplier to Retailer | | EDI 997 | Functional Acknowledgment | Both directions |

Grocery-Specific Transactions

EDI 852 (Product Activity Data). This transaction carries point-of-sale (POS) data and inventory movement information from the retailer back to the supplier. In grocery, the 852 is critical for demand planning, category management, and scan-based trading programs. It tells you how fast your products are moving off the shelf at a store or regional level.

EDI 880 (Grocery Products Invoice). The 880 is a grocery-specific invoice format that handles the unique billing requirements of the food industry, including catch-weight pricing, random-weight items (like deli meats priced per pound), and allowances or deductions. If you sell anything with variable weight, you will almost certainly encounter the 880 instead of (or in addition to) the standard 810.

EDI 832 (Price/Sales Catalog). Used to communicate product pricing, promotional pricing, and catalog updates between suppliers and retailers. Grocery suppliers use the 832 to push updated cost files, new item introductions, and promotional deal structures to their retail partners.

EDI 894 (Delivery/Return Base Record). Specific to DSD operations, the 894 confirms what was actually delivered to a store, including quantities, substitutions, and returns. It acts as both a delivery receipt and a settlement document.

For a deeper look at any of these transactions, use our free EDI Inspector to parse and visualize real EDI files.

Food-Specific Data Requirements

Beyond the transaction types themselves, food distribution EDI requires additional data elements in standard transactions:

| Transaction Set | Name | Food-Specific Notes | |---|---|---| | 850 | Purchase Order | Includes GTIN, catch weight indicators, temp zone requirements | | 855 | PO Acknowledgment | Required by most grocery retailers | | 856 | Advance Ship Notice | Must include lot numbers, expiration dates, catch weights | | 810 | Invoice | Actual shipped weights for variable-weight items | | 846 | Inventory Advice | Segmented by lot, expiration date, and temperature zone | | 880 | Grocery Products Invoice | Handles deal allowances, billbacks, and multi-store billing |

The EDI 856 ship notice is where food distribution gets especially complex. Beyond standard carton and pallet data, food ASNs require lot and batch numbers at the item level (critical for recalls), production and expiration dates in the DTM segments, catch weight data in the MEA segments for variable-weight items, temperature zone indicators for multi-temp shipments, and SSCC-18 barcodes for carton and pallet-level tracking.

A missing lot number in your 856 does not just trigger a chargeback. It can flag your shipment for rejection at the receiving dock, which means spoilage and a total loss on perishable goods.

Scan-Based Trading and EDI

Scan-based trading (SBT) is a consignment-like model that has become common in grocery, particularly for categories like bread, snacks, beverages, and dairy. It fundamentally changes the EDI flow.

How SBT Works

In a traditional model, ownership of the product transfers when the supplier ships it. In scan-based trading, the supplier owns the product until a consumer buys it at the register. The retailer only pays for what actually scans at the point of sale.

This changes the EDI transaction flow:

1. No traditional purchase order. The retailer may not send an 850 for SBT items. Instead, the supplier manages inventory levels and restocks based on POS data.
2. EDI 852 becomes the trigger. The retailer sends POS data via the 852, showing what sold at each store. This drives both replenishment decisions and payment calculations.
3. Invoicing follows sales, not shipments. The supplier invoices based on scanned sales data, not on what was delivered. The 880 grocery invoice ties back to POS records rather than ASN quantities.

For suppliers, SBT means carrying more inventory risk but gaining better shelf placement and fewer out-of-stock situations. The EDI challenge is data accuracy. If POS data from the 852 does not match what you delivered, reconciliation becomes a headache. You need tight integration between your EDI system, your DSD route accounting, and your invoicing process. Many grocery suppliers handling SBT programs find that automated order processing becomes essential for keeping up with the volume of POS-driven transactions.

DSD (Direct Store Delivery) EDI Requirements

Direct store delivery is standard for many grocery categories: bread, beverages, snacks, dairy, and produce. Instead of shipping to a retailer's distribution center, you deliver directly to individual stores.

The DSD EDI Flow

1. Route planning. The supplier determines delivery schedules based on historical demand, POS data (EDI 852), and store-level inventory targets.
2. Pre-notification. Some retailers require an EDI 856 ASN before the delivery truck arrives, even for DSD. Others accept notification at the time of delivery via handheld devices.
3. In-store receiving. The driver delivers product and records what was actually received, including any refused items or returns. This generates an EDI 894 (Delivery/Return Base Record).
4. Settlement. The 894 serves as the basis for invoicing. What was accepted at the store is what gets billed.

Key DSD Compliance Points

• Store-level identification. Every transaction must reference the specific store location, typically using the retailer's store number or a GLN (Global Location Number) per GS1 US standards.
• Real-time data capture. Many retailers now expect DSD data transmitted the same day as delivery. Handheld devices or mobile apps capture delivery details and transmit EDI data from the field.
• Return handling. DSD involves more returns than warehouse-delivered product (stales, damaged goods, unsold perishables). The 894 must accurately capture return quantities and reason codes.

If you are exploring DSD alongside warehouse distribution, check out our page on EDI for grocery suppliers for a broader look at how these models work together.

FSMA and Traceability Requirements

The FDA's Food Safety Modernization Act (FSMA) changed how food distributors handle traceability. The FSMA Section 204 rule, which went into effect in January 2026, requires additional traceability records for foods on the Food Traceability List (FTL), including fresh fruits and vegetables, certain cheeses, shell eggs, nut butters, and fresh-cut produce.

What FSMA Requires

For each Critical Tracking Event (CTE) in the supply chain, you need to record Key Data Elements (KDEs):

• Traceability lot code for each product
• Location identifiers (where the product was received, stored, shipped)
• Date and time of each event
• Quantity and unit of measure
• Reference document numbers (PO numbers, BOL numbers)

How EDI Supports FSMA Compliance

EDI does not replace your traceability system, but it provides the structured data backbone that makes compliance practical at scale:

• The 856 ASN carries lot codes, production dates, and expiration dates at the item level
• The 850 PO provides reference document numbers and location identifiers
• The 810 invoice links financial records to specific lots and shipments

When the FDA requests a trace-back, you need to produce records within 24 hours. If your lot data lives in EDI transactions that are already structured and searchable, that is a realistic timeline. If it lives in paper BOLs and spreadsheets, it is not.

Cold Chain Documentation in EDI

Perishable food shipments require temperature documentation that non-perishable goods do not.

Temperature Data in ASNs

The EDI 856 can include temperature-related data in the TD1 (Carrier Details) and MEA (Measurements) segments:

• Required temperature range for the shipment (frozen at -10F to 0F, refrigerated at 33F to 40F)
• Temperature zone codes distinguishing frozen, refrigerated, and ambient items in multi-temp loads
• Carrier and trailer identification for temperature monitoring correlation

Multi-Temperature Shipments

Food distributors commonly ship frozen, refrigerated, and ambient products on the same truck using multi-temp trailers. Your ASN needs to clearly associate each product with its temperature zone. Retailers will reject mixed-temp ASNs that do not specify which items are in which zone.

A retailer receiving a pallet of frozen shrimp needs to verify it was maintained at the correct temperature throughout transit. If your ASN does not include temperature zone data, the receiving team may hold the shipment for manual verification, increasing spoilage risk.

Common Challenges for Food Distributors

Catch Weight Pricing

Variable-weight products (meat, cheese, seafood, produce sold by weight) create a mismatch between what is ordered and what is shipped. The PO says 100 cases. You ship 100 cases, but each case weighs slightly different. Your ASN and invoice must reflect actual weights, not ordered weights. This means your warehouse management system needs to capture weights at pick/pack time and pass them into your EDI system before the 856 and 810 are generated.

Short Shelf Life

When a product has a 14-day shelf life, a one-day delay in order processing can mean the difference between an accepted and rejected shipment. Retailers specify minimum remaining shelf life requirements (often 70% to 75% of total shelf life at delivery). Automating order receipt and processing through EDI removes the manual delays that eat into your delivery window.

Promotional and Deal Pricing

Grocery operates on thin margins with frequent promotions. Your EDI 810 (or 880) must correctly calculate deal allowances, billbacks, and promotional pricing. A mismatch between the promotional terms in the PO and the pricing in your invoice triggers deductions that are painful to resolve.

High-Volume, Low-Error Tolerance

Food distributors often process thousands of line items per day. At that volume, even a 1% error rate means dozens of problems daily. Automated order processing and ERP integration reduce errors by eliminating manual re-entry between systems.

Major Grocery Retailer EDI Programs

Kroger

Kroger is the largest supermarket chain in the U.S. with nearly 2,800 stores across multiple banners (Ralphs, Fred Meyer, Harris Teeter, King Soopers, and others). All banners operate under a single EDI framework.

• Required transactions: 850, 855, 856, 810, 997
• Additional for grocery: 852 for POS data, 880 for grocery invoicing
• Key detail: Kroger's 84.51 data analytics division drives category management, and POS data exchange via EDI 852 is tightly integrated into their supplier programs. Promotional allowances embedded in POs must match invoices exactly.

For the full breakdown, see our Kroger EDI requirements guide.

Walmart

Walmart is the largest grocery retailer in the U.S. Food suppliers must meet the same EDI standards as other Walmart vendors, plus additional food safety requirements:

• GTIN compliance: Every product needs a valid GS1 GTIN. No exceptions.
• Catch weight handling: Variable-weight items must include actual weights in both the 856 and 810.
• OTIF (On Time In Full): The target is 98% for warehouse-delivered goods. Failures carry financial penalties.
• Lot tracking: Required for all perishable items in the ASN.

See our full Walmart EDI requirements guide.

Albertsons / Safeway

Albertsons Companies operates Safeway, Vons, Jewel-Osco, Shaw's, ACME, and other banners across 2,200+ stores.

• Required transactions: 850, 855, 856, 810, 997
• DSD support: Extensive DSD programs, especially for bakery, beverage, and snack categories. Expect EDI 894 requirements.
• Key detail: Albertsons runs a large scan-based trading program. If your category qualifies, expect the SBT EDI flow described above.

Publix

Publix operates 1,300+ stores across the Southeast.

• Required transactions: 850, 855, 856, 810, 997, 852
• Key detail: Publix tracks ASN compliance at the item level. Missing or inaccurate ASN data triggers chargebacks and can affect vendor scoring.

Whole Foods (Amazon)

Whole Foods operates under Amazon's supply chain infrastructure:

• Strict quality and sourcing standards on top of EDI requirements
• Lot and batch tracking required for all products
• Shorter shelf-life windows than conventional retailers
• EDI through Amazon's systems, including their vendor portal

Costco

• Pallet-level SSCC-18 barcodes on every shipment
• Catch weight accuracy (Costco is one of the strictest on weight tolerances)
• Tight delivery windows with penalties for early or late arrivals

Ahold Delhaize (Stop & Shop, Giant, Food Lion, Hannaford)

• Required transactions: 850, 855, 856, 810, 997
• Active DSD programs with EDI 894 support
• Key detail: Ahold Delhaize's Retail Business Services (RBS) subsidiary manages IT and supply chain for all U.S. banners, so EDI standards are consistent across brands.

Each retailer has their own testing and onboarding process. Budget 4 to 8 weeks for EDI testing with a new grocery trading partner.

Getting Started with Grocery EDI

If you are new to grocery EDI, adding a new retail partner, or upgrading from a basic setup to handle food-specific requirements, here is a practical path forward:

1. Get your trading partner's EDI requirements document. Every grocery retailer publishes an EDI implementation guide. This spells out exactly which transactions they require, which segments are mandatory, and what data formatting they expect.

2. Determine your delivery model. Warehouse-delivered and DSD have different EDI transaction requirements. Clarify whether you are shipping to distribution centers, delivering directly to stores, or both.

3. Map your product data. Make sure every product has a valid GTIN, correct catch weight flags, lot tracking in your WMS, and accurate shelf life data.

4. Handle grocery-specific transactions. If you already do EDI with non-grocery retailers, you likely have 850, 856, and 810 covered. Grocery will add the 852, 880, and potentially the 894 to your transaction set.

5. Test thoroughly. Grocery EDI testing is more rigorous than many suppliers expect. Retailers will validate your ASN accuracy, invoice matching, and acknowledgment timing. Expect multiple rounds of test transactions before going live. Use our free EDI Inspector to parse and validate your files before submission.

6. Plan for ongoing compliance. Grocery EDI is not "set it and forget it." Retailers update their requirements, add new transaction types, and adjust compliance scoring. Walmart EDI requirements change regularly, and grocery chains follow a similar pattern.

If you are handling orders across multiple grocery partners with different formats and requirements, a platform like OrderSync can normalize everything into a single workflow through multi-format order processing. Book a call to see how it works with grocery-specific EDI.

FAQ

What EDI transactions are unique to the grocery industry?

The grocery industry commonly uses EDI 852 (Product Activity Data) for POS reporting, EDI 880 (Grocery Products Invoice) for variable-weight and catch-weight billing, EDI 832 (Price/Sales Catalog) for pricing updates, and EDI 894 (Delivery/Return Base Record) for DSD operations. These supplement the standard 850, 856, and 810 transactions used across all retail.

How does scan-based trading affect EDI requirements?

Scan-based trading shifts the invoicing trigger from shipment to point-of-sale. Instead of invoicing when you ship product, you invoice based on what actually scans at the register. This makes the EDI 852 (POS data) transaction critical, since it drives both replenishment and payment. The traditional 850 purchase order may be reduced or eliminated for SBT categories.

How does catch weight work in EDI?

Catch weight items are products sold by weight where each unit weighs slightly different. In EDI, the 850 PO specifies an estimated quantity, but your 856 ASN and 810 invoice must include actual weights captured during warehouse picking. The MEA segment in the 856 carries weight data at the item level.

What happens if my ASN is missing lot numbers?

Most grocery retailers will either reject the shipment at the dock or accept it with a chargeback. For perishable products, a dock rejection often means total product loss due to spoilage. With FSMA traceability requirements now in effect, missing lot data also creates regulatory compliance gaps.

How does FSMA Section 204 affect food distributor EDI?

FSMA Section 204 requires additional traceability records for products on the Food Traceability List. Food distributors must track and share lot codes, location identifiers, and dates for each Critical Tracking Event. EDI transactions (especially the 856 ASN) provide the structured format to carry this data between trading partners.

Do small food distributors need EDI?

Yes, if you are selling to major grocery retailers. Walmart, Kroger, Costco, and most regional chains require EDI regardless of supplier size. Modern EDI platforms have lowered the cost and complexity compared to legacy systems. You do not need a dedicated IT team to get started.

Do I need different EDI setups for each grocery retailer?

The core transactions (850, 856, 810) are standardized under ANSI X12, but each retailer has specific segment requirements, data formatting rules, and compliance expectations. You do not need a completely different setup for each partner, but you do need to configure mappings and validation rules per retailer. A flexible EDI platform handles this through trading partner profiles.

How long does it take to set up grocery EDI with a new retailer?

Plan for 4 to 8 weeks from start to go-live, depending on the retailer and your current EDI capabilities. This includes obtaining the retailer's companion guide, configuring your mappings, completing test transactions, and getting approval from their compliance team.