EDI 850 Purchase Order
An EDI 850 is the X12 purchase order. A buyer sends it to a supplier to order goods, and it starts the order cycle that continues with the 855 acknowledgment, the 856 ship notice and the 810 invoice. We read every 850 inside your ERP and turn it into a real order against your own items.
+ RULES
- Top Rated PlusUpwork talent badge
- 100%Upwork Job Success score
- 17,800+Hours billed on Upwork
- 2012AppsXone established
“They integrated with multiple third-party systems and they did a great job with it. It’s stable, scalable, which was our goal, and we saved a lot of time and effort.”
What the 850 does, and what follows it
-
850Purchase order. The buyer orders. It names the items, quantities, prices, ship-to locations and the dates the buyer expects. -
997Functional acknowledgment. Your system confirms the 850 arrived and could be read. It says nothing about whether you accept the order. -
855Purchase order acknowledgment. You confirm what you can actually ship, line by line, with quantities and dates. -
860Purchase order change. Some buyers send changes to an order already placed. Whether your partner uses it is set by its implementation guide. -
856Advance ship notice. Sent when the goods ship. See EDI 856 advance ship notice. -
810Invoice. Bills for what shipped. See EDI 810 invoice.
Key data in an 850 purchase order
An 850 answers four questions: who is ordering, what they want, where it goes and when. The segments below usually carry that information. Which segments are required, and how each field is filled, is set by the buyer's implementation guide and not by the X12 standard alone.
-
BEGBeginning segment. The purchase order number, the order date and the order type. -
REFReferences. Extra identifiers the buyer attaches, such as a department or vendor number. -
DTMDates. Requested ship, delivery or cancel dates. -
N1Parties and locations. Buyer, ship-to and bill-to, with address detail in the segments that follow. -
PO1Line items. One per line: quantity, unit, price and the item identifiers, which may be the buyer's item number, a UPC or your own SKU. -
CTTTotals. The number of lines, used to check that the whole order arrived.
Wholesale and dropship orders both arrive as an 850
The same transaction set carries different kinds of order. A wholesale 850 orders stock in bulk for the buyer's own warehouse. A dropship 850 is a single customer order that you ship to the customer's address. They need different handling downstream, which is why programs such as Amazon Vendor Central Wholesale and Direct Fulfillment are mapped separately.
Amazon uses the 850 in both of its Vendor Central programs. Sellers on Seller Central do not receive 850s at all, because that side runs on SP-API. What Amazon EDI is explains the split.
How we build 850 processing inside your ERP
Parsed straight into the order tables
The 850 is read inside your ERP with the EdiFabric .NET library and written as a real sales order. Nobody retypes it from a portal.
Partner items mapped to your SKUs
The buyer's item numbers and UPCs are cross-referenced to your own items. A line that does not map is flagged for a person instead of being dropped.
Acknowledged from the order as accepted
The 855 is generated from the order as your system accepted it, so the acknowledgment confirms quantities and dates you can actually meet.
Raw file stored with the order
The original 850 is kept next to the order it created. A later dispute about what was ordered is a lookup.
The 850 in a live multi-partner ERP
- 850 purchase orders from retail trading partners, including Amazon Vendor Central and Costco Wholesale, read inside one ERP using the EdiFabric .NET library, with the mapping in the ERP's own code.
- Amazon Vendor Central Wholesale and Direct Fulfillment orders handled as separate connections, each with its own mapping.
- Orders from EDI partners and from marketplace APIs land in the same order queue, against one inventory position.
- Scheduled EDI jobs polling FTP on schedules as short as every ten minutes, tracked on a monitoring dashboard.
What goes wrong with an 850
- An item on the 850 that your system does not recognize A common pattern. The buyer orders by its own item number or a UPC and no cross-reference exists. Keeping the partner item mapping in the ERP, and holding the order for review when a line does not map, stops it disappearing.
- The price on the 850 differs from yours A common pattern after a price change that reached only one side. Comparing the 850 price with your own price list on arrival shows the difference before the order ships, when it is still cheap to resolve.
- The same order arrives twice A common pattern when a file is resent. Checking the purchase order number against orders already received prevents a duplicate order.
- Pack or unit of measure mismatch A common pattern. The buyer orders in cases and your system holds eaches, or the reverse. The unit conversion belongs in the item mapping, so quantities are right on the order, the ship notice and the invoice.
EDI 850 questions
What is an EDI 850?
The X12 purchase order. A buyer sends it to a supplier to order goods. It carries the purchase order number, the items, quantities, prices, ship-to locations and dates.
What is the difference between an 850 and an 855?
The 850 is the buyer's order. The 855 is the supplier's reply, confirming what will actually ship, with quantities and dates.
Does a 997 mean the 850 was accepted?
No. A 997 only confirms the file arrived and could be read. Accepting the order is the job of the 855.
Can an 850 be changed after it is sent?
Some buyers send an 860 purchase order change. Others cancel and reissue. Your partner's implementation guide says which applies.
Can 850s be loaded into an ERP we did not build?
Often yes. What matters is whether your order and item data is reachable, not who wrote the ERP. We confirm that during scoping.
Related to the EDI 850
Are purchase orders still being retyped from a portal?
Tell us which trading partners send you orders and what your ERP runs on. We will tell you what it takes to have each 850 arrive as a real order.