Menu Engineering: Price Dishes with Better Evidence

Menu engineering compares how often dishes sell with the contribution they generate. It gives restaurant managers a practical way to decide which dishes to promote, refine, test, or retire. Start with reliable sales and recipe records, then treat the analysis as a decision aid rather than an automatic instruction to raise prices.

Choose a meaningful period and compare dishes within similar menu sections. A coffee, a main course, and a sharing platter serve different purposes, so putting them in one popularity ranking can hide useful detail. Record seasonal changes, promotions, and unavailable items before interpreting demand.

Calculate ingredient contribution per dish

A simple ingredient contribution measure is selling price minus recipe ingredient cost, using a consistent treatment of tax and discounts. A hypothetical dish sold for £14 with £4 of ingredients contributes £10 before labour, rent, utilities, payment fees, and other costs. It would be misleading to call that £10 net profit.

Multiply contribution per portion by portions sold to understand the dish's total contribution over the period. A dish with a smaller contribution per portion may contribute more overall if it sells frequently. Keep preparation effort visible too: two dishes with the same ingredient contribution can place very different demands on a busy station.

Compare popularity within a menu section

Calculate each dish's share of sales in its section. If you sold 200 main courses and 40 were the same pasta dish, that pasta represented 20% of main-course sales. Check whether it was available throughout the period before comparing it with another dish that ran out on two busy evenings.

Create a simple working sheet with dish, portions sold, recipe cost, realised selling price, contribution per portion, and total contribution. Add notes for prep complexity and guest feedback. You do not need a complicated scoring model to identify your first few questions.

Turn the analysis into specific experiments

Popular dishes with strong contribution deserve consistency in recipes and availability. A popular dish with limited contribution may need a portion review, a supplier discussion, or a modest pricing test. A less popular dish with strong contribution may need clearer menu wording or a better place on the menu.

• Verify the recipe before changing the price.
• Ask staff what guests misunderstand about the dish.
• Check whether preparation slows another high-demand item.
• Record one proposed change and the measure you will watch.

Do not remove a low-volume dish solely because it sits near the bottom of a spreadsheet. It may serve a particular dietary preference or complete a group's ordering options. Consider its purpose, stock overlap, and operational cost together.

Test one change over comparable services

Suppose a rarely ordered starter has good ingredient contribution but a vague name. Test a clearer description first, keeping its recipe and price stable. Compare comparable services and record changes in availability, guest count, and promotions. If you alter five things at once, it becomes difficult to understand what helped.

A menu review should end with a short action list and a review date. Keep the original numbers so your next decision is based on a comparison rather than memory. Share changes with the kitchen and floor team before printing menus or updating digital channels.

How often should you review the menu?

Use a regular review cycle that suits your concept, with extra checks when ingredient costs or the menu change substantially. Avoid rewriting the menu after one unusual week. Use enough comparable sales to see a pattern, then test a manageable improvement.