How Many Items Should Be on a Menu? The Right-Size Rule
Social posts for this article
“Something for everyone” is the most expensive sentence in the restaurant business. It is how a menu grows from 24 items to 60 over a few years, one well-meaning addition at a time, until the walk-in is packed with single-use ingredients and the line cook cannot fire half the tickets without reading the recipe. So how many items should be on a menu? Fewer than most independents run, and the right number has less to do with taste than with math you already track.
This is not an argument for a tiny menu as an aesthetic. It is an argument for a menu sized to what your kitchen can execute perfectly and what your guests can actually choose from without stalling. Both of those ceilings are lower than they feel.
TL;DR
- Target roughly 7 items per category, and keep total items in a range your kitchen can execute flawlessly at peak. For most independent full-service restaurants that lands around 25 to 40 total dishes.
- Menu length has a peak, not a slope. Too few looks thin and limits check size; too many slows decisions, bloats inventory, and drags food cost. The profit lives in the middle.
- The paradox of choice is real. Past about 7 options in a section, guests decide slower and feel less satisfied with what they picked.
- Cut by data, not by feel. Use the menu engineering matrix to find the dogs, then consolidate dishes that share most of their ingredients.
Why menu length matters more than menu content
A dish you add to the menu does not just sit on the page. It has a full cost of ownership that most owners never add up:
- Inventory. A dish that uses one ingredient nothing else uses means you carry that ingredient, and it spoils on the slow weeks. That is cash sitting in the walk-in going bad.
- Prep and labor. Every item is a prep the kitchen has to hold in its head and execute consistently. More items means more mise en place, more waste, more chances to run out or 86 something at 8pm.
- Speed and consistency. A line that fires 30 dishes from muscle memory is faster and more consistent than one juggling 60. Ticket times matter to your Google rating and your table turns.
- Guest attention. This is the one owners underrate. A guest’s eyes have a budget. Every extra line on the page competes with the dishes you most want them to order, the high-margin stars you should be steering them toward.
None of that shows up on a single dish’s food cost line. It shows up in the aggregate: a slower kitchen, a fatter inventory, and a check average that is lower than it should be because guests defaulted to the safe, cheap, familiar option instead of the thing you make money on.
What the choice research actually says
The instinct behind a long menu is that more options make more people happy. The research on how humans handle choice says the opposite past a surprisingly low threshold. When people face too many options, they take longer to decide, are more likely to defer or default, and report lower satisfaction with the choice they eventually make, a pattern usually called choice overload or the paradox of choice.
For a menu, the practical translation is the rule of 7: aim for about seven items per category. Seven appetizers, seven or so entrees, a handful of desserts. A guest can hold a category of that size in their head, compare within it, and feel good about landing somewhere. Stretch a category to fifteen and you get the opposite of abundance, you get a guest who skims, gives up, and orders the burger they always order.
How many items by restaurant type
There is no single right number, because a diner and a tasting-menu spot are different machines. But the ranges below are where healthy menus tend to live. Count only real menu items (individual dishes), not modifiers, sides, or the beverage list.
| Concept | Typical total items | Per-category target | Why |
|---|---|---|---|
| Coffee shop / cafe | 10 to 25 | 5 to 8 | Speed is the product; a short board keeps the line moving |
| Fast casual / counter | 12 to 25 | 4 to 7 | Fewer builds, faster throughput, tighter inventory |
| Full-service bistro | 25 to 40 | ~7 | Enough range to feel complete, few enough to execute at peak |
| Pizzeria / focused concept | 15 to 30 | varies | Depth in one thing beats breadth across many |
| Diner / all-day | 40 to 70 | higher by design | Breadth is the concept, but this is the hardest kitchen to run well |
| Fine dining / tasting | 8 to 20 | 3 to 6 | Precision demands a short, controlled list |
If you are a full-service restaurant running 55 or 60 items, you are almost certainly carrying dead weight. The diner exception is real, but a diner earns its long menu with a kitchen and prep system built specifically for breadth. Most restaurants that drifted to 60 items did not build for it, they accumulated to it.
How to right-size your menu
Do not cut by gut feeling or by which dishes you are personally tired of. Cut by data, in this order.
1. Pull 60 to 90 days of item-level sales
You need units sold and contribution margin per item. If you are not sure of your plate costs, fix that first with the food cost percentage method, because every decision below depends on honest margins.
2. Run the menu engineering matrix
Sort every item into stars, plowhorses, puzzles, and dogs using popularity and margin. The full method is in the menu engineering matrix guide. Your cut list starts with the dogs: low sales, low margin. They cost you inventory, prep, and page space while barely ringing in.
3. Consolidate overlapping dishes
Two dishes that share 80% of their ingredients can often become one, or one dish plus a modifier. Three chicken preparations that each sell modestly might become one chicken dish that sells well and moves faster. Consolidation shrinks the item count without shrinking the perceived range.
4. Protect the strategic keepers
A few low-sellers stay on purpose: the one vegan entree, the kids option, the dish whose ingredients are fully shared with a winner so its true carrying cost is near zero. Cutting those can cost you whole tables. Judge at the check level, not the item level, since a cheap appetizer that starts 40% of tables is doing work its own row never shows.
A worked example: 58 items down to 34
A neighborhood bistro came in at 58 items across apps, salads, sandwiches, entrees, and desserts. Ninety days of sales told the story fast.
- Appetizers: 11 items. Four were dogs selling under 15 units a month each, three of them using ingredients nothing else touched. Cut all four. Down to 7.
- Salads: 6 items, two nearly identical but for the protein. Consolidated into 4 with a “add chicken / add salmon” modifier. Down to 4.
- Sandwiches: 9 items. Three were plowhorses, popular but thin, and two were dogs. Cut the two dogs, kept and re-engineered the plowhorses with the pricing and description fixes. Down to 7.
- Entrees: 18 items. This was the bloat. Six sold fewer than 20 units a month; four of those were true dogs, two were puzzles worth one more promotion cycle. Cut the four dogs, consolidated two overlapping pasta dishes into one. Down to 11 (rounded into a tighter list).
- Desserts: 8 items, mostly bought-in. Cut to the 3 that actually sold and carried margin. Down to 3, plus 2 shared components elsewhere.
The result landed at 34 items. Over the following quarter, food cost fell from about 33% to 29% as single-use ingredients left the walk-in, ticket times at peak dropped, and the check average rose because the menu now steered guests toward stars instead of hiding them among dogs. Nobody complained the menu felt small. Guests noticed it felt confident.
When a longer menu is the right call
Rules have exceptions, and a few concepts legitimately run long:
- Diners and all-day spots, where breadth is the promise and the kitchen is built for it.
- Delivery-first kitchens running multiple virtual brands out of one line, where the “menu” a guest sees is a filtered slice.
- Places with deep ingredient overlap, where 40 items are really 12 components recombined, so the true carrying cost of the list is low.
The test is not the raw item count, it is whether each item pays its full cost of ownership. If a dish sells, carries margin or strategic value, and does not drag your speed or inventory, keep it. If it fails all three, its length on the page is length you are paying for.
Frequently asked questions
How many items should a restaurant menu have? For most independent full-service restaurants, roughly 25 to 40 total dishes, or about 7 per category. Cafes and counter concepts run leaner (10 to 25), tasting menus leaner still, and diners run longer by design. The right number is the largest one your kitchen can execute perfectly at your busiest hour.
Is a smaller menu always better? No. Too few items looks thin and caps your check size, and can push guests to a competitor with more range. Profitability peaks in the middle, not at either extreme. The goal is right-sized, not minimal.
How do I decide which items to cut? Pull 60 to 90 days of item-level sales, run the menu engineering matrix, and start with the dogs (low sales and low margin). Then consolidate dishes that share most of their ingredients, and protect a few strategic keepers like a vegan or kids option.
Will cutting dishes upset regulars? Rarely, if you cut the right ones. The items you remove are, almost by definition, the ones few people order. Communicate any change to a genuinely beloved item, but a dog selling ten covers a month leaving the menu goes unnoticed by nearly everyone.
How often should I re-check menu length? Quarterly, alongside your menu engineering review. Ingredient costs shift, seasons change, and new additions creep in. A menu that was right-sized in spring can be bloated by fall. See how often to update your menu for the full cadence.
The bottom line
The answer to “how many items should be on a menu” is not a magic number, it is a discipline: about seven per category, every item earning its full cost of ownership, reviewed every quarter. Get there by data, not by taste. Cut the dogs, consolidate the overlap, protect the strategic few, and let the stars breathe.
Then make the shorter menu real everywhere a guest looks. Once you have trimmed the list, the version on the table, the one on your website, and the menu on Google all need to match, or you have done the hard work and left guests reading the old, bloated version. Keeping those in sync from one place is the last mile of any menu change; see how to keep your menu accurate everywhere for the workflow.