> ## Documentation Index
> Fetch the complete documentation index at: https://storekit.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Removal Modifiers

> Let customers remove default ingredients from storekit products with removal modifier groups. Show 'no onion' or 'no cheese' without cluttering the menu.

Removal modifier groups allow customers to remove standard ingredients from a product. Unlike regular modifiers that add options, removal modifiers represent ingredients that are included by default and can be taken away.

<Info>
  This feature requires support to enable for your account. [Contact support](/getting-started/contact-support) to request access.
</Info>

## How It Works

When a modifier group is marked as a removal type:

* Options represent ingredients that come standard with the product
* Customers select items they want **removed**
* Selected options are communicated to the kitchen as exclusions

### Example

A burger that comes with lettuce, tomato, onion, and pickles by default:

**Removal modifier group: "Remove Ingredients"**

* Lettuce
* Tomato
* Onion
* Pickles

Customer selects "Onion" and "Pickles" → Ticket shows: `No Onion, No Pickles`

## Why Use Removal Groups

### Cleaner Kitchen Tickets

Without removal groups, you'd need to list all default toppings as regular modifiers. If a customer orders a pizza with standard toppings, the ticket would list every single topping - even though nothing changed from the default. Kitchen staff would need to scan through a long list to spot any actual customisations.

With removal groups, tickets only show **deviations from the default**. A standard pizza prints with no modifiers listed. A customised pizza shows only what was removed: `No Olives, No Anchovies`.

### Clearer Customer Experience

Removal groups make it obvious to customers what's already included. Instead of wondering "do I need to add cheese?" they see a list of what comes standard and can simply uncheck anything they don't want.

### Alternative Approach

You can achieve similar results with regular modifier groups by pre-selecting all default options. However, removal groups are often clearer because:

* The group name signals intent ("Remove Ingredients" vs "Toppings")
* Customers immediately understand these items are included
* Less cognitive load than a pre-checked list of additions

## Use Cases

### Allergen Accommodation

Allow customers to remove allergen-containing ingredients:

* No nuts
* No dairy
* No gluten-containing items

### Dietary Preferences

Let customers customise based on preferences:

* No onions
* No cilantro
* No spicy sauce

### Default Toppings

For products with standard toppings that some customers may want removed:

* Pizza default toppings
* Sandwich standard ingredients
* Salad default components

## POS Integration

### Zonal (Aztec)

When syncing menus from Zonal (Aztec), removal modifier groups are automatically detected based on the presence of default selections in choice groups. The `isRemoval` flag is set automatically during import.

## Compared to Regular Modifiers

| Aspect                    | Regular Modifiers | Removal Modifiers    |
| ------------------------- | ----------------- | -------------------- |
| **Default state**         | Nothing selected  | All items "included" |
| **Customer action**       | Add options       | Remove options       |
| **Kitchen communication** | "Add X"           | "No X"               |
| **Typical pricing**       | Often charged     | Usually free         |