Retail EDI: What Suppliers Need to Know

Retail EDI is the mandatory electronic exchange of purchase orders, ship notices, invoices, and acknowledgments between suppliers and major retailers, enforced through chargeback programs that can cost 3% of COGS per non-compliant shipment. You signed a deal with a major retailer. Then the vendor compliance packet arrives, and it says you need to be EDI-capable in 60 to 90 days. If you've never worked with retail EDI before, that timeline feels aggressive. But the requirements aren't optional, the deadlines are real, and the chargebacks for non-compliance start on day one.

This guide covers exactly what supplier EDI looks like in retail: which transactions you need, what each major retailer actually expects, and where suppliers most commonly trip up.

Key standards and compliance context for retail EDI:

• The ANSI X12 standard defines the transaction set numbers (850, 856, 810, 997, 846) that all retail EDI compliance programs are built around
• GS1 US barcode standards govern the GTIN, UPC, and SSCC-18 identifiers that retailers scan at receiving to match physical shipments against electronic ASNs
• GS1 US guide to UPCs covers the SSCC-18 format and serial number allocation rules that Walmart and Target use for carton-level compliance

What Is Retail EDI?

Retail EDI is the electronic exchange of standardized business documents between retailers and their suppliers using the ANSI X12 standard, replacing manual document exchange with automated system-to-system communication. Instead of emailing purchase orders, faxing invoices, or calling in shipment details, both parties send and receive structured data files that their systems can process automatically.

The standard behind most retail EDI in North America is ANSI X12, maintained by the Accredited Standards Committee. Each document type has a three-digit transaction set number. An EDI 850 purchase order is a purchase order. An EDI 856 ship notice is an advance ship notice (ASN). An EDI 810 is an invoice. These aren't proprietary formats. They follow a shared specification that thousands of trading partners use.

If you're new to the concept entirely, start with our essential guide to EDI for a full breakdown of how electronic data interchange works.

The short version: retail EDI replaces manual document exchange with automated, system-to-system communication. Your retailer's system sends you a purchase order electronically. Your system receives it, processes it, ships the goods, and sends back the required documents, all without anyone re-keying data from a PDF.

Why Retailers Require EDI

Retailers don't require EDI to make your life harder. They require it because their supply chains can't function without it.

Volume

A retailer like Walmart processes millions of purchase orders per year across tens of thousands of suppliers in high-volume states like California and Texas. There is no manual process that scales to that level. EDI is the plumbing that makes automated replenishment, cross-docking, and just-in-time inventory work.

Accuracy

Manual order processing introduces errors at every touchpoint. A miskeyed quantity, a wrong item number, an incorrect ship-to address. According to GS1 US, standardized data exchange reduces order processing errors by up to 40% compared to manual methods. When you're shipping 10,000 cases a week, a 2% error rate creates hundreds of problems.

Speed

Retailers expect acknowledgment of purchase orders within hours, not days. They expect ASNs transmitted before the shipment arrives at the distribution center. EDI makes that possible because the data moves between systems in minutes.

Chargebacks

This is the part that gets suppliers' attention. Retailers enforce EDI compliance through chargebacks, and they're not small. Walmart's OTIF (On Time In Full) program can result in penalties of 3% of the cost of goods for late or incomplete shipments. Target charges $500 or more per shipment for ASN failures. These costs add up quickly and can wipe out the margin on a retail account if you're not set up correctly.

Understanding what EDI capable means is the first step toward avoiding these penalties.

Core Retail EDI Transactions

Not every retailer uses every transaction type, but six transactions form the backbone of most retail EDI programs. Here's what each one does and when it's used.

Transaction	Name	Direction	What It Does
850	Purchase Order	Retailer to Supplier	The retailer sends you an order with items, quantities, prices, and ship-to locations
855	PO Acknowledgment	Supplier to Retailer	You confirm receipt of the order and indicate whether you can fill it as requested
856	Ship Notice (ASN)	Supplier to Retailer	You notify the retailer that goods have shipped, with carton-level detail and tracking
810	Invoice	Supplier to Retailer	You send an electronic invoice tied to the original PO number
997	Functional Acknowledgment	Both directions	An automated receipt confirmation that says "I received your EDI file and it was valid"
846	Inventory Inquiry/Advice	Supplier to Retailer	You share current inventory levels so the retailer can plan replenishment

The 850 and 856 are the most compliance-sensitive. If your system can't receive an EDI 850 and respond with an accurate 856, you will get chargebacks. The 997 is usually automated by your EDI platform, but missing 997s can also trigger compliance flags.

For detailed segment-by-segment breakdowns, check our EDI 850 guide and EDI 856 ship notice guide.

Retailer-Specific Requirements

Every major retailer has its own EDI compliance program with specific rules, deadlines, and penalties. Here are the ones that trip up suppliers most often.

Walmart

Walmart's supplier EDI program is the most demanding in retail. Key requirements include:

• OTIF compliance: Walmart measures On Time In Full at the PO line level. The target is 98%. Falling below triggers chargebacks of 3% of COGS on the non-compliant portion.
• ASN timing: Your 856 must be transmitted before the shipment arrives at the DC. Late ASNs are treated as OTIF failures.
• GS1 barcodes: Every case and pallet needs GS1-128 labels with valid SSCC-18 numbers. Walmart scans these at receiving. If the barcode doesn't match the ASN data, the shipment gets rejected or charged back.
• Retail Link: Walmart expects suppliers to monitor inventory and PO status through Retail Link, their supplier portal.

For the full breakdown, read our guide to Walmart EDI requirements.

Target

Target's EDI compliance is built around their DPCI (Department, Class, Item) numbering system. Requirements include:

• DPCI codes: Every item in your EDI transactions must reference the correct Target DPCI number. This is Target's internal item identifier, and they won't accept orders or ASNs with UPC-only references.
• Carton-level ASN detail: Target requires SSCC-18 barcodes and carton content detail in the 856. Each carton must be individually identified.
• Partners Online portal: Target manages vendor compliance through Partners Online. Non-compliance notifications, chargeback disputes, and routing guides all live here.
• Chargeback amounts: ASN failures at Target commonly result in $500+ per shipment chargebacks. Repeated failures can trigger vendor scorecard reviews.

See our complete guide to Target EDI requirements.

Costco

Costco's approach to supplier EDI is somewhat different from Walmart and Target:

• Simpler item structure: Costco carries fewer SKUs per supplier, so the item master is typically smaller and easier to manage.
• Depot vs. cross-dock: Costco uses different shipping models depending on the product category. Your ASN requirements change based on whether you're shipping to a depot or direct to a warehouse.
• EDI 846 inventory reporting: Costco is more likely than other retailers to require regular inventory feeds via the 846 transaction.
• Vendor compliance manual: Costco's compliance requirements are outlined in their vendor manual, which covers everything from pallet configuration to labeling.

Read the full details in our Costco EDI requirements guide.

Amazon (Vendor Central)

Amazon Vendor Central suppliers (1P) operate under a different EDI model than marketplace sellers:

• PO confirmation windows: Amazon expects PO confirmations (855) within 24 hours. Missing this window can result in the PO being canceled.
• ASN requirements: Amazon requires ASNs before shipment arrival at their fulfillment centers. Their system uses these to pre-plan receiving dock assignments.
• Shortage claims: Amazon aggressively reconciles what the ASN says was shipped against what their receiving team counts. Discrepancies result in shortage claims that are notoriously difficult to dispute.
• EDI or API: Amazon offers both EDI and API-based order exchange. Larger suppliers typically use EDI; smaller vendors sometimes use the Vendor Central portal for manual entry, though this doesn't scale.

Common Compliance Pitfalls

After working with hundreds of suppliers entering retail, these are the issues we see most often.

1. Late or Missing ASNs

The single biggest source of retail chargebacks. Your 856 ship notice must be transmitted after the shipment leaves your dock but before it arrives at the retailer's DC. Many suppliers generate ASNs manually or in batch at end of day, which creates a window where shipments arrive before the ASN. Automate ASN generation to trigger at the point of shipment.

2. Missing or Incorrect GS1 Barcodes

Retailers scan GS1-128 barcodes at receiving to match physical cartons against the electronic ASN. If the SSCC-18 on the label doesn't match what's in the 856, the shipment fails receiving. Common causes: reusing SSCC numbers, generating barcodes from a test range, or printing labels from a system that isn't connected to the ASN generation process.

The GS1 US barcode standards documentation covers the SSCC-18 format and serial number allocation rules.

3. Wrong Unit of Measure (UOM)

Your system says you shipped 12 eaches. The retailer's PO was for 1 case of 12. The ASN says 12 EA instead of 1 CA. This mismatch cascades through the entire transaction chain: the invoice won't match the PO, three-way matching fails, and payment gets held. Always confirm UOM at the item setup level with each retailer.

4. PO Acknowledgment Delays

Some retailers (especially Amazon) cancel POs if the 855 acknowledgment isn't received within their window, typically 24 to 48 hours. If your EDI system doesn't auto-generate 855s, you need a process to review and respond to inbound POs the same day they arrive.

5. Incorrect Segment Data

EDI files are built from segments, and each retailer has specific requirements for which segments must be populated and how. A missing REF segment with a department number, an incorrect DTM date format, or a wrong qualifier code in the N1 loop can cause the entire transaction to be rejected. Use our free EDI Inspector to parse and validate your EDI files before sending them to a trading partner.

Getting Started as a Retail Supplier

If you're setting up retail EDI for the first time, here's the sequence that works.

Step 1: Get the Retailer's Vendor Compliance Guide

Every major retailer publishes a vendor compliance manual or routing guide. This document tells you exactly which EDI transactions they require, what segments must be populated, what barcoding standards they expect, and what their chargeback schedule looks like. Read it before you do anything else.

Step 2: Choose Your EDI Approach

You have three main options for supplier EDI:

• Web EDI portal: You log into a website and manually enter order data. Low cost, but doesn't scale and still involves manual data entry. Works for suppliers with fewer than 5 orders per week from a single retailer.
• Full-service EDI provider: A traditional VAN (Value Added Network) or managed EDI service handles translation, mapping, and transmission. Monthly costs range from $300 to $2,000+ depending on volume and number of trading partners.
• Order automation platform: A modern platform like OrderSync that handles EDI alongside other order formats (PDF, email, CSV), with built-in validation and ERP integration. This approach makes sense if you're dealing with multiple retailers or mixed-format order channels.

For a deeper look at options for smaller teams, see our guide to EDI for small business.

Step 3: Set Up Your Item Master

Before you can exchange EDI documents, your item data needs to match the retailer's. That means mapping your internal SKUs to the retailer's item numbers (UPC, GTIN, DPCI, or whatever identifier they use). Get this wrong and every transaction fails.

Step 4: Test with the Retailer

Every retailer has a testing phase where you exchange sample EDI documents and they validate the format, content, and timing. This is typically done through their EDI coordinator or a testing portal. Don't rush this step. Failed testing means you go back to the end of the queue.

Step 5: Go Live and Monitor

Once testing passes, you start processing real orders. Monitor your first 30 days closely. Watch for rejected transactions, chargeback notifications, and compliance scorecard updates. Fix issues immediately because most retailers have a grace period for new suppliers, but it's short.

Step 6: Validate Your Files

Even after go-live, validate your EDI files regularly. Transaction formats change, retailers update their requirements, and system updates can introduce new issues. Use the free EDI Inspector to spot problems before your trading partner does.

Frequently Asked Questions

What does retail EDI cost for a new supplier?

Costs vary based on your approach. Web EDI portals start around $50 to $100 per month. Full-service EDI through a VAN runs $300 to $2,000+ per month depending on transaction volume and number of trading partners. Order automation platforms with built-in EDI typically cost $500 to $1,500 per month. The bigger cost consideration is chargebacks: a single ASN failure can cost $500 or more, which quickly exceeds a monthly EDI subscription.

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

Plan for 8 to 12 weeks from the time you start vendor onboarding. That includes selecting an EDI solution (1 to 2 weeks), mapping and configuration (2 to 4 weeks), testing with the retailer (2 to 4 weeks), and go-live stabilization (2 weeks). Some retailers move faster, but Walmart and Target often have queues for testing slots.

Can I use the same EDI setup for multiple retailers?

Yes, but with caveats. The core transaction types (850, 856, 810, 997) are standardized under ANSI X12, so the general structure is the same. However, each retailer has unique segment requirements, qualifier codes, and data expectations. Your EDI platform needs retailer-specific maps for each trading partner. A good EDI provider handles this mapping for you.

What happens if I miss an EDI compliance deadline?

The consequences depend on the retailer. Walmart applies OTIF chargebacks at 3% of COGS for the non-compliant portion. Target issues per-shipment chargebacks, often $500 or more. Amazon may cancel POs entirely. Repeated failures can lead to reduced order volume, vendor scorecard downgrades, or in extreme cases, loss of the retail account.

Do I need EDI if the retailer only sends me a few orders per week?

Most likely, yes. Retailer EDI requirements are usually mandatory regardless of order volume. Even if you only receive 3 POs per week from Target, they still expect electronic 850s, 856s, and 810s. A web EDI portal can handle low volume affordably, but you still need to be in the electronic loop. Check the retailer's vendor compliance guide to confirm whether there's a volume threshold or manual exception.

---

Retail EDI isn't optional if you want to sell to major retailers. The good news is that the technology is more accessible than it was a decade ago, and the requirements, while specific, are well documented. Start with the compliance guide, pick the right EDI approach for your volume and budget, and invest time in testing before you go live.

If you're evaluating EDI solutions or need to validate your transaction files, try OrderSync's free EDI Inspector to parse and check your EDI data instantly.