Menu engineering for the hotel restaurant: stars, plow horses, puzzles and dogs

The chef of your hotel restaurant knows which dishes are their favorites, and the manager knows which ones sell the most. Neither one, without a report that crosses both, knows which dishes are actually worth pushing, which need adjusting, and which should come off the menu before they keep taking up a spot another dish would use better.

Two questions, four groups

Menu engineering starts from two simple questions about each dish: does it sell a lot or a little compared to the rest of the menu, and does it earn a lot or a little margin compared to the rest of the menu. Crossing those two answers produces four groups, each with a name that comes from the original discipline but is explained here in plain terms.

• Stars: sell a lot and earn good margin. They are the backbone of the menu.
• Plow horses: sell a lot but earn low margin. They carry volume, not profitability.
• Puzzles: sell little but earn good margin when they do sell. The challenge is getting them ordered more.
• Dogs: sell little and earn low margin. Clear candidates to come off the menu.

Where the data comes from: the sales mix report

None of this works from the chef’s intuition or the manager’s memory. It needs a sales mix report over a reasonable period, usually a month or a full season, showing how many units of each dish sold and what the contribution margin was for each one, that is, the selling price minus the recipe cost.

In a hotel restaurant, this report has an extra layer an independent restaurant does not have: sales need to be split by revenue center, because a dish can be a star in the main restaurant and a dog at the pool bar, as explained in the guide to closing out by revenue center (A guide to the shift close by revenue center in a hotel). Mixing all revenue centers into one number hides that difference.

How to calculate the line between high and low

A dish is classified as high-selling when its number of units sold sits above the simple average for the whole menu, and as high-margin when its contribution margin sits above the simple average for the whole menu. You do not need a fancier formula than an average to start; what matters is applying the same cutoff to every dish in the same period.

What to do with each group in a hotel restaurant

Stars: protect them, do not experiment on them

The common mistake with stars is touching them exactly because they are doing well. Changing the recipe of a star dish to cut cost, hoping the guest will not notice, is a high risk for a small gain. Stars are protected by keeping consistency: same flavor, same portion, same photo on the digital menu.

Plow horses: the volume that carries the operation

These dishes are usually the classics guests expect to find, even if they are not the most profitable. The lever here is not removing them, it is checking whether the recipe cost went up without the price adjusting, or whether a small price adjustment fits without changing the guest’s sense of value.

Puzzles: the potential nobody sees

A dish with good margin that almost nobody orders may be hiding in a low-visibility spot on the menu, without a photo, or with a name that does not explain what it is. Before removing it, it is worth moving it to a more visible spot, describing it better, or actively suggesting it, and measuring whether that changes its sales before deciding its fate.

Dogs: the hardest decision

Taking a dish off the menu creates resistance, almost always from the chef who designed it. But a dish that sells little and earns little takes up space on the menu, in inventory and in kitchen attention that a better dish would use more effectively. The decision does not have to be drastic: sometimes redesigning it is enough before removing it entirely.

The cycle: reviewing the menu is not a one-time task

Menu engineering is not an exercise done once and filed away. Recipe cost changes with the supplier, the season shifts guest volume, and a dish that was a star in high season can turn into a puzzle in low season. The practical recommendation is to run this report every quarter, or whenever the hotel’s guest volume shifts noticeably.

The starting point for this cycle is the hotel’s reports (Reports), where the sales and margin history per dish should live, ready to be compared period against period without someone having to build that comparison by hand on a separate sheet.

1. Run the sales mix report for the period, split by revenue center.
2. Calculate the average units sold and the average contribution margin for the whole menu.
3. Classify each dish into one of the four groups based on those two averages.
4. Decide a concrete action per group, not a generic action for the whole menu.
5. Apply the changes and run the report again next period to see if dishes moved groups.

An illustrative example with numbers

The figures below are invented to show the calculation. Imagine a menu of ten main dishes in a hotel restaurant, with an average of 42 units sold per month and an average contribution margin of 95 pesos per dish.

• The grilled steak sold 68 units with a margin of 80 pesos: high sales, margin below average, it is a plow horse.
• The Veracruz-style fish sold 25 units with a margin of 130 pesos: low sales, margin above average, it is a puzzle.
• The shrimp pasta sold 61 units with a margin of 110 pesos: high sales and high margin, it is a star.
• The seasonal salad sold 14 units with a margin of 60 pesos: low sales and low margin, it is a dog.

With this classification, the action for the quarter is clear: protect the shrimp pasta as it is, check whether the grilled steak can go up 15 pesos without losing volume, move the Veracruz-style fish to a more visible spot on the digital menu, and decide whether the seasonal salad gets redesigned or removed before the next period.

The four-quadrant classification only works if it is repeated on a fixed schedule, not just once after a slow month. A hotel restaurant that reviews its sales mix every quarter catches a puzzle before it quietly becomes a dog, and catches a star before its rising cost erodes the margin nobody is watching. The report is cheap to run again; the guesswork it replaces is what used to cost real revenue.

Common mistakes in menu engineering

• Classifying dishes by the chef’s intuition instead of the real sales mix report.
• Mixing sales from every revenue center in the hotel into a single number.
• Calculating margin with the tax-inclusive price instead of the real contribution margin.
• Touching a star’s recipe to cut cost without measuring whether the guest notices the change.
• Keeping a dog on the menu for years just because the chef is fond of it.
• Doing the exercise once and never repeating it when the season changes.

What to do this week

1. Ask for last month’s sales mix report, split by the hotel’s revenue centers.
2. Calculate the average units sold and the average contribution margin for the menu.
3. Classify at least the ten dishes with the highest share of sales.
4. Identify which star dish should not be touched and which dog is a clear candidate to remove.
5. Define a concrete action for the puzzles: where to move them on the menu or how to describe them better.
6. Schedule the next review of the report for three months from now.

Inn Restaurant generates the sales mix report by revenue center for the hotel, with the contribution margin calculated from the recipe cost you already have loaded. If you want to see how your restaurant’s menu would be classified today, book a 15-minute demo (contact).