How to Decide What Items Should Be on Your Restaurant Menu

Start from your concept and build a long list

Before choosing dishes, write one sentence describing what your restaurant is for: for example, a neighbourhood place for quick, honest lunches, or a place for slow shared dinners with local wine. That sentence is your filter. A dish that does not fit it confuses guests and complicates the kitchen.

Then brainstorm freely. Ask the kitchen team, the servers and regular guests what they would like to see. Collect twice as many ideas as you expect to keep. The point of a long list is that you choose from it, rather than defending the first idea that came to mind.

Score every dish on the same five questions

For each candidate, ask five questions and give it a simple score from one to three on each. Do our guests want it? Does it earn a healthy margin at a price they would accept? Can the kitchen produce it quickly and consistently? Does it share ingredients with other dishes? Does it strengthen the menu, or duplicate something we already have?

Add up the scores. The aim is not mathematical precision but an honest conversation. A dish with high guest appeal and a poor margin might be kept as a signature and priced carefully. A dish that is cheap and easy but that nobody asks about probably does not earn a place.

Do the scoring with the people who will cook the dishes. They will spot problems, such as a garnish that needs its own prep station, that never show up in a menu draft.

Use overlapping ingredients to keep the kitchen sane

Every unique ingredient is something to buy, store, prepare and, if it does not sell, throw away. When several dishes share components, such as a sauce, a marinade, a base or a vegetable, you buy in more sensible quantities and waste less.

Look at your shortlist and write down the ingredients for each dish. Any ingredient that appears in only one dish deserves a second look. Sometimes it can be replaced by something you already stock; sometimes it is exactly what makes the dish special, and worth keeping.

Also think about prep timing. Dishes that can be partly prepared in advance are easier to serve at speed during a rush than dishes that must be built from scratch every time.

Balance the menu across categories, prices and dietary needs

A good menu is more than a list of good dishes. Look at the balance: a mix of lighter and heavier plates, several kinds of protein, and a spread of price points so that both the budget-conscious guest and the celebrating table find something. Include at least a few dishes for guests who do not eat meat, and make sure they are genuinely appealing rather than an afterthought.

Describe dishes clearly, including the main ingredients, so guests with allergies or restrictions can ask informed questions. If a guest has a serious allergy, the reliable route is always a conversation with staff; no menu, printed or digital, should replace that.

Keep the total manageable. Guests facing too many choices tend to slow down, and your kitchen faces too many possible combinations of orders. If a category is crowded, cut the weakest items before adding new ones.

Launch, watch the sales and prune

The first version of a menu is a hypothesis. Once it is live, the real test starts: what do guests actually order? The gap between what you expected to sell and what really sells is the most useful information you will get.

ChargeM3's analytics dashboard shows order trends and best-sellers, so you can see which dishes carry your menu and which barely move. Check it on a regular schedule and act on items that consistently sell poorly: reposition them, rewrite the description, adjust the price or remove them.

Because items can be added, edited or removed in minutes, you can test a new dish for a few weeks and drop it without a reprint if it does not work. When something runs out, real-time availability lets you mark it sold out instantly, so guests only see what you can serve.

Frequently Asked Questions