Case Velocity vs. SKU Velocity: Which Should Guide Your Replenishment Strategy?

Case Velocity The rate at which cases of a product are sold, ordered, or moved through a channel. Comparing that rate to SKU (unit) velocity clarifies which metric should drive a particular replenishment or warehousing decision.

Both case and SKU velocities describe movement; they differ in their operational implications. SKU velocity tracks sell-through at the unit level and is ideal for merchandising, pricing, and e-commerce fulfillment. Case velocity translates that activity into the physical units suppliers and logistics partners handle — cases, cartons, and pallets — and is therefore indispensable for ordering, shipping, and DC operations.

When To Use Case Velocity

Case velocity is the preferred metric when decisions involve packaging, transportation, or minimum-order constraints. Use it to size purchase orders, schedule carrier pickups, determine pallet build rules, and allocate DC space. When suppliers invoice or ship in cases, case velocity aligns internal processes with external constraints.

• Ordering and procurement: Suppliers with MOQs in cases require case-velocity inputs for frequency and quantity decisions.
• Warehouse operations: Case-based pick paths, pallet positions, and pallet replenishment use case velocity for labor and space planning.
• Freight planning: Case volumes determine pallet counts, weight, and freight class estimates.

When To Use SKU (Unit) Velocity

SKU velocity — units sold per period — drives merchandising, pricing, and e-commerce fulfillment where consumer behavior (unit sales, pack-break) is the focus. Use SKU velocity to decide shelf facings, promotional assortment, and unit-pick labor. For online orders shipping single units to customers, SKU velocity often matters more than case velocity.

• Merchandising and space planning: Shelf facings and planogram decisions reflect unit sales patterns.
• E-commerce fulfillment: When most orders are single units, SKU velocity affects pick rates and cartonization.
• Promotional analysis: SKU-level sell-through shows the exact consumer response to promotions.

How To Reconcile Both Metrics

Best practice is to compute both metrics and use them where they are most relevant. Convert SKU velocity into case velocity using a central case-configuration table. When the two diverge — for example, high SKU velocity but low case velocity due to case breakage — surface that variance in dashboards and apply different rules for ordering versus store replenishment.

• Convert consistently: Maintain accurate cases-per-SKU values in a master product file.
• Dual KPIs: Report both KPIs to planners so procurement sees case implications while merchandisers see consumer-unit reality.
• Exception rules: Flag items where pack-break or multipacks distort the relationship between SKU and case velocities.

Decision Flow Examples

Example 1 — Reorder: Procurement uses case velocity and lead time to calculate reorder points, while store replenishment teams use SKU velocity to set shelf restocking frequencies. Example 2 — Promotions: Merchandising uses SKU velocity to predict unit uptake and expected uplift; supply chain converts that uplift into required case volumes to satisfy the promotion.

Implementation Tips

Operational alignment requires clear ownership of each metric and automated conversion. Design dashboards that show SKU and case velocity side-by-side, include notes on conversion assumptions, and surface when velocity drivers change (promotions, seasonality, distribution-center outages).

• Tip: Use velocity bands (fast/medium/slow) defined separately at the SKU and case level.
• Tip: Build automated alerts when SKU velocity implies a case shortfall within lead time.
• Tip: In multi-pack SKUs, consider capturing both pack-level and individual-unit GTINs to avoid miscounting.

In short, the Case Velocity metric — the rate at which cases of a product are sold, ordered, or moved through a channel — should guide any decision involving cartons, pallets, carriers, and supplier MOQs. Use SKU velocity for consumer-facing and single-unit fulfillment choices, and reconcile both measures to create replenishment plans that are both commercially sensible and operationally executable.