How to Improve Demand Forecasts With Sales & Inventory Data

TL;DR

Most mid-market companies already have the sales and inventory data they need to forecast better. The problem isn’t the algorithm, it’s the data pipeline. Sales data tells you what happened; inventory data tells you why. Combine them, clean them, and build a feedback loop, and your forecast becomes a decision tool your team actually trusts.

---

Every mid-market product company has sales history sitting in an ERP or a set of spreadsheets. Most have inventory snapshots too. And yet, nearly 80% of small and mid-size businesses suffer from a combination of insufficient forward planning and being overstocked at the same time. The data exists. The forecasts still miss.

The gap between having data and having a useful forecast isn’t about needing a fancier model. It’s about understanding which data matters, cleaning it properly, and connecting it to decisions. This guide walks through exactly how to use sales and inventory data to improve demand forecasts, from raw inputs to actionable output.

See how BetterDemand builds live forecasts on your actual sales and inventory data.

What Is a Demand Forecast?

A demand forecast predicts how much of each product customers will want over a future period. It drives purchasing, production scheduling, inventory positioning, and capacity decisions. Get it right and you buy the right amount at the right time. Get it wrong and you either run out of product or drown in excess stock.

One critical distinction: a demand forecast is not the same thing as a sales forecast. Sales data reflects what you actually sold, which is always constrained by what you had available to sell. A demand forecast tries to capture what customers would have bought if you’d had unlimited supply. That difference matters enormously, because if you forecast using only sales data, you’re baking your past stockouts into your future plans.

This is precisely why both sales and inventory data are required. Sales alone tells you what moved. Inventory context tells you whether demand was satisfied or suppressed.

Sales Data: The Starting Signal

Historical sales data is the foundational input for any demand forecast. Most practitioners recommend a minimum of two to three years of history to capture seasonal patterns, growth trends, and cyclical behavior.

But the type of sales data matters more than the volume.

Shipment Data vs. POS Data

Shipment or order data, the kind most companies pull from their ERP, is a lagging indicator. It reflects when product left your warehouse, not when a consumer actually bought it. Between your dock door and the customer’s shopping cart sit distributors, retailers, and weeks of pipeline inventory. Small fluctuations in consumer demand at the shelf cause increasingly larger variances in orders as you move up the supply chain, a phenomenon known as the bullwhip effect.

Point-of-sale (POS) data is closer to actual consumer demand. When you can see what’s selling at the register, you can make faster adjustments to purchasing and replenishment. For CPG and food and beverage companies selling through retail, integrating POS data is one of the highest-value improvements available.

That said, many mid-market companies don’t have access to POS data. If you’re working with shipment data, acknowledge its limitations and correct for them during data cleansing, which we’ll cover below.

Why Sales Data Alone Is Incomplete

Here’s the concept that separates good forecasters from mediocre ones: sales data reflects constraints, not actual need.

MIT’s Dr. Larry Lapide coined the term “supply-neutral demand” to describe customer demand stripped of all distortions from supply limitations and surpluses. His argument is that over time, forecasting on constrained data conditions customers to order based on what they expect to be available rather than what they actually need.

As one supply chain practitioner put it on Substack: “Forecast using sales data, and you’re locking in future stockouts. But forecast true demand, and now you’ve got options: increase shelf space, order more product, and actually meet what customers want.”

Four common distortions that shape your sales data away from true demand:

• Stockouts create false zeros. The product didn’t sell, but not because nobody wanted it.
• Promotions create artificial spikes that inflate what looks like baseline demand.
• Supply surpluses (fire sales, channel stuffing) make normal demand look higher than it is.
• Allocation constraints cap what customers could have ordered, hiding the true ceiling.

Understanding these distortions is the first step in learning how to use sales and inventory data to improve demand forecasts. For a deeper look at this problem across consumer goods, see our guide on demand forecasting in CPG.

Inventory Data: The Missing Context Layer

This is the insight that most forecasting guides miss entirely. They treat inventory as something you optimize after the forecast is done, an output of the planning process. In reality, inventory data is one of the most valuable inputs to the forecast itself.

How Inventory Distinguishes Demand Drops from Stockouts

If SKU-1234 sold zero units last Tuesday, your sales data shows a zero. But was that because nobody wanted the product, or because the shelf was empty? Without inventory context, those two situations look identical in the data, and the forecast can’t tell the difference.

Pairing on-hand inventory levels with sales data lets you flag periods where zero sales coincided with zero or near-zero inventory. Those aren’t demand drops. They’re lost sales. And your forecast should estimate what would have sold if product had been available.

This correction, called unconstrained demand estimation, is one of the most impactful ways inventory data feeds back into forecast accuracy. Practitioners on Reddit’s r/SupplyChainLogistics frequently highlight data cleanliness and shaped demand as the most underappreciated challenges in predictive forecasting tools.

Key Inventory Metrics That Inform Forecasting

Days on Hand (DOH) translates abstract inventory units into time. Telling your CEO you have 5,000 units doesn’t mean much. Telling them you have 47 days of inventory at current demand rates creates immediate understanding. The formula:

DOH = (On-Hand Inventory ÷ Average Daily Demand)

When DOH is climbing for a SKU while sales are flat, the forecast and purchasing are misaligned. When DOH drops below your lead time, you’re headed for a stockout.

Inventory Turns measures how efficiently inventory moves through the business. Higher turns generally mean the demand forecast is well-calibrated and purchasing is responsive.

Turns = Annual Cost of Goods Sold ÷ Average Inventory Value

Turns connect demand performance to inventory investment. The metric uses historical demand and inventory levels, but its implications are forward-looking: falling turns on a SKU signals that either demand is softening or you’re over-buying.

Weeks of Supply (WOS) shows how long current inventory will last based on the current demand rate. High WOS often signals overestimated demand. Low WOS indicates stockout risk when demand accelerates.

WOS = On-Hand Inventory ÷ Average Weekly Demand

These metrics create a feedback loop. The forecast drives inventory targets, but actual inventory positions, measured through DOH, Turns, and WOS, reveal whether the forecast was right. When these metrics start drifting, it’s a signal to revisit the demand model. To understand where excess inventory hides cash, read about where working capital hides in inventory portfolios.

Safety Stock Calibration

Safety stock protects against forecast variance, but only when it’s set intentionally based on estimated demand volatility and lead time variability. If your safety stock formula uses a static assumption about demand variability rather than your actual forecast error history, it’s probably lying to you. We wrote a detailed piece on why your safety stock formula might be doing exactly that.

Inventory data, specifically the variance between forecasted and actual demand at the SKU level, is the correct input for calibrating safety stock. This is another concrete way inventory data improves the forecasting and planning system as a whole.

Data Cleansing: The Highest-ROI Step

Every practitioner source lands on the same conclusion: fix the data before touching the model. Forecasting problems are usually not math problems. They’re data problems: missing history, late updates, and no context around what happened in the market.

According to McKinsey, AI-driven forecasting can reduce forecast errors by 20 to 50 percent. But those gains depend entirely on data quality. Projects that fail almost always fail at the data quality layer or the absence of a retraining pipeline.

Here’s a step-by-step approach to cleaning your sales and inventory data for forecasting.

Step 1: Flag and Investigate Outliers

Not all demand is created equal. A sudden sales spike could be a promotion, a one-time bulk order, or a data entry error. Precise labeling of data, noting which sales were influenced by promotions or one-time events, prevents anomalies from skewing forecasts.

Before removing any data point, investigate it. Practitioners on LinkedIn emphasize that communicating the data process and assumptions to stakeholders builds the transparency needed for cross-functional trust in the forecast.

Step 2: Correct Sales History for Stockout Periods

This is the single most valuable cleansing step for most companies. Research on retail SKU-level forecasting specifically calls out the need for data cleansing procedures to correct sales observations during out-of-stock days, as well as discrepancies between logical and physical inventory counts.

The approach: identify periods where on-hand inventory was at or near zero and sales dropped correspondingly. Replace those sales figures with an estimate of what would have sold based on recent demand rates. This gives your forecast model a more honest picture of true demand. For a walkthrough on how to reduce stockouts and excess inventory simultaneously, that guide covers the operational side.

Step 3: Separate Promotional Lift from Baseline

Promotional demand and baseline demand follow different patterns and need different treatment. If a product sold 500 units during a buy-one-get-one event and 200 units in a normal week, your baseline is closer to 200. Blending them creates a forecast that’s too high during normal periods and too low during promotions.

Separating baseline demand from promotional lift is necessary to prevent historical data from contaminating future predictions. BetterDemand’s promotion monitoring example illustrates what this looks like in practice.

Step 4: Standardize Formats and Fill Gaps

High-quality forecasts hinge on high-quality data. Standardize units of measure, time buckets, and location codes across your data sources. Then look for gaps. Missing values can be filled using interpolation (estimating between known points), extrapolation (extending a trend), or regression methods that use correlated variables to estimate the missing data.

Common Cleansing Pitfalls

• Treating a promotional spike as the new baseline demand level
• Ignoring product returns, which inflate sales figures
• Using aggregate data when SKU-level patterns differ significantly
• Cleaning data once and never revisiting it as new history accumulates

Key Accuracy Metrics: How to Know If Your Forecast Is Improving

You can’t improve what you don’t measure. Here are the metrics that matter when learning how to use sales and inventory data to improve demand forecasts.

MAPE (Mean Absolute Percentage Error)

The most common forecast accuracy metric. It calculates the average absolute error as a percentage of actual demand.

MAPE = (1/n) × Σ |Actual - Forecast| / Actual × 100

APQC reports a median average monthly demand forecast accuracy of 85% (which implies a 15% MAPE) across over 1,000 organizations. CPG companies typically see 80 to 90% accuracy for hero SKUs, 70 to 85% for core products, and 60 to 75% for long-tail items.

MAPE’s weakness: it blows up when actual demand is near zero, making it unreliable for slow-moving items.

MAE (Mean Absolute Error)

The average size of your errors over a period, regardless of whether you over- or under-forecasted. Unlike MAPE, MAE doesn’t divide by actuals, so it works for low-volume SKUs.

MAE = (1/n) × Σ |Actual - Forecast|

Forecast Bias

Forecast error summarizes the size of your misses. Forecast bias shows whether the process repeatedly predicts too much (positive bias) or too little (negative bias). A forecast can have acceptable MAPE but terrible bias, consistently running 10% high every month while occasionally being 10% low. Over time that bias compounds into excess inventory or chronic stockouts. For a deeper exploration of how aggregate bias masks SKU-level problems, see the piece on the aggregate bias trap.

Tracking Signal

The Tracking Signal monitors bias over time. It calculates cumulative error and flags when the forecast is consistently deviating in one direction beyond an acceptable threshold. A triggered tracking signal is a clear alert that the forecasting model may no longer be valid and requires re-evaluation.

Forecast Value Add (FVA)

This is the process audit metric that most teams skip entirely, and it might be the most important one. FVA measures whether each step in your forecasting process (statistical model, planner adjustments, management overrides) is making the forecast better or worse.

Consultants and practitioners commonly use FVA to streamline forecasting processes, reduce unproductive overrides, and focus scarce planner time on segments where human judgment demonstrably adds value. If a planner’s overrides consistently reduce accuracy, that’s negative FVA, and those overrides should stop.

Traditional metrics like MAPE tell you how big the error is. FVA tells you whether your process is helping or hurting. For more on this, read why forecast accuracy is a process problem, not just a math one.

The 80/20 Insight: Not All Accuracy Improvements Matter

A simulation study across more than 32,000 time series found that 80% of forecast accuracy improvements had zero economic impact. The gains showed up in metrics but not in decisions.

This finding argues strongly for segmenting your SKU portfolio and focusing improvement efforts on high-volume, long-lead-time, or high-margin items where a better forecast actually changes what you buy and when. Chasing blanket accuracy across every SKU is a waste of planner time. Improving forecast accuracy by just 1% on the right items could mean a 2 to 4% improvement in profit. For more detail on the financial impact, our whitepaper on the cost of forecast error quantifies the downstream effects.

Connecting the Data Pipeline to Decisions

A forecast that doesn’t drive action is just a number on a screen. The value of using sales and inventory data in forecasting comes from the decisions it enables downstream.

The Decision Chain

The logic flows like this: Demand Forecast → Safety Stock Calculation → Reorder Point → Purchase Order. Each step depends on the one before it. If the forecast is biased high, safety stock inflates, reorder points trigger too early, and you over-buy. If the forecast is biased low, the opposite happens, and you run out of product.

S&OP as the Operating Rhythm

The Sales and Operations Planning (S&OP) process is where a forecast number becomes a business decision. In a well-run S&OP cycle, cross-functional teams review forecast performance, adjust assumptions for known events (promotions, new product launches, seasonal shifts), and align on a single plan of record. If you haven’t built this process yet, our S&OP guide with 5 steps and common pitfalls is a practical starting point.

Multi-Horizon Logic

Different decisions need different forecast horizons:

• Short-term (1 to 4 weeks): Drives replenishment and daily order decisions. Needs SKU-location granularity.
• Medium-term (1 to 6 months): Feeds S&OP, capacity planning, and promotional planning. Needs product-family and channel-level views.
• Long-term (6 to 18 months): Supports capital investment, contract negotiations, and network design. Needs category and business-unit aggregation.

Each horizon uses the same underlying sales and inventory data but at different levels of aggregation and with different update frequencies.

Model Drift: Why Continuous Updating Matters

A demand forecasting model trained in January 2024 learned the relationships between variables and demand as they existed from 2021 to 2023. By January 2025, those relationships have changed: a new competitor entered the market, consumer preferences shifted, a supply chain disruption altered availability patterns. The model doesn’t know this. It keeps producing predictions based on old relationships, and its accuracy degrades silently.

This is model drift, and it’s why using sales and inventory data to improve demand forecasts isn’t a one-time project. It’s a continuous loop. Fresh data must flow into the model regularly, and the model’s assumptions need periodic re-evaluation. For companies running forecasts through their ERP, our playbook on operationalizing forecasts into ERP systems covers the integration side.

Common Mistakes That Break the Pipeline

Knowing how to use sales and inventory data to improve demand forecasts also means knowing what not to do. These are the mistakes that show up again and again.

Forecasting on constrained data without correction. If your sales were capped by stockouts, promotions, or allocation limits, and you forecast on that raw data, you’re guaranteeing the same problems repeat. Always estimate unconstrained demand.

Ignoring promotional contamination in the baseline. Blending promo-driven sales into your baseline inflates future expectations for normal periods. Label promotional events in your history and treat that demand separately.

Treating all SKUs the same. Not every SKU deserves the same forecasting effort. Segment by volume, margin, lead time, and demand variability. Put your best data and most planner attention on the items where errors cost the most. Our article on common forecasting mistakes covers five of the most frequent ones in detail.

Siloed data between teams. When sales, inventory, promotions, and supplier data live in different systems, forecasts miss critical context. A 2024 industry survey found that 29% of firms cited data silos and incompatible IT infrastructure as a major barrier to deploying analytics tools. One system of record, or at minimum a consistent data pipeline feeding the forecast, is essential.

Manual overrides that make forecasts worse. This is where FVA becomes essential. Many organizations allow sales leaders or executives to override statistical forecasts based on gut feel. Sometimes that adds value. Often it doesn’t. Measure it. If overrides consistently reduce accuracy, restrict them.

Falling into the just-in-case inventory trap. When forecasts aren’t trusted, teams compensate by holding extra stock everywhere. That ties up working capital without actually improving service levels. The better path is to fix the forecast, not pile on buffer stock.

Getting Started: Practical Steps for Mid-Market Teams

If you’re a mid-market company with $10M to $500M in revenue, you probably don’t have a team of data scientists. You might have one or two planners, an ERP system with decent data, and a set of spreadsheets doing most of the heavy lifting. Here’s how to start using sales and inventory data to improve demand forecasts with the resources you have.

Step 1: Audit data completeness. Pull your sales history (by SKU, by location if relevant, by week). Then pull inventory snapshots for the same period. Do you also have lead times by supplier? A promotional calendar? These are the four data sets you need. If any are missing, that’s your first gap to close.

Step 2: Establish a data cleansing routine. Don’t make this a one-time event. Set a monthly cadence to review new data for outliers, stockout periods, and promotional flags. Document your assumptions so the next person who touches the data understands the logic.

Step 3: Choose the right granularity. For most mid-market companies, SKU-location-week is the right level for operational forecasting. Go more granular than that and noise overwhelms signal. Go less granular and you can’t drive replenishment decisions.

Step 4: Build a forecast-to-actual review cadence. At minimum, once a month, compare what you forecasted to what actually happened. Calculate MAPE and bias by SKU category. Look for patterns: Are you consistently over-forecasting seasonal items? Under-forecasting new products?

Step 5: Introduce FVA to measure process improvement. Start simple. Compare the accuracy of your statistical baseline forecast to the accuracy after planner adjustments. If adjustments aren’t adding value, stop making them and redirect that planner time to data quality work.

Companies managing higher SKU complexity, multiple channels, or volatile demand patterns often reach a point where spreadsheets break down. That’s when purpose-built forecasting and advisory support starts paying for itself.

Explore BetterDemand’s pricing to see what a subscription-based forecasting solution costs for mid-market companies.

---

Frequently Asked Questions

What’s the difference between sales data and demand data?

Sales data reflects what you actually sold, constrained by what you had available. Demand data represents what customers wanted, including lost sales from stockouts or allocation limits. Forecasting on sales data alone risks locking in future shortfalls because past supply constraints get treated as demand reality.

How does inventory data improve a demand forecast?

Inventory data provides the context sales data lacks. When you pair on-hand inventory levels with sales figures, you can distinguish between periods of genuinely low demand and periods where demand existed but product wasn’t available. This correction, called unconstrained demand estimation, prevents your forecast from treating stockout-driven zeros as real demand drops.

How much sales history do I need to start forecasting?

Two to three years is the typical recommendation, which gives most statistical models enough data to capture seasonal patterns and trends. If you’re in a fast-changing market or launching new products, shorter history combined with analogous product data or market inputs can work, but accuracy will be lower initially.

What is Forecast Value Add (FVA) and why does it matter?

FVA measures whether each step in your forecasting process is making the forecast better or worse. It compares the accuracy of a baseline statistical forecast to the accuracy after human adjustments. If planner overrides consistently reduce accuracy, that’s negative FVA, and those overrides should be reconsidered or eliminated.

Which accuracy metric should I use, MAPE or MAE?

MAPE is the industry standard and works well for medium- to high-volume SKUs. It breaks down when actual demand is near zero, which is common for long-tail or intermittent-demand items. In those cases, MAE provides a more stable measure. Many teams use both: MAPE for reporting to leadership, MAE for operational tuning.

How often should I update my demand forecast?

At minimum, monthly, to align with S&OP cadence. Companies with shorter lead times or more volatile demand benefit from weekly forecast refreshes. The key is avoiding model drift, where the relationships your model learned from old data no longer reflect current market conditions. Fresh data input and periodic model re-evaluation are essential.

Do mid-market companies really need AI for demand forecasting?

Not necessarily, at least not as a starting point. Only 23% of SMBs have invested in AI, and the biggest forecasting gains typically come from fixing data quality and establishing a consistent process. That said, McKinsey research shows AI-based forecasting can improve accuracy by 10 to 20%, translating to revenue increases of 2 to 3%. The right question isn’t “Do I need AI?” but “Is my data clean enough for any model to work well?”

What’s the biggest mistake mid-market companies make with demand forecasting?

Treating the forecast as a one-time calculation rather than a continuous feedback loop. Companies build a forecast, use it for a quarter, and wonder why accuracy degrades. The fix is connecting sales data, inventory data, and forecast output into a closed loop with regular reviews, cleansing updates, and model recalibration.