Gierd Inc X12 855 Purchase Order Acknowledgment
X12 855 (Purchase Order Acknowledgment) is the EDI transaction exchanged between Gierd Inc (Gierd Default) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 0
- Loops
- 4
- X12 855
- All partners ↗
Transaction context
Where 855 Purchase Order Acknowledgment fits on Gierd Default
On Gierd Default, the X12 855 Purchase Order Acknowledgment follows the 850 Purchase Order and precedes the 856 Ship Notice Manifest in the Order-to-cash cycle.
- Gierd Inc channels
- 1 of 1
- Trading partners
- 269
- Channels
- 328
1 of Gierd Inc's 1 channel carries 855
partners across the Stacksync network trade 855
channels network-wide carry 855
The 855 is the seller's formal response to an 850 purchase order: accept as submitted, accept with changes to price, quantity, dates, or items, or reject. Buyers require it to confirm the order is committed before shipment and to surface availability, pricing, and item discrepancies while there is still time to correct them. Many retail compliance programs mandate it within a defined window, commonly 24 to 48 hours of PO receipt, and failure to send required response documents on time can result in financial penalties under vendor compliance programs. Sent by the supplier or vendor to the buyer that issued the purchase order.
When it fires: A supplier's order management system finishes validating an inbound purchase order against its item master, pricing, and available inventory.
- Acknowledgments sent after the buyer's required response window, commonly 24 to 48 hours, exposing the supplier to compliance penalties.
- PO number or line references that do not match the original 850, so the buyer's system cannot tie the acknowledgment back to the order.
- Inaccurate product identifiers or prices echoed back on the acknowledgment, creating discrepancies that persist into the ship notice and invoice.
- Missing or inconsistent acknowledgment status codes, leaving the buyer unsure whether changed quantities, dates, or backorders were actually committed.
Specification summary
X12 855 Purchase Order Acknowledgment at the element level
The X12 855 specification defines 54 segments carrying 204 data elements, 72 of which are mandatory.
- Segments
- 54
- Data elements
- 204
- Mandatory elements
- 72
| Segment | Elements | Mandatory |
|---|---|---|
| BAK | 6 | 4 |
| CUR | 2 | 2 |
| REF | 3 | 1 |
| FOB | 3 | 1 |
| SAC | 10 | 1 |
| DTM | 4 | 1 |
| TXI | 7 | 1 |
| N9 | 3 | 1 |
| MSG | 2 | 1 |
| N1 | 4 | 1 |
| N2 | 2 | 1 |
- Transaction Set Purpose Code
- Acknowledgment Type
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Shipment Method of Payment
Full segment guideline — 0 segments 4 loops · X12 855 Purchase Order Acknowledgment
Trading partners
2+ 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.
Gierd Inc Gierd Default EDI 855 FAQ
Common questions about 855 Purchase Order Acknowledgment on the Gierd Default channel.
What is X12 855 Purchase Order Acknowledgment?
Does Gierd Inc Gierd Default require 855 for trading partners?
How fast can I integrate Gierd Inc 855 with Stacksync?
Which documents accompany 855 on Gierd Default?
Ready to automate your Gierd Inc EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
