How To Configure Unit Of Measure Conversion For Cases, Pallets, And Eaches

Unit of Measure Conversion The mathematical or inventory-system conversion between packaging levels such as eaches, cases, and pallets. Proper configuration in your WMS/ERP prevents inventory mismatches and makes picking, receiving and replenishment predictable.

Configuration is both data entry and rule definition. You must record conversion factors on the item master and set system behaviors for partial packs, rounding, and transaction display. A clear configuration reduces exceptions on the dock and avoids downstream accounting impacts.

Essential Fields To Capture

At a minimum, configure these attributes for each SKU:

• Base unit: The smallest saleable or stockable unit (usually EA).
• Case quantity: Number of base units per case (integer preferred).
• Inner pack: If applicable, number of base units per inner pack and inner packs per case.
• Pallet configuration: Cases per layer, layers per pallet and cases per pallet (derived but stored explicitly for clarity).
• Unit weights and dimensions: Weight/volume per base unit, per case and per pallet to support capacity planning and rate shopping.

Rule Settings To Define

Beyond data fields, set operational rules:

• Rounding policy: Choose how to handle partial cases—round down (no partials allowed), round up (conservative), or allow decimal inventory with a separate broken-case process.
• Break-pack handling: Configure whether broken-case inventory is tracked as a child lot, new UOM, or ignored for accounting purposes.
• Picking preference: Define whether picks default to each, case, or pallet based on order type, carrier or client preference.

Step-by-Step Configuration Example

Configure SKU‑456 sold both as each and case and normally stored on pallets:

• Set base unit: EA
• Case quantity: 12 EA per CS
• Pallet: 10 cases per layer, 6 layers = 60 CS per pallet
• Derived conversion: 12 EA × 60 CS = 720 EA per PL stored in the system for quick reference

Testing And Validation

After configuration, validate with real transactions:

• Receiving test: Post an ASN for 2 pallets and verify the system records 1,440 eaches (2 × 720) and creates the correct pallet/layer labels.
• Picking test: Create both a case pick and an each pick and confirm the pick tasks, labels and inventory decrements match expected conversions.
• Edge cases: Test partial-case receipts and broken pallets to ensure rounding or broken-case rules trigger and create the appropriate inventory events.

Operational Controls

Introduce controls to keep conversions correct over time:

• Change management: Require approvals and change logs for edits to pack quantities.
• Supplier master data: Reconcile supplier packaging changes regularly and propagate updates to the WMS.
• Periodic audits: Run targeted cycle counts by packaging level (case counts vs each counts) to catch mismatches early.

Integration Notes

When mapping to ERP, TMS or trading partners, pay attention to UOM code conventions and decimal handling. Explicitly map external codes to your internal base unit and conversion factors during EDI or API onboarding. Where possible, use GTINs for packaging level identification so partners and systems reference the exact pack configuration.

In short, the Unit of Measure Conversion should be a carefully configured set of item master attributes and system rules: base unit, case/inner/pallet quantities, rounding and break-pack policies, plus governance controls. Proper setup and validation ensure inventory accuracy and smooth material flows across receiving, picking, and billing.