What Is an EDI 850 Purchase Order?
The EDI 850 is the X12 transaction set that carries a purchase order between a buyer and a supplier. It tells the supplier what to ship, how much, at what price, where it goes, when it needs to arrive, and under what payment terms. For most suppliers selling into retail, distribution, or grocery, the 850 is the first EDI document of every order and the trigger for every downstream transaction.
EDI 850 Segments and Structure
A standard 850 follows a header / detail / summary pattern. The segments you will see in almost every retailer spec:
- BEG - PO number, PO date, and purpose code (new, change, cancel).
- REF - Department number, vendor number, and contract references.
- DTM - Requested ship, cancel, and delivery date windows.
- N1 / N3 / N4 - Ship-to, bill-to, and buying party names and addresses.
- PO1 - Line item with UPC or GTIN, quantity, unit of measure, and unit price.
- PID - Product description for each line item.
- CTT - Total line item count and hash totals for validation.
- SE - Transaction set trailer and segment count.
EDI 850 Example Flow
A typical retail 850 cycle looks like this: the retailer transmits an 850 to the supplier's VAN or AS2 endpoint. The supplier returns a 997 functional acknowledgment within minutes, then an 855 PO acknowledgment within 24 hours confirming acceptance, changes, or rejection. When the goods ship, the supplier sends an 856 ASN with GS1-128 labels and an 810 invoice that must three-way match the 850 and 856 for the retailer to auto-pay.
Common 850 Compliance Requirements
Large retailers enforce strict rules on how 850s are processed:
- 855 PO acknowledgment must be returned within 24 hours of receipt.
- Every line item must match the current item master - UPC, vendor part, and price.
- Ship-by and cancel dates must be honored to avoid OTIF chargebacks.
- Any deviation requires either an 855 with changes or an 860 PO change.
- Missing or late 997 acknowledgments are treated as non-receipt of the order.
How Yoke Handles the EDI 850 for You
Yoke maps each retailer's 850 directly into your ERP or order system, validates every PO against your item master and pricing rules before it lands, auto-generates the 997 and 855 within the partner's required window, and monitors for missing or duplicate POs. If a retailer changes their 850 spec, we update the map - you do not.
Frequently Asked Questions
Quick answers to the questions buyers and suppliers ask most about this transaction.
- What is an EDI 850? The EDI 850 is the X12 transaction set that carries a Purchase Order from a buyer to a supplier. It contains the items, quantities, prices, ship-to address, dates, and payment terms needed to fulfill the order.
- What is the difference between an EDI 850 and a regular PO? There is no business difference - both are purchase orders. The 850 is simply the standardized electronic format that lets buyers and suppliers exchange POs system-to-system instead of by email, fax, or portal entry.
- What is the response to an EDI 850? Suppliers respond first with a 997 functional acknowledgment (confirming receipt of the file) and then with an 855 Purchase Order Acknowledgment (confirming whether they can ship the order as requested, with changes, or with rejections).
- How long do I have to acknowledge an EDI 850? Most large retailers require the 855 PO acknowledgment within 24 hours of receiving the 850. Missing that window typically triggers compliance penalties and vendor scorecard deductions.
- What comes after the 850 in the EDI cycle? The full cycle is 850 (PO) -> 997 (ack) -> 855 (PO acknowledgment) -> optional 860 (PO change) -> 856 (ASN at ship) -> 810 (invoice) -> 820 (remittance).