Anyone who has handled Advance Ship Notices (ASNs) for retail EDI knows the headaches that follow poor pack hierarchy. 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. Suddenly, a simple mistake in pack structure costs hours and thousands.

Why Pack Hierarchy Matters in ASNs

At its core, a pack hierarchy is how products are grouped as they move from manufacturer to retailer. The three layers you see again and again in retail supply chain are:

• Case Pack: The outer carton shipped to the retailer’s distribution center or store.
• Inner Pack: Sometimes called an inner carton, this is used when there are sub-groupings of product packed within the case (for example, 4 inner packs with 6 items each in a 24-pack case).
• Each/Eaches: The individual selling units (SKU, UPC) retailers expect to see on their shelves or in their systems.

When these levels aren’t correctly mapped in your ASN, you risk:

• Retailers receiving inventory counts that don’t match what arrives physically
• Rejected shipments due to format or data mismatches
• Compliance chargebacks for inaccurate or missing labeling
• Loss of confidence from key customers

How We’ve Seen Pack Hierarchy Break Down in Real Operations

Working with demanding retail partners like Nakoma Products and Razor USA, we’ve seen all the common ways pack hierarchy can go off the rails:

• Case equals Each (when it shouldn’t): Staff pack a case carton that actually contains five retail units, but the ASN is sent as if each case is a selling unit. The retailer’s receiving system is set up to count by Each, leading to confusion and, often, extra manual reconciliation.
• Inner Pack Omitted: Sometimes inner packs are used in physical shipping but ignored in the digital ASN hierarchy. This leaves receivers unsure how to interpret the shipment and results in incorrect replenishment downstream.
• Mixed SKU Packs Not Declared: A case contains several different SKUs but the ASN describes it as a single SKU. This leads to overages for one item and shortages for another in the retailer’s system.

The Anatomy of a Structured ASN: Doing It Right

To avoid headaches, we recommend starting with a crystal-clear definition of your pack levels:

1. Define Selling Units (Each): Know exactly what the retailer expects as the selling unit. Is it a single bottle? A 6-pack? This defines how you structure the most granular level of your ASN shipment detail.
2. Map Inner Packs: If you use sub-cartons within your cases, ensure these inner packs are clearly labeled and included in the ASN hierarchy.
3. Specify Case Packs: The outer carton—the one you label for carrier and customer—must accurately reflect quantities and any mix within.
4. Use Matching Data Across Labels and ASNs: The SSCC or UCC-128 codes on your physical cartons should sync with the ASN information. This ensures the retailer can use scans at receiving to accurately verify your shipment.

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

• Mismatch between ASN and Physical Packaging: If the ASN lists a single item per case but the physical case contains six, expect a chargeback or rejection.
• Ignoring the Inner Pack: Leaving out this level in cartonization causes confusion and manual labor at both ends.
• Poor Barcode Mapping: Out-of-sync SSCC/UCC-128 (or GS1) barcodes make automated receiving impossible. Check out our detailed breakdown in GTIN, SSCC, and label data basics.
• Lack of System Integration: Errors often come from disconnected order management, ERP, and warehouse systems. The connection isn’t just technical—it has to structure the data identically all the way through to the ASN.

Steps to Building a Compliant Pack Hierarchy

1. Review Retailer Routing Guides: Most major retailers publish routing and ASN mapping requirements. Set time aside to compare your pack levels against your customers’ expectations.
2. Audit Your Warehouse Process: Don’t guess. Confirm if actual packing on the floor matches what you think your system is outputting.
3. Assign Clear Carton and Pallet Identifiers: Use serialized identifiers (SSCC) that are unique for every carton and can be scanned by the retailer.
4. Test Your ASN with Trading Partners: Send test shipments and have your retailer walk through receiving with you. Fix mapping as needed.
5. Automate and Standardize Wherever Possible: Modern platforms (including ours) can automate ASN creation, barcode printing, and picking workflows so manual errors are caught early rather than at the retailer’s dock. Learn about automation approaches in our guide on plugging money leaks in EDI shipping.

What Retailers Look for in Your ASN and Packing

The receivers at large retailers work under serious time constraints. Their systems typically expect:

• Every shipping carton to be clearly labeled and easily scannable
• ASN data to match up, line for line, with physical units, inner packs, and case packs
• No surprises on mix, count, or pack structure
• Clear, consistent use of carton and pallet numbering

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

• Spot the Pattern: If you see recurring chargebacks for unit mismatch or barcode problems, start by examining your latest ASN files alongside your actual cartons.
• Double-Check Pick/Pack Lists: Make sure your team uses current pick/pack instructions reflecting updated pack structures, especially after changes in product or customer requirements.
• Sync with Your System-of-Record: The product and pack data in your ERP (or order management software) should flow seamlessly into your shipping and WMS workflows. Any manual workarounds introduce risk.
• Train Teams on Hierarchy Impact: When pack structure is routinely wrong, front-line staff might not see why it matters. Include ASN and pack structure training in your SOPs. For more on training approaches, see SOPs that stick.

Best Practices for Long-Term Success

• Always involve IT and warehouse leads when making changes to pack hierarchy or ASN mapping.
• Set up regular audits against retailer chargeback data and ASN feedback to catch problems early.
• Implement test modes in your ASN workflows to trial changes before they hit live shipments.
• Use documentation and labeling that matches exactly to your ASN structure. If you call it an inner pack in the ASN, it should say that on the carton.
• Leverage automation (when available) to reduce reliance on manual data entry and ad hoc fixes.

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.

Want to Streamline Pack Hierarchy and EDI Compliance?

If you want to fix pack hierarchy issues for good, take a look at your ASN process, how your labeling is structured, and where automation could step in. We’ve helped several high-volume shippers (like Nakoma Products and Razor USA) audit and fix pack hierarchy breakdowns, leading to faster receiving, fewer chargebacks, and greater trust with retail partners.

For plain-English deep dives into the technical side, check out our other posts on common ASN errors and barcode quality essentials.

Need help getting your ASN workflow in order? Get in touch with Octasyn to talk with experts who have tackled these challenges at scale, or browse our logistics resource library for more best practices.