Using HDoS for Inventory Audit and Waste Reduction

Historical Days of Supply (HDoS) measures how many days current inventory will last based on actual historical sales volume. It helps logistics managers identify slow-moving stock, stockout risk, and opportunities to reduce waste and excess catalog SKUs.

What HDoS is and why it matters.

Historical Days of Supply (HDoS) is a simple, demand-driven metric that converts historical consumption into a horizon for current inventory: how many days the on-hand quantity would have lasted if recent historical sales rates repeat. For logistics and inventory management, HDoS is valuable because it links stock levels directly to real, observed demand—so decisions about reordering, promotions, and SKU rationalization are rooted in what actually sells rather than in optimistic forecasts or static safety-stock rules.

How HDoS is calculated (basic formula and example).

The common formula is: HDoS = (Current On-Hand Inventory) / (Average Daily Usage over a past period). Average daily usage is usually computed over a window such as 30, 60, or 90 days depending on seasonality and product lifecycle.

Example: If you have 500 units on hand and sold 150 units in the last 30 days, average daily usage = 150 / 30 = 5 units/day. HDoS = 500 / 5 = 100 days. That means current stock would have lasted 100 days at the recent sales rate.

Interpreting high vs low HDoS values.

HDoS is most useful when interpreted relative to business rules and the product’s role:

• High HDoS (much greater than target range) suggests slow-moving or over-supplied items—potential “dead stock.” High HDoS increases storage costs, ties up working capital, and raises risk of obsolescence or expiry for perishable goods.
• Low HDoS (much lower than target range) signals fast-moving items or potential stockout risk if below safety thresholds. Low HDoS may justify priority replenishment, higher safety stock, or expedited replenishment strategies.

Choosing the right historical window.

Pick a lookback period that matches demand patterns: 30–60 days for fast-moving, highly seasonal or promotional items; 90–180 days for slow movers or B2B catalog items. Short windows are more responsive but can be noisy; longer windows smooth noise but may hide recent demand shifts.

Using HDoS to identify slow-moving inventory.

To find slow movers, run HDoS across your SKU base and flag items above a defined threshold (for example, >180 days for non-perishables or >365 days for long-tail SKUs). Create tiers such as:

• Normal flow: HDoS within target policy range
• Slow-moving: HDoS in an elevated range requiring action (promotion, bundling)
• Dead stock candidate: Very high HDoS where liquidation or delisting is warranted

Actions for flagged SKUs include targeted promotions, price markdowns, bundling with complementary items, moving to lower-cost storage, or initiating return-to-vendor or disposal processes.

Minimizing storage costs with HDoS-driven actions.

High HDoS identifies inventory that consumes space without generating turnover. Use HDoS to prioritize cost-saving moves:

1. Re-slot or relocate slow SKUs to less expensive locations to free premium pick-face space.
2. Remove excess safety stock on items with consistently high HDoS and replace with reorder policies tied to observed demand.
3. Implement timed promotions or clearance events for SKUs above a disposal threshold.
4. Negotiate return or buyback with suppliers for large slow inventories where possible.

Cleaning up catalog clutter and SKU rationalization.

HDoS helps make catalog pruning objective rather than opinion-based. Combine HDoS with margin, customer importance, and strategic fit to decide which SKUs to delist. Typical rationalization steps:

• Rank SKUs by HDoS, margin contribution, and order frequency.
• Mark SKUs with persistently high HDoS and low margin for phase-out.
• Test phase-out through limited availability or ‘last-chance’ promotions and monitor customer impact.
• Document delisting rules and lead times in procurement and marketing systems to avoid accidental reintroduction.

Practical implementation: processes and systems.

Integrate HDoS into regular inventory audit workflows. Steps include:

1. Automate HDoS calculation in WMS, ERP, or inventory analytics tool with configurable lookback windows.
2. Define policy thresholds per product class (e.g., perishables, fast-moving, seasonal, high-value slow movers).
3. Schedule periodic reports that flag SKUs outside target HDoS ranges for review by category managers.
4. Link flagged SKUs to automated workflows: promotions, reallocation, repricing, transfer, or disposal.

Common mistakes to avoid.

Do not treat HDoS as the sole decision input. Common pitfalls include:

• Using a one-size-fits-all HDoS threshold regardless of product type or seasonality.
• Ignoring demand volatility—HDoS calculated over a short promotional window can mislabel items.
• Failing to account for incoming replenishments, outstanding purchase orders, or inbound transit stock when assessing stockout risk.
• Mistaking temporarily low sales (e.g., between seasons) as permanent decline and delisting prematurely.

KPIs to monitor alongside HDoS.

Combine HDoS with metrics such as inventory turnover, days inventory outstanding (DIO), carrying cost per SKU, service level, and fill rate to get a fuller picture. Monitor trend changes in HDoS rather than single snapshots—an upward trend signals building excess, a downward trend warns of increased consumption or potential stockouts.

Real-world example.

Imagine a retailer with 1,200 units of a winter jacket and average daily sales of 4 units over 90 days: HDoS = 1,200 / 4 = 300 days. That is likely excessive for a seasonal item. The retailer might mark down the jacket, run bundled promotions, move remaining stock to discount channels, and reduce future purchase orders. Conversely, if a popular replacement part shows HDoS of 5 days, procurement can prioritize replenishment and raise safety stock to avoid costly stockouts.

Conclusion and recommended next steps.

HDoS is a practical, easy-to-calculate metric that, when applied with product-specific policies and integrated into automated workflows, helps logistics managers identify slow movers, reduce storage costs, and clean up catalogs. Start by automating HDoS calculation, set sensible thresholds per product category, and tie flagged results to predefined corrective actions—promotion, reallocation, replenishment, or delisting. Review outcomes and refine lookback windows and thresholds quarterly to align HDoS with changing demand patterns.