> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-3/modifiers.md).
# Modifiers
The **Modifiers** feature is used to define additional options or customizations for menu items in the system. These modifiers allow customers to modify items based on their preference, such as extra ingredients, spice level, or add-ons.
### Steps to Create and View Modifiers
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master3 > Modifiers**.
* The Modifiers screen will appear.
Step 2: Click on the **Open** button to proceed.
Step 3: Select the required **Outlet Name** from the available list.
* Click on the **Search icon** in the item selection field.
* Choose the required items for which modifiers need to be applied.
Step 4: Click on the **Add** button.
* Select the required items from the list shown.
* Assign or map the selected items as modifiers for the chosen menu items.
Ensure all selections are correct before proceeding.
Step 5: After configuring the required modifiers, click on the **Save** button to successfully store the Modifiers setup.
---
# 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.rbsgo.com/point-of-sale/point-of-sale-module/masters-3/modifiers.md?ask=&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.
