Pack Size Versus Case Pack Versus Inner Pack: What Warehouses Need To Know

Pack Size The number of units grouped together within a defined packaging level or orderable pack.

In multi-level packaging, similar terms are used interchangeably but they represent different physical and transactional levels. A warehouse manager must distinguish between a pack size (a generic count of units per pack), a case pack (the number of units in a supplier carton), and an inner pack (a sub-case bundle inside a case). Clear definitions determine how inventory moves through receiving, storage, and order fulfillment.

Confusion among these labels is common when suppliers, retailers and carriers use different vocabulary. One vendor's "case" might be another's "master carton." The warehouse needs to record explicit numeric attributes so systems won’t misinterpret a barcode scan or EDI message.

How Each Term Functions

• Pack Size: A system-level attribute that may reference any orderable or packaged grouping (e.g., 6-pack, 12-pack, case of 24).
• Case Pack: The supplier carton count — what arrives on the pallet and what a vendor invoices as a case quantity.
• Inner Pack: A sub-unit inside a case (for example, two 6-packs inside a 12-count case) used for promotions or retail presentation.

Why Precision Matters In Systems

When the ERP or WMS treats pack size differently from case pack, transactional errors occur. For example, replenishment algorithms might order by case, but sales are recorded in eaches. If pack sizes aren’t aligned, the reorder point calculation will be wrong and stockouts or overstocks follow.

Barcodes and GTINs often exist at multiple packaging levels: each, inner pack, case and pallet each have their own GTIN. Services like GDSN (Global Data Synchronization Network) communicate pack-size attributes to trading partners. Your item master must map each GTIN to the correct pack-size attribute.

Operational Rules For Warehouses

Set explicit rules for how to treat each packaging level. Define whether picking is by each, inner pack, or case. Configure break-case transactions and specify whether pickers should break packs at a pick face or only at packing stations.

• Receiving Rule: Accept and record supplier case count as the case-pack value and scan the case GTIN.
• Storage Rule: Store by the most efficient handling unit — often the case pack for bulk storage and the each for pick faces.
• Picking Rule: Use the pack-size field to determine whether to pick whole packs or break cases.

Sample Scenario

A beverage supplier ships a product in a master pallet of 72 bottles. The master pallet comprises six cases of 12 bottles each; each case contains two inner packs of 6 bottles for retail promotions. The warehouse must map three GTINs to three pack-size values: units-per-each = 1, units-per-inner-pack = 6, units-per-case = 12. When an order for 18 bottles arrives, the fulfillment system can suggest one case + one inner pack or three inner packs depending on picking efficiency and packing rules.

Checklist For Avoiding Confusion

• Document Terms: Keep a packaging glossary for vendors and internal teams that maps local terms to numeric pack-size fields.
• Use GTINs: Capture GTIN at the proper packaging level to validate inbound and outbound units.
• Audit Packs: Perform periodic audits verifying that case pack counts match the WMS item master, especially after vendor changes.

In short, the Pack Size sits at the center of packaging hierarchy. Distinguishing pack size from case pack and inner pack — and recording each with its GTIN — eliminates ambiguity and supports accurate receiving, storage, and order fulfillment.