> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/documentation-simax-anglais/functional/management-of-stock-and-logistics/dashboard.md).
# Dashboard
To effectively **manage your stock**, both when r**eceiving supplier items** and when **delivering to customers**, the **dashboard** provides you with all the necessary information and allows you to access the main features of the **Stock module**.
**(Stock > Stock dashboard)**
**The dashboard** is **structured into four sections**:
1. **Shortcuts and filters**
This section provides s**hortcut buttons** to stock status, orders to be prepared, etc. You can also **filter information by establishment** or display an **overview** of all your establishments.
2. **Key performance indicators (KPIs)**
**KPIs** show the number of **supplier orders** **to be received** and **customer orders to be prepared**.
The cards are **clickable** and provide direct access to the list of orders concerned.
3. **Most active items**
This section lists the three (3) items with the most movement.
4. **Stock value**
A summary of stock values is provided for each of your warehouses.
{% hint style="info" %}
Information about the **most active items** and **stock values** **is automatically updated every night.**
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.simax.fr/documentation-simax-anglais/functional/management-of-stock-and-logistics/dashboard.md?ask=&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.
