How many dishes should a small restaurant menu have
A bistro in Lisbon kept losing money on its pasta section even though the dining room was full. The chef assumed the problem was portion size, but the real issue was the menu itself: 78 dishes across four pages, half of which sold fewer than two covers a night. Six weeks after trimming to 32 dishes, food cost dropped, the kitchen stopped 86-ing specials at the pass, and average ticket went up. The change was not a marketing trick. It was a menu math problem.
If you are asking how many dishes should a small restaurant menu have, you are not really looking for a single number. You are looking for a range, a method, and a way to check whether your current count is helping or quietly hurting the business. A small restaurant menu is one of the few assets that controls food cost, labor, speed of service, and perceived quality at the same time. That is why the question matters, and why the wrong answer is expensive.
What “small restaurant” actually means for menu size
Before picking a number, the word “small” has to be defined in operational terms, not in square footage. A small restaurant, for menu planning purposes, is usually one of the following:
- Independent single location with seating for 20 to 60 guests.
- A kitchen working with two to four cooks during service, sometimes fewer on weeknights.
- A concept where one or two people handle purchasing, prep, and menu design.
- A venue with limited storage, often a single reach-in and a small dry shelf.
If your operation matches any two of these, the “small restaurant” rules below apply. A 120-seat venue with five line cooks and a separate prep team is a different problem, even if the dining room feels cozy. Defining the operating envelope first keeps the rest of the decisions honest.
The practical range: how many dishes most small menus should carry
Across most working small restaurants, the answer to how many dishes should a small restaurant menu have falls inside a fairly tight band. Stripping categories down to their core items, the typical working total is:
| Menu type | Typical dish range | Where the count works |
|---|---|---|
| Single-concept small restaurant (one cuisine, one style) | 18 to 28 dishes | Neighborhood bistros, ramen shops, taco spots, pizzerias, neighborhood Thai or Italian places |
| Small restaurant with a small daily special board | 20 to 32 printed dishes, plus 3 to 6 daily specials | Chefs who like to flex with what’s in season or what came in too good to ignore |
| Small restaurant with broad appeal (multi-cuisine or bar plus kitchen) | 28 to 42 dishes | Gastropubs, hotel restaurants, and small venues that need to feed a wide range of guests |
| Small restaurant still building its identity | Start at 16 to 22 dishes | Pop-ups, recent openings, and operators who would rather under-promise than over-spread |
If you are starting from zero, treat 24 as a working baseline for a small restaurant. It is small enough that a two-person kitchen can run it, large enough that a guest with a restrictive diet can usually find something, and tight enough that purchasing stays sane. From there, the right number is the one your sales data, your kitchen capacity, and your storage will actually support.
Why the count matters more than the dishes themselves
Most menu problems in small restaurants are not really about food. They are about complexity. Every extra dish costs the business in four directions at once, and most operators only notice one of them.
- Food cost: each additional dish that sells fewer than a few covers a night forces you to keep slow-moving ingredients in stock, often in small quantities where unit pricing is worst.
- Labor cost: more dishes mean more prep lists, more misfires, and more time spent 86-ing items that ran out at the wrong moment.
- Speed of service: tickets get longer, line cooks switch stations more often, and the window between order and table slides past the point guests consider normal.
- Perceived quality: guests scanning a long menu often default to the safest option, which means your best dishes get fewer orders and your weaker dishes get dragged down by association.
That is the real reason the question of how many dishes should a small restaurant menu have is worth taking seriously. Each item you keep should be earning its place against all four costs, not just one.
Calculate the dish count your kitchen can actually run
Instead of guessing, the size of a small restaurant menu can be derived from three inputs that you already have or can estimate in an afternoon. The result will be more useful than any industry average because it reflects your room, not someone else’s.
| Input | How to estimate it | Why it limits the menu |
|---|---|---|
| Covers per service on a busy night | Take your last month’s busiest Friday or Saturday | Drives the minimum number of dishes you need so guests can find something |
| Active line cooks during that same peak service | Count hands, including the chef if they are on the line | Each cook can realistically own 6 to 8 dishes without breaking down |
| Distinct core ingredients you can store and rotate | Walk the walk-in and count proteins, key produce, key dry goods | Each dish is usually 3 to 6 ingredients, so this caps how many dishes are realistic |
As a rough formula, a small restaurant menu can usually support about 6 to 8 active dishes per line cook on a busy night, with a small buffer for the chef or expo. If you have two cooks and a chef who jumps in, that puts a realistic ceiling around 20 to 24 dishes, before you start adding daily specials or a dessert section. If the math gives you a number far below what you currently print, the menu is almost certainly doing too much.
How to count dishes so the number is honest
The range in the table above can be misleading if you count dishes the wrong way. Two small restaurants can claim the same number on the menu and have very different complexity behind it. To For additional context, make the count comparable across menus, use the same definition every time.
- One dish equals one printed line with its own price. If “mussels” and “mussels with frites” are listed separately, that is two dishes for counting purposes.
- Size variants count as separate dishes only if the kitchen builds them differently. A small, medium, and large pad thai usually does not, because the line treats them as one build.
- Daily specials count separately if they require their own prep, even if they are not on the printed menu.
- Modifiers are not dishes. “Add chicken,” “add avocado,” or “spice level” do not change the dish count, even though they affect kitchen load.
- Sides and starters are dishes too. A small restaurant menu of 24 should be roughly 5 to 7 starters, 12 to 16 mains, and 2 to 4 desserts, not 24 mains and three token sides.
Counting this way exposes a common distortion. A menu that says 30 dishes is often really 30 lines plus a long list of optional proteins, add-ons, and variations that the line has to remember. The kitchen feels the second number, not the first.
The balance test: how many dishes in each section
Total count is only half the question. How those dishes are spread across starters, mains, sides, and desserts shapes how the menu actually reads, and how much the kitchen can hold. A workable balance for a small restaurant is closer to a rule of thirds than a flat number.
| Section | Share of total dishes | Example for a 24-dish menu |
|---|---|---|
| Starters and small plates | About 25 to 30 percent | 6 to 8 dishes |
| Mains and signature dishes | About 55 to 65 percent | 13 to 16 dishes |
| Sides and shared plates | About 5 to 10 percent | 1 to 3 dishes |
| Desserts and after-dinner | About 8 to 12 percent | 2 to 4 dishes |
| Drinks and coffee | Not counted toward dish total, tracked separately | Owned by the bar program |
These ratios are not a law. A ramen shop will lean heavier on mains and lighter on starters. A tapas bar inverts the ratio. The point is to keep the menu from drifting toward 40 mains and a single dessert, which is one of the most common small restaurant mistakes and a strong signal that the menu was built around the chef’s enthusiasm rather than the guest’s decision.
Signs your small restaurant menu has too many dishes
Most small restaurants do not notice the menu is too large until something breaks. By then, the cost has usually been compounding for months. A few practical checks are more reliable than gut feel.
- The 80/20 test: if 20 percent of your dishes are generating less than 5 percent of sales, the long tail is the first place to cut.
- The 86 log test: if your team is 86-ing more than two or three items most nights, the menu is sized beyond what your purchasing and storage can support.
- The prep list test: if prep takes more hours than your labor budget can absorb, you are paying for a menu sized for a different restaurant.
- The new hire test: if a new line cook needs more than two services to feel confident, the menu is too wide, not the cook.
- The reorder test: if you are ordering low-volume ingredients more than once a week, you are spending purchasing time on dishes that barely move.
Any two of these on a regular basis is a strong sign that the right answer to how many dishes should a small restaurant menu have is a smaller number than the one currently printed.
Signs your small restaurant menu might be too short
The opposite problem is less common, but it is real, and it shows up most often in newer restaurants trying to keep things simple. A menu that is too tight can be just as costly, because it pushes guests into choices the kitchen does not do well and forces daily improvisation that the team has not planned for.
- Guests ask for substitutions more than a few times a night, especially around dietary restrictions the menu does not address.
- Average ticket plateaus or drops even when traffic is up, because there is no clear step-up option.
- The same three dishes appear on every review and every Instagram post, which means the menu has not been built to flex across moods.
- Servers steer constantly toward one or two items because the rest of the menu is not selling on its own.
- You are afraid to remove a dish because you worry there will be nothing left.
In those cases, the fix is not to print 50 dishes. It is to add two or three well-chosen ones that fill the gap, with the same care you would use to remove ten. A small restaurant menu that grows back to 26 well-targeted dishes will outperform a 40-dish menu almost every time.
How menu engineering changes the answer
Once the count is in the right range, the next question is which dishes earn their place. Menu engineering is the practice of sorting items by popularity and profit, then deciding what to keep, move, reprice, or remove. For a small restaurant, the most useful version is a simplified four-quadrant view applied to the top 20 sellers and the slow movers.
- Stars: high popularity, high contribution margin. These are the dishes that pull the room. They should be the easiest to find on the menu and the hardest to drop.
- Plowhorses: high popularity, lower margin. They bring people in but quietly leak money. These are candidates to rework, not to delete.
- Puzzles: low popularity, high margin. They often need a description rewrite, a price nudge, or a better spot on the menu, not removal.
- Dogs: low popularity, low margin. These are the dishes that justify trimming the menu down to its real working size.
If you want a deeper look at how to apply this without flattening the personality of the menu, the journal piece on Menu Engineering Without Killing the Soul of the Menu walks through the same logic with a more editorial lens. For the language on the page itself, the guide to menu descriptions that actually sell covers how to lift the puzzles without adding new dishes.
What to cut first when a small restaurant menu is too big
Trimming a menu is usually emotional, especially when the chef built it personally. A simple order of operations keeps the cuts focused on the business, not the feelings.
- Cut duplicate effort first. If two dishes use the same base and only differ in a garnish, merge them and let one carry the category.
- Cut the lowest sellers that also have the lowest margin. They are losing on both axes, which is rare and usually safe to remove.
- Cut dishes that no server is willing to recommend. If your own team is not selling it, guests are not going to either.
- Cut dishes that depend on a single supplier you do not trust, because every delivery is a risk you can avoid.
- Cut dishes that exist “for the regulars.” If a regular truly loves a dish, they will tell you. If you are guessing, you are probably wrong.
After those cuts, rerun the 80/20 test and the 86 log test. If both improve, the trim worked. If they do not, the problem was probably not the count, and the next place to look is pricing, placement, or description.
Seasonal menus and how they shift the count
Small restaurants that change their menu with the seasons are not really asking how many dishes should a small restaurant menu have, they are asking how many dishes at a time. A seasonal menu usually runs on a three- to four-month cycle, with a small core that stays year-round.
- Core menu: 8 to 12 dishes that almost never change, often the identity of the restaurant.
- Seasonal rotation: 8 to 16 dishes that change two to four times a year, built around what is actually good right now.
- Daily specials: 3 to 6 dishes that change based on what came in, written on a board rather than printed.
That structure keeps the printed menu lean while giving the chef room to cook. It also makes the question of size easier to answer, because the count is really about the printed menu, not the total number of dishes the kitchen can produce in a quarter.
How service style changes the right number
A small restaurant that runs full table service has different constraints than one that runs counter service, and the menu count should reflect that. Service style affects how many dishes a guest will actually consider, and how much the front of house can carry.
| Service style | Realistic dish count | Why the number is different |
|---|---|---|
| Full table service with a server | 22 to 32 dishes | Servers can describe and recommend across a wider list, and guests expect more choice |
| Counter service with a cashier | 14 to 22 dishes | Guests decide faster from a smaller visual field, and the kitchen needs a tight loop |
| Order-at-table with QR or tablet | 18 to 28 dishes | Photos and structure do the selling, so the menu can be a bit wider than counter service |
| Tasting menu only | 5 to 9 courses, not 5 to 9 dishes | The total dish count is fixed, but each course is a build that needs to be rehearsed |
None of these are rules. A small ramen counter can carry 30 dishes because most of them share broth, noodles, and a small set of toppings. A small tasting-menu restaurant might serve 80 covers a night with a 7-course menu because the kitchen is built for repetition, not flexibility. The count is a function of the kitchen, not the format.
A simple method to set your number
For a small restaurant that wants a number it can defend in a budget meeting, a four-step method is usually enough.
- Set a target count between 22 and 30 based on the ranges above.
- Audit the current menu for dishes that do not pass the 80/20 test, the 86 log test, or the new-hire test.
- Cut first, then add, so the new menu is built on what works, not on top of what does not.
- Lock the menu for at least 8 to 12 weeks before judging the results, so the data is real and not a noisy week.
After that cycle, repeat. The size of a small restaurant menu is not a once-a-year decision. It is a quarterly review, because guest behavior changes faster than the menu does.
How to introduce a smaller menu without losing regulars
The hardest part of answering how many dishes should a small restaurant menu have is not the math. It is the conversation with regulars who had a favorite dish that did not survive the cut. A few habits make that conversation easier.
- Frame the cut as focus, not reduction. “We are making fewer dishes, better” is a much better sentence than “We are cutting the menu.”
- Tell servers first, and tell them the reason. A server who understands the food cost story will sell the change instead of apologizing for it.
- Offer to make a removed dish as a special for the first two weeks if you can, so the regular feels heard without the menu carrying the cost year-round.
- Post the new menu online the night before, and pin a short note about the change. Silence is what makes guests imagine the worst.
- Watch the first two weeks closely. A small restaurant menu is a living document, and the first revision after a big change is almost always needed.
Common mistakes when sizing a small restaurant menu
Most of the menus that fail the size test do so for one of a small handful of reasons, all of which are worth naming because they are easy to fall into.
- Building the menu for the chef’s range instead of the kitchen’s capacity. Talent is real, but it is not infinite on a Saturday at 7:30 p.m.
- Adding a new dish every time something runs out, until the menu is a running log of fixes.
- Treating the menu as a marketing brochure, full of options guests enjoy reading but never order.
- Copying a competitor’s count without copying their kitchen, their labor, or their storage.
- Refusing to remove dishes that the team is quietly embarrassed by. Pride is expensive when it lives on the line every night.
Avoiding those traps is more important than landing on any specific number. A small restaurant menu that is owned by the team will outperform a perfectly sized menu that nobody believes in.
Frequently asked questions
What is a good number of dishes for a small restaurant menu to start with?
For most new small restaurants, a working range of 22 to 30 dishes across starters, mains, sides, and desserts is a sensible place to start. That is usually small enough to run with two cooks and a chef, and large enough that a guest with a common restriction can find something without needing a special. The first month is the time to learn, not to lock the menu in stone.
Is 50 dishes too many for a small restaurant?
For most small restaurants, 50 dishes is well past the practical ceiling. Once you are above 35 to 40 dishes, food cost, labor cost, and prep time usually start to climb faster than sales. If a venue is running 50 dishes well, it is almost always because the kitchen and storage are larger than the dining room suggests, or the menu is a collection of small variations on a few real dishes.
How many mains should a small restaurant have on the menu?
A small restaurant menu of about 24 dishes usually carries 12 to 16 mains, depending on the concept. A ramen or taco shop will lean toward the higher end of that range because mains are small and similar. A bistro with a few large signature dishes will lean toward the lower end. The total number matters less than whether each main earns its place against your sales data.
How many dishes should a small restaurant menu have if I also run daily specials?
If you run daily specials, keep the printed menu toward the lower end of the range, around 20 to 26 dishes, and add 3 to 6 specials that change based on what came in. That keeps the printed menu stable enough to manage and gives the chef room to flex without turning every service into an improvisation.
Does cuisine type change the right menu size?
Yes, because cuisine type changes how much the kitchen can share. A cuisine with a narrow base of techniques and ingredients, like ramen, pizza, or a taco program, can run a longer menu without extra strain. A cuisine with wide technique and ingredient variance, like a modern European small restaurant, usually needs a shorter menu to keep quality consistent. The count follows the kitchen, not the cuisine label.
How often should a small restaurant change its menu size?
A practical cadence is to review the menu every 8 to 12 weeks, even if nothing changes. That is enough time to gather real sales data and to notice patterns in 86 logs and prep time. Major reshapes can run on a seasonal cycle, but the size review should be lighter and more frequent, because small drifts add up.
Should a small restaurant cut the menu to save money or to grow the check?
Both, but in that order. A smaller menu almost always lowers food cost and labor cost first, and only later creates room for average ticket to grow through better plating, better descriptions, and a clearer step-up dish. If the only goal is bigger checks, the menu is not the first lever to pull. Pricing, training, and menu descriptions usually move the needle faster with less risk.
How do I know if a dish is earning its place on a small restaurant menu?
The clearest test is a combination of sales rank and contribution margin. If a dish is in the bottom 20 percent of sellers and in the bottom half of margin, it is a strong candidate to cut. If it is low-selling but high-margin, the description, placement, and price are usually the problem, not the dish itself. Single-metric cuts, like removing anything below a sales threshold, tend to throw out puzzles that were close to working.
Does a tasting menu change how I should size my small restaurant menu?
If the entire restaurant runs on a tasting menu, the question of dish count shifts to course count, usually 5 to 9 courses depending on price point and pacing. The kitchen load is then a function of how many covers you do per night and how rehearsed each course is, not how many separate dishes the menu lists. A small tasting-menu restaurant is one of the few cases where a higher dish count per cover is normal, because the menu is a single product, not a catalog.
Where can I learn more about building a small restaurant menu that actually works?
For a broader view of how a menu connects to the rest of the business, the journal pieces on menu engineering without killing the soul of the menu and on menu descriptions that actually sell are the closest companions to this article. Together, they cover the size, structure, and language side of the same decision, and they are written for the same kind of operator.
The honest answer to how many dishes should a small restaurant menu have is the number your kitchen can run, your storage can hold, and your guests can actually read without giving up. For most small restaurants, that number lives between 22 and 30, with a small buffer for daily specials. The job is not to find a magic count. The job is to build a menu that earns its size every night, and to have the discipline to keep it that way.