.png){kind=small}
ISA Interchange Control Header
Zappos and 6pm X12 855 Purchase Order Acknowledgment
X12 855 (Purchase Order Acknowledgment) 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 855
- All partners ↗
Schema reference
16 segments · 5 loops · X12 855 Purchase Order Acknowledgment
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order Acknowledgment
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
Baseline Item Data
Loop
Product/Item Description
Loop
Line Item Acknowledgment
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 855 FAQ
Common questions about 855 Purchase Order Acknowledgment with Zappos and 6pm.
What is X12 855 Purchase Order Acknowledgment?
X12 855 (Purchase Order Acknowledgment) is the EDI transaction set used to exchange purchase order acknowledgment data. Zappos and 6pm requires it from trading partners.
Does Zappos and 6pm require 855 for trading partners?
Yes — Zappos and 6pm supports X12 855 Purchase Order Acknowledgment. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Zappos and 6pm 855 with Stacksync?
Most companies go live with Zappos and 6pm 855 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.