Usually, label a temporarily unavailable item rather than hide it if guests are likely to look for it or the shortage is short. A clear notice preserves the menu’s usefulness and prevents a wasted trip. Hide the item when its return is uncertain, the notice would be difficult to keep current, or leaving it visible would make the menu misleading.
The important distinction is between an informational menu and an ordering menu. An informational menu helps someone decide whether to visit. An ordering menu must also prevent a guest from buying something the kitchen cannot supply. A label on one page does not necessarily change what can be ordered on another.
Decide when the website needs a notice
Start with the guest’s likely decision. A sold-out special may matter to someone coming specifically for that dish. A missing side might be less important if the menu already makes clear that sides vary. The more central the item is to a visit or order, the more useful a prominent update becomes.
Before editing the site, get four answers:
- What is unavailable? The kitchen identifies the exact item, size, ingredient, or preparation affected. A missing sauce does not always mean the whole dish is unavailable.
- Where and when does it matter? The shift manager confirms the affected location, service period, and whether the issue applies to dine-in, pickup, or delivery.
- When will it be checked again? The person responsible for supply gives a review time. If the return is uncertain, say so internally rather than guessing a date for guests.
- Where does it appear? The website owner identifies the informational page, downloadable menus, and any separate ordering destination that need attention.
A review time is not a promised return time. “Check again before tomorrow’s lunch” tells staff when to act; “back tomorrow” tells guests to expect the item. Use the latter only when the restaurant can support it.
Look at the format as well. Text on a web page may be easier to update than an image or PDF, but that depends on the editing setup. If staff cannot update a menu promptly, consider a dated notice near the menu link or a standing explanation that availability varies. Neither should substitute for a specific warning about a popular item that is known to be unavailable.
Choose whether to label or hide the item
Use this decision tree when a shortage is confirmed. The table turns each answer into a website action and a follow-up. It applies to the informational menu; the ordering destination still needs its own check.
| Situation | Website action | Follow-up |
|---|---|---|
| Item is available as described | Keep it visible without a shortage notice. | Check again if supply changes. |
| Shortage is temporary and a useful review time is known | Keep it visible and label it unavailable, including the affected service or location when relevant. | Assign a person and time to review the label. |
| Return is uncertain or the item has effectively left the menu | Hide or remove it from the informational menu. | Review whether it should return after supply is confirmed. |
| Only an ingredient or option is affected | Describe the actual change if the remaining dish can still be served accurately. | Confirm the description with the kitchen before publishing. |
Labeling is useful when guests recognize the dish and would otherwise wonder whether it still exists. Keep the wording direct: “Lobster roll unavailable at the downtown location today” is more helpful than “market availability.” If you do not know when it will return, avoid an estimated date in the public notice.
Hiding reduces clutter and avoids keeping an old warning on the page for weeks. Its drawback is that a regular customer may assume the item has been discontinued. If that distinction matters, a short general notice can explain that a seasonal or temporarily absent item may return, without promising when.
Hypothetical example: A restaurant’s informational menu lists a popular mushroom flatbread. The kitchen confirms that mushrooms are unavailable for tonight’s dinner, but expects a supply update before the next lunch service. The manager labels the flatbread “Unavailable for dinner today” and assigns a lunch manager to check it before opening. The notice answers the immediate guest question without claiming the dish will be back at lunch.
If the supplier later cannot give a reliable return date, the manager can remove the listing and set an internal review date. If only one topping is missing and the kitchen approves a replacement, the site should describe the dish guests will actually receive. Do not leave the original description up and rely on a server to explain every change.
Give one person responsibility for restoring it
Publishing the shortage is only half the job. An item left hidden after it returns can mislead guests just as surely as an available-looking item that cannot be served. Assign a named role to each action, even if one person fills several roles on a quiet shift.
- The kitchen or purchasing lead reports the shortage and the next time supply can be checked.
- The shift manager decides the guest-facing wording and which services or locations it affects.
- The website editor publishes the change and confirms it appears on the public page.
- A named manager checks supply at the agreed time, then asks the editor to restore, revise, or extend the notice.
Keep a simple shared log: item, affected location and service, public wording, pages changed, owner, next review time, and final action. For the flatbread example, the lunch manager should confirm the mushrooms have actually arrived and the kitchen can serve the dish before removing the notice. If supply remains uncertain, the manager should update the review time rather than silently letting it expire.
Make the handoff specific. “Please check the flatbread before lunch and tell the website editor whether to restore it” is actionable. “Fix the menu tomorrow” leaves too much room for a missed step. If the usual editor is off, name a backup with permission to make the change.
Also decide how quickly an edit needs to appear. Ask your provider who can change menu text, whether changes require approval, and how staff can verify the published version on a phone. For a PDF or image menu, ask how the file is replaced and whether an old copy can still be reached from the website. A restaurant website builder comparison can help frame those editing questions when evaluating a new setup.
Check the path from menu to order
A guest may read the informational menu, tap an order button, and arrive at a separate ordering page. Follow that path yourself whenever an important item changes. The two pages do not have to look identical, but they should not give opposite answers about availability.
For the flatbread example, a notice on the website is not enough if the ordering page still lets a dinner guest add the flatbread and place an order. The manager needs to use the ordering system’s available controls to stop that purchase or otherwise resolve the mismatch. If staff cannot make that change promptly, contact the ordering provider and decide how to handle orders until the menu is corrected. Do not assume that hiding text on the website changes the ordering menu.
Check these points on both desktop and mobile:
- Does the notice name the right item, location, and service period?
- Does the order button lead to the intended location and menu?
- Can a guest select an unavailable item or an affected option?
- After the item returns, are both the notice and the ordering status updated?
- Do linked menu files or other prominent menu pages still show an outdated description?
For practice, ask the provider for a safe demo or test environment and simulate a shortage there. Check the displayed notice and selection behavior without placing a real order, taking a card payment, sending a guest message, or dispatching a courier. A simulation shows how that environment behaves; it does not prove the live menus are current. Separately, inspect the live pages without submitting an order, and follow your normal operational process to correct any mismatch.
If your website and ordering destination are managed by different providers, ask who owns each edit and how long a change takes to publish. Fleksa describes options for an ordering-ready website or an existing site with an ordering button or link. Ask how menu changes would be managed in your particular setup, including whether the informational and online ordering menus require separate updates.
Use the checklist above on one item and trace it from the kitchen’s report to the public menu and ordering page. Then ask Fleksa about its restaurant website, including current US availability and how your team would publish and restore an item.
Frequently asked questions
Should a sold-out item stay on an informational menu?
It can stay if a clear, current label helps guests understand the shortage. Hide it when the return is uncertain or the listing would be difficult to maintain accurately.
Does a website notice stop guests from ordering the item?
Not necessarily. Check the ordering destination separately and use its controls to prevent an unavailable item from being purchased.
When should staff remove an unavailable notice?
After the kitchen confirms the item can be served again. The assigned owner should also check the ordering menu and any other prominent menu pages before closing the update.
