Gierd Inc X12 856 Ship Notice/Manifest
X12 856 (Ship Notice/Manifest) 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
- 2
- X12 856
- All partners ↗
Transaction context
Where 856 Ship Notice/Manifest fits on Gierd Default
On Gierd Default, the X12 856 Ship Notice/Manifest follows the 850 Purchase Order and 855 Purchase Order Acknowledgment in the Order-to-cash cycle.
- Gierd Inc channels
- 1 of 1
- Trading partners
- 350
- Channels
- 457
1 of Gierd Inc's 1 channel carries 856
partners across the Stacksync network trade 856
channels network-wide carry 856
The 856 Ship Notice/Manifest, known in practice as the Advance Ship Notice (ASN), describes the contents and packing configuration of a shipment before it arrives, using nested hierarchical levels for shipment, order, pack, and item. Buyers use it to schedule dock labor and to match scanned GS1 carton labels against expected contents at receiving. Retail compliance programs treat the ASN as mandatory, and ASN errors are widely reported to generate more supplier chargebacks than any other EDI document type. Sent by the supplier, or a 3PL shipping on its behalf, to the buyer (retailer or distributor) at the time the order ships.
When it fires: A packed order is ship-confirmed and tendered to the carrier; the warehouse system generates the 856 so it reaches the buyer before the goods do.
- SSCC-18 on the physical carton label does not match the SSCC in the ASN, so receiving scans fail and cartons are processed manually.
- Quantities in the ASN differ from what was physically packed or from the purchase order, a chargeback event commonly billed at 25 to 200 USD per incident.
- ASN transmitted after the truck arrives, or never sent, which retailers penalize regardless of whether the physical shipment was accurate.
- HL hierarchy (shipment/order/pack/item) flattened or nested incorrectly during mapping, causing receiving systems to misread carton contents.
Specification summary
X12 856 Ship Notice/Manifest at the element level
The X12 856 specification defines 32 segments carrying 147 data elements, 50 of which are mandatory.
- Segments
- 32
- Data elements
- 147
- Mandatory elements
- 50
| Segment | Elements | Mandatory |
|---|---|---|
| BSN | 6 | 4 |
| HL | 3 | 2 |
| LIN | 19 | 2 |
| SN1 | 4 | 2 |
| PRF | 2 | 1 |
| PID | 3 | 1 |
| REF | 2 | 1 |
| MAN | 4 | 2 |
| DTM | 3 | 1 |
| FOB | 4 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
- Transaction Set Purpose Code
- Shipment Identification
- Date
- Time
- Hierarchical ID Number
- Hierarchical Level Code
- Product/Service ID Qualifier
- Product/Service ID
Full segment guideline — 0 segments 2 loops · X12 856 Ship Notice/Manifest
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 856 FAQ
Common questions about 856 Ship Notice/Manifest on the Gierd Default channel.
What is X12 856 Ship Notice/Manifest?
Does Gierd Inc Gierd Default require 856 for trading partners?
How fast can I integrate Gierd Inc 856 with Stacksync?
Which documents accompany 856 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.
