> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/level-modifiers.md).

# Level Modifiers

### Level Modifiers

#### How to use level modifier

Level modifiers are designed to work with a price structure. Your menu setup, modifier or weight modifier can produce the same list of modifiers or price roll-ups, and each time, the item price will change according to the price structure.

 

For example, imagine that your special on medium pizzas is as follows: the price for a medium pizza is $10.00 including 1 topping. Adding one or two toppings to that will cost $3.00 more ($13.00), adding yet another one or two toppings to the pizza will cost $2.00 more ($15.00), and finally, all additional add-ons will cost $1.50 more.

**Pizza**

| <p>Medium</p><p>+ 1 topping</p> | <p>Medium</p><p>+ 2 topping</p> | <p>Medium</p><p>+ 3 topping</p> | <p>Medium</p><p>+ 4 topping</p> | <p>Medium</p><p>+ 5 topping</p> | <p>Medium</p><p>+ 6 topping</p> | <p>Medium</p><p>+ 7 topping</p> |
| ------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- |
| <p> </p><p>$10.00</p>           | <p> </p><p>$13.00</p>           | <p> </p><p>$13.00</p>           | <p> </p><p>$15.00</p>           | <p> </p><p>$15.00</p>           | <p> </p><p>$16.50</p>           | <p> </p><p>$18.00</p>           |

**To do so**

On your pizza item you set the price of $10.00. This item will call a modifier screen that could be reach from modifier #1 or weight modifier option. In addition, this item will call a level modifier to set the modifier prices according to your structure.

![Level Modifier Diagram](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/POSControl/LevelModifierDiagram.gif)

With this setup, when you select MEDIUM PIZZA, the program calls the MED TOP group up to 10 times and each time you select something from it the program apply the price structure build in the level modifier MEDIUM PRICES. As you can see, because the USE PRICE option is enabled, the first five item prices will be $0.00, $3.00, $0.00, $2.00, $0.00. Then because level price option is disabled the program will apply the price of the modifier it self ($1.50 per selection).

**Description**

Enter the level modifier description here.

**Use Price**

Enable this option to make the following amount field available.

**Price #1 to Price #20**

Enter the price amount; it will be available if the previous option is enabled.


---

# 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.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/level-modifiers.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.