Your menu is only as good as the choices customers can make against it. A café that sells a flat list of drinks online is leaving money and accuracy on the table: no oat-milk upcharge, no “extra shot,” no way to flag a nut allergy. Square handles all of this through modifiers — but a sloppy modifier setup produces confusing online menus, wrong orders, and kitchen tickets nobody can read. A clean one upsells automatically and keeps customers safe.
This guide walks through building modifiers, modifier sets, selection rules, and allergen information for Square online ordering, the way an operator should — so the menu reads clearly to customers, your kitchen, and the order ticket alike. It assumes you are running a café or restaurant on Square. If you haven’t switched online ordering on yet, start with our Square online ordering setup guide and come back here to make the menu actually good.
Modifiers vs. variations: get the model right first
Square gives you two ways to express choice, and mixing them up is the root of most messy menus.
- Variations are the core forms of an item, usually each with its own price and SKU — Small / Medium / Large, or Hot / Iced. A customer must land on exactly one variation; it is the thing they’re buying.
- Modifiers are customizations layered on top — oat milk, an extra shot, no whip, add caramel. They’re optional choices that adjust an item, not separate items.
Rule of thumb: if it changes what the item fundamentally is and its base price, it’s a variation. If it’s an add-on or tweak, it’s a modifier. Size is a variation. Milk type is a modifier.
Step 1: Plan your modifier sets before you touch Square
A modifier set is a reusable group of options — “Milk Choice,” “Syrups,” “Toppings.” The mistake is building them ad hoc, item by item, until you have five overlapping milk lists. Plan first. Write down the customization groups your whole menu needs:
| Modifier set | Example options | Required? | Selection rule |
|---|---|---|---|
| Milk choice | Whole, oat (+), almond (+), skim | Yes | Exactly 1 |
| Espresso shots | 1, 2, 3 (+per shot) | No | Up to 2 extra |
| Syrups | Vanilla, caramel, hazelnut (+each) | No | Up to 3 |
| Pastry add-ons | Butter, jam, warmed | No | Up to 2 |
Build each set once, reuse it everywhere it applies. One canonical “Milk Choice” set attached to every milk-based drink beats ten near-identical copies you have to edit one at a time when oat milk’s cost changes.
Step 2: Build the sets in your Item Library
In the Square Dashboard, go to Items & Orders → Modifiers and create each set with its options. The key move here is pricing the options that cost you more: put $0.75 on oat milk, $1.00 on an extra shot. Square adds these to the order total automatically at checkout, which turns every customization into quiet upsell revenue — no prompting from staff, no manual math. A café that prices its modifiers correctly captures margin on premium milks and add-ons it would otherwise eat.
Keep option names short and customer-readable. “Oat milk” not “ALT-MILK-OAT-002.” The customer sees these names; so does your barista on the ticket.
Step 3: Set min and max rules so orders are makeable
This is the step that separates a professional menu from a buggy one. Every modifier set lets you set a minimum and maximum number of selections:
- Milk choice: min 1, max 1 — the customer must pick exactly one, and can’t accidentally order two milks.
- Syrups: min 0, max 3 — optional, but capped so nobody orders a nine-syrup monstrosity your kitchen can’t price or make.
- Toppings: min 0, max 3 — same logic.
Required-but-single sets (min 1, max 1) are how you force a necessary choice without leaving it blank. Optional-but-capped sets keep customization from running away. Without rules, online customers will eventually submit a combination that’s unmakeable, mispriced, or both — and you only find out when the ticket prints.
Step 4: Attach sets to the right items — and only those
Apply each set only to items it actually belongs to. “Espresso shots” goes on coffee drinks, not on a muffin. Square lets you bulk-apply a set to many items at once, so attaching “Milk Choice” to every latte, cappuccino, and flat white takes one action, not twenty. Over-attaching is its own bug: a modifier that appears where it makes no sense confuses customers and produces nonsense tickets.
Step 5: Handle allergens and dietary info properly
Modifiers customize an order; allergen and dietary information keeps customers safe and informed. Square gives you two complementary tools:
-
Item-level fields. On each item, fill in the description and any dietary-preference and allergen fields Square offers (calories, dietary tags, allergens). This information surfaces to customers browsing online and to staff — on Square POS, staff can press and hold a menu tile to see an item’s description, dietary preferences, and allergens. Filling these fields moves allergy knowledge out of one barista’s head and into the system.
-
A text modifier for custom notes. Square supports two modifier types: list modifiers (preset options) and text modifiers (a free-text field). Create a text-based modifier so customers can type an allergy or substitution request your preset options don’t cover — “severe nut allergy, please use clean equipment.” Decide whether it’s optional, and make sure it prints to the kitchen ticket so it isn’t silently dropped.
A word of honesty: digital allergen fields are an aid, not a legal guarantee. They don’t replace staff training or your local food-safety obligations. But surfacing the information beats relying on memory during a rush, and a clear allergy-note field signals to customers that you take it seriously.
Step 6: Confirm channel and location visibility
Here’s the single most common “why is my menu broken” issue: a modifier set only appears where it’s assigned. In Square, sets are scoped to channels and locations. If a set isn’t enabled for the online ordering channel, or for the specific location selling the item, online customers won’t see it — even though the item itself shows up fine.
So after building everything, verify each set is turned on for online ordering at every location that needs it. Multi-location operators should be especially careful, since menus and availability can differ by store; our guide to multi-location mobile ordering on Square covers keeping those in sync.
Step 7: Place a live test order before going live
Never trust a menu you haven’t ordered from. Place a real online order for your most-customized item: pick a milk, add two syrups and an extra shot, type an allergy note. Then confirm three things:
- The price added up correctly — every paid modifier hit the total.
- The ticket printed clearly to the kitchen, with modifiers and the allergy note legible and not truncated.
- The rules held — you couldn’t break the min/max limits.
This five-minute test catches the errors customers would otherwise catch for you. For more on making sure online tickets reach the line cleanly during service, see managing online orders in a Square kitchen.
Common modifier mistakes to avoid
- Duplicate sets — five “Milk” lists instead of one reusable set. Edits become a chore and they drift out of sync.
- No selection rules — letting customers pick zero milks or ten toppings.
- Unpriced premium options — giving away oat milk and extra shots because the modifier option has no price on it.
- Allergy notes that don’t print — a text field the kitchen never sees is worse than none, because it implies the note was received.
- Forgetting channel visibility — building beautiful sets that never appear online because they’re not enabled for the ordering channel.
Where a branded app changes the equation
A clean Square modifier setup is the foundation, and it carries straight through to a branded ordering app, because the app reads the same Square Item Library — your modifiers, prices, and allergen fields live in one place and stay consistent across web, app, and counter. The upgrade an app adds is on top of accuracy: saved “usual” orders so repeat customizations are one tap, and a smoother customization flow than a generic web menu.
That’s the approach Tany takes — a branded iOS and Android order-ahead app built directly on your existing Square POS, so the menu you carefully set up here powers the app automatically, live in about a day for $99 CAD/month per location. Whether or not you add an app, the work is the same and worth doing: build modifier sets once, rule them tightly, price the premium options, surface allergens honestly, and test a real order before you trust it.