> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/menu/customisations/creating-a-customisation.md).

# Creating a Customisation

1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Menu** > **Customisations**.
2. Click **Add Customisation**.
3. Fill in the following fields:
   1. **Name** — internal reference for the customisation (e.g., Pizza Toppings)
   2. **Display Name** — this will appear as the header (e.g., Edit your toppings)
   3. **Addition Name** (for Integrations) — prompt for adding (e.g., Add any toppings?)
   4. **Removal Name** (for Integrations) — prompt for removing (e.g., Remove any toppings?)
   5. **Type**
      * **Regular —** for modifying ingredients
      * **Upsell —** for upselling products
   6. **List Order** — define the positioning (ascending order)
4. Click **Create** to save the customisation.
5. Once created, click on the customisation and navigate to **Selection options**.
6. Click **Add product** or **Add multiple**.
7. Select the product you want to put in the customisation. You can search by Department name to choose from products within the Department.
8. You have the option to override the product name and price for the customisation if needed.
9. Click **Save**.


---

# 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.bossithq.com/menu/customisations/creating-a-customisation.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.