A Longer Menu Makes People Spend Less
Owners add dishes to grow the order value. It usually does the opposite.

The instinct is completely reasonable. More options means more chances that something appeals, which should mean more orders and bigger tickets. Every operator has added a dish for exactly this reason.
The behaviour runs the other way, and the reason is not about food at all.
The study everyone quotes, and the problem with it
Any article about menu length eventually reaches for the jam study. In 2000, Sheena Iyengar and Mark Lepper set up a tasting booth in a California supermarket, alternating between 24 jams and 6. The larger display attracted more browsers, with 60% stopping to sample versus 40% for the small one. But only 3% of those who sampled the large display bought anything, against 30% at the small one.
Ten times the conversion from a quarter of the options. It became one of the most cited findings in consumer psychology, and it is the reason a generation of restaurants pruned their menus.
Here is the part that almost no restaurant blog mentions.
In 2010, Scheibehenne, Greifeneder and Todd aggregated 50 studies of choice overload covering around 5,000 participants. Across the literature as a whole, the average effect of more choice on conversion was essentially zero.
That is a serious problem for the naive version of this advice. If you have been told "shorter menus sell more" as a general law, the evidence does not support it as a general law.
When it does hold, and why restaurants qualify
The more useful research is a later meta-analysis by Chernev, Böckenholt and Goodman, which re-examined 99 studies and isolated the specific conditions under which more choice reduces sales.
Four conditions matter:
When people want to make a quick and easy choice. When the decision itself is difficult. When the options are hard to compare against each other. When customers are unclear about their own preferences.
Now picture someone opening your menu at 9pm on a Friday.
They want this decided fast, because they are hungry and it is one of a hundred small decisions they have already made today. The decision is harder than it looks, since they are choosing for a mood they have not fully identified. Your dishes are difficult to compare, because a biryani and a noodle bowl and a thali have no shared axis. And they frequently do not know what they want, which is the entire reason they are scrolling.
All four conditions. Simultaneously.
The general law does not hold. The restaurant case does, and it holds about as cleanly as any case in the literature. That is a more defensible argument than quoting the jam study and hoping nobody checks.
What actually happens on a long menu
The failure mode in a supermarket is walking away without buying. In a restaurant it is different and easier to miss, because you still get an order.
An overwhelmed diner does not leave. They retreat.
They stop reading somewhere in the middle, abandon the comparison, and fall back on the safe option: the thing they ordered last time, or the dish they recognise the name of, or whatever their eye happened to land on. Larger choice sets make people more likely to fall back on a default, and in a restaurant the default is always the familiar item.
The familiar item is almost never your highest margin dish. It is usually the cheapest recognisable thing on the list.
So the long menu does not cost you the order. It costs you the upgrade. The customer who might have tried the ₹420 dish orders the ₹260 one they have had before, because considering the ₹420 dish required effort they had already spent scrolling.
You did not lose a sale. You lost the difference.
Twelve versus sixty
The practical version is simple. On a menu of twelve items, a customer can genuinely hold the whole thing in their head, compare properly, and let themselves be persuaded by a description or a photograph. The expensive dish gets considered on its merits.
On a menu of sixty, nobody compares sixty things. They compare four and pick one. Which four they compare is determined by position, familiarity and luck, not by which dishes you actually want to sell.
A long menu feels like generosity. Functionally it hands the decision to a tired person and then leaves the room.
The costs nobody counts
Menu length has a second bill that arrives in the kitchen.
Every additional dish adds inventory that can spoil, a prep step, a recipe someone has to remember under pressure, and a slower ticket time when it is ordered rarely. Menu engineering literature calls the low popularity, low profitability items dogs and is unusually blunt about them: every day they stay on the menu, profit is left on the table.
The dishes you would cut to shorten a menu are almost always exactly these. They sell rarely, they slow the kitchen, and they lengthen the list that is suppressing your better items. Removing them is a triple win, which is rare enough in this business to be worth noticing.
What to do
Count your items per category. Menu design research repeatedly lands near seven per category as the point where more options stop helping. If any category is at fifteen, that is where the problem lives.
Find the dishes that sell rarely and make little. These are not close calls. Most menus have six or eight items that could disappear without anyone noticing.
Cut them and watch your average order value, not your order count. This is the part operators get wrong. Order count may barely move. The number to watch is what people spend per order, because the mechanism you are fixing is the retreat to the cheap familiar option.
Do it gradually. Trimming a portion of the menu at a time is safer than an overhaul, and it lets you see what actually happened before continuing.
Resist the instinct to replace what you removed. The gain comes from the absence, not from a better dish in the gap.
The one line version
A long menu is not generosity. It is a decision you handed to a tired person, and tired people choose what they already know.
Menuthere makes it easy to see which dishes are earning their place, and easy to retire the ones that are not.
