> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/mcp/what-you-can-do/reports-and-help.md).

# Reports and help

Ask for authorised business reports or guidance on using Supply'd.

Business questions use your authorised ERP records and reports. How-to questions search Supply'd help documentation.

## Business reports

| Area          | Available report groupings                                                                                             |
| ------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Sales         | Date, delivery date, customer, product, category, warehouse, department, group, representative, user, channel and hour |
| Margins       | Date, customer, product, category, warehouse, department, group and channel                                            |
| Purchases     | Date, supplier, product, category, department and location                                                             |
| Production    | Date, product, batch, category and warehouse                                                                           |
| Inventory     | Product, category, warehouse and batch; days, weeks or months on hand; inventory on order and inventory feed           |
| Write-offs    | Product, category, type, user and warehouse                                                                            |
| Deliveries    | Date                                                                                                                   |
| Pick-and-pack | Date, customer, group, picker, packer, channel and warehouse                                                           |
| Tasks         | Date, department, group, location and user                                                                             |
| Customers     | Customer overview                                                                                                      |

Use an explicit start and end date for time-based reports. Current-state reports, such as stock on hand, normally do not require a period. Filters and fields depend on the selected report.

Examples:

* “Show sales by customer for the last calendar month.”
* “Compare margin by product category this month.”
* “How many units of each product were produced last week?”
* “Show current weeks on hand by warehouse.”
* “Show write-offs by type for the last month.”

Report access depends on your ERP plan, selected MCP access and user permissions. A record-level history and a grouped report answer different questions. Ask for order history when you need individual orders, or a report when you need totals across a period.

## Supply'd help

Ask how to complete a workflow in Supply'd. The assistant can search approved documentation and provide guidance with source links.

* “How do I assign an ingredient to a recipe stage?”
* “How do I receive a purchase order?”
* “How can I see proof of delivery?”

A help answer explains the platform. It does not perform the workflow or change ERP records.

## Usage

Each MCP server call uses **0.01 Supply'd usage tokens**. One answer may require multiple searches, record reads or report calls. See [Private beta availability and limits](/mcp/manage-your-connection/availability-and-beta-limitations.md).


---

# 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://help.supplyd.co/mcp/what-you-can-do/reports-and-help.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.