Audit Restaurant Modifiers to Raise Online Order Value

Start with the decisions guests actually make

A modifier is useful when it helps a guest customize an item without changing what the item fundamentally is. Square's seller documentation describes modifiers as options such as toppings, add-ons, and special requests, with rules that can control how many choices a buyer may select. That is a useful audit lens even if your restaurant uses another POS or ordering platform.

Walk through the ordering path as a first-time guest. Every required choice should answer a real kitchen or service question. Every optional choice should be easy to understand without opening extra screens or guessing whether it changes the price.

• List the five items that receive the most online orders.
• Mark each choice as required, optional, or unnecessary.
• Flag vague labels that a new guest or new employee could interpret differently.

Separate sizes from true add-ons

Square distinguishes variations from modifiers: variations are fixed forms of an item, such as small or large, while modifiers customize the sale, such as adding cheese to a burger. Keeping that distinction clear can make the menu easier to maintain and the order easier to read.

Use a variation for the version the guest is buying. Use a modifier for what the guest wants added, removed, substituted, or prepared differently. If the same choice appears as both, clean up the duplicate before trying to promote more add-ons.

• Variation: size, portion, or another fixed version of the base item.
• Modifier: topping, sauce, preparation request, substitution, or paid add-on.
• Separate item: a product the kitchen and reporting should treat independently.

Put useful choices in a helpful order

Square documents item-level control over modifier-set order across POS modes, kiosk, and online ordering. Platform details vary, but the operating question is universal: does the sequence match how a guest builds the meal and how the kitchen prepares it?

Place required decisions first, then the most relevant optional additions, followed by less common requests. A burger flow might move from doneness to cheese, then toppings, sides, and sauces. The goal is not to hide a charge or pressure the guest. It is to surface a useful choice at the moment it makes sense.

• Keep the same logical sequence on staff POS and guest-facing ordering when possible.
• Place common paid add-ons beside the item they improve, not in a distant catch-all list.
• Keep allergy and preparation choices clear and separate from promotional extras.

Review defaults, limits, prices, and availability

Square's modifier controls include online visibility, default selection, stock status, required-choice rules, multiple-selection settings, and minimum or maximum selections. Do not assume every platform exposes the same controls; use the list as a checklist for your own system.

A required rule should prevent an incomplete order, not force an unrelated purchase. A default should never create a surprise charge. Limits should reflect what the kitchen can produce and what the item can reasonably hold. When an option sells out, remove or clearly disable it instead of letting the guest order something the restaurant cannot fulfill.

• Confirm every paid choice shows its price before the guest commits.
• Check that minimum and maximum rules allow every legitimate order.
• Test sold-out behavior on the real guest-facing channel.
• Remove old modifiers rather than leaving staff to interpret them.

Make the guest screen and kitchen ticket agree

Square says modifiers can appear on order tickets, customer receipts, the item library, and sales reports, and that modifier sets can be assigned by location and channel. That makes cross-channel readback part of the audit, not an afterthought.

Place a disposable test order on each active path: web, app, kiosk, delivery marketplace, and staff POS where applicable. Stop before payment when the channel permits; otherwise use an authorized low-risk test and void it correctly. Confirm the guest label, price, kitchen ticket, receipt, and reporting label all describe the same choice.

• Verify the correct restaurant location and menu are active.
• Compare guest-facing wording with kitchen-facing wording.
• Confirm the same add-on does not carry different prices by accident.
• Check that reporting can identify the modifier without manual decoding.

Run one measurable modifier test

Choose one popular item with a confusing or underused modifier set. Record a clean baseline, change one guest-facing variable, and leave the rest of the item alone for a defined test period. That makes the result more useful than changing names, prices, order, and photography all at once.

Compare modifier attachment, revenue per item, cart completion where available, and operational signals such as remakes, refunds, and staff questions. A change in one metric does not prove the modifier caused it, so also note promotions, traffic mix, outages, and menu changes during the test. If the ordering path becomes clearer without creating kitchen problems or guest surprises, expand the approach carefully.

This workflow fits naturally with the Restaurant Tech Report's Average Spend, Menu Secrets, Customer Growth, and Resources guides: use the POS as a measurement tool, but judge the decision by the complete guest and kitchen experience.

• Baseline: current attachment rate and revenue per item.
• Change: one label, sequence, default, or visibility rule.
• Guardrails: completion, remakes, refunds, and staff confusion.
• Decision: keep, revise, or reverse based on the full evidence.

FAQ

Sources and further reading

• Create and edit modifiers | Square Support Center

Related reading

• Featured businesses
• Stories archive
• Request a feature