How to Import Modifiers, Sizes, and Add-Ons Correctly

Menu migration gets complicated fast when an item has sizes, extras, combo choices, or special pricing. If you import menu modifiers without a clear structure, guests hesitate, staff guess, and your online ordering flow creates avoidable mistakes. This guide shows you how to set up modifier groups, sizes, and add-ons so ordering feels simple for customers and fulfillment stays accurate during busy service.

Map the ordering logic before you import anything

The biggest menu migration mistake is copying the visual layout of a PDF instead of the way an order actually gets placed. A printed menu might show notes under an item, symbols next to prices, or multiple size options in one line. Online ordering needs something more precise: a clear set of choices, rules, and prices that a guest can complete without asking for help.

Before you set up a single modifier group, think about what your staff asks at the counter or over the phone. Is size required? Can the guest pick one side or two? Are add-ons unlimited, capped, or only available for certain versions of the item? When you answer those questions first, your digital menu becomes easier to import and far easier to use.

This is where AI-powered import helps, especially if you are moving from a PDF or older file. EasyMenus can extract items, prices, and categories from uploaded menus with 99% accuracy, but operators should still review the tricky logic around options, combos, and upsells. Clean menu data is not just about speed. It is about making sure every item can be ordered correctly.

What to identify on every item before setup

For each item, confirm five things: the base item name, whether a choice is required, whether multiple choices are allowed, whether any option changes the price, and whether the option applies to dine-in, pickup, delivery, or all service modes. A pasta dish with a required size and optional protein add-on should not be built the same way as a combo meal with one included side and one paid upgrade.

Quick prep checklist for menu migration

Use this checklist before import: 1) mark which items have sizes, add-ons, or combo choices; 2) separate required choices from optional extras; 3) note minimum and maximum selections for each group; 4) flag any price differences by size or option; 5) remove vague notes like "extras available" and replace them with exact choices. This prep work makes your restaurant menu add-ons setup much faster.

For a comprehensive overview, see our guide: AI Menu Import for Restaurants: PDF, Photo, and Existing Menu Migration Guide

Related: Import a Restaurant Menu from PDF Without Retyping Every Item

Build modifier groups that are easy to choose

A good modifier group online ordering setup should answer one question at a time. Guests should see clear group labels such as "Choose a Size," "Pick Your Side," or "Add Extra Toppings." If a group mixes different decisions together, people slow down or order the wrong thing. Keep each group focused on one type of choice.

The structure matters just as much as the wording. Required groups should force a selection before checkout. Optional groups should stay skippable. If a guest can only choose one option, set the group as single-select. If they can choose several, set a maximum that matches real kitchen policy. That keeps orders realistic and prevents tickets like five free sauces on one sandwich because no limit was set.

Single-select vs. multi-select rules

Use single-select groups for choices where only one answer is valid, such as size, cooking temperature, or one included side. Use multi-select groups for extras like toppings, sauces, or added proteins. Be careful with groups that look optional on paper but are required in practice. If your team always has to ask "white rice or fries?" then that is a required group, not an optional note.

Checklist for clean modifier group setup

For each group, write a clear group name, decide whether it is required or optional, set the minimum and maximum selections, add only relevant choices, and test the group on mobile. If the item has several groups, place them in the order a guest thinks: size first, included choices second, paid extras last. That sequence reduces confusion and increases completion.

Photo by Clay Banks on Unsplash

Handle sizes, combos, and pricing rules without conflicts

Sizes are one of the most common failure points in menu import. Many restaurants store them inconsistently in source files: small and large versions as separate lines, half and full portions inside the item name, or prices buried in a note. Pick one structure and use it consistently across the menu. That helps both guests and staff understand your menu sizes and options restaurant setup at a glance.

Pricing rules need the same discipline. If the base burger is $10 and cheese is a $1 add-on, that is straightforward. But if a large pizza already includes a higher base price, do not also add a hidden size surcharge somewhere else. The cleanest menus make every price change visible and predictable. When combo logic, upgrades, and extras overlap, confusion turns into refund requests, missed modifiers, or kitchen remakes.

Two reliable ways to structure sizes

Method one is a single item with a required size group, which works well for pizzas, coffees, wings, and dishes with clearly shared descriptions. Method two is separate items for each size, which works better when the ingredients, photos, prep time, or included options change a lot between versions. Choose one method per category where possible. Mixing both methods inside the same section makes the menu harder to scan.

Pricing rules to test before publishing

Run through these checks: does each required size show the correct price; do optional add-ons stack correctly; are combo upgrades priced only once; are included choices clearly labeled so guests do not think everything costs extra; and do taxes and totals look right at checkout. A good rule is simple: if staff cannot explain the final price in one sentence, the setup is too complicated.

Name options the way guests and staff actually use them

Clear naming prevents ordering mistakes. Modifier labels should be specific enough for guests and operational enough for staff. "Add Cheese" is better than "Cheese." "Choose 1 Side" is better than "Sides." "Large +$3" is better than just "Large" if the price changes. The goal is to remove guesswork before the order reaches the kitchen.

This matters even more if you serve tourists or multilingual customers. EasyMenus supports menus in 16 languages with AI translation and full editing control, which is useful when you want your modifier groups to stay understandable across languages. But translation works best when your source naming is already clean. Short, direct labels translate better than internal shorthand or inconsistent abbreviations.

Examples of better modifier naming

Instead of "Extras," use "Add Extra Toppings." Instead of "Protein," use "Choose Your Protein." Instead of "Sauce," use "Pick Up to 2 Sauces." Instead of "Meal," use "Make It a Combo." These small changes help guests understand what they are choosing, how many selections they can make, and whether a price change is involved.

When to split a modifier into a separate item

If an option changes the product too much, it may be better as its own item. For example, a lunch combo with a drink and side may deserve its own listing instead of being buried as a modifier under a single sandwich. The same is true when prep time, packaging, or kitchen routing changes significantly. Separate items can be cleaner than overly deep modifier trees.

Test the full ordering flow before you publish

Even a well-structured menu can break at the last mile if nobody tests it like a real guest. Open the item on mobile, select options in the wrong order, try to skip required groups, add the maximum number of extras, and place test orders for dine-in, pickup, and delivery if you offer all three. Your goal is to catch friction before customers do.

This is also the moment to involve operations. Ask a manager, cashier, and kitchen lead to review a few representative items. They will quickly spot missing combo choices, unclear labels, and unrealistic add-on limits. Once you publish, real-time updates matter because issues show up during service, not in a planning meeting. With EasyMenus, you can edit menu structure and push changes live in seconds, which helps you fix problems without waiting on a developer.

Pre-publish QA checklist

Test one item from every category. Confirm required groups cannot be skipped. Confirm optional groups can be skipped. Check that min and max selections behave correctly. Verify that size pricing, combo pricing, and add-on pricing all total correctly in the cart. Read the item page as if you were a first-time guest, not the person who built it. If any step feels unclear, simplify the setup.

What to fix immediately after launch

Watch for customer questions, abandoned carts on complicated items, and staff feedback during peak hours. If the same question comes up twice, the modifier naming or structure probably needs work. Tighten labels, remove unnecessary choices, and separate items that create too many exceptions. The best online menus are not the ones with the most options. They are the ones with the clearest path to an accurate order.

Photo by Pylyp Sukhenko on Unsplash

Related: How to Clean Up AI-Imported Menu Data Before You Publish

Conclusion

If you want to import menu modifiers correctly, start with ordering logic, not formatting. Clean modifier groups, consistent size rules, and transparent pricing make it easier for guests to order and easier for your team to fulfill every ticket accurately. When your online menu mirrors the way your restaurant actually operates, you reduce friction, protect margins, and create a better guest experience from the first tap to the final handoff.