X12 transaction code
X12 860 Purchase Order Change Request
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 860
- Trading partners
- 1
Specification summary
X12 860 Purchase Order Change Request 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 |
- Transaction Set Purpose Code
- Purchase Order Type Code
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Contact Function Code
Trading partners that support X12 860
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 860 Purchase Order Change Request
860 is used most heavily in automotive.
The 860 communicates a buyer's changes to a purchase order it has already transmitted: revised quantities, prices, delivery dates, added or cancelled lines, or cancellation of the entire order. It can also confirm buyer acceptance of changes the seller proposed. Carrying the amendment in EDI keeps the supplier's order record aligned with the buyer's, so downstream ASNs and invoices match the current version of the order and billing disputes are avoided. Sent by the buyer to the supplier against a previously transmitted 850 purchase order; the supplier typically responds with an 865 Purchase Order Change Acknowledgment. A buyer's purchasing or ERP system amends an open order, changing quantity, price, date, or line items, after the original 850 has already gone out.
By industry
- automotive 1 channel
FAQ
X12 860 questions
What is X12 860 Purchase Order Change Request?
X12 860 (Purchase Order Change Request) is an EDI transaction set defined by ANSI ASC X12 for exchanging purchase order change request between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 860?
1 Stacksync partner accepts X12 860: Ford Motor Company. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 860 with my ERP?
Stacksync handles the full X12 860 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
