A Menu Engineering Example That Drives Profit
A menu engineering example becomes useful when it changes what happens during a real service. The goal is not to make a menu look more clever. It is to identify which items create profit, which ones create sales volume, and which ones quietly consume labor, inventory, and attention without paying the restaurant back.
For an independent restaurant, menu engineering is one of the clearest ways to improve margins without immediately raising prices across the board. It connects your recipe costs, POS sales data, menu layout, staff recommendations, and purchasing decisions into one operating system.
What Menu Engineering Measures
Menu engineering compares two things for every menu item: contribution margin and popularity.
Contribution margin is the selling price minus the direct food cost. If a chicken sandwich sells for $16 and costs $5.20 in ingredients and packaging, it generates a $10.80 contribution margin. That money helps cover labor, rent, utilities, marketing, and profit.
Popularity is simply how often the item sells compared with the rest of its category. A high-margin item that barely sells may need better placement, a clearer description, or a staff recommendation. A low-margin item that sells constantly may be protecting sales volume while damaging the bottom line.
This is why food cost percentage alone can mislead operators. A $12 item with a 25% food cost contributes $9.00. A $28 item with a 35% food cost contributes $18.20. The second item has a higher food cost percentage but produces more dollars toward overhead and profit.
A Practical Menu Engineering Example
Consider a fast-casual Mediterranean restaurant reviewing its lunch entree category. The owner has clean sales data from the POS and standardized recipes for each item. Over a 30-day period, the restaurant sells 1,000 entrees across four core dishes.
| Menu item | Menu price | Direct food cost | Contribution margin | Units sold | Classification | | — | —: | —: | —: | —: | — | | Chicken shawarma bowl | $15.00 | $4.80 | $10.20 | 420 | Star | | Falafel bowl | $13.00 | $3.60 | $9.40 | 310 | Plowhorse | | Lamb kebab plate | $22.00 | $10.50 | $11.50 | 95 | Puzzle | | Veggie wrap | $11.00 | $4.70 | $6.30 | 175 | Dog |
The average contribution margin is $9.35 per entree. The average sales volume is 250 units per item. From there, each dish falls into one of four familiar categories.
Stars: Protect and Promote
The chicken shawarma bowl sells well and delivers above-average margin. This is a Star. The restaurant should protect it from unnecessary changes and give it prominent placement on the menu, online ordering site, and third-party delivery platforms.
The operational question is whether the dish can maintain quality during busy periods. If the bowl is popular but line staff build it differently every shift, the theoretical margin on the spreadsheet will not match actual cost. Standard portion tools, recipe cards, prep labels, and assembly training matter as much as the menu design.
Plowhorses: Improve Margin Without Losing Demand
The falafel bowl has strong demand but sits just under the category’s average contribution margin. It is a Plowhorse. These items deserve careful attention because even a small improvement affects a large number of sales.
The owner should not automatically increase the price. First, review the recipe. Is the tahini portion consistent? Is the bowl receiving too much rice? Are guests choosing costly modifications that are not priced correctly online? Could a $1 add-on for premium toppings protect the base price while raising the average check?
A modest $0.60 reduction in food cost would move the contribution margin to $10.00. Across 310 monthly sales, that is $186 more contribution from one item without depending on extra traffic.
Puzzles: Give Guests a Reason to Choose Them
The lamb kebab plate has the best dollar margin in the category, but it sells below average. This is a Puzzle. It may not be a bad menu item. It may be poorly positioned, confusingly described, priced without context, or difficult for staff to recommend.
Before discounting it, test the presentation. Replace a generic name with a description that communicates value, such as char-grilled lamb kebabs with saffron rice, grilled vegetables, and house garlic sauce. Make sure the photo used for digital ordering reflects the actual portion. Train cashiers to suggest it to guests looking for a hearty plate rather than a quick bowl.
Price can also be part of the issue, but it depends on the restaurant’s market and portion strategy. If the plate is priced at $22 while similar competitors sell comparable entrées at $19, lowering the price may increase volume. If it is clearly more substantial than nearby options, the better answer may be to reinforce the value rather than reduce the price.
Dogs: Decide, Do Not Ignore
The veggie wrap has low sales and low contribution margin. That places it in the Dog category. The worst response is to leave it untouched because removing a menu item feels risky.
Start by checking whether it serves a real purpose. It may be the only handheld vegetarian option, which could make it strategically necessary even if sales are modest. If that is the case, simplify the build, use ingredients already stocked for higher-selling dishes, and improve the margin.
If the wrap has no clear role and creates separate prep, spoilage, or training complexity, removal may be the right decision. A small menu is not automatically a better menu, but every item should justify its inventory, labor, and space.
Turn the Analysis Into Menu Changes
The numbers are only the starting point. A usable menu engineering process turns findings into controlled changes that staff can execute.
First, validate the data. POS item names should match the recipes and the menu labels. If one chicken bowl appears under several buttons, or modifiers are not tracked consistently, the sales analysis will be unreliable. This is a common issue when in-store POS menus, online ordering menus, and delivery platforms are managed separately.
Next, review recipe costing before changing prices. Ingredient costs move, portions drift, and vendor substitutions happen. A menu price based on last year’s chicken cost can create a false sense of profitability. Update costs from current invoices and confirm that each recipe reflects the way the kitchen actually prepares the item.
Then make targeted changes. Place Stars where guests will see them first. Improve descriptions for Puzzles. Adjust portioning or add-ons for Plowhorses. Simplify or remove Dogs that create operational drag. Avoid redesigning the full menu based on one week of sales or a single vendor price increase.
Finally, measure the result for at least four weeks. Watch unit sales, contribution margin, food cost, modification behavior, refund patterns, and ticket times. A menu change that increases margin but slows the line during lunch may not be a win. The best decision balances profit, guest demand, and operational capacity.
Why Menu Design Still Matters
Menu engineering is not limited to a spreadsheet. Guests cannot order what they do not notice or understand.
Use clear category structure, readable item names, and descriptions that answer the buying question: what is it, what comes with it, and why is it worth the price? On digital menus, this also means accurate photos, logical modifier groups, and no duplicate items across channels.
Do not rely on gimmicks like excessive boxes, arrows, or inflated descriptions. Guests should feel guided, not pushed. A clean bilingual menu can be especially valuable when it helps more customers order confidently without creating confusion for the kitchen.
A well-run restaurant does not treat menu engineering as a one-time redesign. It is a recurring operating review, usually quarterly or whenever costs, sales patterns, or service models change. When the POS, recipes, kitchen procedures, and menu presentation are aligned, the menu becomes easier to sell, easier to produce, and more profitable to operate.
Start with the items your team already makes every day. The clearest opportunity is often not a new dish, but a better decision about the menu item already sitting in front of your guests.
Is Your Menu Working as Hard as Your Kitchen?
We analyze POS workflows, item engineering, and design layout to eliminate operational bottlenecks and boost profitability.







