Home · Business · Operations & Logistics · Inventory & stock
As of 13 August 2026, AI can only partly forecast demand for your products.
This still needs a person who signs their name to it.
Can you do it?
15 minutesto a draft.
1 hourto something you’d act on.
Cost, all in£0
Skill neededpower-user
Who has to check ityou
What the alternative costsThe supplied tool data does not list a price for a demand-forecasting service.
If this goes wrong: you buy too much stock or run out during a demand increase, leaving your business with tied-up cash, missed sales or urgent supplier costs.
What to actually do
Hand it to a person
The route this page recommends
A person who owns the outcome does this end to end, worth it when the failure is dear.
Use a tool built for this
Second choiceDo it yourself
The distant thirdA chat interface, power-user skill, and roughly 1 hour until you can act on the result.
How to actually do it
- Open your sales or stock system and export dated product-level records covering units sold, selling price, promotions, returns, stock availability and stockouts.
- Create one clean spreadsheet with one row per product and period, and mark periods where demand was limited because the product was unavailable.
- Add known future events such as promotions, price changes, launches, closures, bank holidays and supplier constraints, then remove duplicate rows and clarify any product name changes.
- Paste the business context and the cleaned table into the prompt, and ask the chatbot to identify missing or unreliable fields before it produces a forecast.
- Paste the resulting forecast into a spreadsheet and compare its backtested predictions with the actual sales in the held-back periods, checking that it has not treated stockouts as low demand.
- Discuss the central, lower and upper scenarios with the person responsible for purchasing, then record which scenario you will use for stock and supplier decisions and when you will update it with actual sales.
Prompt
Forecast demand for the following product using the data provided below. Treat the forecast as a planning aid, not a certainty. Business context: - Product: [product name] - Market and sales channel: [market and channel] - Forecast horizon: [period to forecast] - Forecast frequency: [weekly or monthly] - Known future events: [promotions, launches, closures, price changes, holidays or supplier constraints] Historical data: [paste a dated table with units sold, selling price, promotions, stock availability and any known stockout periods] Instructions: 1. Check the data for missing dates, duplicate rows, changing product definitions and periods when sales were limited by stock availability. 2. Do not invent missing figures. List the assumptions and data problems before forecasting. 3. Produce a forecast for each period, with a central estimate and a clearly labelled lower and upper planning scenario. Explain how each scenario was chosen without presenting it as a probability unless the data supports that. 4. Separate observed patterns from assumptions about future demand. Discuss seasonality, promotions, price changes, trend, one-off events and stockouts where the data supports them. 5. Hold back the most recent complete periods as a test set if the data allows. Compare the forecast with actual sales and report the error in plain English. If meaningful backtesting is not possible, say so. 6. Show the result in a table that I can paste into a spreadsheet. 7. Recommend what additional data would most improve the forecast. 8. End with a short list of decisions that still require my judgement, including stock, promotions and supplier commitments. Use only the information I provide. Ask concise questions before forecasting if a missing input would materially change the result.
Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.
What it gets wrong
- AI cannot know whether a past sales drop reflected weak demand, a stockout, poor visibility, a competitor's action or a data error unless you supply that context.
- AI cannot reliably predict an unrecorded change in customer behaviour, competitor pricing, regulation, weather or supplier performance.
- AI cannot choose the acceptable balance between excess stock, missed sales, cash tied up and storage costs for your business.
- AI cannot take responsibility for a purchase commitment or the consequences of a forecast error.
- A plausible forecast is not evidence that the underlying data or assumptions are sound.
What caps this at PARTLY: verification cost, judgement under ambiguity and stakes of error.
How we scored this
Five axes, each scored nought to two by hand: ten means AI carries the task cleanly, and the thresholds that turn a total into YES, PARTLY or NO are published in the methodology. Each axis name links to its definition.
| Axis | Score (0–2) |
|---|---|
| Output | 2 |
| Inputs | 1 |
| Verification | 1 |
| Liability | 1 |
| Effort delta | 2 |
| Total | 7 / 10 |
The methodology and its thresholds are published in full.
FAQ
- Can ChatGPT predict demand for my products?
- Yes, it can produce a demand forecast from historical sales and relevant business data. It cannot know whether a pattern will continue, and you need to test the forecast against past periods before using it for purchasing.
- What data do I need for an AI demand forecast?
- Start with dated units sold, price, promotions, product availability and stockouts. Add returns, channels, seasonal events, launches, closures and supplier constraints where they affected sales.
- Can AI forecast demand for a new product?
- It cannot forecast a new product from its own sales history because there is no history. It can organise comparable-product data and your assumptions into scenarios, but the result is more dependent on judgement and external evidence.
- Can I use an AI demand forecast to decide how much stock to buy?
- You can use it as one input alongside lead times, minimum order quantities, cash limits and the cost of running out. Check the forecast against actual sales and keep the purchasing decision with someone who understands the products and supply risks.
Nearby answers
Assessed by gpt-5.6-luna (gpt-5.6-luna) on 2026-08-13, second-checked by an independent model. Wrong somewhere? Email [email protected] and it gets re-checked.
The newsletter
AI news, new answers and product picks, straight to your inbox.