Bad modifier setup quietly turns into remake orders
OmNom gives restaurants a direct ordering channel with zero commission and zero monthly platform fees. Standard Stripe processing still applies. That lower-cost setup matters, but the ordering flow still has to produce tickets the kitchen can trust.
Modifier groups are one of the first places that trust breaks.
If a customer cannot tell which choices are required, they guess. If the kitchen gets a ticket full of half-clear notes, staff guess too. That is how online orders turn into remake requests, front-counter clarifications, and small mistakes that eat time during a rush.
The goal of modifier setup is not to show every possible customization. The goal is to collect the choices the kitchen actually needs, price them clearly, and keep the order readable from checkout through handoff.
Start with kitchen decisions, not menu design ideas
The cleanest modifier groups usually come from one simple question: what does the station need to know before it can make this item correctly?
That answer is often more useful than a marketing-style menu brainstorm.
For a sandwich, the kitchen may need:
- bread choice
- side choice
- cheese add-on
- sauce selection
- no-onion or no-tomato style removals
For a pizza, the kitchen may need:
- size
- crust
- required topping rules
- premium topping charges
- half-and-half limits
For a bowl or salad, the kitchen may need:
- protein
- dressing
- add-ons
- allergy-sensitive removals
That is the right place to begin. If the kitchen would stop and ask a question before making the item, the menu should probably answer that question in a structured way.
Make required choices obvious and optional choices lightweight
Many bad tickets come from one specific problem: the customer does not realize a choice is mandatory until checkout is already confusing.
Required modifiers should feel impossible to miss. Optional modifiers should stay easy to skip.
That usually means:
- use required groups only for decisions the kitchen truly needs
- avoid burying required choices under optional upsells
- keep optional add-ons separate from yes-or-no production choices
- do not force customers through extra groups just because more options exist
If every item has six required groups, checkout starts to feel like paperwork. If nothing is required, customers fall back to notes and staff end up decoding intent later.
The best setup keeps that balance clear. Ask for the decisions that matter. Let the rest stay simple.
Limit modifier clutter before it reaches the ticket printer
A long modifier list can look flexible on the storefront and still be painful in real service.
When customers see too many overlapping choices, they slow down. When staff see too many near-duplicate options, they miss details or waste time double-checking what the ticket actually means.
A few practical cleanup moves usually help:
- merge duplicate choices that mean the same thing
- keep names short and literal
- separate removals from paid add-ons
- avoid stacking multiple groups that solve the same problem
- use quantity-based add-ons only when the kitchen can actually honor them consistently
This is especially important for mobile ordering, where modifier overload feels even heavier. A customer who wants to place a quick direct order should not have to decipher a form that feels more complex than the meal itself.
Use notes for edge cases, not for everyday customization
The notes field is useful, but it should not carry the whole menu.
If customers repeatedly type the same request, that is usually a sign the request should become a proper modifier instead. Structured modifiers are easier to price, easier to read, and easier to fulfill the same way every time.
Common examples include:
- sauce on the side
- no pickles
- extra cheese
- dressing choice
- spice level
- utensil requests
Notes still matter for unusual cases, but they should be the exception. If the standard order path depends on free-typing, the restaurant is asking staff to translate customer intent on every shift.
Price add-ons clearly so the cart total never feels random
Modifier pricing should be boringly clear.
If bacon costs extra, show it. If avocado is included only on one variation, make that obvious. If some substitutions are free and others are not, the menu should explain that through the option structure rather than leaving the customer to discover it at the final total.
This matters for two reasons.
First, customers are less likely to abandon checkout when the price change makes sense in the moment. Second, staff are less likely to override or adjust tickets manually when the modifier logic already matches the restaurant's real pricing rules.
With direct ordering, the restaurant owns that experience more directly. Clear modifier pricing helps the order feel fair before the customer pays and keeps the kitchen from re-litigating add-ons after the ticket prints.
Test modifiers from the kitchen side before pushing traffic
Before a restaurant sends customers to a new ordering page, it should read a few sample tickets exactly the way staff will.
Test at least:
- one bestseller with no changes
- one item with required choices
- one item with paid add-ons
- one item with a removal plus a substitution
- one multi-item order that touches several stations
Then ask:
- can the kitchen make this without a follow-up question?
- are paid add-ons obvious?
- do modifier names sound like the way staff talk internally?
- would anyone need to read the notes field to understand a normal order?
If the answer is yes to that last question, the setup probably needs another pass.
This is also a good point to review the rest of the menu structure. If you have not done that broader pass yet, start with the Restaurant Online Ordering Menu Checklist. If your handoff timing is the bigger problem, read Restaurant Online Ordering Prep Times.
Where OmNom fits
OmNom is a strong fit for restaurants that want direct online ordering without another commission layer sitting on top of each order. Restaurants pay no OmNom commission and no monthly platform fee. Standard Stripe processing still applies.
That simpler cost structure gives operators more room to focus on the setup details that actually decide whether online ordering feels reliable. Modifier groups are one of those details. When they are clean, customers move through checkout faster and staff spend less time fixing avoidable mistakes.
OmNom can also help with free menu setup, which matters because modifier cleanup is usually easier with a second set of eyes before launch. If you want a direct ordering page that is easier for both customers and the kitchen to use, start from OmNom or browse more operator guides on the OmNom blog.