The cost of guessing
Order too much and cash is tied up in stock that may need discounting. Order too little and customers find empty shelves or sold-out product pages. Many small retailers buy based on last year’s numbers and instinct, which works until trends, promotions or supply delays change the picture.
Forecasting replaces some of the guesswork with numbers you can test.
What data you need
| Data | Why it matters |
|---|---|
| Sales history by product and date | The basis for patterns and seasonality |
| Stock levels over time | Shows when sales were lost to stockouts, not low demand |
| Promotions and price changes | Explains spikes and dips |
| Lead times from suppliers | Determines how far ahead you must forecast |
| Product attributes and launch dates | Helps with new products that have no history |
| Events and holidays | Known demand drivers |
At least a year, and ideally two or more, of reliable history is needed to learn seasonality. Clean data matters more than clever models.
Start simple
Before using machine learning, try methods that a spreadsheet or inventory system can handle:
- Moving averages: average sales over recent weeks.
- Seasonal adjustment: compare this period with the same period last year, scaled for recent growth.
- Safety stock: extra inventory to cover variability and supplier delays.
- ABC classification: spend most effort on the products that drive most revenue.
Simple methods often perform surprisingly well for stable products.
When machine learning helps
Machine learning can add value when you have many products, complex seasonality, frequent promotions or several sales channels. Models can consider price, promotions, weather, events and related products together. They do not predict the future from nothing; they learn from your history, so poor data limits them.
For small catalogs, a good simple method may beat a poorly set up model. Compare them on your own data.
Measuring forecast accuracy
Choose a measure and track it:
- Weighted absolute percentage error and similar measures compare forecast with actual sales across products.
- Bias shows whether you consistently over- or under-forecast.
- Service level measures how often you had stock when customers wanted it.
Test any method by forecasting a past period you already know, and see how close it would have been.
From forecast to order
A forecast is only useful if it changes ordering decisions.
- Forecast demand over the supplier lead time plus the review period.
- Subtract current stock and incoming orders.
- Add safety stock for variability.
- Round to pack sizes and minimum order quantities.
- Review the suggestion before placing the order.
Handling new products and promotions
New products have no history. Use similar products as a guide, start with cautious quantities and update quickly with early sales. For promotions, record the dates and discount level so future forecasts can learn the effect.
Common mistakes
- Treating stockout periods as low demand.
- Ignoring supplier lead time variability.
- Forecasting every item the same way.
- Not reviewing accuracy regularly.
- Trusting a model without checking its output against common sense.
FAQ
What is demand forecasting?
It is predicting future sales of each product so you can order the right quantities at the right time. Methods range from simple averages to machine learning models that learn from historical data.
Do small retailers need AI for forecasting?
Not always. Simple seasonal methods work for many stable catalogs. AI becomes useful with many products, strong seasonality, frequent promotions or several channels, and with enough clean history.
How much sales history do I need?
At least a year is needed to see seasonality, and two or more is better. Newer businesses can start with simple methods and improve as history grows.
How do I know whether my forecast is any good?
Compare forecasts with actual sales for periods you have already completed, track error and bias, and watch service level. Improve the method if it consistently misses.
Sources and further guidance
Platform features and requirements change. Check the linked primary documentation for your implementation.
TURN INSIGHT INTO ACTION
Let’s talk about your next step.
Share your workflow, your current systems and what you want to improve. We’ll help shape a practical way forward.
Discuss your project ↗