Cases, Eaches, and Pallets: Resolve Units Before Blaming the Stock Count
Receiving records ten cases. Picking expects individual units. The integration sends “10” without explaining the unit.
Both teams may have followed their screens correctly while the shared inventory record becomes misleading.
Microsoft's warehouse unit-sequence documentation requires conversions between units in a group and explains that warehouse work may use different units while inventory retains a base unit. This is a concrete vendor example of why unit definitions belong in the workflow requirements. Microsoft unit-sequence documentation.
Make quantity inseparable from its unit
Our recommendation is to capture the unit with every relevant quantity and establish the approved conversion for the actual product or variant. “Case” is not a universal number of pieces.
Specify receiving units, inventory units, order units, and count units. Agree how fractional quantities, rounding, damaged packaging, and split cases are handled.
Use one explicit example
In a hypothetical product, one case contains 12 pieces. Ten cases therefore represent 120 pieces. A pick of 15 pieces should leave 105 pieces before other movements.
Ask the team to demonstrate that sequence from the receiving device through the inventory record and picking task. Then introduce a second product with a different case size. A global case conversion should not silently apply to both.
The example is arithmetic, not a recommendation about your packaging hierarchy. The actual rules must match what the warehouse receives and ships.
Include the integrations
Inspect how purchase orders, store orders, carrier weights, and inventory exports label units. A field name that looks familiar may have a different meaning in another system.
Record the conversion source and owner, and review the effect of changing a pack size on open work and historical records. Do not retroactively rewrite past quantities without an agreed business process.
Bring a quantity mismatch to a systems call or explore Warehouse Management.
Bring One Workflow to a Systems Call
Walk us through a normal example and a recurring exception. Within two working days you get a short written summary of options and a recommended next step, with no obligation to build.
