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:
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
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:
Guardrails for Master Data Quality
Connecting to WMS Functions
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.
