Updating Your Menu During Peak Hours: How to Make Instant Changes

Saturday 13:15. The kitchen calls — the avocado for today's special salad just ran out. With paper menus, your only option is sending servers to all 80 tables one by one. With a digital menu, "Mediterranean Avocado Salad" disappears from every table in 30 seconds. Done right, updating your restaurant menu in real time saves both inventory and the guest experience. Done wrong, it turns into chaos.

Sold-out tags: the most common and most critical use

The single most frequent peak-hour operation is taking an item out of stock. Don't delete it from the category — that breaks ordering when you re-add it tomorrow. Most modern admin panels offer two options:

1. Hide item — removes it from the menu entirely. Guests never see it.
2. "Sold out" badge — item still visible but unorderable, signalling "we're out today, come back".

Use the sold-out badge if you'll reopen by dinner. Use hide for longer absences. Edge case: a guest added the item to cart 30 seconds before you toggled — server-side recheck at checkout returns "this item is no longer available", and the cart updates gracefully.

Price changes during peak: handle with care

Raising prices mid-rush erodes trust. Golden rule: update between shifts (say 16:00-17:00), never during service. If forced (supplier crisis), tell the cashier first — if a guest ordered at the old price, honor it.

Technically: platforms like thMenu enforce a server-side canonical price. New orders use the new price, but a guest who already has the item in cart sees the original snapshot. Only a page refresh shows the new price. That cushions the experience.

Adding new items: prep ahead

Don't add new items live during service. Draft them the night before — title, description, photo, price, allergens, category. The item stays unpublished until you flip the switch. Publish at 11:00, brief the kitchen, no service surprises.

The real peak-hour need is daily specials. Keep a draft slot in a "Specials" category and only update its content, then publish. Takes under a minute.

Cache and client-side sync

How fast does the menu actually refresh on the guest's phone? Depends on CDN TTL, Service Worker strategy, and how long the page has been open. PWA-backed systems like thMenu use stale-while-revalidate — guests see the cached version first while a fresh one fetches in the background. In practice: 15-45 seconds to propagate.

Zero-delay scenarios (hotels with international guests, for example): trigger a soft cache purge from the admin panel. The CDN flushes instantly. Do this once or twice a day max — over-purging hurts cold-start performance.

Found this helpful? Share it.