> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/stock/demand-forecast.md).
# Demand Forecast
The Demand Forecast tool provides a view of expected stock consumption for each product. It is designed to help managers anticipate stock requirements, reduce risk of running out of key items, and make more informed purchasing decisions.
## How the Forecast Works
The forecast is generated from historical sales activity and manufacturing jobs.
{% hint style="warning" %}
Stock transfers between locations are not included in the forecast.
{% endhint %}
The forecast analyses the previous 6 weeks of data. For each product, the system calculates the median consumption for each day of the week across the 6-week window. More recent weeks are given more weight. This means that if patterns have shifted in the recent weeks, the forecast will reflect that change.
The system also detects whether demand is trending up or down, and factors this into the forecast. This is shown as the Trend Factor in the report.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bossithq.com/stock/demand-forecast.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.