EDI 850 Purchase Order: What Small Suppliers Need to Know to Get Paid

The EDI 850 Is Where the Money Starts — and Where Mistakes Are Expensive

The EDI 850 purchase order is the transaction set that kicks off every retail relationship. Walmart sends you an 850. Target sends you an 850. Kroger sends you an 850. If you can’t receive it, parse it correctly, and respond to it properly, nothing else in the supply chain works — and you’ll be eating chargebacks before your first pallet ships.

For small suppliers getting into retail EDI for the first time, the 850 is often where the confusion starts. This post breaks down exactly what the transaction contains, what the big three retailers actually require, and where suppliers most commonly blow it.

What’s Actually Inside an EDI 850

The 850 is an X12 transaction set structured in segments. The ones that matter most in practice:

• BEG segment — purchase order type, PO number, date. Miss a required qualifier here and your system may reject the order silently.
• REF segments — retailer-specific reference numbers. Walmart uses these heavily for department and buyer codes.
• DTM segments — ship dates, cancel dates, and delivery windows. These are not suggestions. A cancel date on a Walmart 850 means the DC will refuse the shipment after that date, full stop.
• PO1 line items — each item with quantity, unit price, unit of measure, and item identification (UPC, buyer part number).
• CTT transaction totals — line item count. If your system’s count doesn’t match, expect a 997 rejection.

A typical Walmart 850 for a consumables supplier will have 15–40 PO1 segments. A seasonal PO for a mid-size general merchandise supplier can run 200+ lines. Your EDI software needs to handle both without choking.

Walmart, Target, and Kroger: Where Their Requirements Diverge

All three retailers use the 850, but their implementation guides are not interchangeable.

Walmart is the most prescriptive. Their EDI 850 requires AS2 connectivity (no SFTP option for most suppliers), specific qualifier values in the N1 ship-to and bill-to segments, and a strict item setup process through Retail Link before any PO will even reference your items correctly. If you’re a new supplier and haven’t completed item setup in Retail Link, the 850s you receive will have UPCs that don’t match your catalog. That’s a setup problem, not an EDI problem — but it shows up as an EDI problem at 11pm when your first PO drops.

Target uses AS2 and requires 850 acknowledgment via a 997 within 24 hours. They also use the REF*DP segment for their department number, which some generic EDI translators strip out. Lose that segment and your 856 ASN won’t map correctly downstream.

Kroger allows SFTP for smaller suppliers and their 850 structure is comparatively straightforward, but their cancel date enforcement is aggressive. Kroger will chargeback 2–3% of PO value for late shipments tied to dates in the DTM segment. That’s a real number — on a $50,000 PO, you’re losing $1,000–$1,500 for a shipment that arrives two days after a cancel date.

The Four Compliance Failures That Generate Chargebacks

After working through hundreds of supplier setups, the same failures show up repeatedly:

1. Ignoring the cancel date — The DTM*002 segment contains the cancel-by date. Suppliers treat it as a soft deadline. Retailers treat it as a hard cutoff with financial consequences.
2. Unit of measure mismatches — Your item catalog says “EA” (each). The 850 says “CA” (case). You ship eaches. The DC rejects the pallet. This is an item setup issue that surfaces as a shipping compliance failure.
3. Not sending a 997 acknowledgment — Technically the supplier receives the 850 and sends back a 997. If your system swallows the 850 but doesn’t fire the 997, the retailer’s system will resend the PO — and now you have a duplicate order problem. See our full guide on 997 acknowledgments here.
4. ASN timing failures tied back to the 850 — Your 856 ASN has to reference the correct PO number and line items from the 850 exactly. One transposed digit in the PO number reference segment means a non-matching ASN, which means a receiving chargeback. More on ASN requirements here.

What This Means for Your EDI Software Choice

Enterprise EDI platforms will happily charge you $500–$800/month to handle your Walmart 850s. For a supplier doing $300K in retail revenue, that’s 2–3% of top line going to software fees before you count chargebacks. That’s not a reasonable trade.

Smaller, implementation-focused solutions built specifically for suppliers — like EDIBridge — handle the 850/856/810/997 workflow at a fraction of that cost, with mapping that’s already configured for Walmart, Target, and Kroger implementation guides rather than requiring you to build it from scratch.

The 850 isn’t complicated. But it does require that your software handles it correctly and that your team understands what the segments mean before a $200,000 seasonal PO drops on a Friday afternoon.

Get that foundation right and the rest of the EDI workflow follows. Get it wrong and you’re negotiating chargebacks instead of reorders.

---

Need help mapping your first 850 or auditing existing EDI compliance? Tebco Forge works with small suppliers to get compliant without enterprise pricing.