/
Most restaurant operators know their overall food cost percentage, but far fewer know the contribution margin of every item on their menu. That gap is where profit quietly disappears. See how R365’s recipe costing tools and menu engineering reports bring food cost data and sales analytics together so operators can act on what the numbers actually show.
Menu engineering is one of the most powerful profitability levers available to restaurant operators — and one of the most underused. The concept is straightforward: analyze every menu item by how much profit it generates and how often guests order it, then adjust pricing, placement, and composition accordingly. The challenge is not the theory. The challenge is having the right data, in the right format, updated frequently enough to act on. We built Restaurant365 to bring those data streams together and make menu engineering repeatable for operators.
This guide walks you through the complete menu engineering framework, the specific data you need, how to source it, and the software that makes the process repeatable. You will learn how to classify every item on your menu, make smarter pricing decisions, and turn menu analysis from an annual project into a quarterly management tool.
For a foundational overview of the discipline, see R365’s guide to menu engineering for restaurant owners and operators and what is menu engineering and how does it increase restaurant profit.
Menu engineering was formalized by professors Michael Kasavana and Donald Smith in the 1980s. The core framework classifies every menu item along two dimensions:
Profitability: The contribution margin of each item — selling price minus food cost
Popularity: The number of orders each item receives as a share of total category orders
By plotting each item against these two dimensions, you create a clear picture of which items drive your bottom line and which ones drag it down.
For more on how the framework applies to modern restaurant operations, see R365’s guide to recipe and menu engineering and 6 menu engineering tips and tricks to impact your restaurant’s bottom line.
Before diving into the framework, here are the essential terms you will encounter throughout this guide:
Contribution margin: The menu selling price minus the food cost of an item. This represents the absolute dollar profit per item sold, before labor and overhead. A $22 entrée with $6 in food cost has a $16 contribution margin.
Food cost percentage: Food cost divided by selling price, expressed as a percentage. That same $22 entrée has a 27.3% food cost percentage.
Price elasticity: How much guest demand changes when you change the price. An item with low price elasticity holds its sales volume even after a price increase. An item with high price elasticity loses volume quickly when the price goes up.
Sales mix: The breakdown of which items guests order and in what proportions. Your POS system generates this data.
Actual vs. theoretical (AvT) food cost: The difference between what your food cost should be (based on recipes and sales mix) and what it actually is (based on purchases and inventory). The gap reveals waste, portioning errors, and theft.
For a deeper look at each of these concepts, see R365’s recipe costing vs. food costing guide and the actual vs. theoretical food cost guide.
The Kasavana-Smith matrix sorts every menu item into one of four categories. Each category calls for a different strategy.
| Quadrant | Profitability | Popularity | Strategy |
|---|---|---|---|
| Stars | High | High | Protect and promote |
| Plowhorses | Low | High | Optimize margins |
| Puzzles | High | Low | Increase visibility |
| Dogs | Low | Low | Remove or redesign |
Stars are your best performers. Guests love them, and they generate strong margins. Your strategy is simple: protect these items.
Plowhorses sell well but leave less money on the table per order. These items deserve careful attention because small changes can produce big results across high volume.
Options for improving Plowhorse margins:
Melissa Rickman, a restaurant operator, described this exact scenario when reviewing her appetizer category. She discovered a 30% increase in pasta sheet costs was crushing margins on one item. After analyzing her full sales mix, she realized she sold 3 times more of her higher-margin appetizers. The math showed that a $1 price increase on the low-margin item, combined with strong sales of the profitable items around it, made the overall category work. “At the end of the day, you’re taking dollars to the bank, not percentages,” she explained.
Puzzles make you good money when ordered — guests just do not order them often enough. The goal is to increase their visibility without fundamentally changing them.
Dogs take up menu space, complicate prep, increase inventory complexity, and generate minimal revenue. In most cases, you should remove them.
Before cutting a Dog, ask two questions:
If the answer to both is no, remove it. Maru Hospitality Group took this approach after running their menu item analysis report in Restaurant365. “Overall, we reduced our menu options by about 20% so that we could focus on our more profitable and more popular items,” explained Lorenzo Castillo. The result: sales on repositioned items jumped more than 20% on the very next menu.
For a deeper breakdown of how each quadrant strategy plays out in practice, see R365’s how to identify top-selling and least profitable menu items and menu engineering: 9 steps to drive greater restaurant profit.
The framework is simple. The data requirements are not. Here is exactly what you need and where to get it.
This is the total cost of all ingredients in one serving, using current purchase prices. Not the price you paid 3 months ago — the price you are paying now. A 15% increase in protein prices over 6 months can silently move a Star into Plowhorse territory.
You need:
How many of each item sold over a given period, organized by category. Appetizers, entrées, desserts, and beverages should each be analyzed separately. Your POS system generates this data.
Selling price minus food cost equals contribution margin. This is the number that matters most for menu engineering — not food cost percentage.
Why contribution margin matters more than food cost percentage: a $30 steak with a 35% food cost ($10.50) generates a $19.50 contribution margin. A $12 pasta with a 25% food cost ($3.00) generates a $9.00 contribution margin. The steak has a worse food cost percentage but puts more than twice as many dollars in your pocket per order.
An item that represents 35% of all entrée orders is popular. An item at 3% of entrée orders is a Puzzle or a Dog, depending on its margin.
Most restaurant operators know their overall food cost percentage. Fewer know the food cost percentage of each individual menu item. Fewer still can produce an updated analysis quickly when ingredient prices change.
As Gregg Majewski, a multi-unit franchise operator, put it: “We have franchisees that tell me they’re running food costs and their food costs is their purchases. That’s not food costs. You got $10,000 of inventory sitting in your freezers. That’s not food costs. That’s just waste.”
For a practical breakdown of how to pull and organize this data, see R365’s 6 key operational reports to boost your menu engineering and the food cost guide: formula, benchmarks, and how R365 helps.
Follow these 8 steps to run a complete menu engineering analysis.
Define your analysis period. Use at least 90 days of data, ideally 6 months. Short periods overweight unusual days and underweight seasonal patterns.
Pull your sales mix. From your POS, export the count of each menu item sold over the analysis period. Organize by category — appetizers, entrées, desserts, and beverages analyzed separately.
Calculate current food cost per item. For each item, total the ingredient cost at current purchase prices. This requires a standardized recipe with precise, yield-adjusted quantities multiplied by current vendor prices. If you do not have current prices, use your most recent invoices.
Calculate contribution margin. Menu price minus food cost equals contribution margin. Focus on absolute dollars, not percentages.
Establish thresholds. For popularity, the threshold is typically the average number of items sold per category. Items above average are popular; below average are not. For profitability, the threshold is the average contribution margin for the category.
Plot and classify. Place each item into Stars, Plowhorses, Puzzles, or Dogs based on where it falls relative to your thresholds.
Act on the findings.
Dogs below 3% of category volume: candidates for removal.
Plowhorses with contribution margins more than 20% below the category average: candidates for price increases or portion adjustments.
Puzzles: reposition on the menu, improve descriptions, train servers.
Stars: protect and promote.
Reassess quarterly. Ingredient prices change. Guest preferences shift. A Star in January may become a Plowhorse by July if protein costs have moved. The analysis is only as useful as it is current.
For a step-by-step walkthrough of the full process, see R365’s menu engineering: 9 steps to drive greater restaurant profit and how to calculate food cost percentage for a practical breakdown of the cost calculations each step requires.
Menu engineering without software is possible but slow. The manual workflow looks like this:
A skilled analyst can produce a complete analysis in a day. Most operators do not have that analyst and do not have that day. The result: menu engineering becomes an annual exercise instead of a quarterly discipline.
Software makes this practical by connecting recipe costs to current purchase prices automatically. When chicken prices increase, the food cost of every item containing chicken updates instantly. The contribution margin analysis always reflects current costs, not last month’s prices. Restaurant365 automates those connections so operators can update analyses quickly and repeatedly.
For more on how automation transforms the menu engineering workflow, see R365’s ultimate guide to recipe costing and menu engineering and boosting restaurant profitability through menu engineering strategies.
Toast POS produces strong sales mix data — which items sold, how many, at what price, and when. This covers the popularity side of menu engineering well.
However, Toast does not include recipe costing. It does not know what each item costs to produce. To run a full menu engineering analysis, Toast users must export sales data and import it into a separate recipe costing tool or spreadsheet. The sales data and cost data live in different systems, which means the analysis requires manual assembly each time you run it.
For more on what a fully integrated workflow delivers versus a disconnected one, see R365’s 6 key operational reports to boost your menu engineering and R365 integrations page to see how POS data flows automatically into the platform.
We integrate the sales data (from your POS) and the cost data (from the recipe management and Inventory & Purchasing modules) in one platform. A menu engineering analysis in Restaurant365 uses current purchase prices — because those prices flow from the purchasing and receiving workflow in the same system — alongside current sales mix data from your POS.
The result:
Eric Steinbach, COO of Eli’s Restaurant Group, described the transformation: “Being able to have that data built out in the system through the AP gives us the ability to do that, without having to go to a file cabinet, pull out an invoice, and do all the mental math.” After implementing Restaurant365, Eli’s improved their theoretical food costs by 2.5%–3% and saved $500,000 in food and LBW costs.
Matchbox LLC experienced similar results. Operating Systems Manager Brian Anderson used Restaurant365 to verify recipe accuracy, compare theoretical and actual cost variances, then ran a menu engineering report that ranked each item by its bottom-line contribution. The result: a 2% reduction in food cost.
See how Restaurant365 connects recipe costing and sales data for ongoing menu engineering. Request a Demo →
For a broader look at how the platform’s reporting tools drive these results, see R365’s webinar: three operators share how they turned data into profitability and how to identify top-selling and least profitable menu items.
Menu pricing is not purely a cost calculation. Price elasticity varies significantly by item, price point, and concept. Here is practical guidance for making pricing decisions with data.
Unique, high-popularity items with no close substitute on your menu. A 10% price increase on a Star item that drives 8% of total revenue typically generates minimal volume decline and meaningful margin improvement.
Items where your price is below the local market average. Melissa Rickman discovered her libations pricing was 3 years stale. After comparing her prices against similar full-service restaurants in her county, she found room for $3–$4 increases on some cocktails. “That was my fault for waiting so long,” she said.
Commodity items where guests have ready alternatives. A 10% increase on a Plowhorse that competes directly with similar items at nearby restaurants may generate measurable volume decline.
Items near a psychological price ceiling. Moving an appetizer from $17 to $19 crosses a threshold that can feel significant to guests, even if the math supports it.
One of the most common pricing mistakes is obsessing over food cost percentage rather than contribution margin dollars. A high-volume item with a 33% food cost that generates $14 in contribution margin per plate is more valuable than a low-volume item with a 22% food cost that generates $7.
As Melissa Rickman learned during her menu engineering process: “At the end of the day, you’re taking dollars to the bank, not percentages.”
For a deeper dive into pricing strategy, see R365’s restaurant menu pricing strategy guide and how to calculate food cost percentage to build the cost foundation that pricing decisions depend on.
The operators who commit to regular, data-driven menu engineering consistently outperform on food cost and profitability. Here are documented results.
Read the full Maru Hospitality Group case study.
Read the full Eli’s Restaurant Group case study.
Read the full Matchbox LLC case study.
Michael Leemann, who operates restaurants across 12 states, combines the menu item analysis report with the AvT report on a period basis. “What is our sales mix? What is the profitability of those items? So really that’s how we’re measuring it and see who the top winners are, where we have opportunities as well,” he explained.
The restaurant industry moves fast. Ingredient prices shift with commodity markets, tariffs, and supply chain disruptions. Guest preferences evolve with seasons, trends, and economic conditions. A menu engineering analysis from 6 months ago may no longer reflect reality.
Best practices for staying current:
For more on how to build a recurring menu engineering discipline, see R365’s actual vs. theoretical food cost: closing the gap and 11 essential techniques for controlling restaurant food costs.
Run a full menu engineering analysis at least quarterly. If ingredient prices are volatile or you are preparing for a menu change, increase to monthly. Use a platform like Restaurant365 that keeps recipe costs updated in real time so you can pull reports whenever you need them. See how R365’s recipe costing tools keep costs current automatically.
Food cost percentage tells you what share of the selling price goes to ingredients. Contribution margin tells you how many dollars each sale puts toward covering labor, overhead, and profit. Menu engineering prioritizes contribution margin because it measures absolute profit per item. See R365’s recipe costing vs. food costing guide for a full breakdown of how each metric is used.
Not necessarily. Some Dogs serve a strategic purpose — a kids’ menu item that keeps families coming, or a low-cost option that rounds out a category. But Dogs that represent less than 3% of category volume and have no strategic value should be removed. They add complexity to prep and inventory without generating meaningful revenue. See R365’s guide to identifying top-selling and least profitable menu items for help making the call.
Increase prices on unique, high-popularity items first — they have the most pricing power. Avoid large jumps; incremental increases of 3–5% are less noticeable to guests. Compare your prices against similar concepts in your market to ensure you remain competitive. Always base increases on current food cost data, not instinct. See R365’s restaurant menu pricing strategy guide for a full framework.
Restaurant365 connects with leading POS platforms — including Toast, Square, and Aloha — to import sales and labor data automatically. This POS integration feeds the sales mix data directly into the same platform where your recipes, inventory, and purchasing data live, enabling real-time menu engineering analysis. Learn more about R365 integrations.
Yes, but it is slow and difficult to repeat. Manual analysis requires exporting POS data, building cost spreadsheets, and recalculating every time prices change. Most operators who attempt manual menu engineering do it once a year at most. Software like Restaurant365 makes the process fast enough to do quarterly or even on demand. See R365’s ultimate guide to recipe costing and menu engineering for more on what a repeatable process looks like.
Menu engineering is not a one-time project. It is an ongoing discipline that separates the most profitable restaurants from the rest. The operators who connect their food cost data to their sales analytics — and act on what the data reveals — consistently outperform on margins, reduce waste, and build menus that guests love.
Ready to see how Restaurant365 streamlines menu engineering with real-time recipe costing, sales analytics, and AvT reporting in one platform?
Blog Menu
Menu engineering works. The operators featured throughout this guide did not find an extra $1.2 million or close a $1.5 million profit gap by accident. They ran the analysis, acted on what the data showed, and repeated the process until it became a discipline. The barrier for most operators is not motivation, it is the speed and accuracy of the data. When recipe costs are stale, when sales data lives in a separate system, and when the analysis takes a full day to assemble, it gets done once a year if at all. Restaurant365 was built to close that gap, connecting current ingredient prices, real-time sales mix, and AvT reporting in one platform so the analysis takes minutes instead of a day. The menu is one of your most powerful profit levers.
Request a free demo to see how R365 makes menu engineering something you can act on every quarter, not just when the margins are already hurting.
Share this blog:
See why more than 50,000 restaurants use Restaurant365
Restaurant365 brings together accounting, operations, scheduling, and more in a flexible platform—empowering restaurants to choose the solutions they need and scale with confidence.
