Demo business - no real orders or payments. This is a fictional sales demo, not an operating restaurant.

Read-only menu editor preview

Read-only menu editor preview

Show how an owner-facing menu detail could organize a flagship item, photo readiness, availability labels, and modifier sections after a future production scope is approved.

Generated demo mixed platter with chicken, lamb-style pieces, falafel, yellow rice, salad, hummus, and white sauce

Platters

$13.95

Representative owner-side detail for one static menu item. The future production version would need authorization, validation, and audit history before staff can change any value.

Preview-only labels

Readiness snapshot

Availability
Visible in demo menuPreview only; no storefront setting is stored.
Photo readiness
Photo slot readyUses the existing demo image slot.
Modifier readiness
Modifier groups mappedRead-only structure for sauces, spice, extras, and base.
Preview-only availability labelPreview-only price displayPreview-only photo readiness

Configurable sections preview

Read-only modifier groups

Single choice; 1 required

Rice & salad preference

Yellow rice with saladRice onlySalad bowlHalf rice, half fries
Future adapter: menu modifier group and option records.

Choose 1-3 preview options

Sauces

White sauceHot sauceGreen herb sauceBBQ drizzleSauce on the sideNo sauce
Future adapter: menu modifier group and option records.

Single choice; 1 required

Spice level

No spiceMildMediumHotExtra hot
Future adapter: menu modifier group and option records.

Choose 0-4 preview options

Extras

Extra proteinExtra white sauce cupExtra hot sauce cupWarm pitaAdd bottled drink
Future adapter: menu modifier group and option records.

Future production scope

What an owner could change later

  • Future production scope could allow authorized price, availability, category, and tag changes.
  • Modifier rules would need server validation and audit history before owner access.
  • Photo changes would need approved media storage, licensing checks, and rollback behavior.

Static boundary

  • A real menu editor would require authenticated staff roles and server-side authorization.
  • Price and availability changes would need validation, audit events, and staged release rules.
  • Photo handling would require a media policy before uploads or owner-managed assets exist.
  • This preview does not contain text inputs, uploads, forms, storage, or publishing behavior.