.png){kind=small}
ISA Interchange Control Header
Zappos and 6pm X12 856 Ship Notice/Manifest
X12 856 (Ship Notice/Manifest) is the EDI transaction exchanged between Zappos and 6pm and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 21
- Loops
- 2
- X12 856
- All partners ↗
Schema reference
21 segments · 2 loops · X12 856 Ship Notice/Manifest
GS Functional Group Header
Transaction Set Header
Beginning Segment for Ship Notice
Loop
Hierarchical Level
Item Identification
Item Detail (Shipment)
Purchase Order Reference
Product/Item Description
Carrier Details (Quantity and Weight)
Carrier Details (Routing Sequence/Transit Time)
Reference Identification
Marks and Numbers
Date/Time Reference
F.O.B. Related Instructions
Loop
Name
Additional Name Information
Address Information
Geographic Location
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 856 FAQ
Common questions about 856 Ship Notice/Manifest with Zappos and 6pm.
What is X12 856 Ship Notice/Manifest?
X12 856 (Ship Notice/Manifest) is the EDI transaction set used to exchange ship notice/manifest data. Zappos and 6pm requires it from trading partners.
Does Zappos and 6pm require 856 for trading partners?
Yes — Zappos and 6pm supports X12 856 Ship Notice/Manifest. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Zappos and 6pm 856 with Stacksync?
Most companies go live with Zappos and 6pm 856 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.