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.

Sent by: Buyer/ Retailer/ Distributor

Received by: Supplier/ Vendor/ Manufacturer

Response documents: EDI 997 (Functional Acknowledgement) + EDI 855 (Purchase Order Acknowledgement)

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

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 Each Line in EDI 850 Format Means

Segment	What it does
ISA	Interchange header — identifies sender, receiver, date, and control number
GS	Group header — identifies the transaction type (PO = Purchase Order)
ST*850	Marks the start of the 850 transaction set
BEG	Beginning segment — contains PO number, PO type, and order date
CUR	Currency — specifies the transaction currency (e.g., USD)
REF	Reference numbers — buyer’s internal identifiers (store number, dept, etc.)
FOB	Freight terms — who pays shipping and how
TD5	Carrier routing — preferred carrier or shipping method
N1	Party identification — identifies buyer (BT = Bill To), ship-to (ST), sold-to (SO)
N3/N4	Address lines — street address, city, state, ZIP, country
PO1	Line item detail — item number, quantity, unit of measure, price, item identifiers
CTT	Transaction totals — number of line items and total quantity
SE	Transaction set trailer — marks end of the 850

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.

How to Start Receiving EDI 850 Purchase Orders

Get your trading partner’s implementation guide — Every retailer publishes their specific 850 requirements. This document defines required segments, valid values, timing, and response expectations.
Set up EDI connectivity — Choose your communication method: AS2 (most common for large retailers), SFTP, or VAN. Your trading partner’s guide will specify which they require.
Build or configure your 850 map — Your EDI system needs a map that translates the incoming 850 into a format your ERP or order management system can process.
Connect to your ERP — The real value of EDI 850 is automatic sales order creation in your ERP (Elevate NetSuite, SAP, Acumatica, QuickBooks, etc.) without manual entry.
Test with your trading partner — Most retailers require a testing cycle before going live. You will send and receive test transactions and get sign-off before production.
Go live and monitor — Once live, monitor for 997 acknowledgements and watch for 855 response deadlines.

Need help with EDI 850 Implementation and more?

Elevate handles every step from trading partner setup to ERP connection to ongoing monitoring. No IT team required.

Tell me more about Elevate

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.

Common 850 EDI Errors and How to Avoid Them

Incorrect PO number format — Most retailers have a specific PO number format. A mismatch causes the supplier’s system to reject or misroute the order. Always validate PO number structure against the trading partner’s implementation guide.
Wrong or missing item identifiers — If the UPC, SKU, or GTIN in the 850 does not match the supplier’s item master, the order cannot be processed automatically. This is one of the most common causes of manual intervention.
Missing or incorrect ship-to location — Multi-location buyers (like Walmart or Target) send 850s to different DCs. If the N1*ST segment has the wrong location code, the supplier ships to the wrong warehouse.
Pricing discrepancies — If the price on the 850 does not match the supplier’s price file, the system flags a discrepancy and holds the order for manual review, delaying fulfillment.
Quantity errors — Ordering in the wrong unit of measure (cases vs. units, pallets vs. cases) causes fulfillment errors that trigger chargebacks.
Late or missing 855 acknowledgement — Many retailers require an EDI 855 response within a specific window (24-48 hours). Missing this window can result in the retailer cancelling or reissuing the order.

EDI 850 Requirements by Major Retailer

Retailer	PO Acknowledgement (855) Required	Window	Notes
Walmart	Yes	24 hours	Must reference Walmart PO number exactly as sent
Target	Yes	24 hours	Requires item-level detail including TCIN
Amazon	Yes (via Vendor Central)	Same day	ASIN must match item master exactly
Home Depot	Yes	48 hours	Requires vendor number in REF segment
Chewy	Yes	24 hours	Drop-ship 850s include consumer address
Kroger	Yes	24 hours	Grocery-specific — some use EDI 875 instead

How EDI 850 Works Across Different Fulfillment Models

DC replenishment (most common): Retailer sends 850 to supplier for bulk shipment to a distribution center. Standard order quantities, ship dates, and pack requirements apply. The 850 includes the DC location code in the N1*ST segment.
Direct-to-store (DTS): Retailer sends 850s with individual store location codes. One purchase order may reference multiple ship-to locations. Suppliers must be able to split fulfillment by store.
Drop-ship: Retailer sends 850 with end consumer’s address in the ship-to field. Order quantities are typically 1 unit per line. The 850 may include gift messaging and special packaging instructions in REF or NTE segments.
Vendor-managed inventory (VMI): The supplier generates the 850 themselves based on inventory data from an EDI 846. The buyer has pre-authorized the supplier to place replenishment orders within agreed parameters.

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.

Last updated: March 2026

FAQs

Q1: Do I need EDI software to receive an EDI 850?

Yes, you need an EDI-capable system like Elevate to receive, translate, and process an EDI 850. Your three options are:
1.In-house EDI software that your IT team manages
2. a fully managed EDI provider like Elevate that handles everything including setup, mapping, trading partner connectivity, and ongoing support — no IT team required
3. a web EDI portal for very low transaction volumes where you manually key in order data.

Most SMBs choose a managed provider because it requires no internal EDI expertise.

Q2: How do I set up EDI 850 with Walmart?

To receive EDI 850 purchase orders from Walmart:
1. Register as a Walmart supplier and obtain your Walmart vendor number.
2. Download Walmart’s EDI implementation guide from Retail Link.
3. Set up AS2 connectivity or connect through a Walmart-approved VAN.
4. Build your 850 map to Walmart’s specifications.
5. Connect the incoming 850 to your ERP for automatic sales order creation.
6. Complete Walmart’s EDI testing cycle and get go-live approval.

A managed EDI provider like Elevate handles all of this for you and has pre-built Walmart maps ready to deploy.

Q3: How long does it take to set up EDI 850 with a new trading partner?

For a straightforward setup with no ERP integration, expect 2-4 weeks from kickoff to go-live with Elevate. If ERP integration is required — connecting NetSuite, SAP, Acumatica, or another system to automatically create sales orders from incoming 850s, the timeline extends to 8-12 weeks depending on complexity. The longest delays typically come from waiting on trading partner test approvals end-to-end, not the technical build itself.

Q4: What ERP systems can process EDI 850 purchase orders automatically?

EDI 850 purchase orders cannot be automatically processed by an ERP because an ERP does not have the EDI functionality. You need to integrate your ERP with an EDI platform like Elevate that maps the incoming 850 data into the ERP’s sales order format and creates orders without manual entry. Elevate supports integrations with all major ERPs like Acumatica, NetSuite and more used by SMBs.

Q5: What are the most common EDI 850 errors?

The most common EDI 850 errors are: incorrect or misformatted PO numbers, wrong item identifiers (UPC or SKU does not match the supplier’s item master), missing or incorrect ship-to location codes, pricing discrepancies between the 850 and the supplier’s price file, quantity errors from wrong units of measure (cases vs. units), and missing required segments based on the trading partner’s implementation guide. Most of these errors cause automatic order holds requiring manual intervention.

Q6: What happens if I don't acknowledge an EDI 850?

If a supplier fails to send an EDI 997 or EDI 855 within the trading partner’s required window, the retailer’s system typically flags the order as unacknowledged. Depending on the retailer, this can result in the order being cancelled and reissued, a compliance violation being logged against the supplier’s scorecard, or a chargeback. Some retailers auto-cancel unacknowledged orders after 24-48 hours.

Q7: What is a chargeback related to EDI 850?

An EDI 850-related chargeback is a financial penalty applied by a retailer when a supplier fails to comply with their PO requirements. Common triggers include: failing to acknowledge the PO within the required window, shipping quantities that differ from the PO without prior approval, missing the requested ship date, and shipping to the wrong location. Chargeback amounts vary by retailer. For e.g. they can be a flat fee per violation or a percentage of the invoice value.

Q8: What does it mean when an EDI 850 is rejected?

An EDI 850 rejection can happen at two levels. A technical rejection (indicated by an EDI 997 with error codes) means the file had structural or syntax problems like missing required segments, invalid values, or formatting issues. A business-level rejection (indicated by an EDI 855 with a rejection code) means the supplier cannot fulfill the order as submitted — due to product unavailability, pricing disagreement, or other business reasons. Technical rejections require a corrected retransmission; business rejections require negotiation with the buyer.

Q9: What happens after a supplier receives an EDI 850?

After receiving an EDI 850, the supplier takes three actions:
1. Sends an EDI 997 Functional Acknowledgement to confirm the file was technically received without errors.
2. Sends an EDI 855 Purchase Order Acknowledgement to confirm acceptance, rejection, or proposed changes to the order.
3. Fulfills the order — sends an EDI 856 Advance Ship Notice when goods ship and an EDI 810 Invoice to request payment.

Q10: What is the response to an EDI 850?

There are two response documents. The EDI 997 (Functional Acknowledgement) confirms technical receipt of the file. The EDI 855 (Purchase Order Acknowledgement) is the business-level response confirming whether the supplier accepts, rejects, or proposes changes to the order. Both may be required depending on the trading partner’s implementation guide.

Q11: How long does a supplier have to respond to an EDI 850?

Response windows vary by trading partner. Most major retailers require an EDI 855 acknowledgement within 24-48 hours of sending the 850. Walmart and Target typically require a 24-hour response window. Missing the acknowledgement deadline can result in the retailer cancelling or reissuing the order, which disrupts fulfillment and can trigger chargebacks.

Q12: Can an EDI 850 be changed after it is sent?

The EDI 850 itself cannot be modified once sent. If the buyer needs to change the order — adjusting quantities, updating delivery dates, or substituting items — they send a separate EDI 860 Purchase Order Change Request. The supplier then responds with an updated EDI 855 acknowledging the changes.

Q13: What triggers an EDI 850?

An EDI 850 is triggered when a buyer’s purchasing or inventory system determines that a replenishment order needs to be placed. In automated systems this happens when inventory drops below a reorder point, when a consumer places an order (drop-ship), or on a scheduled buying cycle. The buyer’s ERP or order management system generates and transmits the 850 automatically.

Q14: How does EDI 850 work in a drop-ship model?

In drop-ship, the retailer sends an EDI 850 with the end consumer’s shipping address in the ship-to field rather than a distribution center. Order quantities are typically 1 unit per line. The 850 may also include gift messaging, special packaging instructions, or a packing slip suppression flag in the REF or NTE segments. The supplier ships directly to the consumer and sends the EDI 856 and 810 back to the retailer.

Q15: What is the EDI 850 order-to-cash cycle?

The full order-to-cash cycle starting from an EDI 850 is:
1. Buyer sends EDI 850 Purchase Order.
2.Supplier sends EDI 997 to confirm receipt.
3.Supplier sends EDI 855 to acknowledge the order.
4. Supplier picks, packs, and ships the goods.
5. Supplier sends EDI 856 Advance Ship Notice when goods depart.
6. Goods arrive at the buyer’s DC or store.
7. Supplier sends EDI 810 Invoice requesting payment.
8. Buyer performs a three-way match (850 vs. 856 vs. 810) and releases payment.

Q16: What is the difference between EDI 850 and a regular purchase order?

A regular purchase order is a paper or email document that requires manual entry on both sides. An EDI 850 is machine-readable. It transmits directly from the buyer’s system into the supplier’s system with no manual data entry required. This eliminates transcription errors, speeds up order processing, and creates an automatic digital audit trail from order placement through payment.

Q17: Who sends the EDI 850 and who receives it?

The EDI 850 is sent by the buyer, retailer, or distributor. It is received by the supplier, vendor, or manufacturer. The flow is always buyer to supplier. EDI 850 is never sent in the other direction.

Q18: Is EDI 850 the same as an EDI PO?

Yes. EDI PO and EDI 850 refer to the same document. EDI PO is the common industry shorthand; 850 is the official ANSI X12 transaction set code. You will hear both terms used interchangeably in supply chain and retail contexts.