EDI 850 Purchase Order

EDI 850 Definition

The EDI 850 Purchase Order is an electronic version of a paper purchase order transaction that is used by buyers to place an order for goods or services from a supplier. The supplier sends an EDI 997 functional acknowledgment back to the buyer to confirm the receipt of the EDI 850 Purchase Order. The trading partner sends an EDI 855 Purchase Order Acknowledgement (EDI 855) to the supplier to confirm the requirements in the purchase order.

What EDI 850 Represents in Real Life

An EDI 850 is not just a file format. It is the trigger for real operational activity.

When an EDI 850 is received:

• • A sales order is created in the supplier’s ERP
  • Inventory is allocated or production is scheduled
  • Warehouse teams prepare to pick and pack
  • Shipping and billing workflows are set in motion

In other words, the EDI 850 is the starting signal for order-to-cash.

EDI 850 Specification

This X12 Transaction Set contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

Source: Accredited Standards Committee X12. ASC X12 Standard [Table Data]. Data Interchange Standards Association, Inc., Falls Church, VA. https://x12.org/node/4397

Components of an EDI 850 Purchase Order include:

• Purchase order number & date
• Shipping details & instructions
• Item brand names, SKUs or model numbers
• Payment terms, such as on delivery or in 30 days
• Carrier details

EDI 850 can also include:

• Item Price and Quantity
• Name & Address of the Buyer
• Name & Address of the Supplier
• Any additional terms for the sale, such as discounts, etc
• Billing address
• Delivery date
• Price per unit

Related EDI Transactions

• EDI 810 – Invoice 
• EDI 856 – Advance Ship Notice 
• EDI 855 – Order Acknowledgement 
• EDI 860 – Order Change Request 
• EDI 812 – Credit / Debit Adjustment
• EDI 820 – Payment or Order Remittance 
• EDI 832 – Price/Sales Catalog
• EDI 830 – Planning Schedule with Release Capability
• EDI 846 – Inventory Inquiry
• EDI 867 – Product Transfer and Resale Report File Format
• EDI 870 – Order Status Report
• EDI 875 – Grocery Products Purchase Order
• EDI 990 – Response to a Load Tender
• EDI 997 – Functional Acknowledgment

EDI 850 Sample File Format (Raw EDI 850)

ISA*00*          *00*          *12*111111111      *12*222222222      *230516*1440*U*00401*000192755*0*P*>
GS*PO*111111111*222222222*20230516*1440*220893*X*004010
ST*850*0001
BEG*00*SA*240585438**20230516
CUR*X6*USD
REF*SU*LFK*8004456937
REF*CO*000000000913278425
REF*IA*25122
REF*MR*D2C
REF*SA*NAME NOT SUPPLIED
REF*X9*3335455393
REF*YD*8004456937
FOB*DF********CC
TD5*****UNSP
CTB*OR*.
N1*BT*John Doe
PER*BD**TE*8001234567
N1*PO**93*00907
N1*SO*John Doe
PER*BD****NP*850 3041407*EM~
N1*ST*John Doe
N3*1234 Test Dr
N4*Test*FL*32566*USA
PER*RS********1

What an EDI 850 Looks Like Inside Elevate

While the raw EDI file is machine-readable, our cloud-based EDI platform Elevate presents the data in a clear, business-friendly format.

Inside Elevate, users can see:

• • Who sent the PO
  • When it was received
  • Which items were ordered
  • Quantities, pricing, and ship-to details

Any special instructions included by the buyer

EDI 850 Purchase Order in Elevate

This visibility allows operations, customer service, and IT teams to understand the order without reading raw EDI code.

Real-World Example: Manufacturer Receiving an EDI 850

A retailer sends an EDI 850 for 1,500 units of a product.

• • The EDI 850 arrives via AS2
  • Elevate validates and parses the file
  • A sales order is created in the ERP
  • Inventory is allocated or production is scheduled
  • The supplier sends an 855 acknowledgment
  • Warehouse fulfillment begins

Without EDI, this process would require manual entry and multiple handoffs.

Why EDI 850 Accuracy Matters

Even small errors in an EDI 850 can cause:

• • Incorrect shipments
  • Pricing disputes
  • Missed delivery windows
  • Chargebacks
  • Delayed payment

That’s why monitoring, validation, and visibility are critical, especially when handling multiple trading partners.