Skip to main content
Removal modifier groups let customers take standard ingredients off a product. The ingredients are options that come already selected; the customer unticks the ones they don’t want, and the POS is told which default ingredients were removed.
Removal groups currently come from Zonal (Aztec) menus only. They are set automatically during the menu sync — there is no removal setting in the dashboard and nothing for support to switch on. On other menus, use a regular modifier group with default options instead (see Default Quantity).

How It Works

A Zonal choice group that has default selections is imported as a removal group:
  • Options represent ingredients that come standard with the product, and start selected (their Default quantity is above zero)
  • Customers untick the ingredients they want taken off
  • When the order is sent to Zonal, each unticked default is sent as a removal (quantity -1) of that ingredient, and anything added beyond the default is sent as an extra

Example

A burger that comes with lettuce, tomato, onion, and pickles by default: Removal modifier group Remove Ingredients:
  • Lettuce (selected by default)
  • Tomato (selected by default)
  • Onion (selected by default)
  • Pickles (selected by default)
Customer unticks Onion and Pickles → Zonal receives the burger with Onion and Pickles removed.

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, Zonal only receives deviations from the default. A standard pizza is sent with no modifiers. A customised pizza carries only what was removed (or added on top), and your Zonal setup decides how that prints — for example 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.

Without Zonal

On a menu that isn’t synced from Zonal, you get a similar result with a regular modifier group whose options have a Default quantity of 1. Customers see them pre-selected and untick what they don’t want; give the group a clear name such as “Remove Ingredients” so the intent is obvious. Unticked defaults are not sent to the kitchen as “No X” lines, so check how your tickets or POS show them before relying on this.

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), a choice group with default selections is automatically imported as a removal group. There is nothing to configure.

Compared to Regular Modifiers