The EDI 856 hierarchy, explained
An EDI 856 advance ship notice is a nested description of a shipment. It starts with the truck, breaks down to each order on it, then to each pallet and carton, and ends with the items in each carton. The retailer scans a carton label at the dock and expects the 856 to say exactly what is inside. Most ASN chargebacks come from a hierarchy that does not match the freight.
The five hierarchical levels
Each level of an 856 is an HL loop that names its parent, so the receiver can rebuild the tree. The shipment level (S) describes the whole delivery: carrier, routing, ship date, bill of lading, and ship-from and ship-to. The order level (O) carries each purchase order on the shipment. The tare level (T) describes a pallet. The pack level (P) describes a carton. The item level (I) lists each SKU and the quantity shipped.
A single shipment can carry several orders, each order several pallets, each pallet several cartons, and each carton several items, so a full truck can produce hundreds of HL loops.
SOPI vs SOTPI
The order of levels is called the hierarchy structure. SOPI (shipment, order, pack, item) describes cartons only and is common for parcel and floor-loaded freight. SOTPI (shipment, order, tare, pack, item) adds the pallet level for palletized freight, so the receiver can scan a pallet label and know every carton on it.
Retailers specify which structure they accept, sometimes by ship method, in their EDI guideline. Sending SOPI to a partner that expects SOTPI, or the reverse, is a structural error the retailer’s system can reject outright.
How the carton label ties in
Every carton, and every pallet in a SOTPI ASN, carries a GS1-128 label printed with its 18-digit SSCC. The same SSCC appears at the matching pack or tare level of the 856. At the dock the receiver scans the label, looks up that SSCC in the ASN, and receives the contents without opening the carton.
That link is why label and ASN errors cost so much. A duplicate SSCC, a label printed for one carton and stuck on another, or an ASN generated before the cartons were packed all break the scan, and the retailer falls back to manual receiving and bills the supplier for it.
The ASN mistakes that cause chargebacks
The most common are: an ASN sent late, after the truck arrives, or not at all; quantities on the ASN that differ from what was packed; SSCCs that do not match the labels on the freight; the wrong hierarchy structure; PO numbers, ship-to locations, or carrier details that do not match the order or the routing guide; and missing required references such as the bill of lading or PRO number.
Almost all of them start the same way: the ASN is built from what was planned instead of what was packed. Building it from scan data at pack-out, after the cartons are closed and labeled, removes most of the risk.
Where Endless fits
EndlessEDI builds carton-level 856s tied to GS1-128 labels from pick and pack data, using the hierarchy each trading partner requires, so the ASN describes the freight that shipped.
FAQ
What does HL mean in an EDI 856?
HL is the hierarchical level segment. Each HL starts a level of the ASN, such as the shipment, an order, a pallet, a carton, or an item, and points to its parent level so the receiver can rebuild the structure.
What is the difference between SOPI and SOTPI?
SOPI nests shipment, order, pack, and item, describing cartons only. SOTPI adds a tare level for pallets between the order and the cartons. The retailer’s guideline says which one it accepts.
Where does the SSCC go in an 856?
Each carton’s SSCC is reported at its pack level, and each pallet’s SSCC at its tare level in a SOTPI ASN. The same number is printed on the GS1-128 label on that carton or pallet.
When should an ASN be sent?
After the freight is packed and before it arrives, and within the window the retailer specifies, usually tied to when the truck leaves. An ASN that arrives after the freight is treated as late or missing.
