A sold-out item is not a pricing issue or a general menu rewrite. It is a live availability change. The job is to make the kitchen, public menu and guest conversation agree before a person decides around an item that cannot be served.

Use this process for a dish, drink, modifier or limited batch that becomes unavailable during service. It is an operational guide, not food-safety or legal advice.

What belongs in a sold-out item process?

The useful unit is the guest decision, not the inventory field. A guest needs to know whether the item is available at this location for this service, whether a listed choice still works and what to do next.

Check Confirm before calling the menu current Named owner
Scope Item, location, service period and affected choices Kitchen lead
Public status Remove or clearly label every guest-facing path Menu editor
Mobile proof QR code, shared link and public menu state Shift lead
Team handoff Approved wording and any approved alternative Front-of-house lead
Restore Supply is confirmed before the item reappears Kitchen lead

This avoids the usual failure: the kitchen has stopped serving an item while a QR menu, saved link or modifier still invites a guest to choose it.

1. Treat sold out as a guest-facing decision

Name the item exactly as a guest sees it. Record the affected location, the service period and whether a modifier, combo or set menu is also affected. A vague note such as “out of chicken” leaves the next person to decide which dishes and choices must change.

Do not treat an old screenshot or staff chat as the source of truth. The kitchen lead confirms the scope once, then the menu owner works from that confirmed state. A small record makes restoration deliberate rather than accidental.

2. Make the unavailable status clear without relying on colour

Use words such as “Sold out for dinner today” or remove the choice entirely. Do not rely on a muted photo, an icon or a colour change to communicate that a guest cannot select it. The W3C guidance on use of colour explains why colour alone should not carry meaning.

If the item stays visible, keep the status next to its name and stop the guest from treating it as available. Do not replace the name with an unapproved alternative or bury the limit in an image caption.

3. Test the public menu, not only the editing screen

Publish or preview the approved change through the restaurant’s normal process. Then leave the staff account and test the same route a guest uses.

  1. Scan the table, window or takeaway QR code.
  2. Open any category, combo or modifier that could expose the item.
  3. Confirm the right location and service context.
  4. Check that the unavailable status is understandable without internal knowledge.
  5. Repeat through a saved public link if guests commonly use one.

This is distinct from the digital menu price update checklist. Price work checks the amount a guest sees; this check makes sure the guest is not invited to select an item the kitchen cannot provide.

4. Give the team one safe response

The handoff can be brief: “That item is unavailable for this service. I can check the approved alternatives.” The team should not invent a replacement, promise a return time or make an ingredient claim they cannot verify.

Questions about ingredients or allergen handling need the same discipline. The FDA food-allergy guidance is a reminder to use current, confirmed information rather than assume one dish is interchangeable with another. If the team cannot verify a substitution, they should say so and escalate it under the restaurant’s policy.

Record only the operational cause after service, such as a stale category or a missed QR path. Do not copy a guest’s name, phone number or order into the availability note.

5. Restore availability only after a fresh confirmation

“Back in stock” needs the same owner as “sold out.” Confirm that the kitchen can serve the item for the named location and service, then restore the item, test the public path and brief the team. Do not leave the menu owner to infer that a delivery or prep task solved the shortage.

The restaurant mini-site content checklist helps when the same change affects hours, a service notice or the guest’s next action. If the visit also includes a live queue, keep that separate from availability through restaurant waitlist software. A waitlist answers when a table may open; it should not hide that a menu choice is unavailable.

A five-question pre-service check

Before the next rush, the owner should be able to answer yes to each question:

  • Is the item’s scope clear by location and service?
  • Is every public menu path removed or labelled in plain words?
  • Did someone test the QR code or public link on a phone?
  • Does the team know the approved response and escalation?
  • Has restoration been kept separate until supply is confirmed?

That is enough to turn a temporary shortage into a clear guest decision instead of a surprise at the table.