.png){kind=small}
ISA Interchange Control Header
iTradeNetwork, Inc. X12 860 Purchase Order Change Request
X12 860 (Purchase Order Change Request) is the EDI transaction exchanged between iTradeNetwork, Inc. and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 18
- Loops
- 6
- X12 860
- All partners ↗
Schema reference
18 segments · 6 loops · X12 860 Purchase Order Change Request
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order Change
Reference Identification
F.O.B. Related Instructions
Loop
Service, Promotion, Allowance, or Charge Information
Date/Time Reference
Carrier Details (Routing Sequence/Transit Time)
Loop
Reference Identification
Message Text
Loop
Name
Address Information
Geographic Location
Loop
Line Item Change
Loop
Product/Item Description
Loop
Transaction Totals
Transaction Set Trailer
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.
iTradeNetwork, Inc. EDI 860 FAQ
Common questions about 860 Purchase Order Change Request with iTradeNetwork, Inc..
What is X12 860 Purchase Order Change Request?
X12 860 (Purchase Order Change Request) is the EDI transaction set used to exchange purchase order change request data. iTradeNetwork, Inc. requires it from trading partners.
Does iTradeNetwork, Inc. require 860 for trading partners?
Yes — iTradeNetwork, Inc. supports X12 860 Purchase Order Change Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate iTradeNetwork, Inc. 860 with Stacksync?
Most companies go live with iTradeNetwork, Inc. 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your iTradeNetwork, Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.