> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/getting-started/overview-of-key-terms-and-concepts/demand-planning.md).

# Demand planning

Ensure you've always got the right stock amount on hand and alleviate concerns about order delays, dissatisfied customers, high holding costs, or wasted stock.

{% hint style="info" %}
User permissions: Budgets & Forecasts and Manage Budgets & Forecasts
{% endhint %}

While most of the information in this user documentation is focused on sales and financial use cases, the Budgets & Forecasts module can also be used with purchasing and inventory databases to help you make decisions around demand. This includes decisions on the future purchases you need to make to ensure you can meet customer demand and avoid overholding stock.

{% hint style="success" %}
Watch this Phocas Demo video: [Demand planning](https://www.phocassoftware.com/watch-demo/demand-planning?autoplay=true) - overview of how you can use Budgets & Forecasts to create a demand plan that integrates your sales forecasts and purchasing data
{% endhint %}


---

# 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.phocassoftware.com/budgets-and-forecasts/getting-started/overview-of-key-terms-and-concepts/demand-planning.md?ask=<question>&goal=<endgoal>
```

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