Industries/ Wholesale/ Demand forecasts and reorder alerts
Know what to reorder from each supplier before the line runs short
Forecasts for each product line, built from your own sales and tested against your own history, with seasonality, promotions and supplier lead times included. Buyers see suggested reorder quantities as a range, and an alert arrives when a line starts selling faster or slower than the forecast said.

- Used by
- Buyers, purchasing managers and the commercial director
- Takes the place of
- Last year's figures, gut feel and min and max levels nobody revisits
- Connects to
- Your ERP sales history, stock, purchase orders and promotions
- Built with
- Our forecasting & alerts service
Where it hurts today
A normal week, before it exists
Buying usually starts with last year. A buyer pulls last year's sales out of the ERP into a spreadsheet, adds a bit for growth and places the order. The spreadsheet doesn't know that last July had a heatwave, that a promotion lifted one line for three weeks, or that a supplier's lead time has quietly grown from one week to three.
The result is cash sitting in slow lines while fast ones run out and customers buy them elsewhere. A short line means substitutions, part deliveries and a phone call from an unhappy account. Each buyer looks after hundreds of lines and can't watch them all closely, so attention goes to the lines that shout, usually after the stock-out has already happened.
The ERP has reorder points, but they were set as fixed numbers years ago and rarely revisited. They trigger too early on lines that have slowed and too late on lines that are growing, so buyers learn to ignore them. The knowledge that would fix this is in your own sales history. It just needs reading properly, line by line, every week.
What it does
Demand forecasts and reorder alerts, feature by feature
Forecasts a buyer can check for themselves, and alerts that only arrive when something is worth acting on.
- 01
Product-level demand forecasts, as ranges
Each product line gets a weekly forecast shown as a likely range, not a single number. A buyer sees that next month's demand is probably between two figures, how confident the forecast is, and which weeks of history it was built from.
- 02
Seasonality and promotions built in
Weekly rhythm, seasonal peaks, bank holidays and your own promotion calendar are modelled explicitly. A promotion planned for next month lifts that line's forecast ahead of time, and last year's one-off spike from a single bulk order does not inflate this year's.
- 03
Suggested order quantities by supplier
Suggestions take account of supplier lead times, minimum order quantities, pallet and layer multiples, and stock already on order. The buyer sees a suggested order per supplier, ready to adjust and raise as a purchase order in the ERP.
- 04
Reorder alerts when demand shifts
When actual sales move outside the forecast range for long enough to matter, the buyer who owns that line gets an alert with the chart, any likely cause the data shows, such as one new account taking large volumes, and the next purchase order it affects.
- 05
Backtested against your own history
Before you rely on a forecast, it is run against past months where the answer is already known, and you see how far off it was, line by line. Where it does no better than your current method on a line, that line stays on simple rules.
- 06
Slow-moving and dead stock flagged
Lines with more weeks of cover than they need, and lines that have stopped selling, are listed by the stock value tied up in them, so the buyer can stop reordering, put the line into a promotion or talk to the supplier while there is still time.
A day with it
How the day runs instead
A normal week for a buying team with forecasts and alerts running.
- Monday, 6amThe planner
Overnight, last week's sales are read from the ERP and every forecast is refreshed. Suggested reorders are grouped by supplier, using current stock, open purchase orders, and each supplier's lead time and minimum order.
- Monday, 9amBuyer
Opens the reorder list for this week's supplier orders. For a paper goods supplier, the suggestion is higher than usual because a large account's promotion starts in three weeks. The buyer rounds up to a full pallet and raises the purchase order in the ERP.
- WednesdayBuyer
An alert arrives: barbecue charcoal has sold above its forecast range for two weeks running, mostly to one new account. The buyer checks the supplier's lead time, brings the next order forward and lets the account's rep know.
- ThursdayPurchasing manager
Reviews the slow stock list. A seasonal line has far more cover than it needs, so the manager cancels a repeat order still open with the supplier and asks for the line to go into next month's trade promotion.
- Month endCommercial director
Looks at forecast accuracy by category beside stock-outs and stock value. One category's forecasts are drifting, and it is flagged for review. The buying meeting discusses it with the numbers in front of everyone rather than impressions.
What it connects to
Works with what you already run
A forecast is only as good as the history it is built from. These are the sources we usually connect.
ERP sales and stock history
Sales by line, by account and by week, stock on hand and open purchase orders, read from your ERP, for example Sage, NetSuite or Business Central, through its API where it offers one or a scheduled export.
Supplier terms
Lead times, minimum order quantities, pallet multiples and delivery days for each supplier, kept in one table the buying team maintains and updates when a supplier changes them.
Promotions calendar
Your planned trade promotions and price changes, wherever they live today, so planned promotions lift the forecast before they start and past ones are recognised in the history rather than mistaken for demand.
Email and team chat
Alerts reach the buyer who owns the line in the tool they already use, for example Microsoft Teams or Slack, with the chart attached and a link to the forecast, rather than in a dashboard nobody opens.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- Forecasts for your most important product lines, tested against past months
- Supplier lead times and minimum order quantities in one table
- A weekly reorder list per supplier with suggested quantities as ranges
- Alerts to the line's buyer when sales leave the forecast range
- A slow stock list ordered by weeks of cover
Once it is in use
- The promotions calendar feeding planned uplifts into forecasts
- Suggested purchase orders sent to the ERP as drafts for approval
- Forecasts extended to every line and every depot
- Accuracy tracked by category, with drifting forecasts flagged
Buyer's guide
Before you commission one
Four decisions worth making before you commission forecasts, so they answer the buying questions you actually have.
- 01
Planning software or built for you
Inventory planning and demand forecasting software is a mature category, and many ERPs include a planning module. If one fits your data and your buyers trust it, buy it, or tune what your ERP already has. Built for you earns its place when your promotions, accounts or supplier terms need modelling the packages handle poorly, or forecasts must feed tools you already run.
- 02
What to gather first
Weekly sales by line and account for as long as you have them, records of stock-outs, your promotions history and plan, and each supplier's lead times, minimums and pallet quantities. Most of all, the buyers' knowledge of which past weeks were odd and why, because that is what makes the history usable.
- 03
Who should own it
The purchasing or buying manager. They decide which lines are forecast first, who receives which alerts, and when a buyer's override should become a rule. The commercial director owns the stock investment the forecasts drive, and sales should feed in promotions and new accounts, or the forecast will be the last to know.
- 04
How you will know it is working
Watch stock-outs on the lines that matter, weeks of cover on slow lines, forecast error and bias by category, and how often buyers override suggestions and whether their overrides were right. When buyers start the weekly order from the suggestion rather than last year's spreadsheet, it has earned its place.
Terms worth knowing
The words you will meet
- Reorder point
- The stock level at which a line should be reordered, so new stock arrives before the old runs out. It depends on how fast the line sells and how long the supplier takes, so a fixed number set years ago drifts out of date as both change.
- Safety stock
- Extra stock held to cover demand that runs above forecast or a supplier that delivers late. Too little and lines run out; too much and cash sits on the racking. Setting it per line from the forecast range is more honest than a flat number of weeks for everything.
- Forecast bias
- Whether a forecast tends to run high or low, as opposed to how far off it is. A forecast that is always a little high fills the warehouse, and one that is always a little low causes stock-outs. Watching bias by category catches a drifting forecast early.
Handled with care
The details that matter here
A forecast changes how much money you put into stock. These are the details we handle with care.
Your history, cleaned honestly
Sales history contains stock-outs that look like low demand, one-off bulk orders and returns. We go through these with your buyers before modelling, mark what should be left out or adjusted, and record each decision, so the forecast starts from demand rather than from what happened to be in stock.
Buyers stay in charge
A forecast is a suggestion. We design every screen so the buyer can see why a quantity was suggested, change it and note why. Over time those overrides show where the forecast needs work, and where the buyer knows something the data does not.
Accuracy reported, not assumed
We report how far forecasts were from what actually sold, by line and by category, every month. Where accuracy drifts because your business has changed, it shows up in that report and we retune, rather than leaving a model to get worse while people keep trusting it.
Alerts kept few and owned
An alert nobody reads is worse than none. We agree with your purchasing manager which lines alert whom, tune thresholds to each line's normal pattern, and review how many alerts are going out after the first few weeks, so each one is worth reading.
Questions
What buyers ask first
Do we need demand forecasting if our ERP has reorder points?
Reorder points work when they are kept up to date, and they are often set once and left. If yours are maintained and your buyers trust them, you may not need forecasts, and we would say so. This earns its place when demand is seasonal or driven by promotions, when supplier lead times change, or when there are too many lines for buyers to review by hand.
How accurate is demand forecasting for wholesale?
We won't promise a number before we have seen your data. Some lines sell steadily and forecast well. Others are lumpy, driven by a few large accounts, and no method forecasts them closely. We test on your own history first and show you the error line by line, so you decide where to rely on the forecast and where to keep your current method.
How do you calculate a reorder point for wholesale stock?
In outline, it is the demand expected during the supplier's lead time, plus safety stock for the uncertainty. The hard part is the inputs: demand that changes with seasons and promotions, lead times that drift, and stock-outs that hide real demand in your history. We calculate reorder points per line from the forecast range and recalculate them as sales and lead times change.
Can demand forecasting create purchase orders automatically?
It can, but we would suggest not at first. The planner suggests quantities and the buyer raises the order. Later, suggested orders can go to the ERP as drafts for a buyer to approve. Fully automatic ordering only makes sense for steady lines with reliable suppliers, and only once the forecasts have held up on your own data.
How much sales history do you need for demand forecasting?
More history helps with seasonal lines, but you don't need perfect records. Two full years of weekly sales by line is a comfortable start for seasonal products, and steady lines need less. New lines have no history, so we forecast them from similar lines or from the buyer's own estimate, and say clearly which forecasts rest on thin data.
Which lines keep catching you out?
Tell us how buying is done today and send a sample of sales history if you can. We will reply within 48 hours with what a forecast could and could not tell you about your lines.
More for wholesale
What else we build for wholesale and b2b
Trade ordering portals
A logged-in store for trade buyers with account-specific price lists, minimum quantities, pack sizes, order pads and one-click reorder from history. Customers order when it suits them, and orders arrive already checked against price and credit rather than in an inbox.
Ordering apps for reps
Your field reps take orders on a tablet at the customer's premises, with live prices, stock and the account's history to hand. The app keeps working in a cellar or a basement with no signal and syncs as soon as it is back online.
Email and PDF order capture
For customers who will always email: orders read from emails, PDFs and spreadsheets, matched to the right account and product codes, checked against price and stock, then created automatically or held for a person when something does not match.
Pricing and quoting tools
Your pricing rules, from contract prices and volume breaks to promotions and approval thresholds, taken out of a fragile spreadsheet and turned into a tool anyone on the team can use, with a full history of what was quoted to whom.
ERP and accounts integration
Orders, customers, prices and stock flowing between the portal and your ERP, warehouse system or accounts package, with one agreed system in charge of each piece of data. Nothing is retyped, and a failed sync alerts someone instead of vanishing.
Everything we build for wholesale
The same idea, in other sectors