Skip to content
EDI X12 860

X12 transaction code

X12 860 Purchase Order Change Request Buyer Initiated

Stop Mapping. Start Trading.

Standard
X12
Code
860
Trading partners
140
Book a demo ← All trading partners

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
Segments with mandatory elements
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

Trading partners that support X12 860

140 partners, 171 channels. Click a channel for the full segment guideline.

Usage breakdown

Who trades X12 860 Purchase Order Change Request Buyer Initiated

860 is used most heavily in retail, apparel & footwear and grocery & food.

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. 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.

By industry

  • retail 50 channels
  • apparel & footwear 30 channels
  • grocery & food 25 channels
  • furniture & home 23 channels
  • building & hardware 12 channels
  • e-commerce & marketplaces 11 channels

By network

  • SPS Commerce 56 channels
  • TrueCommerce 16 channels
  • Rithum 7 channels
  • InterTrade 2 channels
  • OpenText 2 channels
  • CommerceHub 2 channels
Largest 860 implementations

FAQ

X12 860 questions

What is X12 860 Purchase Order Change Request Buyer Initiated?

X12 860 (Purchase Order Change Request Buyer Initiated) is an EDI transaction set defined by ANSI ASC X12 for exchanging purchase order change request buyer initiated between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 140 Stacksync trading partners support this code across 171 channels.

Which trading partners use X12 860?

140 Stacksync partners accept X12 860: 7-Eleven (SEDC: Seven Eleven Distribution Company), 99 Cents Only, AAFES (Army and Air Force Exchange Service), Academy Sports + Outdoors, AGCO Your Agriculture Company, Al's Sporting Goods, Aldi, Backcountry.com, and more. 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.

Book a demo Tour the platform on your own