To start and identify an interchange of zero or more functional groups and interchange-related control segments
Ulta Beauty X12 860 Purchase Order Change Request - Buyer Initiated
X12 860 (Purchase Order Change Request - Buyer Initiated) is the EDI transaction exchanged between Ulta Beauty (Ulta Beauty via OpenText) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 21
- Loops
- 5
- X12 860
- All partners ↗
Transaction context
Where 860 Purchase Order Change Request - Buyer Initiated fits on Ulta Beauty via OpenText
- Ulta Beauty channels
- 3 of 3
- Trading partners
- 140
- Channels
- 171
3 of Ulta Beauty's 3 channels carry 860
partners across the Stacksync network trade 860
channels network-wide carry 860
Most common alongside 860
On OpenText, 860 runs on 2 channels.
This is the X12 860, formally titled Purchase Order Change Request - Buyer Initiated. It lets a buyer amend a purchase order already in the supplier's hands: quantity adjustments, price corrections, rescheduled delivery dates, added or removed line items, or full cancellation, and it can confirm acceptance of seller-proposed changes. Trading partners require it so the order of record stays identical on both sides and invoices reconcile against the amended order rather than the original. Always sent by the buyer to the supplier, referencing the original 850; the supplier accepts or contests the change with an 865 Purchase Order Change Acknowledgment.
When it fires: A buyer needs to change quantities, pricing, dates, or line items on an open order, or cancel it outright, at any point in the order cycle including after partial shipment.
Common 860 rejection causes
- PO number or POC line-item references that do not match the original 850, so the supplier's system rejects or misapplies the change.
- Changes arriving after picking or shipment has begun, which the supplier can no longer execute, leaving quantity and date mismatches downstream.
- Missing or late 865 acknowledgment, so neither side can prove the amended terms were agreed before the goods shipped.
- Post-shipment price corrections sent by retailers via 860 that the supplier fails to apply before invoicing, causing invoice rejections.
Specification summary
X12 860 Purchase Order Change Request - Buyer Initiated at the element level
The X12 860 specification defines 55 segments carrying 162 data elements, 62 of which are mandatory.
- Segments
- 55
- Data elements
- 162
- Mandatory elements
- 62
| Segment | Elements | Mandatory |
|---|---|---|
| BCH | 4 | 4 |
| CUR | 2 | 2 |
| REF | 3 | 1 |
| PER | 2 | 1 |
| FOB | 5 | 1 |
| N9 | 2 | 1 |
| N1 | 4 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
| POC | 13 | 1 |
Key identifiers in 860
- Transaction Set Purpose Code
- Purchase Order Type Code
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Contact Function Code
Full segment guideline — 21 segments 5 loops · X12 860 Purchase Order Change Request - Buyer Initiated
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 Change 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 terms of sale
To specify pertinent dates and times
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 the location of the named party
To specify the geographic place of the named party
POC Loop Repeat: 1,000
To specify changes to a line item
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
CTT Loop Repeat: 1
To transmit a hash total for a specific element in the transaction set
To indicate the total monetary amount
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
2+ 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.
No trading partner matches your search.
Browse the full directory
Trading partners
5+ 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.
SH Ship Notice Manifest PR Product Activity Data PU Purchase Order IN Invoice PU Purchase Order Acknowledgment
No trading partner matches your search.
Browse the full directory
Ulta Beauty Ulta Beauty via OpenText EDI 860 FAQ
Common questions about 860 Purchase Order Change Request - Buyer Initiated on the Ulta Beauty via OpenText channel.
What is X12 860 Purchase Order Change Request - Buyer Initiated?
X12 860 (Purchase Order Change Request - Buyer Initiated) is the EDI transaction set used to exchange purchase order change request - buyer initiated data. Ulta Beauty's Ulta Beauty via OpenText channel requires it from trading partners.
Does Ulta Beauty Ulta Beauty via OpenText require 860 for trading partners?
Yes, Ulta Beauty (Ulta Beauty via OpenText) supports X12 860 Purchase Order Change Request - Buyer Initiated. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Ulta Beauty 860 with Stacksync?
Most companies go live with Ulta Beauty 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Ulta Beauty channels accept 860?
X12 860 runs on 3 of Ulta Beauty's 3 channels. Besides Ulta Beauty via OpenText, it is accepted on Ulta Beauty (Legacy ISA ID: 3103438052), Ulta Beauty (Legacy ISA ID: 608168597). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your Ulta Beauty EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
