> 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/setting-up-customisation-options.md).

# Setting Up Customisation Options

{% stepper %}
{% step %}

### Create the Department 

Begin by creating a Department to group related ingredients, such as a *Toppings Department* or *Sauces Department*. Ensure the **Shown individually?** property is disabled so the Department itself does not appear as a menu item.

[Creating a Department](/menu/departments/creating-a-department.md)
{% endstep %}

{% step %}

### Create the Products

Once the Department has been created, create new products for each individual ingredient (e.g., for Toppings: Pepperoni, Bacon, Olives; for Sauces: Tomato, Barbecue, White sauce). Disable **Sold individually** property so these ingredients are not shown as standalone menu items.

[Creating a Product](/menu/products/creating-a-product.md)
{% endstep %}

{% step %}

### Create the Customisation

This will allow the ingredients to appear as selectable options when a customer chooses a Detailed Product, such as a pizza or burger.

[Creating a Customisation](/menu/customisations/creating-a-customisation.md)
{% endstep %}

{% step %}

### Assign the Customisation to the Product

Once the Customisation is created, assign it to the relevant product. This makes the options available during the order process, allowing staff to add or adjust ingredients as required.

[Assigning Customisations to a Product](/menu/products/product-configurations/product-customisations/assigning-customisations-to-a-product.md)
{% endstep %}
{% endstepper %}


---

# 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/setting-up-customisation-options.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.