.png){kind=small}
ISA Interchange Control Header
CVS X12 860 Purchase Order Change Request
X12 860 (Purchase Order Change Request) is the EDI transaction exchanged between CVS and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 17
- Loops
- 4
- X12 860
- All partners ↗
Schema reference
17 segments · 4 loops · X12 860 Purchase Order Change Request
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order Change
Reference Identification
Administrative Communications Contact
Date/Time Reference
Loop
Name
Loop
Line Item Change
Currency
Period Amount
Loop
Product/Item Description
Item Physical Details
Reference Identification
Carrier Details (Quantity and Weight)
Loop
Transaction Totals
Transaction Set Trailer
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.
CR Credit/Debit Adjustment SH Ship Notice/Manifest AP Application Advice PL Planning Schedule with Release Capability IN Invoice PU Purchase Order
No trading partner matches your search.
Browse the full directory
CVS EDI 860 FAQ
Common questions about 860 Purchase Order Change Request with CVS.
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. CVS requires it from trading partners.
Does CVS require 860 for trading partners?
Yes — CVS supports X12 860 Purchase Order Change Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate CVS 860 with Stacksync?
Most companies go live with CVS 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your CVS EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.