> 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.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2F4zKdXGw9k6mLq1KG6fVg%2Fimage.png?alt=media&amp;token=9b32d850-d20c-4373-af85-de16a6dfaba7" alt=""><figcaption></figcaption></figure>

## How the Forecast Works

The forecast is generated from historical sales activity and manufacturing jobs.&#x20;

{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bossithq.com/stock/demand-forecast.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
