.png){kind=small}
ISA Interchange Control Header
Zappos and 6pm X12 860 Purchase Order Change Request
X12 860 (Purchase Order Change Request) is the EDI transaction exchanged between Zappos and 6pm 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
Service, Promotion, Allowance, or Charge Information
Terms of Sale/Deferred Terms of Sale
Date/Time Reference
Loop
Name
Additional Name Information
Address Information
Geographic Location
Loop
Line Item Change
Loop
Product/Item Description
Loop
Transaction Totals
Transaction Set Trailer
Trading partners
3+ 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.
No trading partner matches your search.
Browse the full directory
Zappos and 6pm EDI 860 FAQ
Common questions about 860 Purchase Order Change Request with Zappos and 6pm.
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. Zappos and 6pm requires it from trading partners.
Does Zappos and 6pm require 860 for trading partners?
Yes — Zappos and 6pm supports X12 860 Purchase Order Change Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Zappos and 6pm 860 with Stacksync?
Most companies go live with Zappos and 6pm 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your Zappos and 6pm EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.