The house pasta sells all night, but do you know what each plate leaves behind? A short weekly menu review can help you spot the dishes worth featuring, fixing, or reconsidering.

It is Friday night. The house pasta has gone out twelve times, the new chicken bowl twice, and someone at the pass is asking whether the special should stay on next week's menu. You know what guests ordered. You may be less sure what each dish cost to make after the latest supplier invoice, a generous pour, or a change in portion size.

A useful menu review does not need a spreadsheet worthy of a finance department. Set aside a short block once a week, look at what sold beside what each serving costs, and decide what to test next. The point is not to turn dinner into an accounting exercise. It is to avoid making menu decisions from memory alone.

Two questions, not one

Start with two separate signals: popularity and contribution margin. Popularity answers, "How often did guests order this?" Contribution margin is the menu price minus the direct ingredient cost for one serving. It is the amount left to help cover labor, rent, utilities, and the rest of the restaurant's costs. It is not the same thing as final profit.

Those signals tell different stories. A popular dish can have a slim margin. A dish with a healthy margin can sit untouched because guests do not notice it, do not understand it, or simply prefer something else. Looking at only sales volume can reward the first dish while overlooking the second. Looking only at ingredient cost can lead you to keep a profitable item that barely sells.

That popularity-and-margin pairing is a common menu-analysis framework. You can borrow the basic questions without adopting anybody else's labels or buying a new tool.

Gather a small, honest set of numbers

Pick a consistent period, such as the last full week. For each menu item you want to review, write down its number of orders, menu price, and estimated ingredient cost per serving. A point-of-sale sales report can help with the first number if it records items clearly. Your recipes, purchase invoices, and portion notes help with the cost estimate.

Keep the first pass manageable. You might review the ten items with the most orders, plus a few new or slow-moving dishes you care about. If the menu is small, review all of it. A short list you revisit is more useful than a giant file nobody wants to open after week one.

For a simple example, imagine a soup sells 18 portions at $8 each. If its ingredients cost about $2.40 per portion, the estimated contribution margin is $5.60 per bowl. A grilled sandwich might sell 30 portions at $12, with $5.50 in ingredients, leaving $6.50 per sandwich. The soup sells less often and leaves less per serving, but it may still earn its place. These figures are examples, not a target or a verdict.

To see the total contribution from an item during that period, multiply its per-serving margin by portions sold. In this example, the soup contributes about $100.80 before other restaurant costs, while the sandwich contributes about $195. That comparison can help with planning, but it does not tell you which dish is more profitable after labor, waste, rent, or every other expense. Keep the label honest: estimated contribution, not profit.

Check the recipe before you blame the menu

Ingredient cost is only useful when the recipe and serving size are close to what the kitchen actually puts on the plate. Before changing a price, check a few ordinary details:

• Are the recipe quantities current, including garnishes, sauces, cooking oil, and sides?
• Did supplier prices change, or did the team switch brands or pack sizes?
• Are portions consistent across shifts?
• Does the cost estimate account for edible yield when trimming or cooking changes the usable amount?

You do not need laboratory precision for every herb leaf. You do need a reasonable estimate for the ingredients that move the number most. If the salmon portion varies by a few ounces from plate to plate, refining the cost of a pinch of pepper will not fix the bigger uncertainty.

Check one or two recipes with the person who prepares them. A recipe card may say four ounces, while the real serving has quietly grown because the team wants guests to feel well fed. That might be a deliberate choice. Either way, write down the version you actually serve before deciding the item is underpriced.

Sort the results into decisions

Once you have a consistent week of estimates, place each item in a simple working group. You can use a sheet with columns for orders, price, ingredient cost, estimated margin, and next action. Avoid turning the groups into permanent labels. They are prompts for a conversation, not a menu horoscope.

• Popular and healthy margin: Keep the item dependable. Make sure the kitchen can produce it consistently, and consider giving it visible menu placement if that suits the guest experience.
• Popular but thin margin: Check portions, current ingredient prices, and add-ons. You might adjust the recipe, price, or side, but consider guest expectations and nearby alternatives before changing a familiar favorite.
• Less popular but healthy margin: Ask whether guests can find and understand it. A clearer description or a small, time-limited feature can test interest without committing the whole menu.
• Less popular and thin margin: Look for a specific reason to keep it, such as a dietary option, a seasonal role, or a useful ingredient shared with other dishes. If there is no good reason, consider a careful replacement.

These are not universal rules. A vegetarian dish may matter to the restaurant even if it does not lead the sales report. A slow-selling item may bring a guest through the door, complete a family meal, or use an ingredient that would otherwise spoil. Add those realities to the discussion instead of asking a table of numbers to make the whole decision.

Change one thing, then watch

When an item disappoints, avoid changing its price, portion, name, placement, and recipe all at once. If sales improve or fall, you will not know which change mattered. Choose one sensible test and give it a set review date.

For instance, if a side dish is rarely ordered, try a more concrete description for two weeks while leaving its price and recipe alone. If a high-volume entree has a shrinking margin, check the serving weight and current invoice before deciding whether a portion adjustment or price change is appropriate. Tell the team what changed and when to flag guest reactions. Keep notes, even if they are only two sentences in a shared shift log.

Compare similar periods when you can. A rainy Tuesday is not a fair match for a sunny holiday weekend, and a new menu item may need time before its sales settle. If the week was unusual, note why and avoid treating it as a clean trend.

A review the team can actually keep

Make the routine small enough to survive a busy month. One person can pull sales counts, another can confirm recipe costs, and the owner or chef can choose the next test. If those jobs all belong to one person, that is fine too. Put the review on the calendar and keep the same handful of measures from week to week.

At the end, write down three things: what changed in the numbers, what you decided, and when you will check again. A note such as "Chicken bowl orders rose after the menu description changed; check again next Friday" is more useful than a color-coded chart no one remembers how to read.

If you use a POS to track item sales, keep the item names and modifiers tidy enough that the report answers a real question. A report cannot distinguish a side from an entree if both ring under the same vague button. For help managing everyday sales and operations, you can download M&M POS.

Menu review works best as a recurring conversation between the numbers and the people cooking and serving the food. The report can point to a question. The team can explain what changed on the plate, what guests say, and whether the next adjustment makes sense. Then you try one thing and look again next week.

Direct URL: https://mmpos.app/download