Menu Engineering: The 4 Dishes Every Restaurant Menu Has, and What to Do With Each

What menu engineering is: the four dishes every menu has

Menu engineering plots each dish on a simple two-by-two grid. One axis is popularity, meaning how many units you sold in the period. The other is profitability, meaning the contribution margin per unit: the selling price minus the cost of the ingredients on the plate. A dish is either high or low on each axis, which gives four types. Each type calls for a different decision, and that is the whole value of the method: it turns a list of forty dishes into four short to-do lists.

Why food-cost percentage alone misleads

Most owners track food cost as a percentage, and a low percentage feels like a good dish. But a percentage does not pay rent, salaries or suppliers; cash does. A lentil soup with a 20% food cost looks excellent, yet if it sells for QAR 12 it leaves QAR 9.60 a bowl. A burger at 50% food cost looks poor, yet at QAR 34 it leaves QAR 17.00 a plate and sells 400 times a month. The soup's percentage is better, and the burger still contributes far more money. This is the central idea of the Kasavana and Smith method: judge dishes by the margin they bank per plate and by how often they sell, not by the cost ratio alone.

Step 1: Give every dish a costed recipe

Menu engineering is only as good as the cost behind it. In Culina you open Recipes, pick the menu item, add each ingredient with its quantity and unit, and set the yield, which is how many servings the recipe makes. Because your raw materials are received into stock with a real purchase cost, the builder shows the ideal cost per serving, the food-cost percentage and the margin live as you type. That ideal cost is what the Menu Engineering report subtracts from the selling price. Start with your twenty best-selling dishes rather than the whole menu; they usually carry most of your revenue, and you can add the rest as you go.

Step 2: Let sales feed the report, then read the matrix

Switch on recipe depletion (also called backflush) so that every sale issues its ingredients from the kitchen or ingredient warehouse and books the real cost to the ingredient COGS account. With that running, open Reports and then Menu Engineering and choose a period, such as the last 30 days. Culina places each recipe-backed dish on the four-quadrant matrix: popularity is units sold in the period, and profitability is the contribution margin per unit, selling price minus ideal food cost. Items without a recipe are listed but not classified, and a recipe-coverage figure at the top of the report tells you how much of your menu is included.

Step 3: Decide one action per quadrant

The matrix is useful only if it changes what you do on Monday morning. Work through the four types in this order. First protect the Stars: keep recipes and portions stable and keep them visible on the menu. Second, fix the Plowhorses, because they are your biggest volume and a small change repeats hundreds of times a month. A modest price rise, a cheaper but equal ingredient, or a paid extra built as a priced modifier, such as a side or a premium topping, all work. Third, give the Puzzles a chance: place them higher in their category, give them a clearer name and a photo, and have staff suggest them. Last, deal with the Dogs: rework the recipe, reprice, or remove them to simplify the kitchen. Change one or two things at a time, so you can see what worked.

Worked example: a café-restaurant in Doha

Take an eight-dish menu at a Doha café-restaurant, call it Al Dana Kitchen. The figures below are illustrative assumptions, not benchmarks, so replace them with your own. Prices are shown before any tax. The table shows one month of sales, with units sold, selling price, ideal food cost from the recipe, and the margin per plate (price minus cost). The median of units sold across the eight dishes is 270, and the median margin per plate is QAR 19.00. A dish above the median on an axis is high; at or below it is low.

Read the table by margin, not by cost percentage. The Chicken Shawarma Plate and the Lamb Machboos are Stars: both sell above 270 units and earn above QAR 19.00 a plate. The Beef Burger and the Hummus & Bread are Plowhorses: they sell 400 and 390 units but leave only QAR 17.00 and QAR 12.00. The Grilled Hammour and the Mixed Grill Platter are Puzzles, with the two best margins on the menu, QAR 45.00 and QAR 38.00, but only 110 and 240 sales. The Kunafa and the Lentil Soup are Dogs. Notice that the Lentil Soup has the best cost percentage on the menu, 20%, and is still a Dog, while the Hammour at 40% earns QAR 45.00 a plate. Total contribution for the month is QAR 48,155.

Now act on two quadrants only. For the Plowhorse burger, raise the price from QAR 34 to QAR 37. For the Puzzle Hammour, move it to the top of the mains, add a photo and have the team recommend it, with a goal of 30 more plates a month. The table shows the gain, assuming the burger holds its 400 units and the Hammour reaches 140.

The burger move carries a safety margin worth knowing. At the new margin of QAR 20, the burger earns the same QAR 6,800 as today (400 × QAR 17) at 340 units, because 6,800 ÷ 20 = 340. So the price rise still pays off unless the burger loses more than 15% of its sales. Test it for a month, watch the report, and reverse it if the units fall further. These are two small moves on two dishes, and neither needs a new supplier, a new menu or new equipment.

What to check before you trust the matrix

Check three things before acting on any report. First, recipe coverage: if half your menu has no recipe, the matrix describes only half of your sales. Second, the period: choose at least a month of normal trading, and avoid a month dominated by Ramadan or a holiday, since popularity shifts sharply. Third, yield and units: a recipe with the wrong yield gives a wrong cost, and a wrong cost puts a dish in the wrong quadrant. Review the matrix on a regular rhythm, commonly every quarter or whenever ingredient prices move noticeably, and remember that a Dog today may be a borderline case that a small price or cost change would lift into another quadrant.

The bottom line

Menu engineering replaces opinion with a simple rule: judge each dish by how often it sells and how much cash it leaves per plate, then take one action per quadrant. Protect the Stars, fix the Plowhorses, promote the Puzzles and rework or retire the Dogs. Culina, a restaurant management system built on ERPNext and used across the GCC and Iraq, makes this routine: costed recipes with live ideal cost and food-cost %, automatic ingredient depletion on every sale, and a Menu Engineering report that places each recipe-backed dish on the Star, Plowhorse, Puzzle and Dog matrix, with bilingual English and Arabic screens and local-currency reporting in each branch. Cost your top twenty dishes this week, run the report on the last 30 days, and pick one Plowhorse and one Puzzle to act on.