What Is EDI 850 Purchase Order? A Retail Overview

EDI 850 Purchase Order is the EDI transaction used by a buyer to transmit a purchase order to a supplier. In retail, the 850 replaces paper or emailed purchase orders with a structured, machine-readable message that carries line-item details, quantities, agreed prices, delivery dates, ship-to and bill-to information, and special instructions.

The 850 serves as the primary electronic notice that a retailer intends to buy goods. Unlike a human-readable PDF or an email, the 850 follows a defined segment and element structure (typically ASC X12 in the United States) so receiving systems — a supplier's ERP or WMS — can automatically validate, acknowledge, and convert the order into fulfillment workflows. That automation reduces transcription errors, speeds order processing, and supports higher transaction volumes across omnichannel retail networks.

How The 850 Is Structured

The 850 uses a series of segments and elements. Common segments include:

• BEG: Purchase order beginning segment with PO number and type.
• REF: Reference identifications such as customer or contract numbers.
• N1: Party identification for buyer, ship-to, and sold-to locations.
• PO1: Line-item detail: SKU, quantity, unit of measure, unit price.
• TDS/CTT: Summary totals and transaction count.

Retailers may extend the 850 with trading-partner-specific requirements (e.g., additional reference qualifiers, promotional flags, or routing codes) documented in an EDI implementation guide or trading partner agreement.

Why Retailers Use The 850

Retail operations choose the 850 because it streamlines the order-to-fulfill process. Key benefits:

• Speed: Electronic transmission occurs instantly versus days for manual orders.
• Accuracy: Standardized fields reduce incorrect SKUs, quantities, and addresses.
• Scalability: Handles large volumes typical of category buyers and omni-channel distribution.
• Integration: Direct mapping into ERP, WMS, and order-management systems for faster pick/pack/ship.

How The 850 Fits Into Retail Workflows

Typical retail sequence: planner or ordering system generates an 850 → transmitted via VAN, AS2, or API gateway to supplier → supplier system validates and sends a 997 Functional Acknowledgment (or a 997-equivalent) → supplier confirms availability via a 855 Purchase Order Acknowledgment or proposes changes via a 860 Change Order. On fulfillment, suppliers send 810 invoices and 856 advance ship notices (ASNs) that reference the original PO number. Proper PO number and line-level matching are critical for receiving, invoice reconciliation, and chargebacks.

Common Variations And Practical Considerations

Retailers must plan for variations:

• Master Data Alignment: SKUs and GTINs must match between buyer and supplier to prevent mismatches.
• Unit Of Measure: BOL vs. pack vs. each requires consistent UOM codes.
• Routing And Carrier Info: Some retailers include carrier and freight terms on the 850; others use separate TMS messages.
• Promotions And Allowances: Discount or promotional codes may be transmitted as additional segments, but require prior agreement to avoid disputes.

Who Is Responsible For What

Responsibility for data quality and integration is shared:

• Buyer: Generates the 850, ensures accurate unit prices, delivery terms and ship-to data, and maintains master item data with suppliers.
• Supplier: Validates the 850, sends acknowledgments (855), confirms availability, and maps PO lines into fulfillment systems.
• IT/Integration Provider: Manages translation, communication protocols (AS2, SFTP, VAN), and error handling.

Practical Example

A regional retailer issues an 850 for 300 units of SKU 12345 with requested delivery to a distribution center on 2026-11-01. The 850 includes BEG with PO number, PO1 lines with quantities and price, N1 for ship-to, and REF with the retailer’s contract ID. The supplier receives the 850 via AS2, validates SKU mapping, sends a 997 acknowledgement within minutes, and an 855 later that day confirming 300 units available and scheduled for shipment. The supplier then generates an 856 ASN when goods leave the dock, referencing the PO number so the retailer’s inbound system can pre-advise receipts.

Best Practices For Retail Implementation

Retailers should adopt these practices to reduce friction:

• Standardize Item Identifiers: Use GTINs/UPC and ensure master-data synchronization with suppliers.
• Agree On Protocols: Establish clear AS2/VAN/SFTP arrangements and expected acknowledgements and turnaround times.
• Test Early: Perform thorough mapping tests and sample transactions before going live.
• Monitor Transactions: Implement alerts for missing 997s, failed transmissions, or failed line-level validations.

In short, the EDI 850 Purchase Order is the standardized electronic message that initiates retail purchasing between a buyer and a supplier, enabling automated order processing, fewer errors, and faster replenishment cycles.