Shipment Level Vs Order Level: Choosing The Right ASN Granularity

The ASN level containing information about the overall shipment, carrier, trailer, tracking, bill of lading, and dates.

Shipment Level is the ASN level containing information about the overall shipment, carrier, trailer, tracking, bill of lading, and dates. Deciding whether to operate primarily at shipment level or to push more granularity to order- and pack-level ASNs affects receiving complexity, carrier coordination, and reconciliation work for warehouses and shippers.

Shipment-level ASNs summarize transport context and are best when goods travel together under one BOL or trailer. Order-level ASNs attach details to individual purchase orders, while pack-level ASNs describe cartons and SKU counts. Each level serves different operational needs: shipment level optimizes dock handling and transport management, order-level supports PO reconciliation and invoicing, and pack-level supports piece-level scanning and compliance labeling. The challenge is choosing the right mix to balance data volume against operational control.

When Shipment Level Is The Better Choice

• Mixed POs On One Trailer: Use shipment-level summaries to coordinate trailer arrival and door allocation quickly.
• Carrier Focused Processes: When operations depend on SCAC, trailer ID, or BOL to route freight, the shipment level is primary.
• Low Tolerance For Data Volume: If suppliers or systems struggle with heavy EDI feeds, shipment-level ASNs reduce the data burden.

When Order Or Pack Levels Are Preferable

• PO-Level Reconciliation Need: Retailers or finance teams that require PO-by-PO matching for payment should insist on order-level ASNs.
• Item-Level Compliance: When regulatory or retailer compliance requires carton-level barcodes or serial numbers, pack-level ASNs are necessary.
• Automated Putaway/Sorting: Fulfillment centers with automated conveyors and sorters depend on pack-level detail to route cartons without manual inspection.

How The Levels Complement Each Other

Most mature operations use a hybrid approach. The shipment level handles transport attributes and provides a single source for arrival and carrier references; order-level lines provide PO matching and quantities per purchase order; pack-level detail supports carton labeling and serial tracking. Properly configured WMS or middleware will import all three levels and reconcile them so that shipment totals equal the sum of child elements. This prevents double-counting and speeds exception resolution.

Operational Tradeoffs

Shipment-level ASNs are lighter on upstream systems and reduce errors tied to SKU-level mismatches, but they limit the ability to auto-receive into PO-specific workflows. Order-level ASNs increase reconciliation accuracy yet require stricter vendor discipline. Pack-level ASNs deliver the most visibility but introduce the most data volume and integration overhead. Consider the business case: high SKU velocity and automation justify pack-level detail; complex PO billing or vendor chargebacks justify order-level details; basic transport coordination relies on shipment level.

Practical Example—When Hybrid Works Best

A 3PL receives cross-dock LTL shipments containing multiple retailer POs. The shipper sends a shipment-level ASN with carrier, trailer, BOL, and ETA plus order-level lines listing PO numbers and pallet counts. The recipient’s WMS uses the shipment-level data to assign a door and order-level lines to route pallets to corresponding customer bays. Pack-level detail is only required for some retailer POs and is provided separately when needed. This hybrid model minimizes data for the carrier while preserving PO accuracy for customers.

Decision Checklist For Choosing ASN Granularity

• Volume And Velocity: High SKU throughput favors more granular ASNs to support automation.
• Billing And Compliance Needs: If invoicing or regulation requires PO- or carton-level detail, opt for order/pack-level data.
• Tech Capability: Evaluate whether suppliers and your WMS/TMS can reliably transmit and consume detailed ASNs.
• Exception Handling: Consider how often mismatches occur and whether shipment-level summaries provide sufficient context to resolve them.

In short, the Shipment Level simplifies transport coordination and is the natural parent in ASN hierarchies. Use shipment-level ASNs when the priority is carrier coordination and dock planning; add order- or pack-level detail where PO reconciliation, compliance labeling, or automation demands more granularity.