A dish can become unavailable in the middle of service, but its menu listing may still be visible to guests. That mismatch can lead to questions, disappointment and extra work for the team. A clear process helps small restaurants and cafés update a QR menu when a dish is unavailable, then make sure the change is understood by both staff and customers.
The process does not need to depend on automatic stock tracking. Instead, agree who confirms the change, who updates the digital menu and how the team checks the result. Treat availability as service information that needs an owner, just like a change to a dish description.
Why stale menu information creates confusion
When a customer sees a dish on a menu, it is reasonable for them to think they can order it. If the kitchen has run out, staff have to explain the mismatch and help the guest choose something else. This can happen whether the menu is printed or digital, but a digital menu can be changed without reprinting once someone has confirmed the item is unavailable.
Unclear availability can also create friction between front-of-house and kitchen teams. One person may know an ingredient has run out while another is still taking orders from a menu that shows the dish as available. If the information is not shared promptly, the same explanation may have to be repeated throughout service.
A useful restaurant menu availability update answers a simple question: can a guest order this dish right now? Keep the change focused on that fact. Avoid making customers interpret vague notes or assume that an item is available because it remains listed.
Agree who confirms the dish is unavailable
Before service, decide who can confirm that a dish should no longer be offered. The right person will depend on how the restaurant operates. It may be a shift lead, a kitchen lead or another staff member who has reliable information about what can be prepared. The important point is that the person making the decision is clear to the team.
Then decide who is responsible for changing the digital menu. In a small team, the same person may confirm and publish the update. In other teams, one person may report the issue and a shift lead may make the change. Either arrangement can work if the handoff is direct and the update is not left as an informal request.
Agree on the basic message staff should use while the menu is being updated. For example, they can let a guest know that the dish is currently unavailable and suggest checking the menu for available choices. Use wording that matches your service style, and make sure staff do not promise a return time unless they have confirmed one.
Keep the decision practical. The team does not need to turn every unavailable ingredient into a complicated process. It does need a reliable signal that the dish cannot be served, followed by a clear responsibility for changing what customers see.
Update availability and check the customer view
Once the item is confirmed unavailable, update its availability in the digital menu. With QR Menu for restaurants and cafés, businesses can change dish availability instantly, alongside menu details such as dishes and prices. This gives the team an option for publishing a change without reprinting menus; it does not mean stock records automatically update the menu, so someone still needs to make and confirm the change.
After publishing, check the menu as a customer would see it. Use the QR code and review the relevant section on a mobile device. Confirm that the unavailable dish is no longer presented as an option to order, and look at the surrounding items to make sure the menu still reads clearly. If your menu communicates unavailability in another way, check that the wording is easy to understand at a glance.
This customer-view check matters because completing an edit is not the same as confirming that the result is clear. Look for ambiguity: could a guest mistake the dish for something they can order? Does the menu leave the impression that the whole category is unavailable when only one dish has changed? Keep any message concise and specific.
It can help to separate three actions in the team’s routine: confirm the dish is unavailable, update the menu, and verify what guests see. Skipping the final check can leave staff believing a change is live when the customer-facing information has not been reviewed. A quick check makes the process easier to trust during a busy shift.
Leave a short handover note
An availability change can outlast the person who made it. Leave a short handover note so the next shift knows what changed and can decide whether the listing should stay unavailable. Include the dish name, the fact that it was marked unavailable, and any confirmed information the next shift needs to reassess it. Do not guess when it will be available again.
Keep the note in the communication method your team already uses for shift handovers. The goal is not to create a new record-keeping system, but to prevent a menu change from being forgotten when staff change over. The note should distinguish between confirmed status and an expectation. For example, “unavailable at handover; check with the kitchen before restoring” is more useful than an unconfirmed promise that it will return soon.
When the next shift begins, make checking the note part of its normal opening or handover routine. If the dish is still unavailable, leave the menu as it is. If the kitchen confirms that it can be served again, the person responsible can restore its availability and check the customer view once more.
Review availability when service conditions change
Availability is not always fixed for an entire day. A delivery, a change in preparation capacity or a newly depleted ingredient may affect what the kitchen can serve. Ask staff to share relevant changes promptly with the person responsible for the menu, rather than assuming the digital listing will reflect them on its own.
Use natural checkpoints to review the menu: when the kitchen reports a change, at a shift handover, or when service conditions clearly change. Avoid unnecessary edits when nothing has changed. The aim is to keep the menu aligned with what the team can offer, not to add steps for their own sake.
If a dish becomes available again, confirm that with the appropriate team member before changing its status. Then check the customer view. The same simple workflow applies in both directions: confirmed change, menu update, customer-view check, and handover if the status needs attention later.
A clear availability update is a team habit
To update a QR menu when a dish is unavailable, give the change an owner. Confirm the dish’s status, update its availability, check the menu from the customer’s perspective and pass on any unresolved status at handover. Revisit it when service conditions change, rather than relying on memory or assuming the menu follows stock automatically.
If you are considering a way to publish menu availability changes without reprinting, review the QR Menu app as one option. A consistent team workflow is what helps keep the information clear for guests and useful for staff.