> 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/example-questions.md).

# Example questions

Natural-language examples for using Supply'd with an AI assistant.

Ask Supply'd questions in ordinary language. Add a date range, location, status or exact reference when it will help narrow the result.

## Company information

* “Show our company locations and departments.”
* “Which integrations are configured for our company?”
* “List the tax rates available to my company.”

## Sales

* “What were our total sales from 1 August to 7 August?”
* “Compare sales this week with the previous week.”
* “Show orders awaiting fulfilment.”
* “Open order SO-1234 and summarise its items, customer and status.”
* “Show the sales history for SKU ABC-123.”

## Products and recipes

* “Find Chocolate Chip Cookie 80 g.”
* “Show the complete recipe, including ingredients assigned to each stage.”
* “Include the method, labour time and processing time for every stage.”
* “Which suppliers and substitutes are linked to this product?”
* “What is the recent demand for this product?”
* “Which recipes use or relate to this product?”
* “Which sales channels are linked to this product?”

## Production

* “When was this product last produced?”
* “Show the five most recent production runs for SKU ABC-123.”
* “Open the latest run and show its quantity, yield and status.”
* “Which products were produced yesterday?”

## Purchases and expenses

* “What is the latest purchase order from this supplier?”
* “Which purchase-order items are still outstanding?”
* “Show the purchase history for this product.”
* “Find expenses from this month awaiting reconciliation.”
* “Compare expense EXP-123 with its purchase order and scanned invoice. Separate scanned values from saved expense values and show unmatched lines or adjustments.”

## Inventory and batches

* “How much of this product is available by warehouse?”
* “Show the batches for SKU ABC-123.”
* “Which batches expire in the next 30 days?”
* “Show recent inventory activity for this product.”
* “Show activity for this specific inventory record or batch.”

## Customers and suppliers

* “Find customers containing ‘Harbour’ in the name.”
* “Show this customer's most recent orders.”
* “Which products does this customer order most often?”
* “Find the supplier and summarise its account details.”

## Fulfilment, deliveries and tasks

* “Show fulfilments currently being picked.”
* “What is the progress of fulfilment F-123?”
* “Which deliveries are scheduled for today?”
* “Show the stops in today's North delivery run.”
* “What open tasks are assigned to my department?”

## Supply'd help

* “How do I create a product recipe in Supply'd?”
* “How does batch tracking work?”
* “Where do I manage delivery runs?”

For follow-up questions, keep the relevant product, customer or order in the same conversation. If the client becomes ambiguous, repeat the exact SKU or reference returned in the previous answer.


---

# 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/example-questions.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.