.png){kind=small}
ISA Interchange Control Header
Buc X12 855 Purchase Order Acknowledgment
X12 855 (Purchase Order Acknowledgment) is the EDI transaction exchanged between Buc and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 6
- X12 855
- All partners ↗
Schema reference
16 segments · 6 loops · X12 855 Purchase Order Acknowledgment
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order Acknowledgment
Reference Information
Date/Time Reference
Carrier Details (Routing Sequence/Transit Time)
Loop
Extended Reference Information
Text
Loop
Baseline Item Data
Loop
Product/Item Description
Loop
Line Item Acknowledgment
Loop
Extended Reference Information
Text
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 Change Request IN Invoice CR Credit/Debit Adjustment SH Ship Notice/Manifest
No trading partner matches your search.
Browse the full directory
Buc EDI 855 FAQ
Common questions about 855 Purchase Order Acknowledgment with Buc.
What is X12 855 Purchase Order Acknowledgment?
X12 855 (Purchase Order Acknowledgment) is the EDI transaction set used to exchange purchase order acknowledgment data. Buc requires it from trading partners.
Does Buc require 855 for trading partners?
Yes — Buc supports X12 855 Purchase Order Acknowledgment. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Buc 855 with Stacksync?
Most companies go live with Buc 855 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your Buc EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.