Every production order is a bet on future demand. Order 500 units of a product that sells 200 and you've buried cash in a shelf; order 200 of a product that sells 500 and you've handed revenue to a competitor. The demand forecasting methods ecommerce brands actually use range from "assume next month looks like last month" to machine-learning models — and the honest news is that the simple end of that range gets you most of the value. This guide works through each method with real numbers, then tells you plainly which one your brand needs.
Key takeaways
- Four core methods cover 95% of D2C needs: naive, moving average, weighted moving average, and exponential smoothing.
- Each step up in complexity buys responsiveness to trends — and costs setup effort. The jump from "nothing" to "moving average" is the biggest win.
- No method survives bad input data: correct for stockout days before you average anything.
- Seasonality is a multiplier on top of any method, not a separate method — build an index from last year's peaks.
- AI earns its keep in automation (daily recalculation, stockout correction, lead-time alerts), not in magic accuracy claims.
Method 1: The naive forecast
The simplest possible forecast: next period equals last period. Sold 240 units in June? Plan for 240 in July.
It sounds too dumb to dignify with a name, but it's the benchmark every other method must beat — and for stable, mature products it's surprisingly hard to beat by much. Its weakness is obvious: it learns nothing from trend or noise. One viral week and you'll massively over-order; one quiet week and you'll starve a healthy product.
Method 2: The moving average
Instead of trusting one period, average the last few. A 3-month moving average smooths out the noise a single lucky or unlucky month introduces:
This is the workhorse of small-brand forecasting, and it's what we recommend most brands start with — a 30-day window per variant, refreshed weekly. The catch is visible in the example: sales are clearly climbing (180 → 210 → 240), yet the forecast says 210, below the most recent month. Moving averages always lag a trend, because they treat three-month-old data as equal to last week's.
Method 3: The weighted moving average
The fix for that lag: keep averaging, but let recent months count for more. A common weighting for three periods is 50/30/20, newest first:
Same data, better answer: 219 versus 210, because the upward trend gets partial credit. The cost is a judgment call — those weights are yours to choose and defend. Too aggressive (say 70/20/10) and you're back to chasing every spike; too flat and you've rebuilt the plain average with extra steps.
Method 4: Exponential smoothing
Exponential smoothing takes the weighting idea to its logical end: every past period matters, with influence that decays smoothly. In practice you only need one line of arithmetic, controlled by a smoothing factor α between 0 and 1:
High α (0.4-0.5) reacts fast and suits volatile products; low α (0.1-0.2) stays calm and suits steady sellers. It's the most accuracy per unit of effort of any classical method — but tuning α per SKU is real work, and it's the point where most founders' spreadsheets start to creak.
Seasonality: the multiplier on everything
None of the four methods above knows that October isn't a normal month. If you sell in India, Diwali and the wedding season can multiply demand 2-4× for weeks; selling globally adds Black Friday–Cyber Monday, Christmas, and category-specific peaks like summer for beverages or winter for knitwear.
The practical fix is a seasonal index: divide last year's peak-period sales by your baseline to get an uplift factor, then multiply this year's forecast by it. If last October did 620 units against a 280-unit baseline month, your index is 2.2 — so a current velocity forecast of 300 becomes a peak plan of 660. Build the index per category rather than per SKU if your history is thin: kurtas as a group have a more stable Diwali pattern than any single colourway does. Two cautions: you need at least one full cycle of history to build the index, and you must order early. Lead times stretch precisely when every brand hits the same suppliers at once, which is why peak planning starts 6-8 weeks out — with safety stock raised on bestsellers before, not during, the climb.
Keeping score: was the forecast any good?
Whichever method you pick, close the loop. Each month, compare forecast to actual per SKU and note the miss as a percentage. A moving average that's consistently 25% low on one product isn't noise — it's a trend the method is lagging, and your cue to switch that SKU to a weighted average or raise its α. Brands that track forecast error for even one quarter develop something more valuable than a better model: a calibrated sense of which of their products are predictable (reorder on autopilot) and which are wild (order small, review weekly). Precision belongs on the predictable ones.
Demand forecasting methods for e-commerce, compared
| Method | Complexity | Accuracy | Best for |
|---|---|---|---|
| Naive | None | Baseline only | Stable products; sanity-checking other methods |
| Moving average | Low | Good for steady demand | Most D2C brands' first real forecast |
| Weighted moving average | Low-medium | Better on trends | Products clearly growing or declining |
| Exponential smoothing | Medium | Best of the classics | Larger catalogues with mixed volatility |
| AI / ML forecasting | Handled by software | Strongest with messy, per-variant data | Brands past ~30 SKUs who want it automated |
Why D2C brands should start simple
There's a temptation to skip straight to the sophisticated end. Resist it, for three reasons. First, your data is small: with 18 months of history on 40 SKUs, a well-kept moving average captures most of the signal that exists. Second, garbage in beats method choice: an exponential smoothing model fed averages that include stockout days will lose to a plain moving average fed clean data. If a SKU sold 80 units in a month but was dark for 10 of 30 days, its real velocity is 4 a day, not 2.7 — we walk through this trap in detail in our Shopify inventory forecasting guide. Third, simple methods teach you your business: computing the numbers yourself for a quarter builds the intuition to know when any forecast — human or machine — smells wrong.
The forecast is also only half the decision. Converting it into an order requires your reorder point and lead times — the mechanics are in our reorder point guide.
Where AI genuinely helps
So is AI forecasting marketing fluff? Not if you look at where it actually wins. It's not clairvoyance about demand — nothing predicts a reel going viral. It's relentless, correct arithmetic at a scale no spreadsheet-keeper sustains:
- Stockout correction, always on. Excluding out-of-stock days from every average, for every variant, every day — the single correction humans most often skip.
- Per-variant velocity. Your M sells at three times the rate of your XL. A model that tracks 200 variants daily catches that; a monthly product-level review never will. This is what Honey Shelf's inventory engine recomputes every day from live sales.
- Lead-time-aware alerts. The useful alert isn't "stock is low" — it's "days remaining just crossed this supplier's lead time plus buffer, order today." That requires joining forecasts to supplier data automatically.
- Answers on demand. Asking "what should I produce this month?" in plain English and getting a demand-backed answer — the job of Honey Shelf's AI Copilot — replaces an afternoon of pivot tables.
In other words: AI's edge is doing the simple things perfectly, daily, on every SKU, and turning the result into a drafted production order instead of a cell in a sheet.
The bottom line
Start with a stockout-corrected 30-day moving average per variant this week. Add a seasonal index before your next peak. Graduate to smoothing — or to software that handles all of it — when the spreadsheet becomes the bottleneck. Forecasting isn't about predicting the future perfectly; it's about being systematically less wrong than guessing, month after month.