Handling menu modifiers without confusing staff

A modifier should capture a real choice in words staff can select and the kitchen can act on. Build groups around the decisions needed to prepare each item, then test that the selected options read clearly on the ticket.

Start with real choices

Start with the kitchen’s decisions, not a long list of possible customisations. For a sandwich, these might be bread, side, cheese add-on, sauce and removals; for a pizza, size, crust and topping rules. Keep size, milk, cooking preference, extras and omissions in distinct groups when they represent different tasks.

Separate the group from the options staff select. In Toast, “Meat Temperature” is a modifier group, while “Rare” and “Medium Rare” are options; the group name does not print on receipts or tickets, but the selected options do. Check that each option says what the kitchen needs to know.

Use plain, consistent labels rather than abbreviations or near-duplicates. Examples include “extra spicy”, “no sour cream”, “extra protein” and “extra dressing”; use “no onions” consistently rather than switching between “hold onions” and “remove onion”. A request such as “no pickles” or “light mayo” should map to an option staff can recognise by sight.

Set selection rules to match the choice. Toast provides required, optional and POS Prompt behaviour; H&L lets you enter minimum and maximum modifier quantities and a maximum quantity for an individual modifier. H&L’s Internal Name field can hold a more descriptive name that is not displayed to the customer.

Give paid add-ons their correct price and keep their labels distinct from free preparation choices. Toast modifier options can be free, upcharged or discounted. Do not attach a price to a staff note unless it is a paid add-on.

Attach groups only where they apply. Toast allows a modifier group at menu group, subgroup or item level, and an existing group can be reused on other items. Radish describes global modifier sets that can be applied across a menu and tailored for individual items.

Use free-text notes for genuine preparation preferences staff can honour consistently, not as a substitute for structured choices the kitchen needs. Staff notes cannot guarantee allergy safety; use reviewed allergen labels and staff confirmation. In Square, staff can press and hold a POS item tile to view details including dietary preferences and allergens.

Give staff a simple wording reference: match the customer’s request to the same option label every time. Include the wording for unusual kitchen rules, and share the rule once each shift so staff do not have to decode abbreviations or guess what a note means.

Modifying modifiers: Structured choices vs. free-text notes

Rehearse awkward orders

Check the selected option names on the kitchen ticket, not just the customer-facing menu. Try examples such as “Rare”, “Medium Rare”, “no pickles” and “LITE mayo”; in Toast, the selected modifier options print on tickets. If a label could be misunderstood, rename it before staff rely on it.

Rehearse conflicting modifiers, a half portion, an allergy-related note and a preference changed after the ticket was sent. Confirm whether the system rejects, flags or records each combination, and keep allergy handling with reviewed labels and staff confirmation rather than relying on free text.

In Square, menus can be sold across the POS, online ordering, kiosks and delivery apps, with menu and item channel and location settings managed in Square Dashboard. Test each relevant route to confirm the choices appear as intended, especially after copying a menu. Staff should also know that team members only see menus assigned to at least one of their assigned locations.

Do a five-minute modifier check before service; twenty minutes is ideal and ten is workable. Hide expired specials and options staff cannot explain, and rename unclear labels using words staff already use. Review the list weekly; archive old options in a backup group if they may be needed later.

During a busy trial, count corrections and notice where staff have to scroll through irrelevant options. Put common swaps near the original item and simplify groups that slow entry without removing decisions needed to prepare the dish correctly.