.png){kind=small}
ISA Interchange Control Header
Cavender's X12 860 Purchase Order Change Request
X12 860 (Purchase Order Change Request) is the EDI transaction exchanged between Cavender's and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 5
- X12 860
- All partners ↗
Schema reference
16 segments · 5 loops · X12 860 Purchase Order Change Request
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order Change
Reference Identification
Loop
Reference Identification
Message Text
Loop
Name
Address Information
Geographic Location
Loop
Line Item Change
Loop
Product/Item Description
Date/Time Reference
Marks and Numbers
Loop
Transaction Totals
Transaction Set Trailer
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.
PU Purchase Order PU Purchase Order Acknowledgment SH Ship Notice/Manifest IN Invoice IN Inventory Inquiry/Advice
No trading partner matches your search.
Browse the full directory
Cavender's EDI 860 FAQ
Common questions about 860 Purchase Order Change Request with Cavender's.
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. Cavender's requires it from trading partners.
Does Cavender's require 860 for trading partners?
Yes — Cavender's supports X12 860 Purchase Order Change Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Cavender's 860 with Stacksync?
Most companies go live with Cavender's 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your Cavender's EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.