> This page is for Product Documentation.
> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.
# Set up item add-ons
> The article consists of main steps that constitute the process of item add-on setup, followed by several common use cases, examples, and best practices.
1. Create the main items that will be sold by configuring the necessary options in their respective **Item Cards.**
2. Define the item add-ons in the [**Item AddOns**](/product/retail-pos-processes-item-addon-ref) administrative section.
3. [Link item add-ons with the main item](/product/retail-pos-processes-create-and-attach-item-addon) they are going to sold with. This is done in the **NPR Properties** section of the **Item Card**.
4. Define the [button on the POS Menu](/product/retail-pos-layout-new-button) which will be used on the POS unit, if you need a standalone menu, without the main item.
## Examples, use cases, and best practices
### Item add-ons with fixed quantity
In the provided example, the first line contains the **Fixed Amount Warranty 50** (which is the item with the item number 100IN005). If the main item is purchased, the item add-on of 50 is automatically purchased as well. This is fixed on the main item, but it is possible to decline this configuration, since it hasn't been set as mandatory.
### Item add-ons without fixed quantity
In the second line of the provided example, **Fixed Quantity** wasn't selected, so the salesperson can modify it on the sales line.
### Item add-ons sub-menu
It's possible to set a sub-menu from which the salesperson can select an option. This is done when choosing the **Select** type in the **Lines** section (as per the 3rd line in the example provided above). As a result, when the main item is inserted, the following window is displayed in the POS:
There are three different combinations of outputs:
### Item add-ons using percentage of main item unit price
If the logic is changed so that the value of the item add-on unit price is a fraction of the main item's unit price, when an item is added, it's not necessary to define a unit price on the **Item Card** of each individual item.
You can select a predefined workflow under the **Before Insert Function** field (displayed when you expand the **Manage** action). If you select **Unit Price From Master**, the **Before Insert Setup** setup button becomes visible on the **Lines** header. You will be prompted to insert a percentage of the main item unit price to be sold.
When the main item is sold, the POS button is activated, and you can press it to open the popup with the list of add-ons to choose from. However, this time, the unit price depends on the percentage of the main item that was used in the setup of item add-ons. In the example, the main item has the unit price of 2000.00.
On the POS, the output is displayed as indicated in the following screenshot:
### Item add-ons as a menu
In this example of setting a menu for selling drinks in a café, you can see how options are used in defining item addons.
You can define individual items (if you're keeping proper inventory) or one item, but set the name that will be displayed on the sales in the **Item AddOn Card**. For example, you can have an item that is called *Soft Drinks*, and then on the **Item AddOn Card**, you can change the name to a different brand of soft drinks (in this case, the inventory isn't sorted per a brand, but every soft drink is kept in one big stock).
Another common way of doing this is to define the *Soft Drink* item, but assign variants to it. In this case, the variant represents each brand. The inventory is kept on variant level.
On the POS, you can create a button with the *POS Action = RUN_ITEM_ADDONS*.
As a result, the output on the POS will be displayed as indicated in the following screenshot:
> **Tip:** The *POS Action = RUN_ITEM_ADDONS* requires that there is already a line in the POS sales line for it to be activated.
### Item add-on variations and combinations
We can combine different methods used for item add-ons. This can be illustrated in the café environment, where combo items are often defined.
In the case of cold drinks, you can define a single item with different descriptions, and if they are offered as a bonus part of some meals, there will already be a unit price defined in the **Item Card**, so you can set the unit price on the **Item AddOns Menu** as *0.00*. Then, with the **Select Option** you can define different options. You can have a combination of food and one free drink that can be selected from the list of options you provide.
### Item add-ons as extra items
You can support both an item accessory and item add-ons on the main item. When you select an item which has an item add-on as extra, item add-ons will be activated, and can then be used. If, however, you define only one item in the add-on, and set it as mandatory, the item line will be added to the **POS Sales Line** automatically.
For example, when selling electrical equipment, and if you want to show an extra levy on it, you can attach a service item with the main item. By selling the main item, the system will automatically insert another line for the levy. It can be a fixed amount or percentage of the main item price. These different ways can be defined in the **Item AddOn Card**.
### Item add-ons as a standalone menu
There is a POS action (**RUN_ITEM_ADDONS**) that can be used to create a button for opening the item add-on menu on the POS. The action has a parameter that needs to contain the item add-on code.
> **Tip:** An item needs to be inserted in the sales line before you can use the button to access the menu on POS.
#### See also
* [Item AddOn overview](/product/retail-pos-processes-item-addons)
* [Item AddOn (reference guide)](/product/retail-pos-processes-item-addon-ref)