EDI 850 Purchase Order: The Complete Guide (2026)

The EDI 850 is the purchase order — the document that starts everything. A retailer wants your product; the 850 says what, how much, where, and by when. Everything else in the order-to-cash chain — the 855 acknowledgment, the 856 ship notice, the 810 invoice — exists to answer it.

What's inside an 850

Strip away the X12 syntax and the 850 is a structured order form:

• BEG — the PO number, order type, and date. Every downstream document must echo this PO number exactly.
• REF — the buyer's reference numbers: department, vendor number, promotion codes. Retailers check that these round-trip.
• DTM — the dates that matter: requested ship, cancel-after, must-arrive-by. This segment starts the compliance clock.
• N1 — who and where: ship-to DCs or stores, bill-to parties, usually by location number.
• PO1 — the lines: quantity, unit, price, and item identifiers (UPC, GTIN, and the buyer's own item number).
• CTT — a control total so nothing gets truncated in transit.

Two retailer-specific wrinkles trip up new suppliers. First, SDQ segments: Walmart, Dollar General, and Home Depot pack store-level distribution quantities into SDQ segments on a single PO line — one line, forty stores, forty quantities. You have to explode those into real allocations before your warehouse can pick. Second, identifier cross-referencing: Target sends DPCI numbers, Walmart wants GTINs, everyone has an internal item number. Your system speaks SKU; the map has to translate both directions.

The lifecycle of an 850

A well-run 850 flow looks like this:

1. The retailer transmits the 850 over AS2, SFTP, or a VAN.
2. Your EDI layer acknowledges receipt with a 997 within minutes — automatic, both directions.
3. The order lands in your ERP as a sales order, items and ship-tos already cross-referenced.
4. You respond with an 855 confirming what you can actually ship — most majors expect it within 24 hours.
5. When freight moves, the 856 mirrors the shipment; the 810 bills it.

The failure mode is almost never syntax. It's reference data: an item number that doesn't cross-reference, a ship-to location missing from your table, a department number that gets dropped and then fails the invoice match three weeks later. The fix is validating against each partner's companion guide before the document reaches your ERP — not discovering the mismatch when the chargeback arrives.

Why same-day processing matters

Retail compliance programs measure you from the moment the 850 transmits. Walmart's OTIF clock, Target's ship windows, Amazon's 24-hour acknowledgment expectation — all start ticking whether or not anyone opened the order. A PO that sits in a portal until Monday is a compliance incident that hasn't happened yet.

That's the case for automation, and it's the whole design of EDISQ: the 850 arrives, validates, lands in NetSuite, QuickBooks, or whichever system you run, and the 855 goes back — no re-keying, no portal checking, no Monday surprises.

What it costs

Traditional EDI providers price the 850 into a monthly subscription plus per-partner fees plus kilocharacter charges. EDISQ prices it like everything else: the first 25 documents each month are free, then from $0.50 per document, decreasing with volume. An 850 in is one document. That's the entire model.

If you're facing your first 850 from a major retailer, start with the partner's page in our trading partner directory — each one lists the documents required, the compliance rules that carry deductions, and how long setup actually takes.

FAQ