When the last portion leaves the kitchen, the menu needs to catch up. Otherwise your counter keeps offering it, someone orders it online, and your team has to interrupt service to explain. A short sold-out routine prevents that avoidable conversation.
The routine has four parts: confirm what is unavailable, update the menu, check orders already accepted, and tell the team what to offer instead. It applies to a bakery’s last tray as much as a restaurant’s evening special.
Assign one person and a backup
Decide who changes availability during each shift. Give that person the access and device they need before service starts. Name a backup for breaks and shift changes so the kitchen is not left searching for whoever knows the password.
The cook or baker should report the change in plain terms: which item, when it stopped being available, and whether another batch is confirmed. “Nearly out” and “sold out” are different messages. Agree how a low-stock warning reaches the counter before the last portion is promised.
Check the remaining portions before switching it off
Count usable portions and account for orders already accepted. Six portions on the shelf do not mean six are free to sell if four belong to tickets in progress. Reserve what has already been promised before deciding what remains.
Use a quick kitchen check for foods prepared in batches. A tray in the oven is not necessarily ready for the next order, and a supplier delivery is not the same as a finished dish. Only promise a return time when the kitchen can support it.
Update availability without deleting the item
Temporary unavailability usually calls for an availability change, not deleting the dish and rebuilding it tomorrow. Keep its name, description and price ready for when it returns.
Simplrr has a manual menu-item availability control. Use it for the actual dish that cannot be served, then open the public menu on another phone and check what a guest sees. Allow the page to refresh; do not assume every already-open screen updates at the same instant.
An availability switch is not a physical stock count. It does not prove that the remaining ingredients are correct or that another ordering platform has also changed. Check every channel you still use.
Look beyond the one dish
A shared ingredient can affect several menu items. If the bakery runs out of the filling used in two pastries and a sandwich, checking only the bestselling pastry leaves two more chances for disappointment.
Make a short dependency list for ingredients that regularly run out. Keep it practical: ingredient, affected dishes, and approved alternatives. Include an extra or size only where it is affected; do not turn off a whole item when a valid remaining choice can still be served.
For example, running out of large takeaway cups may still leave small drinks available. Explain the remaining choice clearly, and check the menu choices guide before changing how sizes or extras are presented.
Handle orders that arrived before the change
Changing today’s menu does not resolve orders already accepted. Look through work waiting to start and identify any order containing the unavailable item. Speak to the person ordering before making a substitution.
Offer a clear choice: an agreed alternative, a realistic wait if another batch is confirmed, or cancellation of the affected item under your normal process. Confirm any price difference. Do not quietly replace an ingredient, especially when the choice involves an allergy or dietary requirement.
Record the agreed change where the kitchen will see it. If payment has already happened, follow the payment provider’s process for any refund; changing an order record is not itself a card refund.
A bakery example: the last cheese man’oushe
Suppose your baker reports three cheese portions left at 10:30. Two are already committed to an accepted pickup order. There is only one left for new orders, even though three portions are physically present.
The counter sells that last portion, and the designated person marks the cheese man’oushe unavailable. They also check whether cheese is used in a mixed topping sold separately. A second phone confirms the public menu no longer offers what cannot be made.
The team tells people what is still available rather than promising “another ten minutes” without checking. At the shift handover, the note says what sold out and whether more ingredients have actually arrived. This is an illustrative service routine, not an automatic stock reservation feature.
Restore it only after checking the food
When the next batch is ready, count it and confirm that the item can be served again. Restore availability, check the public menu and tell the counter. Do not make the opening shift guess whether yesterday’s sold-out item has returned.
In Simplrr, treat restoration as a deliberate manual step. Do not assume items automatically return overnight or that recipe ingredients automatically control every menu item. Inventory tools and menu availability serve different purposes, and inventory access depends on your plan.
If your connection drops, tell the team directly. A change that has not reached the online menu cannot reliably stop fresh online requests.
Keep a small opening and closing checklist
Before service, check yesterday’s unavailable items against today’s actual prep. During service, update sold-out items and review accepted orders. At closing, leave a short note of what needs checking tomorrow.
- Confirm remaining portions after accepted orders.
- Update the affected dishes and choices.
- Check the public menu and other sales channels.
- Contact anyone whose accepted order is affected.
- Restore items only after confirming they are ready.
Explore Simplrr and try the demo. For a useful distinction between availability and counting stock, see Square’s item-availability documentation; its automatic reset features are specific to Square.