A modifier that becomes compulsory on one ordering channel can turn a simple menu change into an ordering problem. To set up menu modifiers in Square, create a modifier set in Dashboard, define its choices and selection rules, assign locations and channels, then apply it to the intended items.
Check the item as well as the shared set before changing a rule. Square’s current US guidance says item-level customizations become independent of later set-level changes until reset. The worksheets below help you record the intended rule, decide whether an exception should remain, and follow a trial order through to the kitchen. They are proposed operating checks, with blank results for your restaurant to fill.
Browse the operational guides for related workflows. If the unresolved question is whether a size should be a variation or a modifier, start with items, variations and modifiers.
Create the set, then check its assignment
Use Dashboard’s Items → Modifiers area to create or edit the set. Add choices, review selection rules, save, and apply the set to items. Check location and channel assignments: an unassigned channel will not show the set to buyers. Dashboard navigation names can vary. See Square’s modifier instructions.
Start with one dish before applying changes across a menu. Write its intended guest choice in ordinary language, then translate that into settings. For example, “Guests may leave off all toppings” and “Guests must choose a side” describe different rules even when both groups contain several choices.
Record the item name, set name, location, channel and date alongside this worksheet. The examples below are proposed menu rules, not software defaults or observed account settings.
| Rule to record | Example intention | Your chosen value / evidence |
|---|---|---|
| Required or optional | Toppings may be skipped | |
| Minimum selections | Zero toppings are acceptable | |
| Maximum selections | No more than two different toppings | |
| Repeat quantities | Decide whether two portions of the same topping are allowed | |
| Default choice | Decide whether any topping starts selected | |
| Price effect | Record the approved charge or no-charge treatment | |
| Visibility | List the locations and ordering channels that should show the set | |
| Item exception | Record why this dish should differ from the shared rule |
Separate selection counts from repeat quantities
A maximum number of choices and permission to repeat one choice answer different questions. Square’s Catalog API documentation distinguishes minimum and maximum selection fields, repeat-quantity permission, and preselected options. Its examples include an optional set that allows repeated additions. These API concepts explain what to inspect; they are not instructions to enter API values into Dashboard.
For your trial, attempt both “croutons plus herbs” and “croutons twice.” Write the expected outcome before trying either. Also attempt to continue without choosing anything. A preselected choice can conceal a required-selection rule, so remove that choice during the check if the interface permits it.
Follow the override and reset decision path
Open the item’s modifier set and inspect Customize before editing the shared set again. Square documents Reset customizations as the route back to shared behavior. Reset only after deciding that the item’s exception is no longer wanted; see the item-level customization section.
Use this branching path to decide where to act. Save the current values before a reset so the menu owner can reconstruct a legitimate exception.
| Check | If yes → next action | If no → next action |
|---|---|---|
| Is this the correct item, set, location and channel? | Inspect the item’s customizations | Find the affected record first |
| Does the item have a deliberate exception? | Keep it; edit and document the item rule | Decide whether shared behavior is intended |
| Should the item follow the shared set again? | Record current values → reset customizations → inspect resulting values | Retain the exception and record its owner |
| Does the saved rule produce the intended order? | Repeat on the other intended channels | Return to the first point where expected and observed behavior differ |
Avoid bulk-resetting the menu to fix one dish. A useful comparison is another item using the same set: record both items’ values, then investigate the difference. This is a diagnostic suggestion, not proof that any particular customization caused the problem.
If Bopple makes an optional choice compulsory
Inspect the imported rule in Bopple Back Office → Menu → Modifiers. Bopple’s integration guide describes an unwanted minimum-one/maximum-one rule imported from Square. Its remedies depend on whether the single-choice maximum is needed: remove that restriction if unnecessary, or customize the item’s minimum while retaining the required maximum, then import the menu again.
That guidance uses older setting labels. Compare the meaning with your current interface before changing anything. Treat it as a Bopple-specific troubleshooting path; it does not establish how another delivery connector imports rules. Record the import time and recheck the guest-facing menu after the import.
Run the same scenarios through every ordering route
Use the matrix to record observed behavior separately for each channel and output. A correct POS screen is only one checkpoint. Use your normal approved test-order procedure and retain an order reference; this article contains no completed transactions or channel test results.
For each ordering route, attempt these scenarios on the same trial dish:
- Skip an optional set and continue.
- Leave a required set incomplete and try to continue.
- Choose the intended maximum, then attempt one more selection.
- Attempt a repeat quantity where the menu allows one.
- Remove or change a default, then inspect the cart and kitchen output.
Write the intended rejection or accepted choice in advance. Use Unknown / verify on the unit when a check cannot be completed, and “Not used” for channels your restaurant does not operate.
| Route or output | Expected rule / display | Observed result | Order or screenshot reference |
|---|---|---|---|
| Staff POS, with device and operating mode | |||
| Square website, guest-facing item and cart | |||
| Each delivery integration, named separately | |||
| Kitchen display, tied to the originating order | |||
| Printed kitchen ticket, if used | |||
| Customer receipt, according to intended visibility |
Do not diagnose a receipt omission solely from the screen: Square offers receipt-hiding controls. It also documents a separate kitchen modifier order under Restaurant Plus, so compare kitchen sequencing independently of POS sequencing. Verify the subscription and available controls in your account. Square’s display guidance describes those conditions.
Have the person preparing the dish read back the selected changes from the actual output. Record missing choices, ambiguous names, repeated additions and a sequence that is awkward to follow. Keep these observations tied to the order reference rather than rewriting them from memory. For the wider packing and handoff check, use the delivery menu item trial.
Check nested choices and reports separately
An old feature-request thread cannot establish today’s nested-modifier behavior. Square now documents nesting with channel-dependent display. Check the actual ordering route before relying on it. Current modifier documentation is the starting point.
For a nested trial, write both the parent choice and the child choice in the expected-result column. Then follow that exact pair into the kitchen output and reporting. Do not mark the whole chain complete merely because the second choice appeared while ordering.
Square’s modifier sales reporting guidance labels nested reporting as beta and says selections are listed individually without their parent-child relationship. It also notes that renamed items or modifiers become separate reporting entries. Preserve the tested names and record the date and location filters when reviewing the trial. A count of a child choice alone does not establish which parent choice it accompanied.
Keep a change record for the next menu edit
Save the intended rule, actual settings, exception decision, import time where relevant, and completed order matrix together. Assign an owner to unresolved cells before expanding the change to other dishes. Reuse the matrix after a shared-rule edit or connector import so that a previous pass does not stand in for the current menu.
Method and sources
This independent editorial guide uses Square’s US support documentation, Square’s Catalog API documentation and Bopple’s own integration guidance, read 16 October 2026. The rule worksheet, branching decision path and blank order matrix are editorial tools for your own checks. We did not access a merchant account or test POS, delivery or kitchen devices. Interface labels, account availability and connector behavior need checking where the menu is used. See menu planning for related guides.
