850 Purchase Order
The buyer sends order instructions.
Purchase-order fundamentals
What Is an EDI 850 Purchase Order?
A practical guide to the X12 transaction set businesses use to send purchase-order instructions.
EDI 850 is the X12 Purchase Order transaction set. A buyer commonly sends it to a supplier to communicate an order number, dates, parties, line items, product identifiers, quantities, prices, shipping instructions, schedules, and other purchasing details. The exact content and required qualifiers depend on the parties' agreement.
What problem does an 850 solve?
An 850 replaces a paper, emailed, or proprietary purchase-order form with a structured business message. A retailer, distributor, manufacturer, healthcare organization, or other buyer can send consistent ordering instructions to a supplier. The receiver can route those instructions into order-management, warehouse, procurement, or ERP workflows without manually rekeying every line.
The transaction can carry a simple one-line order or a much richer order with multiple destinations, delivery schedules, sublines, allowances, tax information, packaging details, and references. It communicates what the source says; it does not by itself prove that the supplier accepted or can fulfill the order.
Where the 850 fits in a B2B purchasing flow
855 Purchase Order Acknowledgment
The supplier may respond with order acceptance or changes. Read the EDI 855 guide.
856 Ship Notice / Manifest
The supplier may describe a shipment before delivery. Read the EDI 856 guide.
810 Invoice
The supplier may request payment for delivered goods or services. Read the EDI 810 Invoice guide.
This is a conceptual sequence, not a universal requirement. Partner workflows vary. Some relationships omit, replace, combine, or add transactions. This product supports 850, 855, 856, and 810 processing.
Important EDI 850 structures
ISA, GS, and ST
Identify the interchange, functional group, and 850 transaction boundary.
BEG
Establishes the purchase-order purpose, type, order number, and order date.
CUR, REF, and DTM
Carry qualified currency, reference, and date information at their applicable scopes.
N1
Introduces a qualified party such as buyer, supplier, Ship-To, or Bill-To; the qualifier controls its role.
PO1, PID, PO4, and CTP
Describe line identity, quantity, unit, price, products, descriptions, packaging, and alternate pricing.
SAC
Reports a qualified allowance or charge occurrence; it is not automatically an order-level adjustment total.
SCH and SDQ
Represent schedules and destination quantity pairs without creating extra canonical line rows.
SLN
Creates a child subline owned by the active PO1 line.
CTT, SE, GE, and IEA
Close and summarize source structures. CTT01 is a reported line-item count, not an order total.
These descriptions are practical orientation, not a reproduction of an X12 implementation guide or proprietary code tables.
PO1 lines, product qualifiers, and SLN children
A PO1 establishes a purchase-order line. Product identifiers appear as qualifier/value pairs: for example, BP often identifies a buyer-assigned part and VP often identifies a vendor-assigned part. Those meanings come from the qualifier; neither code is universally required.
An SLN is a child subline, not another independent parent PO1. Smart Mapping therefore emits one row for each PO1 and one additional row for each SLN child. Repeating structures remain collection fields instead of multiplying a line into Cartesian combinations.
Which 850 releases are tested here?
The current product is tested against the generic releases 004010, 004030, and 005010. Other EDI 850 releases and partner implementation references exist, but they are not advertised as supported/tested by this implementation.
What an 850 does not guarantee
An 850 is an order instruction, not evidence of supplier acceptance, shipment, invoicing, or payment. A mapped amount is not automatically a guaranteed purchase-order total. Currency, unit-of-measure, allowance, tax, schedule, and partner rules can make aggregation unsafe.
This converter is not X12-certified and does not certify trading-partner acceptance. Use the applicable licensed standard and partner guide for production obligations. Continue with the reading guide, inspect the 210-field data map, or open the browser-local EDI Viewer.