EDI 850 Purchase Order: What It Is and How It Works

The EDI 850 is one of the most fundamental documents in electronic data interchange. It is the standardized electronic version of a purchase order, sent from a buyer to a seller to request goods or services. Every supplier trading with major retailers, distributors, or manufacturers will encounter the EDI 850 as the starting point of the ordering process.

This guide explains what the EDI 850 contains, how its segments are structured, where it fits in the order-to-cash workflow, how major retailers like Walmart and Target use it, and what common errors to watch for.

What Is an EDI 850?

An EDI 850 is a purchase order transaction set defined by the ANSI X12 EDI standard. It replaces paper-based or emailed purchase orders with a structured, machine-readable document that can be transmitted directly between business systems. The formal name is the Purchase Order Transaction Set (850), and it is part of the broader family of electronic data interchange documents used in B2B commerce.

The buyer creates the EDI 850 in their ERP system and sends it to the seller (also called the supplier or vendor). The document specifies exactly what products the buyer wants, in what quantities, at what price, and where and when they should be delivered. Upon receipt, the seller can validate the order, confirm acceptance, and begin fulfillment.

The EDI 850 is used across virtually every industry where goods and services are bought and sold, including retail, manufacturing, distribution, healthcare, automotive, and logistics. It supports both one-time purchases and recurring orders. Importantly, the 850 should not be used to convey purchase order changes (that is the EDI 860) or purchase order acknowledgments (that is the EDI 855).

What Information Does an EDI 850 Contain?

An EDI 850 contains the same core information you would find on a paper purchase order, structured into standardized fields that both the buyer’s and seller’s systems can read and process automatically. The key data fields include:

• Purchase order number: A unique identifier that both parties use to track the order through fulfillment and payment
• Order date: The date the buyer issues the purchase order
• Item descriptions: Names, product codes, SKU numbers, or UPC codes identifying each product ordered
• Quantities: The number of units requested for each line item
• Unit price: The agreed price per unit for each product
• Ship-to address: The location where products should be delivered, which may be a distribution center, retail store, or end consumer
• Bill-to address: The location where invoices should be sent for payment
• Requested ship date and delivery date: The dates by which the buyer expects the products to ship or arrive
• Shipping instructions: Carrier preferences, freight terms, and routing requirements
• Payment terms: Net terms, discount schedules, or other payment conditions

Although the ANSI ASC X12 standard allows for hundreds of possible data fields on an EDI 850, any given company will use only a subset relevant to their business. Each trading partner publishes their own EDI requirements specifying which fields are mandatory, optional, or unused.

EDI 850 Segment Structure Explained

The contents of an EDI 850 are organized into segments and elements as specified by the X12 standard. Each segment groups related data, and each segment is identified by a two-or-three-character code. An EDI 850 always begins with envelope headers and ends with envelope trailers.

Here is the segment structure of a typical EDI 850, from top to bottom:

• ISA (Interchange Control Header): Opens the EDI interchange. Contains the sender and receiver identification codes, date, time, and control number
• GS (Functional Group Header): Identifies the type of transaction (PO for purchase order) and groups related documents together
• ST (Transaction Set Header): Marks the beginning of the individual 850 document. The sequence “ST*850” identifies the document as a purchase order
• BEG (Beginning Segment for Purchase Order): Contains the purchase order number, order date, and purpose code (original, change, delete)
• N1 (Name Identification): Identifies parties involved in the transaction, including the buyer (N1BY), the ship-to location (N1ST), and the bill-to party (N1*BT)
• N3 (Address Information): Provides the street address for the party identified in the N1 segment
• N4 (Geographic Location): Specifies the city, state, and postal code for the address in N3
• PO1 (Purchase Order Line Item): Contains the detail for each line item, including quantity, unit of measure, unit price, and product identification codes such as UPC, SKU, or vendor part number
• CTT (Transaction Totals): Provides a summary count of the total number of line items in the purchase order
• SE (Transaction Set Trailer): Marks the end of the 850 document and reports the total number of segments transmitted
• GE (Functional Group Trailer): Closes the functional group opened by the GS segment
• IEA (Interchange Control Trailer): Closes the interchange opened by the ISA segment

Additional segments may appear depending on the trading partner’s requirements. Common optional segments include DTM (date/time references), REF (reference numbers), PER (contact information), SAC (service, promotion, or allowance charges), and EDI communication protocol identifiers for AS2 or VAN routing.

How the EDI 850 Fits Into the Order-to-Cash Workflow

The EDI 850 is the first step in a chain of EDI transaction sets that together form the order-to-cash cycle. Understanding where the 850 sits in this workflow is essential for maintaining compliance with your trading partners’ requirements.

Here is the typical sequence after a buyer sends an EDI 850:

• Buyer sends EDI 850 (Purchase Order) to the seller, specifying products, quantities, prices, and delivery details
• Seller sends EDI 997 (Functional Acknowledgment) to confirm the 850 was received without format errors. An accepted 997 does not mean the order is confirmed; it only confirms receipt
• Seller sends EDI 855 (Purchase Order Acknowledgment) to confirm they can fulfill the order as specified, accepted with changes, or rejected
• If changes are needed, the buyer sends an EDI 860 (Purchase Order Change Request) or the seller initiates an EDI 865 (Purchase Order Change Acknowledgment, seller-initiated)
• Seller ships the goods and sends an EDI 856 (Advance Ship Notice / ASN) with shipment details, carton tracking, and expected delivery dates
• Seller sends EDI 810 (Invoice) to request payment for the goods shipped, referencing the original purchase order number
• Buyer processes payment and may send an EDI 820 (Payment Order/Remittance Advice) with remittance details

Each retailer and trading partner defines which of these response documents are required and within what timeframe. For example, some retailers require the EDI 855 within hours of receiving the 850, while others expect the EDI 856 to be transmitted before the shipment physically arrives. Failure to send required documents on time can result in chargebacks and compliance penalties.

Failure to send required documents on time can result in chargebacks and compliance penalties.

EDI 850 vs. EDI 875: Which Purchase Order Do You Need?

The EDI 875 is the Grocery Products Purchase Order, a separate transaction set designed specifically for the food and beverage industry. While the EDI 850 is a general-purpose purchase order used across all industries, the 875 is tailored for grocery wholesalers and retailers who need additional fields for perishable goods.

Key differences between the two:

• EDI 850: General-purpose. Used for ordering any type of goods or services across retail, manufacturing, distribution, automotive, healthcare, and more. Contains standard fields for item descriptions, quantities, prices, and delivery instructions.
• EDI 875: Grocery-specific. Includes additional segments for product weight, temperature requirements, shelf-life dates, expiry information, lot and batch numbers, and special handling instructions for perishable items. Uses different segment names (G68 for item details instead of PO1, G76 for total weight).

An important practical note: not all grocery retailers use the 875. Walmart uses the EDI 850 exclusively, even for grocery items. Kroger’s EDI requirements also specify the 850 as their standard purchase order across all divisions. The 875 is more commonly used by grocery wholesalers, food service distributors, and some regional grocery chains.

If you are unsure which purchase order format your trading partner requires, check their EDI specification guide or ask your EDI provider.

Common EDI 850 Errors and How to Avoid Them

Even with automated EDI processing, errors in EDI 850 documents can cause order rejections, delays, and financial penalties. The most common data quality challenges include:

• Unknown shipping addresses: The buyer includes a ship-to address that does not exist in the seller’s system, causing the order to fail validation. Solution: keep your address master data synchronized with your trading partners
• Expired or wrong item numbers: The buyer orders a product using a SKU or UPC that has been discontinued or does not match the seller’s catalog. Solution: maintain current item master data and communicate changes proactively
• Price mismatches: The price on the EDI 850 does not match the agreed contract price in the seller’s system. Solution: reconcile pricing regularly and flag discrepancies before fulfillment
• Missing required fields: A mandatory segment or data element is blank or formatted incorrectly, causing the document to be rejected on receipt. Solution: use an EDI provider that validates every document against your trading partner’s specifications before transmission
• Duplicate purchase orders: The same PO number is sent more than once, creating confusion in order processing. Solution: implement duplicate detection in your EDI workflow

Working with a managed EDI provider like Vantree ensures that incoming EDI 850 documents are validated, translated, and delivered to your ERP system with full error checking before any order enters your fulfillment pipeline.

How Major Retailers Use the EDI 850

The EDI 850 is the standard purchase order for virtually every major retailer in North America. However, each retailer has its own specific requirements for document content, timing, and compliance rules. Here is how three of the largest retailers use the 850:

Walmart sends EDI 850 purchase orders to all suppliers via EDIINT AS2 protocol. Each 850 includes a Must Arrive By Date (MABD) that drives Walmart’s OTIF (On-Time In-Full) compliance scoring. Suppliers must respond with an EDI 855, transmit an EDI 856 ASN before shipment arrives, and submit an EDI 810 invoice. Walmart monitors compliance through its Retail Link portal and issues chargebacks for failures.

Learn more about Walmart EDI integration.

Target sends EDI 850 purchase orders using AS2 as the preferred communication protocol. Target requires mandatory certification testing before granting production status, and monitors vendor performance through its Partners Online compliance scorecard. Suppliers must support EDI 855, 856, and 810 at minimum.

Learn more about Target EDI integration.

Kroger sends EDI 850 purchase orders through its Webgate+ platform via IBM Sterling Commerce. Kroger exclusively uses the 850, not the 875, even for grocery items. Suppliers have 60 days to become EDI compliant after receiving a formal notice, or face a penalty of 1% of invoice value or $250 per transaction.

Learn more about Kroger EDI integration.

Vantree supports EDI 850 processing with all of these retailers and hundreds more across our trading partner network.

How Vantree Handles EDI 850 Processing

Whether you are receiving purchase orders from major retailers or sending them to your own suppliers, Vantree’s managed EDI service takes the complexity out of EDI 850 processing.

Vantree offers two solutions for handling EDI 850 documents:

• Web EDI: A cloud-based platform that lets you view, manage, and respond to EDI 850 purchase orders through a browser-based interface. Ideal for smaller businesses or suppliers with lower transaction volumes who need a fast, affordable path to compliance.
• EDI Automation: A fully integrated solution that connects the EDI 850 directly to your ERP or accounting system. Purchase orders flow automatically into your system with no manual data entry, and response documents (855, 856, 810) are generated and transmitted without human intervention. Vantree supports 35+ ERP integrations including SAP, Microsoft Dynamics, NetSuite, Acumatica, QuickBooks, and Sage.

Both solutions include document validation, error monitoring, trading partner management, and dedicated support from Vantree’s team-based solution agents. As your business grows and you add new trading partners, Vantree handles the mapping updates and compliance requirements so you can streamline your operations and focus on fulfillment.

Talk to an EDI Expert →

Frequently Asked Questions About EDI 850

What does EDI 850 stand for?

EDI 850 refers to the Purchase Order transaction set within the ANSI ASC X12 standard. The number 850 is the designated code for purchase order documents in the X12 family. It is one of over 300 standardized transaction sets defined by X12 for use in electronic data interchange.

Who sends the EDI 850?

The EDI 850 is always sent by the buyer to the seller. In a retail context, this means the retailer (such as Walmart, Target, or Kroger) sends the 850 to the supplier or vendor. In a manufacturing context, the manufacturer sends the 850 to their raw materials supplier. The seller then responds with acknowledgment and fulfillment documents.

What is the difference between EDI 850 and EDI 875?

The EDI 850 is a general-purpose purchase order used across all industries. The EDI 875 is a grocery-specific purchase order that includes additional fields for perishable goods, such as weight, temperature requirements, and expiry dates. Most major retailers, including Walmart and Kroger, use the 850 even for grocery items. The 875 is more common among grocery wholesalers and food service distributors.

What documents are sent in response to an EDI 850?

After receiving an EDI 850, the seller typically sends several response documents: an EDI 997 (Functional Acknowledgment) to confirm receipt, an EDI 855 (Purchase Order Acknowledgment) to confirm they can fulfill the order, an EDI 856 (Advance Ship Notice) with shipment details, and an EDI 810 (Invoice) to request payment. The specific documents required and their timing depend on each trading partner’s requirements.

Do I need an EDI provider to send or receive EDI 850 documents?

In most cases, yes. Processing EDI 850 documents requires EDI software or a service that can translate between the X12 format and your internal business systems. An EDI provider like Vantree handles the translation, validation, transmission (via AS2, VAN, or other protocols), and ongoing compliance management. Some businesses attempt to manage EDI in-house, but the complexity of maintaining trading partner maps, handling format updates, and ensuring compliance across multiple partners makes a managed service the most efficient and cost-effective approach for most organizations.