Inventory ManagementShopifyInventory PlanningOctober 28, 2026

How to Analyse an Inventory Health Dashboard for Shopify Brands

Learn how to build a planning-grade inventory health dashboard for Shopify: forward weeks of cover, in-stock rate, aged stock, forecast bias & capital at risk.

TrueGradient Editorial Team

TrueGradient Editorial Team

How to Analyse an Inventory Health Dashboard for Shopify Brands

Shopify brands track revenue, conversion rate, ROAS, and CAC daily, often hourly. Inventory gets a weekly glance at stock levels, if that. The asymmetry is expensive: by the time an inventory problem shows up in a revenue dashboard, as a campaign that sold out on day two or a warehouse full of last season's colourways, the cash and the margin are already gone.

For Shopify teams connecting planning to storefront demand, Install TrueGradient for Shopify to turn store data into demand forecasts, reorder plans, and inventory decisions.

An inventory health dashboard closes that gap. Done properly, it answers four questions every week, before they become P&L problems: Are we going to run out? Are we holding too much? Can we trust the forecast? How much cash is exposed? This guide covers the KPIs that answer each question, how to calculate them, the thresholds that should trigger action, and how to lay the dashboard out so leadership and planners each see what they need.

What is an inventory health dashboard?

An inventory health dashboard is a recurring view that combines stock position, forward demand, forecast quality, and working capital exposure at SKU level, so a team can see where inventory is at risk before it becomes a stockout or excess. The distinction from an inventory report matters. A report describes the stock you have. A health dashboard compares what you have with expected demand and flags where the two are about to diverge.

Why aren't Shopify's native inventory reports enough?

Shopify's built-in analytics include solid inventory reporting: month-end stock snapshots, inventory value, units sold per day, sell-through rate, days of inventory remaining, and ABC grading by product and variant. For a single-channel store with a stable catalogue, that is a reasonable starting point. Shopify's own reporting guidance recommends exactly the right discipline: start from the decision the dashboard supports, pick a small set of KPIs, and assign an owner and a response to each one.

The gaps appear as a brand scales:

  • The metrics are backward-looking. Days of inventory remaining is typically computed from past sales velocity. It cannot see next month's campaign, a seasonal ramp, or a product that is decaying.
  • There is no forecast-quality layer. Nothing tells you whether the numbers you are planning against are biased or trustworthy.
  • Channels outside Shopify are invisible or partial. Amazon, wholesale, and retail accounts draw from the same stock but report elsewhere.
  • There is no link to lead time. Five weeks of stock is healthy for a SKU with a two-week lead time and a stockout in waiting for one with an eight-week lead time.
  • Nothing translates risk into cash. Leadership sees units and days, not the dollar value of excess stock or the margin about to be lost.

For a closer look at the signals that a spreadsheet or native-report setup has hit its ceiling, see signs your demand planning has outgrown Excel.

The inventory health KPIs every Shopify dashboard needs

Group the KPIs by the question they answer. Triggers below are illustrative starting points; set real thresholds from your lead times, margins, and service targets.

Availability: Are we going to run out?

KPIHow to calculateWhat it tells youIllustrative trigger
Demand-weighted in-stock rateForecast demand on in-stock SKU-days ÷ total forecast demandAvailability where it matters, not a simple count of SKUs in stockBelow 95% on A items
Stockout frequencyOut-of-stock SKU-days ÷ total active SKU-days, by segmentWhether stockouts are isolated or systemicRising for three consecutive weeks
Lost sales estimateΣ forecast demand during out-of-stock days × unit marginThe dollar cost of availability gapsAny A item with lost margin in the week
Wholesale fill rateUnits shipped ÷ units ordered by retail and wholesale accountsChannel service levels that drive chargebacks and delistingsBelow the account's contracted rate

Coverage: Is stock matched to upcoming demand?

KPIHow to calculateWhat it tells youIllustrative trigger
Forward weeks of coverWeeks until (on hand + inbound) is consumed by the forward forecastHow long stock lasts against expected demand, including campaignsBelow supplier lead time + review period
Cover-to-lead-time ratioForward weeks of cover ÷ supplier lead time in weeksWhether a reorder placed today arrives in timeBelow 1.0
Sell-through rateUnits sold ÷ units received (or beginning stock + receipts) for the periodWhether a launch or seasonal buy is selling at planBelow plan at week 4 of a season

Excess and aging: Are we holding too much?

KPIHow to calculateWhat it tells youIllustrative trigger
Aged inventory shareValue of stock with no sale in 90 or 180 days ÷ total inventory valueStock drifting toward markdown or write-offAbove 10% of inventory value
Excess stock value(On hand − target maximum) × unit cost, where positiveCash tied up beyond what the plan needsAny C item with excess above a set dollar floor
GMROIGross margin ÷ average inventory at costReturn earned per dollar held in stockBelow category target

Forecast quality: Can we trust the plan?

KPIHow to calculateWhat it tells youIllustrative trigger
WMAPE at SKU-channel levelΣ │actual − forecast│ ÷ Σ actualSize of forecast error, weighted toward volume that mattersWorsening trend over 4 to 6 weeks
Forecast biasΣ (forecast − actual) ÷ Σ actualWhether the forecast leans consistently high (excess) or low (stockouts)Beyond ±5% sustained
Tracking signalCumulative forecast error ÷ mean absolute deviationWhether bias is real or normal noiseOutside ±4

The forecast-quality group is the one native reports miss entirely, and it is the one that explains the others: a sustained positive bias shows up weeks later as excess and aged stock, a negative bias as stockouts. Measure it where decisions are made. Other planning software companies whose platforms serve large grocery and retail networks make the point well: accuracy should be calculated at the grain and horizon that generate orders, such as store-SKU-day for replenishment or DC-SKU-week for distribution planning. For a Shopify brand, that usually means SKU-channel-week, measured over the supplier lead time, not a blended monthly number. The method behind each metric is covered in improving demand forecast accuracy.

Capital: how much cash is exposed?

KPIHow to calculateWhat it tells youIllustrative trigger
Excess capital exposuremax(0, available − P90 forecast demand over the horizon) × unit costStock that is surplus even in a high-demand scenarioTop 20 SKUs reviewed weekly
Shortfall margin exposuremax(0, P50 forecast demand − available) × unit marginMargin at risk from expected shortfallsAny A or B item above a set dollar floor

How to calculate weeks of Inventory cover correctly?

The most common dashboard error is computing cover from trailing sales. Here is why it matters, using one SKU ahead of a campaign: On hand: 1,200 units. Inbound arriving within lead time: 400 units. Available: 1,600 units. Trailing eight-week sales: 150 units a week. Trailing cover: 10.7 weeks. Looks comfortable. Forward forecast: 250 and 250 units in weeks 1 and 2, then 400 a week for a three-week campaign, then 300 and 250. Cumulative forecast demand: 250, 500, 900, 1,300, then 1,700 by the end of week 5. Forward cover: about 4.75 weeks. Supplier lead time: 6 weeks. The cover-to-lead-time ratio is 0.79, so an order placed today will arrive after the stockout, and roughly 400 units of campaign and post-campaign demand are at risk. Same stock, same SKU: one calculation says do nothing, the other says the campaign will sell out. Forward cover needs a forward forecast that includes promotions and seasonality, which is why the dashboard and the forecast have to live on the same data. What the buffer and trigger should be once you see the gap is covered in safety stock vs. reorder point. Adding a forecast confidence layer A single-number forecast hides the most useful information a dashboard can show: how uncertain each SKU is. High-maturity teams overlay a forecast range, typically P10, P50 and P90, on every coverage metric. Two SKUs with identical forward cover need different responses if one has a tight range and the other a wide one. The practical way to use this is to segment the dashboard. Show coverage and exceptions by ABC-XYZ cell, so AX items with a reliable forecast run on automated alerts, while AZ items with high value and high uncertainty go to a planner every week. The range itself comes from probabilistic forecasting with prediction intervals; a dashboard can only show confidence if the forecast produces it. How to quantify inventory capital at risk

The most common dashboard error is computing cover from trailing sales. Here is why it matters, using one SKU ahead of a campaign:

  • On hand: 1,200 units. Inbound arriving within lead time: 400 units. Available: 1,600 units.
  • Trailing eight-week sales: 150 units a week. Trailing cover: 10.7 weeks. Looks comfortable.
  • Forward forecast: 250 and 250 units in weeks 1 and 2, then 400 a week for a three-week campaign, then 300 and 250.
  • Cumulative forecast demand: 250, 500, 900, 1,300, then 1,700 by the end of week 5. Forward cover: about 4.75 weeks.
  • Supplier lead time: 6 weeks. The cover-to-lead-time ratio is 0.79, so an order placed today will arrive after the stockout, and roughly 400 units of campaign and post-campaign demand are at risk.

Same stock, same SKU: one calculation says do nothing, the other says the campaign will sell out. Forward cover needs a forward forecast that includes promotions and seasonality, which is why the dashboard and the forecast have to live on the same data. What the buffer and trigger should be once you see the gap is covered in safety stock vs. reorder point.

Adding a forecast confidence layer

A single-number forecast hides the most useful information a dashboard can show: how uncertain each SKU is. High-maturity teams overlay a forecast range, typically P10, P50 and P90, on every coverage metric. Two SKUs with identical forward cover need different responses if one has a tight range and the other a wide one.

The practical way to use this is to segment the dashboard. Show coverage and exceptions by ABC-XYZ cell, so AX items with a reliable forecast run on automated alerts, while AZ items with high value and high uncertainty go to a planner every week. The range itself comes from probabilistic forecasting with prediction intervals; a dashboard can only show confidence if the forecast produces it.

How to quantify inventory capital at risk?

Leadership acts on dollars, not days. Two illustrative SKUs over an eight-week horizon:

  • SKU A (excess). Available 3,000 units; P90 forecast demand 2,400 units; unit cost $18. Excess capital exposure = (3,000 − 2,400) × $18 = $10,800 surplus stock even if demand lands at the high end.
  • SKU B (shortfall). Available: 900 units; P50 forecast demand: 1,400 units; unit margin: $22. Shortfall margin exposure = (1,400 − 900) × $22 = $11,000 of margin likely to be lost without action.

Summed across the catalogue, these two numbers give a CFO what a stock report never does: how much cash is protecting the plan and how much is simply parked. The working-capital side is explored further in reduce working capital and optimize inventory levels.

Inventory health dashboard layout: three views, three audiences

One dashboard for everyone ends up useful to no one. Split it by decision.

ViewAudienceCadenceWhat it shows
Leadership summaryFounder, COO, CFOWeeklyDemand-weighted in-stock rate, excess capital exposure, shortfall margin exposure, aged inventory share, forecast bias trend
Planner workbenchDemand and supply plannersDailyForward cover vs lead time by SKU-channel, WMAPE and tracking signal by segment, inbound schedule, upcoming campaigns
Exception queuePlanner on dutyContinuousOnly SKUs that breach a trigger, ranked by dollar exposure, each with an owner and a recommended action

The exception queue is where most of the value sits. A planner who reviews 40 ranked exceptions a day outperforms one who scans 4,000 SKUs a week. For monitoring whether a metric has genuinely shifted or is just noise, inventory control charts are the right statistical companion to this layout.

Common inventory health dashboard mistakes

  • Trailing cover instead of forward cover. The dashboard looks healthiest right before a campaign sells out.
  • SKU-count availability. "96% of SKUs in stock" can hide the three best-sellers that are out.
  • Blended, monthly accuracy. A good aggregate WMAPE can hide SKU-channel bias that drives every stockout.
  • No lead-time context. Coverage means nothing without the time it takes to replenish.
  • Units instead of dollars. Leadership cannot prioritise without exposure in currency.
  • No owner per trigger. A red tile nobody is accountable for is decoration.
  • Shopify only. If Amazon or wholesale draw from the same stock, the dashboard must see those channels too.

Inventory health dashboard FAQs

What is an inventory health dashboard?

An inventory health dashboard is a recurring view that combines stock position, forward demand, forecast quality, and working capital exposure at SKU level. Unlike an inventory report, which describes stock on hand, it compares stock with expected demand to show where stockouts or excess are about to occur, and how much cash or margin is at risk.

What KPIs should a Shopify inventory health dashboard include?

Group them by question: availability (demand-weighted in-stock rate, stockout frequency, lost sales), coverage (forward weeks of cover, cover-to-lead-time ratio, sell-through), excess and aging (aged inventory share, excess stock value, GMROI), forecast quality (WMAPE, bias, tracking signal), and capital (excess capital exposure, shortfall margin exposure).

How do you calculate weeks of cover?

Divide available stock (on hand plus inbound arriving within lead time) by forecast demand, week by week, until it is consumed. Using a forward forecast rather than trailing average sales matters: trailing cover ignores upcoming campaigns and seasonality, so it overstates cover exactly when demand is about to rise.

What is a good weeks of cover target?

There is no universal number. A practical target is supplier lead time plus the review period plus safety stock expressed in weeks. A SKU with a six-week lead time reviewed weekly needs more than seven weeks of forward cover before safety stock; a SKU with a two-week lead time needs far less.

How is forecast bias measured on a dashboard?

Bias is the sum of forecast minus actual, divided by the sum of actual demand, over a rolling window. A positive value means over-forecasting, which builds excess; a negative value means under-forecasting, which causes stockouts. The tracking signal, cumulative error divided by mean absolute deviation, shows whether the bias is significant; values outside roughly ±4 usually warrant action.

How often should an inventory health dashboard be reviewed?

Leadership should review the summary weekly, planners should work the planner view daily, and the exception queue should update continuously as sales, inbound shipments, and forecasts change.

Where TrueGradient fits to analyse Inventory Health Dashboard

TrueGradient connects to your store through the TrueGradient Shopify app and brings Shopify, marketplace, and wholesale demand into one plan. Because the inventory health view sits on the same probabilistic forecast that drives AI demand forecasting, forward cover, forecast confidence, and capital exposure are calculated from the same numbers, and breaches flow into ranked exceptions across end-to-end inventory optimization, replenishment, and allocation. More on the integration at TrueGradient for Shopify brands; see what the first 90 days look like.

**Book a demo** · **Talk to us**

Related reading: ABC-XYZ analysis guide · Safety stock vs reorder point · Understanding inventory control charts · Probabilistic modelling using prediction intervals


TrueGradient Editorial Team

TrueGradient Editorial Team

The TrueGradient Editorial Team creates expert, research-backed content on AI-powered supply chain planning, including demand forecasting, demand planning, inventory optimization, production planning, S&OP, and IBP. Our articles are developed with insights from supply chain practitioners, AI specialists, and product experts, and are reviewed for technical accuracy, industry relevance, and practical value. By combining real-world experience with the latest advancements in AI and machine learning, we help consumer brands, retailers, distributors, and manufacturers make smarter, data-driven planning decisions.

SOC 2 Type II certified
Built for enterprise CPG & retail
30-day proof of value

See your supply chain on
autopilot

Turn complex demand signals into clear, confident decisions without adding more tools or manual work.

Want to estimate your savings?Calculate ROI