To start and identify an interchange of zero or more functional groups and interchange-related control segments
Williams Sonoma X12 850 Purchase Order
X12 850 (Purchase Order) is the EDI transaction exchanged between Williams Sonoma (Williams Sonoma via SPS) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 30
- Loops
- 8
- X12 850
- All partners ↗
Transaction context
Where 850 Purchase Order fits on Williams Sonoma via SPS
On Williams Sonoma via SPS, the X12 850 Purchase Order precedes the 855 Purchase Order Acknowledgment, 856 Ship Notice Manifest and 810 Invoice in the Order-to-cash cycle.
- Williams Sonoma channels
- 1 of 2
- Trading partners
- 389
- Channels
- 516
1 of Williams Sonoma's 2 channels carries 850
partners across the Stacksync network trade 850
channels network-wide carry 850
Most common alongside 850
On SPS Commerce, 850 runs on 92 channels.
The 850 is the electronic purchase order a buyer sends to formally request goods or services, carrying items, quantities, prices, ship-to locations, and requested dates. It initiates the order-to-cash cycle and is the reference document that the acknowledgment (855), ship notice (856), and invoice (810) must reconcile against. Trading partners require it because a machine-readable PO removes manual re-keying and the wrong-item, wrong-quantity errors that come with it. Sent by the buyer (retailer, distributor, or manufacturer procurement) to the supplier or vendor fulfilling the order.
When it fires: A buyer's procurement or replenishment system releases an approved order for goods to a specific supplier.
Common 850 rejection causes
- Ship-to addresses or location codes that do not exist in the seller's system, causing the order to fail validation or ship to the wrong warehouse.
- Item identifiers referencing discontinued SKUs or UPCs that do not match the seller's catalog, forcing manual intervention.
- PO line prices that do not match the agreed contract price in the seller's system, triggering business-level rejection on the 855.
- Missing or malformed mandatory segments or data elements, rejected on receipt via the 997, and duplicate PO numbers that confuse order processing.
Specification summary
X12 850 Purchase Order at the element level
The X12 850 specification defines 71 segments carrying 282 data elements, 84 of which are mandatory.
- Segments
- 71
- Data elements
- 282
- Mandatory elements
- 84
| Segment | Elements | Mandatory |
|---|---|---|
| BEG | 5 | 4 |
| CUR | 5 | 2 |
| REF | 3 | 1 |
| FOB | 7 | 1 |
| SAC | 11 | 1 |
| DTM | 4 | 1 |
| PID | 4 | 1 |
| TXI | 8 | 1 |
| N9 | 3 | 1 |
| MSG | 2 | 1 |
Key identifiers in 850
- Transaction Set Purpose Code
- Purchase Order Type Code
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Shipment Method of Payment
Full segment guideline — 30 segments 8 loops · X12 850 Purchase Order
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
To specify identifying information
To identify a person or office to whom administrative communications should be directed
To specify transportation instructions relating to shipment
To specify general conditions or requirements of the sale
To specify terms of sale
To specify the carrier and sequence of routing and provide transit time information
To specify transportation details relating to the equipment used by the carrier
N9 Loop Repeat: 1,000
To transmit identifying information as specified by the Reference Identification Qualifier
To specify textual data
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
PO1 Loop Repeat: 100,000
To specify basic and most frequently used line item data
CTP Loop Repeat: 1,000
To specify pricing information
CTT Loop Repeat: 1
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)
PID Loop Repeat: 1,000
To describe a product or process in coded or free-form format
To specify the physical qualities, packaging, weights, and dimensions relating to the item
SAC Loop Repeat: 25
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
To specify destination and quantity detail
To specify pertinent dates and times
To identify a commodity or a group of commodities or a tariff page commodity
SLN Loop Repeat: 1,000
To specify product subline detail item data
Trading partners
6+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
Williams Sonoma Williams Sonoma via SPS EDI 850 FAQ
Common questions about 850 Purchase Order on the Williams Sonoma via SPS channel.
What is X12 850 Purchase Order?
X12 850 (Purchase Order) is the EDI transaction set used to exchange purchase order data. Williams Sonoma's Williams Sonoma via SPS channel requires it from trading partners.
Does Williams Sonoma Williams Sonoma via SPS require 850 for trading partners?
Yes, Williams Sonoma (Williams Sonoma via SPS) supports X12 850 Purchase Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Williams Sonoma 850 with Stacksync?
Most companies go live with Williams Sonoma 850 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 850 on Williams Sonoma via SPS?
On Williams Sonoma via SPS, X12 850 is typically exchanged alongside 810 Invoice, 856 Ship Notice Manifest, 855 Purchase Order Acknowledgment, 860 Purchase Order Change Request Buyer Initiated. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Williams Sonoma EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
