Amazon multi-PO pallet ASN: preserve every order-to-carton relationship

A pallet containing cartons for multiple purchase orders is where a flat list becomes operationally ambiguous. The ASN hierarchy must let the receiver trace an item to its carton or pallet and to the intended purchase order without inference.

Direct answer: A common detailed shape is SOTPI—Shipment → Order → Tare → Pack → Item. HL01 values must be unique, every HL02 must point to an earlier parent, and each carton/item path must remain under the correct PO. Confirm the exact profile in the current Vendor Central implementation guide because public sources cannot establish one universal hierarchy for every account.

Why multi-PO pallet mappings fail

The physical pallet appears to sit above its purchase orders, while many EDI partner profiles organize the commercial Order level before packaging detail. Reusing one tare or pack loop across order branches can therefore make the message smaller but destroy an unambiguous PO relationship.

Do not select a hierarchy because it has fewer segments. Select the partner-supported hierarchy that faithfully represents the shipment.

Build the tree before assigning HL numbers

1. Create the Shipment root.
2. Create a distinct Order node for every accepted PO represented in the transaction.
3. Under each order, create the Tare/Pack nodes required to describe its share of the physical handling units.
4. Attach items to the correct pack or parent level.
5. Assign HL01 values only after the complete tree is known.
6. Serialize parents before children and write HL02 from the actual parent ID.

HL*1**S~
HL*2*1*O~       PO A
PRF*PO-A~
HL*3*2*T~       pallet representation for PO A
HL*4*3*P~       carton A1
HL*5*4*I~       item under PO A
HL*6*1*O~       PO B
PRF*PO-B~
HL*7*6*T~       pallet representation for PO B
HL*8*7*P~       carton B1
HL*9*8*I~       item under PO B

This example demonstrates parentage, not a universal Amazon mapping. Your current account guide determines which levels and segments are permitted or required.

Crossed-order defect to test explicitly

HL*6*1*O~
PRF*PO-B~
HL*8*3*P~   invalid business relationship: carton B attached to PO A branch

A generic validator may see an existing parent 3 and accept the tree structurally. Reconciliation needs to know that the carton contents and PO reference belong together. That is why Shipment Sentry separates base hierarchy errors from source-to-source reconciliation findings.

Dispatch checks for a multi-PO pallet

• Every PO is accepted and still open for the shipped lines.
• Every carton’s items and quantities roll up to one intentional order path.
• SSCCs are unique and match label scans.
• Pallet and carton totals agree with warehouse closeout.
• Transportation references describe the same physical movement.
• Replacement submissions preserve the identifiers required by the current workflow.

Common questions

Is SOTPI always required for a multi-PO pallet?

No. It is a useful and common description of a detailed hierarchy, not a universal mandate. Follow the current implementation guide for the account and shipment structure.

Can two branches reuse the same HL01?

No. HL01 identifies a hierarchy node within the transaction set and must remain unique even when branches represent different purchase orders.