How to Handle Menu Item Availability in Real Time with a Digital Menu

The Real Cost of a "Sold Out" Surprise

A guest scans your QR code menu, spends three minutes deciding on the pan-seared salmon, flags down a server, and then hears: "Sorry, we're actually out of that tonight." That moment—small as it seems—chips away at trust. The guest feels misled. The server feels awkward. And the table's energy drops right before the order is placed.

In kitchen shorthand, "86ing" an item means it's gone. The problem is that in most restaurants, the only people who know an item is 86'd are the people in the kitchen. Guests reading a printed menu—or a static PDF menu—have no idea. The result is a gap between what guests expect and what you can actually deliver.

A well-managed digital menu closes that gap. When you can update availability in seconds from any device, guests only ever see what you can actually make. This guide walks through exactly how to set that up and maintain it across a real service shift.

Why Printed and PDF Menus Fail at Availability

Printed menus are static by design. Once they're laminated and on the table, there's no practical way to reflect that you ran out of short ribs at 7:45 PM on a Friday. PDF menus shared as QR codes are only marginally better—you'd have to re-upload the file, regenerate the code or update the link, and hope the browser cache clears. In practice, almost nobody does that mid-service.

The workarounds restaurants typically use—verbal announcements, handwritten table tents, servers memorizing the 86 list—all introduce human error. A server forgets. A new table sits down after the announcement. A guest orders online and the item is already gone.

If you're still relying on a static PDF, it's worth understanding what a proper QR code menu looks like compared to a PDF link—the difference in flexibility is significant.

What "Real-Time Availability" Actually Means in Practice

Real-time availability doesn't require a complex inventory system. For most independent restaurants, it simply means:

• An item can be hidden or marked unavailable in under 60 seconds from a phone or tablet, without logging into a desktop or calling a developer.
• The change is immediately visible to guests scanning the QR code or visiting the menu link—no cache issues, no refresh required.
• The item can be just as easily restored when stock is replenished or when the next service period starts.

That's the bar. It's achievable with the right platform and a small process change at the start and end of each shift.

Setting Up Your Menu for Fast Availability Changes

Use a live, hosted menu—not a file

The foundation is a menu that lives on a server and updates instantly when you make a change. With a hosted online menu maker, every change you save is reflected immediately for anyone who opens the menu link. There's no file to re-upload and no QR code to reprint.

Structure your menu with availability in mind

When you first build your menu, think about grouping items in a way that makes toggling availability easy. Practical tips:

• Keep daily specials and limited-quantity items in their own section. It's faster to hide a whole section than to hunt through a long list.
• Use descriptive internal names so anyone on staff can find an item quickly—"Salmon (seasonal)" is easier to locate than "Pan-Seared #4."
• Set up separate menus for different service periods (lunch, dinner, brunch) rather than one giant menu with everything. Switching menus is faster than editing individual items across a 60-item list. See our guide on creating separate lunch, dinner, and brunch menus for a step-by-step approach.

Assign menu editing access to the right people

The person who needs to mark an item unavailable mid-service is usually not the owner. It's the floor manager, the head server, or the expediter. Make sure those people have login access or a shared device they can reach quickly. If updating the menu requires calling the owner, it won't happen consistently.

The Shift Availability Workflow

Real-time availability only works if there's a repeatable process attached to it. Here's a simple workflow that fits into normal pre-service and mid-service operations.

Pre-service: the availability check-in (5 minutes)

Before doors open, the kitchen and floor manager do a quick verbal check: what's low stock, what's a definite 86 from yesterday, what's a daily special? The floor manager then opens the menu dashboard and makes those changes before the first guest arrives. This takes less than five minutes once it's routine.

Mid-service: the 86 call protocol

When the kitchen calls an 86, the standard process should include a menu update—not just a verbal announcement. A simple rule: whoever receives the 86 call is responsible for marking it in the menu within two minutes. Some restaurants post a small laminated card at the host stand or server station with the menu login URL or a shortcut on a shared tablet.

Post-service: restoring availability

At the end of service, or at the start of the next day, restore items that are back in stock. If you have a prep checklist, add "restore menu availability" as the last item. This prevents yesterday's 86 from carrying over into tomorrow's lunch rush by accident.

Communicating Availability to Guests Clearly

Simply hiding an item is the cleanest option—guests never see what they can't have, and there's no confusion. But there are situations where you want to communicate more nuance.

When to hide vs. when to label

• Hide the item when it's definitively gone for the service period. No ambiguity, no disappointment.
• Label it as "Limited" or "Ask your server" when you have only a few portions left and want to create a sense of scarcity that drives orders rather than frustration. This works well for premium items like a daily catch or a special dessert.
• Show it as "Unavailable today" when it's a regular menu item that happens to be off due to supply issues and you want guests to know it normally exists—useful for regulars who come in specifically for that dish.

Avoid the "ask your server" trap

Some restaurants mark everything as "ask your server for availability." This creates extra friction for guests who are trying to make a decision independently, and it adds load to servers who are already busy. Reserve that label for genuinely ambiguous situations, not as a substitute for keeping the menu current.

Handling Availability When You Take Online Orders

If guests can order directly from your digital menu, availability management becomes even more critical. An order placed for a sold-out item creates a cascade of problems: you have to call the guest, offer a substitution, potentially refund a payment, and deal with a frustrated customer—all during your busiest hour.

A few additional steps for online ordering contexts:

• Set inventory limits where the platform supports it. If you only have six portions of a dish, cap the online orders at six. When they're gone, the item automatically becomes unavailable.
• Create a buffer. If you have ten portions, set the online limit to eight. Reserve two for walk-in guests or for error margin.
• Pause online ordering for specific categories during peak hours if your kitchen can't handle the combined load of walk-in and online orders simultaneously. It's better to pause than to overpromise.

Daily Specials and Seasonal Items

Daily specials are one of the most common sources of menu-availability friction. They're by definition temporary, but they often get added to a menu and then forgotten when they sell out or when the day ends.

The cleanest approach is to treat specials as their own section with a clear on/off toggle, rather than editing the item itself each time. Add the special in the morning, toggle the section visible, and toggle it off at the end of service or when it sells out. The item stays in your menu dashboard for next time—you don't have to rebuild it from scratch.

For more on managing specials efficiently, see our guide on how to add daily specials to a digital menu without reprinting.

Seasonal Menu Transitions

Beyond daily 86s, restaurants also deal with larger availability changes when seasons shift—ingredients go out of season, suppliers change, or the menu gets a quarterly refresh. A digital menu handles these transitions far more cleanly than print.

Best practices for seasonal transitions:

• Build the new seasonal menu in draft before the transition date. When you're ready to switch, publish it in one action rather than editing items one by one.
• Archive, don't delete. Keep old menu versions saved so you can reference them or restore items quickly if a supplier comes back.
• Update photos and descriptions at the same time. A seasonal transition is a good moment to refresh the visual presentation of the menu, not just the item list.

Staff Training for Menu Availability Updates

Technology only works if the people using it are comfortable with it. Menu availability management should be part of your standard staff onboarding, not an afterthought.

Keep the training simple:

1. Show, don't just tell. Have new managers or senior servers actually log in and toggle an item during training—not just watch you do it.
2. Post a one-page reference card with the login URL, the steps to mark an item unavailable, and who to contact if something isn't working.
3. Run a monthly "fire drill." During a slow moment, ask a staff member to 86 a test item and restore it. Keeps the skill fresh and surfaces any access issues before they become a mid-service crisis.

If you're rolling out a new QR menu system and need a broader staff training plan, our article on how to roll out QR menus to your staff and train them covers the full process.

Common Mistakes to Avoid

Even restaurants that have adopted digital menus often stumble on availability management. Watch out for these patterns:

• Updating the menu on one device but not syncing. With a cloud-based menu, this shouldn't happen—but double-check that your platform saves and publishes changes in real time, not just locally.
• Forgetting to restore items after service. A dish that's been unavailable for three days because nobody remembered to turn it back on is a quiet revenue leak.
• Only updating availability for online orders, not the dine-in menu. If you have separate menus for online ordering and table QR codes, changes need to happen in both places—or better, use a single menu source for both.
• Treating availability as a kitchen-only responsibility. The kitchen knows what's gone, but they're rarely the ones updating the menu. The handoff between kitchen and floor needs a clear owner.

Frequently Asked Questions

How quickly do digital menu changes go live for guests?

With a hosted digital menu platform like MenuHoster, changes are typically live within seconds of saving. Guests who scan the QR code after you make a change will see the updated menu immediately. There's no need to reprint codes or re-upload files.

Do I need special hardware or a POS integration to manage availability in real time?

No. A smartphone or tablet with a browser is all you need to update a cloud-based digital menu. POS integration can add automation (like auto-hiding items when stock hits zero), but it's not required for basic real-time availability management.

What's the best way to handle an item that sells out during a busy service when staff are too occupied to update the menu?

Designate one person—typically the floor manager or expediter—as the menu availability owner during service. If they're overwhelmed, a brief update takes under 30 seconds once staff are practiced. You can also set up a shared tablet at the host stand specifically for quick menu edits so it's always accessible without interrupting service flow.

Should I hide sold-out items or just mark them unavailable?

Hiding is usually cleaner for guests—they only see what they can order, which reduces decision fatigue and disappointment. Marking as unavailable (rather than hiding) is better when you want regulars to know a dish normally exists but is temporarily off. Choose based on whether the context helps or confuses your guests.

Can I schedule availability changes in advance—for example, turning on a happy hour menu automatically?

Many digital menu platforms support scheduled publishing, which lets you set a time for a menu or section to go live or be hidden. This is particularly useful for happy hour menus, breakfast cutoffs, and seasonal launches. Check whether your platform supports this feature—it can eliminate a lot of manual toggling during busy transitions.

Ready to stop apologizing for sold-out items mid-service? Create your digital menu on MenuHoster and start managing availability in real time—no reprints, no confusion, and no more awkward conversations at the table. Setup takes less than an hour, and your first menu is free to build.