The problem forecasting tries to solve
Every independent retailer faces a version of the same tension. Order too little and popular items run out, so customers leave without buying. Order too much and money sits on shelves as unsold goods, taking up space and sometimes going out of date or out of season. Forecasting is the practice of using what you know, mainly past sales, to make a better-informed guess about what you will need.
It will not remove uncertainty. A forecast is an estimate, and its value lies in being more informed than a gut feeling, not in being right every time.
What a forecast needs
A forecast is only as good as the records behind it. At minimum you need:
- Sales by item and date. Daily or weekly totals for each product, or for product groups if you carry many small items.
- Stock-outs. If an item was unavailable for part of a period, sales were lower than demand. Without this note, the forecast will underestimate the item.
- Lead time. How long it takes from placing an order to having stock on the shelf.
- Context. Promotions, holidays, local events and price changes, which can distort the numbers.
Clean records matter more than clever software. If your point-of-sale system lumps items together or your counts are often wrong, start by fixing that. Poor input can make a sophisticated tool give a polished but unreliable answer.
A simple method you can do by hand
You do not need a machine learning system to begin. Consider a hypothetical product that sold 12, 15, 11 and 14 units over the last four weeks.
- Add the weekly sales: 12 + 15 + 11 + 14 = 52 units.
- Divide by four weeks: 52 / 4 = 13 units per week on average.
- Suppose the supplier takes two weeks to deliver. Expected demand during the lead time is 13 x 2 = 26 units.
- Add a cushion, often called safety stock, because demand varies. The weekly numbers ranged from 11 to 15, so you might decide to hold an extra 6 units. That would mean reordering when stock falls to 26 + 6 = 32 units.
These numbers are hypothetical, and the cushion is a judgment call. A larger cushion lowers the chance of a stock-out but ties up more money. For items that are expensive, perishable or hard to store, you may prefer a smaller cushion; for items that customers would not wait for, a larger one.
This kind of average works reasonably for steady sellers. It works poorly for items with strong seasonal swings, new products with little history, or one-off items.
Where AI and machine learning add value
Software that uses machine learning can handle patterns that are hard to compute by hand:
- Seasonality. Many products sell more at certain times of year or on certain days of the week. A model can learn these cycles from a few years of data, though it needs enough history to do so. With less than a full cycle, it cannot know what happens next season.
- Trends. Rising or falling interest in an item.
- Effects of promotions and holidays. If these are recorded, a model can estimate their usual impact.
- Many items at once. Tools can produce a forecast for hundreds of products and flag those where stock looks low or high.
Some tools also incorporate outside signals such as weather or local events. These can help, but they add complexity, and the benefit for a small shop is often modest. For a broader treatment of how these methods work for small producers, see material on demand forecasting.
If you are shopping for a tool, ask how it handles new products, how it treats stock-outs, whether you can see why it suggests a quantity, and whether you can override it. A forecast you cannot question is hard to trust. Vendor questions of this kind are a useful checklist for any software purchase.
Handling products with little history
New items, one-off buys and fashion-driven goods do not have a past to learn from. Options include:
- using sales of a similar product as a starting point;
- ordering a small first batch and reordering quickly if it sells;
- asking suppliers about minimum quantities and how fast they can restock;
- accepting that some items will be guesses, and keeping them a small part of your spending.
Common pitfalls
- Treating sales as demand. If you ran out on Tuesday, Wednesday’s zero sales do not mean nobody wanted the item.
- Ignoring one-off events. A large order from a single customer or a viral mention can inflate history. Mark these so they do not mislead the next forecast.
- Over-ordering because of fear. Setting every cushion high leads to excess inventory and cash problems.
- Forgetting returns and shrinkage. Stock you think you have may be damaged, lost or stolen.
- Not reviewing. Compare forecasts with actual sales every month or so. If errors are large for particular items, find out why.
Keeping a person in charge
The shop owner knows things the data does not: that a nearby road will be closed for a month, that a supplier has been unreliable, or that a local team is in a playoff run. Treat tool suggestions as a draft order that you review before it goes out, much like any human review step.
For a small shop, a spreadsheet with weekly sales and a simple average may be enough for a long time. Move to specialist software if you have many products, several locations or enough history to learn from. Run it alongside your usual method for a few cycles and compare the results before relying on it. Whatever you choose, outcomes will vary with your product mix and data quality, and savings are not guaranteed.
Related uses include keeping an eye on low-stock alerts for an online shop, which is a related but separate topic from forecasting.