> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/artists/purchasing.md).

# Purchasing

Purchasing reads every rider line of the edition and answers four questions: what to order per supplier, what the whole edition needs, what to carry into which room, and what to unpack per artist.

**Order forms**: one per [supplier](https://docs.eventication.com/event/artists/suppliers.md), with the products and quantities asked from them. The PDF and CSV you send a supplier carry **no prices** by default; tick *with the prices* on the export screen for an internal priced copy.

**Custom**: the lines that are on no order form, because they were typed instead of picked from the catalog (badge *free text*) or because their rider product has no supplier (badge *no supplier*). Each line says who asked for it: one badge per performance and rider, opening that rider. Nothing is sent from here; the PDF is your list for what you source yourself. The tab only shows while the edition has at least one such line.

**Totals**: every product of the edition with its total quantity and its status (*open*, *ordered*, *delivered* or *not available*).

**Dressing room totals**: the hospitality lines per dressing room.

**Unpack list**: every line per artist, filterable by day, rider kind, category, supplier and location, with a PDF that prints exactly what is on screen.

**Per performance**: what each booking asked for, including lines that were denied (marked with a badge).

{% hint style="info" %}
Denied rider lines are left out of the order forms, the Custom tab, totals and unpack list. See [Riders & feedback](https://docs.eventication.com/event/artists/riders.md).
{% 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://docs.eventication.com/event/artists/purchasing.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.
