A Sold Out Item Is Not an Inconvenience. It Is a Cancelled Order.
Every restaurant treats "sorry, that's finished" as a small operational embarrassment. Something you apologize for, offer an alternative, and move past.

The data from adjacent industries suggests it is not small at all.
In online retail, 69% of shoppers abandon their purchase entirely when they hit an out of stock item. More striking: 52% make no purchase at all, not even a substitute. Harvard Business Review research found that when a product is unavailable, retailers lose close to half of all intended purchases. And the damage outlives the stockout, with 63% of customers who abandon over an unavailable item not returning even after it comes back.
Those are retail numbers, not restaurant numbers, and it is worth being honest about that. Nobody has run the equivalent study on a biryani that ran out at 9pm.
But if anything, the restaurant version should be worse. A retail shopper is browsing. A person on your menu at 9pm is hungry, has already decided to eat, and has three other restaurants one tab away. Their intent is higher and their patience is shorter.
Why substitution does not save you
The intuition every operator has is that the customer will simply pick something else. They are already on your menu. They want your food. Surely they order the second thing on their list.
Mostly they do not, and the reason is psychological rather than logical.
By the time someone taps a dish, the decision is already made. They are not choosing anymore, they are confirming. The mental work is finished and they have moved on to anticipating the meal. Telling them no at that exact moment does not send them back one step to pick again. It breaks the whole sequence and dumps them back at the beginning, tired, with the decision to make from scratch.
That is a worse position than when they arrived, because now there is friction attached to your restaurant specifically. Leaving costs them nothing. They leave.
Availability turns out to matter more than most operators assume. In retail research, 23% of consumers name product availability as their primary purchase decision factor, ahead of both delivery speed and price. The restaurant obsession with pricing may be aimed at the second most important thing.
The number nobody calculates
Here is how to convert this from an annoyance into a line item. Use your own figures rather than these.
Say a dish accounts for 8% of your orders. Say you run out at 8pm on a Friday and nobody updates the menu until close at 11pm. During that window you take 120 orders.
Roughly 10 people would have selected that dish. If two thirds of them abandon rather than substitute, that is around 7 lost orders. At a ₹450 average ticket, about ₹3,000 gone in one evening.
Now assume that happens twice a week, which is conservative for a kitchen with any popular item. That is roughly ₹3 lakh a year, disappearing through a gap nobody has ever measured, from a problem everybody considers minor.
And that only counts the orders. It does not count the customers who quietly never come back, which the retail data says is a majority of them.
What it costs upstream
There is a second cost that is easy to miss. Sold out items also waste your acquisition spend.
If you are paying commission on an aggregator, or running ads, or funding discounts, you are paying to get someone onto your menu. When they arrive and hit an unavailable item, you have paid full price for the visit and received nothing. In retail this is well documented: money spent driving traffic to a page that then displays an out of stock message.
For a restaurant with delivery, the sequence is worse. You paid for the click, the customer chose you, and then your own kitchen closed the door.
The fix is boring, which is why it does not happen
The solution is not clever. Take the item off the menu when it runs out.
The reason it does not happen is friction. On a printed menu it is impossible, so a staff member has to say it out loud to every table. On most digital setups it means someone with an admin login, on a laptop, during the busiest hours of the week. So it waits until tomorrow, or never.
What actually works:
Make it a one tap action from a phone. If turning off an item requires more than a few seconds from whoever is standing at the pass, it will not happen at 8pm on a Friday.
Give the kitchen the ability, not just the owner. The person who knows the paneer is finished is not the person with the admin password. That mismatch is the entire problem.
Turn items off before they run out, not after. If you have eight portions left at 8pm on a Friday, that item is functionally gone. Selling the last eight is not worth the abandonments that follow.
Schedule the predictable ones. Items that always run out by nine should switch off automatically at nine. Do not rely on anyone remembering during a rush.
Track it. Note how many hours per week an unavailable item stayed visible. It is the cheapest revenue metric in the business, and almost nobody has the number.
The wider point
The restaurant industry spends enormous energy on acquisition. Commissions, discounts, ads, listings, all of it aimed at getting someone to choose you.
Then it spends almost nothing on the last ten seconds, where a customer who has already chosen you gets turned away by a menu that is out of date by two hours.
A high price loses a customer who was never going to be yours. A sold out item loses one who already was.
Menuthere lets anyone at the pass turn an item off in one tap, from a phone, in the middle of a rush. That is the whole feature, and it is worth more than it sounds.
