Options and modifiers are menu information that helps a guest decide what to ask for. They are not an online ordering cart, a kitchen ticket or a POS handoff. A useful digital menu lets someone see the base item, its listed variations and the information that affects the visit without sending them to the host stand to decode a vague label.
What should a guest see beside a menu variation?
Start with the public information, not the field name in a menu editor. A guest needs to know what the item is, what the variation means, whether it is currently available and whether its published price differs.
| Information to publish | What it clarifies for the guest | Who should verify it |
|---|---|---|
| Base item | The dish, drink or item being described | Menu owner |
| Variant or add-on | What changes in the published item | Kitchen lead and menu owner |
| Exclusion or substitution | What the menu says is omitted or replaced | Kitchen lead |
| Availability note | Location, service period or current limitation | Shift lead |
| Surcharge | Which listed variation carries the different price | Menu owner |
This prevents a common gap: a group called “customize” appears on the page, but nobody outside the restaurant can tell what the menu actually means by it.
1. Separate variants, add-ons and availability notes
Begin with the base item as the guest sees it. Then separate the information that describes a version of the item from information about an add-on, removal or substitution. A size, a side and a preparation note answer different questions. Combining them into one long label makes the menu harder to scan and leaves room for the team to interpret it differently.
Keep availability separate as well. If a variation applies only at lunch, only in one location or only while a named ingredient is available, say that beside the relevant item. Do not use an old screenshot or a staff chat as the source of truth. The kitchen or service owner confirms the current scope; the menu owner publishes that confirmed information.
2. Name information the way a guest would read it
Use a label that works without restaurant context. “Includes one side” or “Extra avocado” is clearer than a generic internal group name. Spell out a limit when one applies. If a variation is unavailable, say so in words rather than relying on a muted photo, an icon or colour alone.
The W3C guidance on labels and instructions offers a practical check: the label should explain the information before someone needs to ask a question. Clear wording helps a guest who is reading quickly on a phone and helps the team point back to one public source.
3. Put a surcharge beside the variation it describes
When a published variation has a different price, show the difference next to that variation. A guest should not need to infer that an extra, side or substituted ingredient changes the displayed price. This is a clarity rule for the page, not a claim about a live cart total.
The FTC’s advertising guidance is a useful general reminder to keep public-facing claims clear and supportable. The restaurant digital menu price update checklist covers the separate operational review after an approved price changes; do not turn this modifier guide into a second price-change procedure.
4. Make unavailable variations unmistakable
Do not leave a listed variation looking current when the restaurant cannot offer it for the named service. Remove it where that makes the menu easier to read, or place a plain-language unavailable label beside it when the context still helps a guest decide. A generic “ask staff” note is not a substitute for current information.
The sold-out item process handles the distinct work of removing, checking and restoring an unavailable item or variation. This guide stays focused on the information architecture: how the public page makes the current state understandable.
5. Review scope by item, location and service
Before publishing, name the item, location and service period affected by the change. A brunch variation at one location can be irrelevant at another location’s evening service. A short note for the team can record what changed and who confirmed it; it does not need a guest name, phone number or order detail.
Open the same public menu a guest sees on a phone. Read the base item, every listed variation and any availability note without relying on staff knowledge. Confirm that the labels and surcharge are visible, the location is correct and the page does not imply an ordering or stock capability it does not provide.
6. Keep one current answer for the team
The handoff can be brief: what item changed, which public link or QR code is current and who can confirm an exception. A host, server or counter lead should not invent a substitute or a menu claim just to answer quickly.
Review these details with the broader restaurant mini-site content checklist when the same guest journey includes hours, location or a waitlist. StoveOps can provide a public mini-site carrying a digital menu and waitlist form alongside the restaurant’s existing POS or checkout stack. The restaurant remains responsible for every guest-facing menu statement; current plan information is on the pricing page.
A six-point review before service
- Does the base item have a clear, guest-facing description?
- Are variants, add-ons and exclusions separated instead of blended into one label?
- Is each surcharge beside the variation it describes?
- Does the page say plainly when a variation is unavailable or limited?
- Are location and service-period differences visible where they matter?
- Does the team know which public menu source answers a question today?
This small review keeps the digital menu in its proper role: a clear source of information that helps a guest decide before the conversation reaches the dining room.