How many items should a restaurant menu have?

There is no right number, only a right number for your volume

Someone outside the industry asked on r/restaurantowners why so many restaurants have so many dishes, and whether five or six starters and seven or eight mains would be easier and cheaper. In the recorded excerpt, the first reply was 'yes and no'. It depends on volume, region and clientele, though the commenter personally believed less is more. Another reply was blunter: you use the same protein in multiple dishes, or you waste a lot, or you serve frozen products.

Those replies already contain the answer. Menu size is not a matter of taste. It is a ratio between how many guests you serve and how many separate things the kitchen has to keep fresh and ready. A busy diner can support a long menu that would sink a quiet bistro, because each item sells often enough to turn over its ingredients. A slower restaurant reaches the limit much sooner. In an excerpt from a separate thread, 'number of menu items?', one commenter made the same point: a restaurant with a large menu that is not busy will struggle to deliver fresh, consistent food.

Volume per item: the first number to look at

Pull one or two months of item-level sales from your point-of-sale system and divide each item's count by the number of days open. That gives average daily orders per item. A commenter in the 'number of menu items?' excerpt observed that customers do not order every dish equally, and your data will almost certainly show the same pattern. A small group of items carries most of the volume, and a long tail sells once a day or less.

The long tail is not automatically a problem. A dish that sells once a day but is assembled entirely from ingredients other dishes also use costs almost nothing to keep. The problem is a slow item that depends on something only it uses: a special cheese, a braise, a sauce, a garnish. That ingredient has to be bought and prepped in batches, and if the item does not sell through the batch, the rest is thrown away or served past its best.

The coverage test: will a batch sell before it expires?

For each item, identify its unique preps, meaning the ingredients or batches no other dish uses. For each of those, note the smallest practical batch in portions and the number of days it stays at the quality you want to serve. Then calculate coverage: average daily orders multiplied by usable days, divided by the minimum batch. Coverage of 1 or more means the batch normally sells through. Below 1 means the item routinely forces waste or stale food.

Usable days here is a quality judgment set by your kitchen, and it must never exceed the legal limit in your jurisdiction. In the District of Columbia, for example, DC Health's guidance on food establishment inspections says that refrigerated ready-to-eat potentially hazardous foods prepared on site and kept longer than 24 hours must be date-marked and can be held for up to 7 days at 41°F or below. That is an outer limit, not a quality target, and that page is a 2018 guidance summary of DC's Title 25 food regulations. Operators elsewhere should check their own health authority's adopted code, because the FDA Food Code is a model that jurisdictions adopt and amend, not law everywhere.

Worked example: a 48-item menu at a neighborhood restaurant (hypothetical numbers)

All figures are invented to illustrate the method.

A restaurant with 48 menu items serves about 260 entrees a day. Sales data shows the top 12 items take about 65 percent of orders, and the bottom 20 items together take about 8 percent, roughly 21 orders a day across 20 items, or about one order per item per day. One of those slow items is a short-rib dish whose braise is used nowhere else. The kitchen's smallest sensible braise is 8 portions, and the chef considers it at its best for 3 days.

Coverage for the short rib is 1 order per day times 3 days, divided by 8 portions, which is 0.375. In a typical 3-day cycle, about 3 portions sell and 5 are discarded. That is 62.5 percent of every batch wasted, before counting the labor of braising. By contrast, a chicken sandwich selling 18 a day uses a grilled chicken prep shared with two salads. Its coverage is far above 1, and its marginal cost to the menu is close to zero.

Map ingredient overlap before deciding anything

Coverage tells you which items are at risk. An overlap map tells you what to do about them. List every perishable ingredient and prep down one side of a sheet and every dish across the top, and mark which dishes use which ingredients. Ingredients with a single mark are the ones that create waste on slow items. Ingredients with many marks are the backbone of the menu.

The commenter in the 'How to decide the number of menu items' excerpt described exactly this advantage. Dishes that can use ingredients interchangeably give guests more variety without building up food waste. Sometimes the fix for a slow item is not to cut it but to rebuild it on the backbone, such as a short-rib dish reworked to use a braise that also feeds a sandwich and a weekend special. Our companion article on cross-utilization covers building and redesigning around this matrix in detail.

Prep and line complexity: the cost you cannot see on invoices

Every item adds prep tasks, storage space, steps for line cooks to remember and ways a ticket can go wrong. A long menu spreads the same kitchen staff across more unfamiliar dishes, and a dish made twice a week is made less consistently than one made forty times a day. That is the consistency problem the 'number of menu items?' commenter described, and it is a quality and reputation cost as much as a financial one.

When counting complexity, look at stations as well as dishes. Ten items that all finish on the same sauté station during the rush create a bottleneck that ten items spread across grill, fry and cold stations do not. If ticket times climb when particular items are ordered, that is a sign those items cost more than their plate cost suggests. Our article on labor-adjusted menu engineering puts a number on it.

Deciding which items to cut

Combine the evidence: daily orders, coverage of unique preps, labor and station load, and contribution margin. An item that is slow, has low coverage and needs a unique prep is the clearest candidate. An item that is slow but built entirely from shared ingredients can often stay. An item that sells modestly but anchors a group order, such as the one vegetarian main or the one kids' dish, may be worth keeping even if its numbers are weak, because removing it can lose the whole table.

In an r/restaurantowners thread about QR-code menus for a father's restaurant with a huge menu, one reply suggested trimming an unwieldy menu would make things easier on the kitchen and wait staff. Another said cutting a menu down a bit and being strategic about ingredients and costing can have a much larger impact than technology. Those are opinions rather than measurements, but they point the same way as the coverage test.

• Cut first: slow, unique-prep, low-coverage items with average or weak margin.
• Rework: slow items whose unique prep can be replaced with a shared one.
• Keep: slow items built entirely from shared ingredients, and items that anchor group orders.
• Move to specials: dishes guests love occasionally but cannot sell through a batch daily.

Rotating specials as a pressure valve

Specials let a kitchen offer variety without committing to stock ingredients every day. A dish that fails the coverage test on the permanent menu can work as a weekend special, when volume is higher and one batch can sell through. Specials are also a low-risk way to test new dishes before giving them a permanent spot, and to use up shared ingredients that are running ahead of demand.

The same QR-menu thread included a suggestion of a rotating menu changing every week or two for an owner reluctant to trim. Rotation has its own costs: menu printing or updates, training and the risk of disappointing a regular whose favorite disappears. Keep a short permanent core that sells through reliably, and let a few rotating slots carry the variety.

Making the change without surprising regulars

Before removing a dish, check who orders it. If a handful of regulars order it every visit, tell them in person, or keep it available on request while the ingredients still overlap with something else. Watch the sales mix for a few weeks afterward. Orders should shift to remaining dishes, not disappear. If total covers fall after a cut, the dish was doing more than its item count suggested.

Run the coverage test again after any change, because removing one item can change the coverage of another that shared some of its ingredients. Keep the before and after numbers for waste, food cost and ticket times so the next menu revision builds on evidence instead of instinct.