Anyone who has handled advance ship notices for retail EDI knows the headaches that follow poor pack hierarchy. According to Octasyn, when your warehouse sends an ASN but gets the inner pack and case pack levels wrong, you start seeing chargebacks, rejected shipments, manual rework, and frustrated partners — a simple mistake in pack structure can cost hours and thousands.

Why pack hierarchy matters in ASNs

When these levels aren't correctly mapped in your ASN, you risk several costly outcomes.

• Rejected shipments at the DC: A hierarchy mismatch between the ASN and the physical carton contents fails automated receiving.
• Chargebacks for quantity discrepancies: If the roll-up from each to inner pack to case doesn't add up, the retailer's system flags an error.
• Manual rework at receiving: Staff have to stop and manually reconcile what arrived against what the ASN claims, slowing the entire dock.
• Strained trading partner relationships: Repeated hierarchy errors damage a supplier's compliance track record over time.

How pack hierarchy breaks down in real operations

Working with demanding retail partners like Nakoma Products and Razor USA, common patterns emerge in how pack hierarchy goes off the rails.

• Inner pack quantities changing at the source without updating the ASN mapping
• Order management and warehouse systems maintaining separate, unsynchronized hierarchy definitions
• Staff manually overriding pack quantities during a rush without updating the electronic record
• New SKUs launched with a different pack structure than the template assumes

The anatomy of a structured ASN: doing it right

To avoid headaches, start with a crystal-clear definition of your pack levels.

1. 01
   Define the each, inner pack, and case pack for every SKU. This should live in your item master data, not be assumed at pack time.
2. 02
   Confirm the roll-up math is correct. Each times inner packs per case should equal the total case quantity, with no rounding or approximation.
3. 03
   Map the hierarchy into the ASN structure the retailer expects. Some retailers want carton-level detail; others expect pallet-level grouping on top of that.
4. 04
   Validate the physical pack matches the electronic record before shipment. A scan-based check at packing catches a mismatch before it becomes a DC rejection.

Breakdowns usually happen when systems or staff skip one of these steps, or when the order management system and warehouse systems aren't talking to each other.

Common pitfalls and how to spot them

• Inner pack quantity drift: A supplier changes multi-pack quantities without updating the corresponding EDI mapping.
• Confusing carton and pallet levels: Treating a pallet-level ASN requirement as if it were carton-level, or vice versa.
• Stale item master data: Pack hierarchy defined once and never revisited as products or packaging change.
• Disconnected systems: Order management, WMS, and EDI platforms each holding a slightly different version of the same hierarchy.

Steps to building a compliant pack hierarchy

1. 01
   Audit your current item master data for hierarchy accuracy. Confirm each, inner pack, and case pack quantities are current for every active SKU.
2. 02
   Centralize the hierarchy definition in one system of record. Avoid maintaining the same data independently across order management, WMS, and EDI platforms.
3. 03
   Map each retailer's required ASN structure explicitly. Confirm whether carton-level, pallet-level, or both are expected.
4. 04
   Automate the ASN generation from validated pack data. Remove the manual step where hierarchy data could be re-typed incorrectly.
5. 05
   Test with a live shipment before scaling. Confirm the retailer's system accepts the hierarchy as structured before committing to full volume.

What retailers look for in your ASN and packing

The receivers at large retailers work under serious time constraints. Their systems typically expect a consistent, predictable structure.

• Quantities at each level that mathematically reconcile without exception
• Consistent hierarchy structure across every shipment, not just most of them
• Carton and pallet labels that match exactly what the ASN declares at each level
• No unexplained gaps between what was ordered and what the hierarchy accounts for

Any missed or swapped level means someone has to stop their flow, try to find the error, and possibly reject the shipment. Mistakes erode trust both in your brand and EDI reliability.

Troubleshooting: how to fix pack hierarchy problems

• Pull the specific ASN and compare it line by line against the physical pack list for the rejected order
• Check whether the item master data has changed recently without a corresponding EDI mapping update
• Confirm the retailer's required structure hasn't changed in a recent routing guide update
• Trace the error back to whichever system introduced the discrepancy, rather than just correcting it downstream

Best practices for long-term success

1. Treat pack hierarchy as master data, not a packing-time decision. It should be defined and locked before an order ever reaches the floor.
2. Review hierarchy accuracy whenever packaging changes. A new case configuration should trigger an automatic review of the EDI mapping.
3. Automate hierarchy validation before ASN transmission. Catching a mismatch pre-send avoids a DC rejection entirely.
4. Audit hierarchy-related chargebacks specifically. Pattern them separately from other chargeback types to spot systemic gaps faster.
5. Keep one centralized source of truth. Multiple systems each holding their own version of the hierarchy is a recurring root cause of failure.

The bigger picture: pack hierarchy as a foundation of supply chain trust

Proper pack hierarchy isn't a minor detail you can gloss over. At scale, it can be the difference between barely surviving chargebacks and building a reputation for flawless compliance. Your ASN and label accuracy show your commitment to your trading partner's requirements. Over time, this saves money, builds credibility, and opens doors to more demanding, higher-value distribution channels.

Frequently asked questions