> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/suppliers-and-purchasing/demand-planning/approaching-the-demand-planner.md).

# Approaching the Demand Planner

You should look at the demand planner as more of a musical instrument to be “played” rather than a piece of artificial intelligence that can tell you exactly how much stock to order with 100% accuracy

Pakk’s demand planner is a tool we’ve built to help with this task. It’s important to note that it doesn’t work completely autonomously - it’s a set of tools and controls that are designed to work in conjunction with, and enhance, expert knowledge about the business. It takes a lot of the guesswork out of the task, makes it more efficient, makes ordering quicker and less error prone and makes some of that ‘owner instinct’ available to everyone else in the business. To get the most out of the demand planner, you’ll need to learn to use it, rather than just creating orders from it with a single click. We often describe it as like playing a musical instrument, or flying an aeroplane - you’ll need some knowledge and practice before really getting to grips with it.

All demand planners rely on historical data to feed their models, and realities can change quickly, so you should use the demand planner as an interactive tool to do your ordering, combining it with the expert knowledge of your business that only you and your team have.

\ <br>


---

# 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.pakk.io/suppliers-and-purchasing/demand-planning/approaching-the-demand-planner.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.