Multi-PO pallet ASN hierarchy without the guesswork

Why multi-PO pallets fail

The same pallet can physically contain cartons belonging to more than one purchase order. If the hierarchy places the pallet above the order, or reuses a carton loop without an unambiguous order parent, the receiver may not be able to reconcile items to the right PO.

Do not choose a hierarchy solely because it uses fewer segments. Choose the shape that preserves the physical and commercial relationships required by the trading-partner guide.

A deterministic tree-building method

• Create the shipment root.
• Create a distinct order node for every PO.
• Within each order, create the required pallet/tare representation.
• Attach each carton/pack to the relevant pallet/order path.
• Attach item loops to the carton or hierarchy level required by the case structure.
• Allocate unique HL IDs only after the full tree is built, then emit parents before children.

What the preflight checks

The validator detects duplicate HL IDs, missing or forward parents, invalid level codes, a non-shipment root, and uncommon profile sequences. It also checks PRF purchase-order presence and SSCC values found in MAN segments.

A warning is not silently upgraded to a universal rule. When public evidence cannot establish the account-specific profile, Shipment Sentry tells the operator exactly what to verify.