To set up menu modifiers in your POS, group every choice a guest can make (size, temperature, add-ons, substitutions, removals) into modifier groups, attach those groups to the right items, and give each option a price and a kitchen-ready name. Done well, modifiers cut order errors, capture upcharges you used to give away, and make tickets readable at a glance. Done badly, they slow servers down and clutter the kitchen printer.
What modifiers actually do
A modifier changes an item without creating a new one. A burger is the item; "medium rare," "add bacon," and "no onion" are modifiers. If you build a separate menu item for every combination, you end up with hundreds of buttons and reports that cannot tell you what is really selling.
Modifiers matter for three reasons:
- Accuracy. Required choices (like a steak temperature) cannot be skipped.
- Revenue. Priced add-ons turn "can I get avocado on that?" into a $2 sale.
- Data. You can see how often guests add, swap, or remove things, which feeds menu decisions.
Choose the right modifier types
| Type | Example | Price effect |
|---|---|---|
| Required choice | Steak temp, size | Usually none, sometimes +$ |
| Optional add-on | Extra cheese, side of bacon | Adds price |
| Substitution | Fries for side salad | Often +$1-$3 |
| Removal | No onions | None |
| Instruction | Allergy, "sauce on side" | None, prints in bold |
Keep removals and instructions free, but flag allergy notes so they print prominently. For more on handling dietary requests, see How to Handle Allergens and Dietary Labels on Menus.
Build modifier groups once, reuse everywhere
Create reusable groups instead of rebuilding choices for each item. A "Burger Temperature" group, a "Salad Dressing" group, and a "Premium Add-Ons" group can each attach to multiple items. Change a price in one place and it updates everywhere.
Set rules on each group
- Minimum and maximum selections. Require exactly one temperature; allow up to three add-ons.
- Defaults. Pre-select the most common option so servers tap less.
- Sort order. Put the most popular choices first.
Price add-ons to protect your margin
Free extras quietly erode profit. If extra cheese costs you $0.45, charge $1.50 or more. Review your add-on costs the same way you cost a plate; Calculating Contribution Margin Per Menu Item shows how to see what each add-on really earns. A group of premium add-ons can lift your average check noticeably on its own.
Takeaway: Every modifier your servers "just do" for free is margin you are paying for. Price it, track it, or take it off the menu.
Make tickets clear for the kitchen
A modifier is only as good as the ticket it prints. Use short, kitchen-friendly names ("NO ONION" rather than "Customer requests no onions"), group modifiers under the item, and print modifiers in a different style than the item name. If you use a screen, Kitchen Display Systems (KDS) Explained covers how to display them cleanly.
Test before service
- Ring in the five most complex orders on your menu.
- Check the ticket at the printer or KDS.
- Confirm pricing on the receipt.
- Have a server try it with no training and note where they get stuck.
Train staff using the steps in How to Train Staff on a New POS so everyone uses the same modifier names.
Use the data
After a month, run a modifier report. Which add-ons sell? Which removals happen constantly (a sign the recipe needs changing)? Which substitutions are free but costly? How to Use Sales Data From Your POS walks through the reports worth checking.
Cobblestone POS supports reusable modifier groups, required choices, and priced add-ons, and it is free for independent restaurants with no monthly fee, compared to the $470+ per month some competitors like Toast charge. That makes it an easy place to build a clean modifier structure and refine it as you learn what guests order.