How to Build a Multi-Horizon Demand Forecast for Mid-Market

TL;DR

A multi-horizon demand forecast predicts demand across multiple time windows simultaneously, from days out to years, so that different business decisions get the right signal at the right granularity. Mid-market companies ($50M to $500M) typically struggle with this because they’re stuck between spreadsheets that can’t scale and enterprise suites that cost too much and take too long to implement. This guide walks through the practical steps to build a multi-horizon forecast with the constraints of lean teams, limited budgets, and imperfect data.

What Is a Multi-Horizon Demand Forecast?

A multi-horizon demand forecast predicts values at multiple future time points simultaneously. Instead of producing a single monthly number that purchasing, production, and finance all try to use, it generates separate but coherent views across short, medium, and long planning windows in a single model pass.

This matters because a model optimized for one specific lookahead performs poorly at other horizons. The error patterns at a 1-week horizon are fundamentally different from those at a 6-month horizon. Training separate models per horizon is expensive and creates inconsistencies, where the weekly forecasts might not add up to the monthly forecast, and the monthly forecast might contradict the annual plan.

For mid-market companies, the pain is specific. Most run a single flat forecast, usually monthly buckets in a spreadsheet, that tries to serve purchasing, production, and S&OP simultaneously. The purchasing manager needs SKU-level weekly signals over the next 12 weeks. The VP of Operations needs category-level monthly views for the next 18 months. The CEO wants annual revenue visibility for three years. One spreadsheet cannot serve all three without forcing compromises that make it useless for at least two of them.

Multi-horizon models solve this by producing temporally consistent forecasts across all horizons. The weekly numbers roll up cleanly into monthly, and the monthly into annual, because they share a common underlying model structure.

See a live multi-horizon forecast built on actual sales and inventory data to understand how this works in practice.

The Three Forecast Horizons, Defined

Building a multi-horizon demand forecast for mid-market companies starts with understanding what each horizon actually covers, which decisions it serves, and what accuracy you can realistically expect.

Short-Term (Operational): Days to 13 Weeks

Short-term forecasts drive the decisions that happen today and this week: replenishment orders, warehouse labor scheduling, production sequencing, and purchase orders against existing contracts. The granularity is typically SKU-location-week, sometimes SKU-location-day for high-velocity items.

Short-term forecasts are the most accurate because they rely on recent data and are less affected by unexpected changes. This is where demand sensing adds the most value, updating predictions daily as orders, POS data, and shipment signals flow in. Benchmark studies show demand sensing cuts error by 30% for new items within the first two weeks of launch.

Accuracy expectations: 5% to 15% MAPE for stable, high-volume SKUs. 15% to 25% for moderate-volume items. For the long tail, you’re managing uncertainty, not predicting precisely.

Medium-Term (Tactical): 3 to 18 Months

This is the S&OP sweet spot. Medium-term forecasts inform production planning, inventory positioning, sales planning, cash budgeting, and supplier capacity commitments. The typical granularity is SKU-family by month.

S&OP focuses on medium to long-term planning horizons of 3 to 24 months, while S&OE (Sales and Operations Execution) concentrates on short-term execution within the 0 to 3 month window. Most mid-market companies conflate these two, which causes the S&OP meeting to devolve into firefighting about this week’s stockouts rather than discussing next quarter’s inventory strategy.

Medium-term forecasts blend statistical models with qualitative judgment. Promotional lifts, new product introductions, and channel shifts all get layered onto the statistical baseline. This is also where working capital hides in inventory, because poor medium-term forecasts create both excess stock and stockouts simultaneously.

Accuracy expectations: 15% to 25% MAPE for CPG and food and beverage. Higher for fashion, electronics, or anything with short product lifecycles.

Long-Term (Strategic): 1 to 5+ Years

Long-term forecasts involve purely strategic decisions: network design, major capital expenditure, new market entry, M&A evaluation, and long-range capacity planning. Granularity drops to category-level or business-unit-level on an annual basis.

Nobody should expect precision here. The goal is directional correctness and scenario evaluation. You’re not trying to forecast exact unit volumes three years out. You’re asking: if demand grows 8% annually versus 15%, does the current warehouse footprint hold? Does the existing supplier base have capacity?

Accuracy expectations: Set them in ranges, not point estimates. A long-term forecast that narrows the strategic decision space is doing its job, even if the MAPE would make a short-term planner cringe.

Decision-Horizon Mapping Table

This table is worth bookmarking. It’s the framework for deciding what to forecast, at what granularity, and with what method.

Decision	Horizon	Granularity	Primary Method
Replenishment and purchasing	1 to 13 weeks	SKU-location-week	Statistical base + demand sensing
S&OP and inventory positioning	3 to 18 months	SKU-family-month	Hybrid statistical + judgment overlays
Strategic and CapEx planning	1 to 5 years	Category-annual	Scenario-based + qualitative

The principle is straightforward: different horizons serve different decisions. Short-horizon, high-accuracy forecasts drive operational decisions. Long-horizon, lower-accuracy forecasts drive strategic ones. Problems start when companies try to use one forecast for everything.

Why Mid-Market Companies Struggle with Multi-Horizon Forecasting

The concept of multi-horizon forecasting is not complicated. Building one with mid-market constraints is. Here’s where things break down.

The Spreadsheet Ceiling

The typical mid-market company hits the spreadsheet ceiling at around 500 to 2,000 active SKUs across multiple channels. Below that threshold, a well-maintained Excel model can limp along. Above it, formulas break, version control disappears, and the person who built the master spreadsheet becomes a single point of failure.

Practitioners on Reddit’s r/supplychain forums regularly describe this exact problem. One thread on demand planning software for mid-market companies revealed a common pattern: the planner spending 80% of their time maintaining the spreadsheet and 20% actually analyzing demand. That ratio should be inverted.

Spreadsheets also cannot handle the temporal coherence that multi-horizon forecasting requires. When the weekly tab, the monthly tab, and the annual tab are maintained separately (often by different people), contradictions are inevitable.

Native ERP Limitations

NetSuite, SAP Business One, and Microsoft Dynamics all include some forecasting capability. It’s basic. Practitioners on Reddit’s r/Netsuite community frequently discuss the limitations of native demand planning, with many concluding they need external forecasting tools once SKU counts and channel complexity grow.

Native ERP forecasting typically offers simple time-series methods (moving average, exponential smoothing) without the ability to layer in promotional history, demand sensing signals, or scenario planning. It generates a single-horizon output, not a coherent multi-horizon view.

Lean Planning Teams

A company doing $100M in revenue might have one demand planner. Maybe two. These people are responsible for purchasing, inventory management, supplier relationships, and “the forecast,” which usually means updating last month’s spreadsheet. There’s no capacity to build and maintain separate models for three horizons. This is why many mid-market AI forecasting pilots stall before delivering value.

The Software Gap

Mid-market companies face a real gap between “too simple” (spreadsheets, native ERP) and “too complex” (enterprise suites that require six-figure investments and 12-plus month implementations). Discussions on Reddit’s r/supplychain about demand planning software selection consistently surface this tension: companies want something more capable than Excel but can’t justify the cost and implementation timeline of platforms designed for $5B+ enterprises.

Most organizations require 6 to 12 months to implement a mature S&OP process, with initial benefits visible within 3 to 4 months. For enterprise software specifically, the timeline can stretch to 18 months before the system is fully operational. Mid-market companies often can’t afford to wait that long for results.

How to Build It, Step by Step

Here’s the practical process for building a multi-horizon demand forecast for mid-market companies. These steps assume you have limited staff, imperfect data, and no appetite for a 12-month implementation.

Step 1: Establish Your Data Foundation

Most models need at least 24 to 36 months of history to properly capture seasonality and year-over-year patterns. Two years is the minimum. Three or more years is ideal, especially if your business has strong seasonal cycles or experienced significant disruptions (like, say, a pandemic that distorted demand patterns for two years).

The data requirements for a clean forecast include historical depth of 12 to 24+ months for seasonality detection, clean POS and order data free from returns duplication and phantom inventory, consistent SKU and channel mappings aligned across all source systems, and complete promotional history.

For mid-market companies, the data challenge is real. Sales data lives in Salesforce, inventory data lives in the ERP, promotional calendars live in someone’s email, and finance data lives in QuickBooks. None of them talk to each other.

Start with what you have. Extract shipment or order history from your ERP. Clean the obvious anomalies: one-time bulk orders that distort seasonality, SKU code changes that split history, and periods of stockout where zero shipments don’t mean zero demand. If your safety stock formula is based on uncleaned historical data, the forecast built on that same data will inherit the same errors.

Step 2: Map Decisions to Horizons

Before selecting any method or tool, document which decisions need which forecast horizon. Use the decision-horizon mapping table from the previous section as a starting template, then customize it for your business.

Common mid-market mappings:

Purchasing with 8-week lead times from Asia: Needs a 13-week SKU-level forecast, updated weekly.

Monthly S&OP meeting: Needs an 18-month SKU-family view, updated monthly.

Annual budgeting and capacity review: Needs a 3-year category-level directional forecast, updated quarterly.

If you can’t articulate which decision each horizon serves, you’ll build a forecast nobody uses.

Step 3: Select Methods per Horizon

The principle is well established: quantitative techniques are effective for short-term accuracy, while qualitative approaches are better suited for long-term planning. Most production forecasts use a quantitative base with a qualitative override.

Short-term: Statistical models (exponential smoothing, ARIMA) form the base. Layer demand sensing on top if you have access to POS or near-real-time order data. ML-enhanced systems show meaningful improvement here, with ML methods reaching 5% to 15% MAPE compared to 10% to 25% for traditional statistical methods in the 1 to 3 month window.

Medium-term: Hybrid approach. Statistical baseline adjusted with structured qualitative input from sales (pipeline visibility), marketing (promotional calendar), and product development (NPI timeline). The key word is “structured.” Unstructured input, where anyone can change any number for any reason, destroys forecast value.

Long-term: Scenario-based planning. Build three to five scenarios around key uncertainty drivers (market growth rate, commodity prices, regulatory changes, channel mix shifts) and model the implications for capacity and capital.

Step 4: Build a Statistical Baseline

Start simple. A seasonal naive model (last year’s demand for the same period, adjusted for trend) is a surprisingly tough baseline to beat for many mid-market product portfolios. It costs nothing to build and gives you a benchmark against which everything else is measured.

From there, add complexity only where it adds value. Try exponential smoothing with seasonal components. If you have the capability, test basic ML approaches on your top 50 to 100 SKUs and compare accuracy against the naive baseline. If the ML model doesn’t meaningfully outperform seasonal naive for a given SKU, stick with the simpler model.

This is where many companies fall into common forecasting mistakes: they adopt complex methods uniformly across the entire SKU portfolio rather than matching model complexity to the predictability of each item.

Step 5: Layer in Demand Shaping Signals

The statistical baseline captures “what would happen if nothing changes.” Real demand is shaped by promotions, new product introductions, price changes, competitor actions, and channel shifts.

For each signal, you need a structured process to capture the expected impact before the event and the actual impact after. This creates the training data for future adjustments. Without it, every promotion is a guess layered on top of a model.

For seasonal SKUs specifically, the interaction between promotional timing and seasonal peaks creates compound forecasting challenges that require dedicated treatment.

Step 6: Connect the Forecast to S&OP

The key challenge is producing a single version of the truth. An organization cannot manage effectively if each function retains its own assumptions. Sales works from a revenue forecast, operations works from a shipment forecast, finance works from a budget, and purchasing works from a consumption plan. They’re all supposed to be the same number expressed differently, but in most mid-market companies, they’re four different numbers maintained by four different people.

S&OP becomes the mechanism for alignment: it transforms multiple views into a single plan of record. This doesn’t mean everyone agrees on one demand number. It means everyone agrees on which demand number the company will plan against, and what the risks are if that number is wrong.

For a mid-market company, a functional S&OP cadence looks like this: monthly cycle, starting with a statistical forecast refresh, followed by demand review (sales and marketing input), supply review (operations and procurement capacity check), and an executive reconciliation meeting where gaps between demand and supply get resolved.

Explore embedded supply chain advisory if your team lacks the bandwidth to build and run this cadence independently.

Step 7: Integrate with Purchasing and Replenishment

A forecast that doesn’t flow into purchasing decisions is a report, not a planning tool. The final step is connecting forecast outputs to your ERP’s replenishment engine so that purchase orders, production orders, and transfer orders reflect the demand signal.

For mid-market companies on NetSuite or SAP Business One, this often means an export/import process rather than real-time API integration. That’s fine as a starting point. What matters is that the forecast is the input to buying decisions, not a parallel document that the buyer glances at before doing what they were going to do anyway.

Key Metrics: How to Know If Your Forecast Is Working

MAPE vs. WMAPE

MAPE (Mean Absolute Percentage Error) is the most common accuracy metric, but it has a well-known flaw: it’s distorted by low-volume SKUs. If you sell 2 units of a SKU and forecast 3, that’s a 50% MAPE on a trivially small error.

WMAPE (Weighted Mean Absolute Percentage Error) solves this by weighting errors proportional to volume. For a mid-market company with a broad SKU portfolio, WMAPE is almost always the better aggregate metric.

Benchmark targets vary by industry: CPG companies generally target 15% to 25% MAPE overall, with hero SKUs hitting 80% to 90% accuracy and long-tail items ranging from 60% to 75%.

Forecast Bias

Bias is the hidden destroyer. A forecast can have acceptable MAPE while being consistently biased, systematically over-forecasting or under-forecasting. Over time, bias creates either excess inventory (over-forecast) or chronic stockouts (under-forecast). The danger is that aggregate-level bias often masks severe SKU-level problems that only show up when you decompose the numbers.

Forecast Value Add (FVA)

FVA is a metric for evaluating the performance of each step and each participant in the forecasting process to determine which one adds value and which one does not. It answers a blunt question: did this person’s adjustment make the forecast better or worse?

Can mid-market companies use FVA? Absolutely. Start small: archive the system forecast and any overrides, compare against a naive baseline over a few months, and adjust override rules based on the results. The method is lightweight and tool-agnostic.

This matters because research across multiple datasets shows that human adjustments often destroy value. In some companies, only 16.5% of SKU-level adjustments actually improved accuracy. The rest either made no difference or made things worse.

Why Stability Matters as Much as Accuracy

This is an insight that experienced planners understand intuitively but rarely see articulated. A slightly less accurate but stable forecast is often more valuable than a highly accurate yet volatile one. Stability reduces last-minute changes, improves capacity planning, and supports cross-functional coordination.

A consistent 75% accuracy you can plan around beats volatile accuracy that swings from 60% to 90% month to month. When the forecast changes dramatically every cycle, purchasing can’t commit to suppliers, production can’t hold a schedule, and nobody trusts the numbers. That trust deficit is the real cost.

Common Mistakes Mid-Market Companies Make

Chasing Aggregate MAPE While SKU-Level Performance Crumbles

A 20% WMAPE across your portfolio sounds reasonable. But if your top 10 revenue SKUs are at 35% MAPE while your slow-movers artificially drag the average down, you have a serious problem disguised by a comfortable number. Always decompose accuracy by SKU tier and review the items that drive 80% of revenue separately.

Overriding the Statistical Forecast Without Tracking Value Add

Everyone wants to add their input. Sales adjusts numbers up because they’re optimistic about a new account. Marketing adjusts numbers up because of an upcoming promotion. Operations adjusts numbers down because they don’t believe the sales team. Without FVA tracking, nobody knows whether these adjustments helped. The evidence suggests gut instinct often costs more than anyone realizes.

Using a Single Horizon for All Decisions

This is the original sin of mid-market forecasting. One monthly forecast cannot simultaneously serve weekly replenishment, monthly S&OP, and annual budgeting. It will be too granular for strategic planning and too aggregated for purchasing. The whole point of building a multi-horizon demand forecast for mid-market companies is to escape this trap.

Not Adjusting Accuracy Expectations as Horizon Lengthens

When the CFO complains that the 18-month forecast was off by 25%, the right response is: that’s actually reasonable for an 18-month horizon. Forecast accuracy degrades as horizon increases. A 1-day forecast might achieve 5% MAPE, a 7-day forecast 15%, and a 30-day forecast 30%. Setting uniform accuracy expectations across all horizons guarantees disappointment.

Measuring Error at a Point Instead of Over Lead Time

What really matters for supply chain decisions is not the error at a specific time but the error over the lead time for the process in question. If your replenishment lead time is 10 weeks, you need to measure cumulative forecast error across that 10-week window, not the error at week 10 in isolation. This distinction changes how you evaluate forecast quality and set safety stock levels.

When to Get Help: Signs You’ve Outgrown DIY Forecasting

There are clear signals that your current approach has hit its limit:

You have stockouts and excess inventory at the same time. This is the classic symptom of a forecast that’s wrong in both directions across different SKUs. You’re buying too much of the wrong things and not enough of the right ones.

S&OP meetings happen without a single plan of record. Everyone brings their own version of the forecast. The meeting becomes a negotiation rather than a decision-making forum.

You spend more time building the forecast than acting on it. If your planner spends 4 days a month maintaining the spreadsheet and 1 day analyzing it, the process is consuming the person instead of informing them.

Accuracy hasn’t improved in 12 months despite effort. You’ve tried new methods, added more data, brought more people into the process, and accuracy is flat. This usually means you’ve exhausted what your current toolset can deliver.

At this point, the options are: build an in-house analytics team (expensive, slow, requires data science talent that mid-market companies struggle to attract), buy an enterprise planning suite (six-figure investment, 12+ month implementation), or work with an advisory and AI model that bundles the forecast with the expertise to operationalize it.

BetterDemand builds a live multi-horizon demand forecast on your actual data and pairs it with dedicated senior supply chain expert hours each month to drive that forecast through purchasing, replenishment, and S&OP, so your team shifts from reactive firefighting to proactive planning.

Frequently Asked Questions

How many months of data do I need to build a multi-horizon demand forecast?

At minimum, 24 months of clean historical data. Ideally 36 months or more, especially if your business has strong seasonality. With less than 24 months, models can’t reliably separate seasonal patterns from one-time events. If you have fewer than 24 months, start with simpler methods (seasonal naive) and add complexity as history accumulates.

Can mid-market companies really do multi-horizon forecasting without enterprise software?

Yes, but there’s a complexity threshold. Below 500 active SKUs with simple channel structure, a well-designed set of spreadsheets with disciplined processes can work. Above that, you need purpose-built tools. The key is that “purpose-built” doesn’t have to mean a $500K enterprise suite. The mid-market software gap is real, and newer solutions are designed specifically for companies in the $10M to $500M range.

What accuracy should I expect from each forecast horizon?

Short-term (1 to 13 weeks): 5% to 15% MAPE for high-volume SKUs, 15% to 25% for moderate volume. Medium-term (3 to 18 months): 15% to 25% MAPE is generally acceptable for CPG. Long-term (1 to 5 years): Don’t measure in MAPE. Measure in scenario accuracy, whether the directional call was right and the range captured reality.

What’s the difference between multi-horizon forecasting and just running three separate forecasts?

Coherence. Three separate forecasts built independently will contradict each other. The weekly forecasts won’t sum to the monthly forecast, and the monthly won’t align with the annual. A true multi-horizon model produces all horizons from a shared structure, ensuring temporal consistency. This means the plan of record is one plan, not three competing ones.

How does Forecast Value Add (FVA) work in practice for small teams?

Archive the unadjusted statistical forecast each cycle. Record every human override with the name of the person and the reason. After three to four months, compare the adjusted forecast accuracy against the unadjusted baseline. You’ll quickly see which adjustments (and which adjusters) actually improve things. Most companies discover that the majority of manual overrides add no value or make things worse.

Should I prioritize forecast accuracy or forecast stability?

For operational planning, prioritize stability. A forecast that’s consistently 78% accurate is more useful than one that swings between 65% and 92% because stable numbers let purchasing commit to suppliers, production hold schedules, and finance trust the budget. For strategic planning, prioritize being directionally correct within a defined range.

How long does it take to implement a multi-horizon forecasting process?

If you’re starting from spreadsheets and building toward a structured S&OP cadence with multi-horizon views, expect 3 to 4 months before you see initial benefits and 6 to 12 months to reach process maturity. The timeline depends heavily on data readiness, team capacity, and whether you’re building internally or working with an external partner. Companies that try to implement enterprise software and process change simultaneously tend to take longer.

What’s the biggest mistake mid-market companies make when starting multi-horizon forecasting?

Trying to boil the ocean. They attempt to forecast every SKU at every horizon with maximum sophistication from day one. The better approach is to start with your top 50 to 100 SKUs by revenue, build a statistical baseline, prove value with FVA measurement, and expand from there. Complexity should be earned by demonstrated improvement, not assumed as a requirement.