Back to Blog
Logistics Automation

Wrong Case Quantities Mean Wrong Inventory: Designing Unit-of-Measure and Packaging Hierarchy Master Data for WMS

If the same SKUs keep showing inventory variances, check the case quantities in your item master before you blame the count. This guide covers packaging hierarchy design, versioned case-quantity changes, and how to apply them in a WMS.

POLYGLOTSOFT Tech Team2026-11-097 min read17
Item MasterUnit of MeasureCase PackPackaging HierarchyWMS

When the Inventory Gap Comes From Master Data, Not the Count

When stock doesn't match, most teams blame the cycle count or a picking error first. But if the same SKUs keep drifting, and the drift builds at a steady rate, check the case quantity in the item master first.

Say a supplier cuts the case pack from 24 to 20, and the master still says 24. Receive 50 cases and the system books 1,200 units, but only 1,000 are on hand. Those 200 units don't exist. They show up weeks later as stockouts and count variances.

And the damage doesn't stop at receiving:

  • Every trading partner uses a different unit. One customer orders eaches, another orders cases, a third orders full pallets
  • Every WMS calculation depends on the case quantity. Pick quantities, replenishment triggers, location capacity, and outbound carton counts all rely on conversion factors
  • One wrong case quantity breaks all of these at the same time.

    Define the Packaging Hierarchy

    Levels and Conversion Factors

    A typical hierarchy runs each (EA) → inner pack (IP) → case (CS) → pallet (PL). With 6 eaches per inner, 4 inners per case, and 10 cases per layer stacked 5 high, the factors are EA 1 / IP 6 / CS 24 / PL 1,200. Store each factor both relative to the level below and relative to the base unit, so you can check one against the other.

    Attributes per Level

  • Barcodes: Eaches and cases carry different GTINs, and cases are often marked with ITF-14. Pallets usually get an SSCC for each shipment unit
  • Dimensions and weight: Keep length, width, height, and gross weight for each level separately
  • Stacking data: Cases per layer and layers per pallet, which feed rack height limits and floor load checks
  • One Base Unit

    Hold inventory in one base unit only (usually EA), and convert to cases and pallets only for display and task instructions. If you store the same SKU separately by unit, the numbers fall out of sync every time a case is opened.

    Handling a Case Quantity Change

    On changeover day, the warehouse holds both old 24-count cases and new 20-count cases. To manage that overlap you need:

  • Versioned master data with effective dates: Add a new version instead of overwriting the case quantity
  • A link to lots and receipts: Record the packaging version on the lot when it's received, so picks use that lot's quantity
  • A supplier change procedure: Set a clear path so a spec-change notice sent to purchasing becomes a master change request. Blocking unknown GTINs at the receiving dock is another safeguard
  • Guardrails for Master Data Quality

  • Check measurements at receiving: If case weight differs from the master by more than ±5%, hold the receipt and check it. Even a 4-unit shortfall shows up on the scale
  • Detect conversion errors: Raise an alert when a case-based order converts to a fractional quantity, or when a less-than-case pick is created for a do-not-break SKU
  • Permissions and history: Require approval to change case quantities, and log who changed what and when
  • Connecting to WMS Functions

  • Unit-based picking: Split an order for 1,250 units into 1 pallet + 2 cases + 2 eaches, each picked from its own zone
  • Case breaking: When a case is opened, post a conversion transaction that moves stock from case to each
  • Replenishment units: Refill each-pick zones by the case and case-pick zones by the pallet
  • Unit code mapping: Map different codes for the same unit, such as `BOX` in the ERP, `CT` in the client's system, and `CS` in the WMS
  • The POLYGLOTSOFT Approach

    POLYGLOTSOFT starts with an item master integrity assessment. We compare receiving measurements, count variances, and conversion-error history SKU by SKU to find suspect case quantities. Then we build WMS master data with a full packaging hierarchy, effective-dated versions, and unit mappings. If your variances keep coming back, check the master data before you add more cycle counts. Contact us and we'll review your current master structure with you.