7 EDI Document Types Every eCommerce Brand Should Know

When a major retailer like Walmart, Target, or Home Depot onboards you as a supplier, they don't hand you a simple purchase order form. They hand you a compliance guide full of three-digit numbers: 850, 855, 856, 810, 997. Each number is a specific document type in the EDI (Electronic Data Interchange) standard, and each one plays a defined role in the order lifecycle.

Understanding what these documents do isn't just a technical exercise. It's the foundation for passing compliance audits, avoiding chargebacks, and keeping your biggest accounts running smoothly. Here are the seven you'll encounter most often.

1. EDI 850: Purchase Order

The 850 is where every retail transaction starts. It's the electronic purchase order a retailer sends to you, containing what they want to buy, how much, at what price, and where to ship it.

If you only learn one EDI document, this is the one. Everything downstream, from acknowledgment to shipment to invoice, depends on how quickly and accurately you process the 850. For a detailed breakdown of what the 850 contains and how it connects to your ERP software, check out our complete guide to the EDI 850 for in-depth coverage.

2. EDI 855: Purchase Order Acknowledgment

The 855 is your reply to the retailer's 850. It confirms that you received the purchase order and tells them whether you can fulfill it. You can accept the order in full, accept it partially (if some items are out of stock), or reject it.

Speed matters here. Most major retailers expect an 855 within hours of receiving the 850, not days. A late or missing acknowledgment can trigger compliance deductions before you've even shipped anything. If your ERP software is connected to your EDI provider, the 855 can generate automatically from the sales order the 850 created, which eliminates the manual step where delays usually happen.

3. EDI 856: Advance Ship Notice (ASN)

The 856 tells the retailer exactly what's on the truck before it arrives: which items, what quantities, how they're packed, and which purchase order lines they fulfill. Retailers use the ASN to plan receiving at their distribution centers, so accuracy is critical.

The 856 is also the document most likely to trigger chargebacks if it's wrong. An ASN that doesn't match the physical shipment, whether it's a wrong quantity, a missing carton, or a mismatched serial number, can result in fines that eat into your margin on the entire order. Walmart's OTIF program and similar retailer compliance frameworks lean heavily on ASN accuracy as a scoring metric.

For eCommerce brands managing EDI costs, the 856 is also worth watching because a single order shipped in multiple cartons can generate multiple ASN transactions, each one billable.

4. EDI 810: Invoice

The 810 is the electronic invoice you send the retailer after shipment. It contains the line items, quantities, prices, and total amount due, drawn from the same order data as the 850 and 856.

The key rule with the 810 is that it has to match. The prices on the invoice must match the prices on the original purchase order. The quantities must match what you actually shipped (per the 856). When the numbers don't align, the retailer's automated three-way match (PO to ASN to invoice) fails, and payment gets held until someone resolves the discrepancy. In an ERP system, the 810 draws from the same transaction record as the 850 and 856, so the matching problem largely disappears.

5. EDI 846: Inventory Inquiry/Advice

The 846 is a real-time or scheduled inventory feed. It tells your retail partner how much stock you have available for them to order against. Some retailers pull this data to inform their own replenishment algorithms. Others use it for drop-ship programs where they're selling your products but you're holding the inventory.

For eCommerce brands managing inventory across multiple channels, the 846 adds another layer of complexity: The inventory you report to a retail partner via EDI needs to reflect what's actually available after accounting for your own direct-to-consumer orders, marketplace commitments, and safety stock reserves. An ERP system that maintains a single real-time inventory pool across all channels will make 846 reporting accurate. A disconnected system will make it a guessing game.

6. EDI 852: Product Activity Data

The 852 is the document retailers send back to you. It contains point-of-sale data or warehouse movement data showing how your products are performing at their end: what's selling, what's sitting, and what's moving between their distribution centers.

Not every retailer shares 852 data, but those that do give you a direct window into demand patterns you can't see from your own sales data alone. Brands that use this data well can adjust production schedules, plan promotions, and fine-tune replenishment quantities based on actual sell-through rather than just reorder signals.

7. EDI 997: Functional Acknowledgment

The 997 is the simplest document on this list, but skipping it creates problems. It's an automated receipt that confirms an EDI document was received and could be read by the receiving system. It doesn't confirm the contents are correct or that anyone has acted on them. It just says "we got it and the format was valid."

Think of it as a read receipt for EDI. Most EDI providers generate 997s automatically, so your team will rarely interact with them directly. But when a retailer claims they never received your ASN or invoice, the 997 is your proof that the document was delivered and accepted by their system.

How These Documents Work Together

A single retail order touches most of these documents in sequence:

• The retailer sends the 850, you respond with an 855.

• You ship and send the 856, you invoice with the 810.

• The retailer confirms receipt of each document with a 997.

And depending on the relationship, you may exchange 846 inventory feeds and receive 852 sell-through data on an ongoing basis.

When these documents flow through a connected ERP system, each one draws from and updates the same transaction record. The 855 generates from the sales order the 850 created. The 856 pulls from the shipment. The 810 matches both. Errors drop dramatically because nobody is rekeying data between systems.

When they flow through disconnected tools, each document becomes a manual touchpoint where data can drift, timing can slip, and compliance penalties can accumulate. For brands scaling into retail partnerships, the document flow is where EDI and ERP integration pays for itself.

Are you on the smaller side and still wondering whether an ERP solution is the right move for your business? Visit our How It Works page to learn more about our implementation process, or click below to take our ERP Readiness Quiz.