Operations Guide
How to Structure Restaurant Menu Modifiers
Last updated: August 2026
Modifiers are where a menu stops being a list and becomes a system: every no-onions, extra-spicy, and substitute-fried-rice travels through them. Structure them well and orders move fast and print unambiguously. Structure them badly and every rush produces remakes, voids, and a kitchen guessing what the server meant.
The concepts below are vendor-neutral — every serious POS has them under some name. The guide ends with the test that matters most in 2026: whether your modifier structure is precise enough for software, not just staff, to take orders through it.
Variants and Modifiers Are Different Things
Variants change what the item is
Size and portion — Small or Large, lunch portion or dinner portion. A variant carries its own price and usually its own kitchen meaning. The test: if choosing between the options changes the base price of the dish, it is a variant, not a modifier.
Modifiers change how it is made
Additions, removals, and preparation: no scallion, extra sauce, steamed instead of fried. Modifiers attach on top of whichever variant was chosen, and each one either prints as an instruction or prices as a change.
Why the split matters
Reports stay truthful — item sales group by the dish, not by twenty name-variations of it. And every ordering channel (online, kiosk, AI phone) needs to know the difference between a question that must be answered — which size? — and options that may be added.
The Four Decisions in Every Modifier Group
A modifier group is a question the order-taker asks. Four properties define every group, whatever your POS calls them:
- -Required or optional — must the question be answered before the item can be rung (choice of rice), or may it be skipped (add-ons)?
- -Single or multiple — pick exactly one (spice level), or several (toppings)?
- -Minimum and maximum — a choose-2-rolls combo is min 2, max 2. Combo logic belongs here, not in item names.
- -Price behavior — each option is free, an upcharge, or occasionally a credit. Price lives on the option, never baked into duplicate item names.
The No / Extra / Add Pattern
Ingredient-level changes read cleanest as one ingredient with three verbs:
One ingredient, three verbs
No X removes it (usually free). Extra X doubles down on it (often charged). Add X introduces it to a dish that does not normally carry it (charged). The kitchen reads the verb first, so tickets stay scannable at speed — and the same three verbs translate cleanly onto bilingual tickets.
Why not free-text notes
A typed note cannot carry a price, cannot be pre-translated for a bilingual kitchen ticket, and is invisible to ordering software — no kiosk, online checkout, or phone AI can act on it. Keep notes for the genuinely one-off; everything guests ask for weekly deserves an option.
A Real Menu, by the Numbers
382 items, 17 groups, 160 options
One real hibachi-and-sushi menu we imported resolves 382 items across 40 categories into just 17 modifier groups holding 160 options — spice levels, protein choices, choose-2-rolls combos — reused across the whole menu. That is the shape to aim for: groups are shared infrastructure. If you find yourself building three hundred groups for three hundred items, the structure is missing.
Scope groups deliberately
Attach a group to categories where possible and to specific items where needed — and never leave one unscoped. A group that applies to everything is almost always a bug: we have watched a children's hibachi plate offer choose-3-rolls because a combo group lost its item list on import.
The 2026 Test: Can Software Order Through It?
Your modifier structure is the AI's vocabulary
An AI phone agent can only capture what the menu encodes. When a caller says no scallions, the agent needs a No Scallion option to select; if removals exist only as typed notes, the request cannot be taken reliably by software at all. The same encoding is what lets a kiosk ask required questions and an online checkout suggest add-ons — one structure, every channel.
The audit
Take your twenty best-selling items and ask, for each: can every request guests actually make be expressed by tapping options alone, with no typed note? The share that can is your automation ceiling — for phone AI, kiosks, and online ordering alike.
Ginger's POS, kiosk, online ordering, and AI phone ordering all run on one modifier encoding — set it up once (AI menu setup does the first pass in about 30 minutes from your menu file) and every channel, including the phone, orders through it. How AI phone ordering uses it
Frequently Asked Questions
What is the difference between a variant and a modifier?
A variant changes what the item is — size, portion — carries its own price, and must be chosen. A modifier changes how the item is made — additions, removals, preparation — and attaches on top of the chosen variant. The quick test: if picking between the options changes the dish's base price, it is a variant.
Should modifier groups be required or optional?
Required when the kitchen cannot proceed without an answer — rice choice on a combo, temperature on a steak, size where there is no default. Optional for genuine extras. Marking a group required is what lets every ordering channel — staff, kiosk, online, phone AI — refuse an incomplete order instead of sending the kitchen a guess.
How should restaurant modifiers be priced?
Price on the option, not the item name. The common convention: removals (No X) free, doubling an included ingredient (Extra X) charged, introducing a new ingredient (Add X) charged, and premium substitutions carried as an upcharge on the substitution option. Duplicating items with edited names to carry prices breaks reporting and every automated channel.
Why should restaurants avoid free-text order notes?
A typed note carries no price, cannot be pre-translated for bilingual kitchen tickets, prints inconsistently, and is invisible to ordering software — kiosks, online checkout, and AI phone agents cannot act on it. Notes belong to genuinely one-off requests; anything guests ask for regularly should become a real option.
How do menu modifiers affect AI phone ordering?
They are its vocabulary. A phone agent maps what the caller says onto the options the menu encodes — no scallions works because a No Scallion option exists to select. Menus that lean on typed notes cap what any AI can capture, whatever the vendor demo shows. The audit: if your top items can be customized by options alone, they can be ordered by software.
Want the Setup Done for You?
Send us your menu and AI menu setup builds the first pass — items, variants, and modifier groups — in about 30 minutes. Every Ginger channel, from the POS to the phone AI, orders through the same structure.
© 2026 Ginger. Free restaurant POS with built-in AI phone ordering.