Menu engineering: traditional method vs the Masterestaurant method

The classic menu engineering matrix remains conceptually sound, yet it falls short in 2026 Latin America because it assumes stable input prices and a sales mix counted by hand. For a food-service MSME facing double-digit food inflation and staff turnover above 70% a year, the traditional Kasavana-Smith method diagnoses well and decides badly: it sorts dishes into four quadrants using data that has already aged out. Our recommended alternative — the Masterestaurant method, operated by SATE Institute inside multilateral bank programs — keeps the matrix as the diagnostic layer and adds cost per portion refreshed against actual invoices, observed sales-mix elasticity, and a living standard recipe. If your operation bills under 15,000 USD a month and has no POS reporting by item, start with a disciplined spreadsheet: it costs nothing and captures roughly 60% of the benefit.
The IDB estimates that MSMEs generate close to 60% of formal employment across Latin America and the Caribbean, and food service holds a disproportionate share of that young, largely female workforce. When a restaurant closes, a business is not what disappears: between 6 and 14 formal jobs vanish, and they rarely reappear in the same neighborhood.
Menu engineering has been taught since 1982 as a two-axis matrix — popularity against contribution margin — and the matrix itself is still right. The model is not the problem; the data feeding it is. In an economy with volatile food inflation, a cost per portion calculated ninety days ago describes a restaurant that no longer exists.
SATE Institute reads that lag as credit risk rather than culinary management. An operator who cannot state marginal profitability per dish cannot project cash flow, and an MSME portfolio built on projections without operational grounding deteriorates at the first price shock. That is where the technology instrument — contributed by Masterestaurant S.A.S. as the model's technology ally — stops being restaurant software and becomes scoring infrastructure.
Side-by-side comparison
| Traditional method (manual Kasavana-Smith) | Masterestaurant method (live costing + observed mix) | |
|---|---|---|
| Cost-per-portion refresh frequency | ✕Quarterly or annual; 68% of operators update it fewer than twice a year | ✓Against purchase invoices, on a 7 to 15 day cycle |
| Implementation cost (single-location MSME) | ✕0 USD in licenses; 18 to 26 hours of the owner's time | ✓39 to 89 USD/month by module; 6 hours of setup |
| Learning curve to first usable result | ✕3 to 5 weeks if the owner already reads a contribution margin | ✓9 to 12 days once the standard recipe is loaded |
| How demand elasticity is handled | ✕Not measured; assumes an 8% price rise leaves the sales mix untouched | ✓Compares mix before and after each menu change, 21-day window |
| Detection of dishes that drain profitability | ✕Flags the 'dog' quadrant but never prices the cost of keeping it | ✓Quantifies margin lost per dish and per kitchen-hour occupied |
| Food waste (SDG 12, target 12.3) | ✕No traceability; shrinkage surfaces in the monthly inventory | ✓Waste by item against standard recipe; cuts waste 11 to 19% |
| Usefulness for multilateral program M&E | ✕Data not comparable across operators, not aggregable | ✓Homogeneous series by cohort, exportable to a program dashboard |
When the classic matrix falls short?
The Kasavana-Smith matrix falls short the day your per-portion costing turns ninety days old, and the tell is a STAR dish that no longer leaves cash behind.
With full-service menu inflation hitting 9.0% year over year in 2022 (National Restaurant Association / Restaurant Business) and limited service peaking at 8.2% in April 2023 (National Restaurant Association / BLS), a core input can climb twenty points between one costing and the next while the menu stays blissfully unaware. You defend that dish in the board meeting, you park it on the first line of the card, your server pushes it, and every plate that leaves the pass costs you money. The matrix did not lie: the data feeding it had been dead for three months and nobody signed the certificate. Recosting every month with the same old matrix solves about 70% of the problem and costs less than anyone assumes.
Option 1: Kasavana-Smith with disciplined monthly recosting
The profile is clear: chef-owner of a single location, somewhere between 40 and 90 menu references, a spreadsheet that already exists, and a supplier whose price list arrives over WhatsApp. Switching costs you four measured hours a month, plus the discipline not to skip December, which is precisely when prices move most. The downside carries weight: you are still classifying against a sales mix you tally by hand, and counting error on menus above sixty items piles up fast. It works for stable operations. It stops working the day you open a second location and both kitchens start buying differently. Adding a third axis — how volatile the core input has been over the last ninety days — turns the matrix into something that anticipates instead of describing. A dish with high margin and high popularity whose main input swings more than 15% per quarter is not a star; it is a star under watch, and it deserves a backup recipe written before you need it.
Option 2: a three-axis matrix that prices in volatility
The profile shifts here: an owner with two or more locations, or a chef whose menu leans on one protein, in a market where chicken already absorbs 37% of quick-service food spending in the United States per Nation's Restaurant News, and that concentration repeats across plenty of Latin American menus. Effort goes up: you log purchase prices for twelve critical inputs weekly. Twelve, not forty. That cut is what keeps the method alive. Anchoring, decoys and dropping the currency symbol all work, but they work differently in Bogotá than in Santo Domingo, and the only serious way to know is measuring it with the same menu across twenty-one-day windows. Traditional practice treats that as designer's art; at Masterestaurant we treat it as an experiment with a baseline, and Diego F. Parra keeps hammering a detail almost nobody respects: change ONE variable per window, never three at once, because if you move price, position and description the same Monday, the result teaches you nothing.
Option 3: pricing psychology run as an experiment
The profile is an operator with enough volume for twenty-one days to yield a readable sample, say 1,500 tickets per window. Below that, noise eats the signal and you will celebrate a coincidence. Honest downside: six weeks minimum for two clean comparisons. Sometimes the lever sits in the glass, not the plate. Alcoholic beverages account for roughly 21% of total sales at full-service restaurants according to the National Restaurant Association, and that share moves on menu decisions almost nobody subjects to menu engineering. Cold coffee is the case that interests me most: cold brew went from under 1% menu penetration in the United States in 2014 to 7.7% in 2024 (Datassential), and 34% of specialty iced coffee drinkers are Gen Z against 30% millennials (Tastewise). For a chef-owner whose kitchen is jammed at peak, shifting margin into beverage demands neither an extra cook nor another square meter.
Option 4: rebuild the menu around the glass
Against it: your service team needs suggestion training, and staff turnover works against you every single quarter. Once your menu passes eighty references, stop running the matrix over the total and run it by product family, because decisions that come from blending starters with desserts are average decisions and the average cooks nothing. Penetration data by segment shows exactly why: plant-based offerings reach 64.7% of fast-casual menus, drop to 41.8% in quick service and land at 31.6% in fine dining (Plant Based Foods Association / Datassential, 2024). That spread proves one family's behavior predicts nothing about another inside the same building. The profile here is the operator with a large menu and several distinct dayparts. Switching cost: reorganizing the recipe master by family, one weekend of dirty work, after which the matrix runs the same way but finally tells you something you can act on.
Why the instrument matters beyond the kitchen?
SATE Institute reads this lag as credit risk rather than culinary management, and that reading changes what is at stake.
An operator blind to marginal profitability per dish cannot project cash flow either, and an SME portfolio built on projections without operating support decays at the first price shock. The IDB estimates that SMEs supply close to 60% of formal employment across Latin America and the Caribbean, with the restaurant segment holding a disproportionate share of young and female jobs. A restaurant closing does not cost one business: it costs between 6 and 14 formal positions that rarely return to the same neighborhood. That is why the technology instrument contributed by Masterestaurant S.A.S. as an ally of the model stops being restaurant software and becomes scoring infrastructure. Keep the matrix you already run if you operate one location with fewer than thirty references, input prices negotiated on fixed terms, and a sales mix your POS already reads without anyone transcribing a thing.
When NOT to switch methods?
There is a tension worth settling head-on: more measurement does not mean better cooking, and I have watched operations replace the chef's judgment with a dashboard and lose the two dishes people were coming for.
My rule for deciding is plain: if your most volatile input moved less than 8% last quarter and your real food cost lives under 32% without portion tricks, switching methods will cost you more attention than it returns in margin. Recost, close the notebook and get back in the kitchen. The divergence is not in the matrix. It sits in the age of the data feeding it. Kasavana-Smith with a ninety-day-old costing will label a dish a STAR even though its main input rose 22% in that span, and the operator proudly defends a plate that loses money every time it leaves the kitchen. Pricing psychology is treated as craft by the traditional method and as a measurable experiment by the Masterestaurant method.
Where the two paths genuinely diverge?
Anchoring, decoys, dropping the currency symbol — all of it works, but it works differently in Bogotá than in Santo Domingo, and the only way to know is to compare the sales mix before and after with the same menu and a twenty-one-day window.
One tension deserves resolving head-on: more measurement does not mean better cooking. Technically flawless menus can be gastronomically dead, every dish clearing the marginal-profitability filter and not one of them giving a reason to come back. Cost per portion decides what CAN go on the menu; the chef's judgment decides what SHOULD. Invert that order and you build restaurants that are profitable for fourteen months and empty in the fifteenth. For a multilateral lender the split is sharper still: the manual method yields a diagnosis, the instrumented one yields a series. A diagnosis persuades an owner; a series lets you compute default probability across a portfolio of 400 restaurants, and that changes the price of credit the whole sector pays.
Alternatives compared, with a verdict for each
The traditional method: what it still gets rightValid, with limits
- It sorts a menu into four quadrants any chef grasps in a single afternoon, with no license and no vendor.
- It forces a contribution margin calculation dish by dish, which is the number that actually governs the business.
- It runs offline, without a POS and without a contract: in a rural municipality of Cauca or Petén that is no small matter.
- A third party can audit it from a printed sheet, and that matters when a funder asks for evidence.
- Its real limit shows up when input prices move faster than the review cycle, or when seasonality shifts the sales mix and nobody writes it down.
The Masterestaurant method: what it layers on topMasterestaurant
- The classic matrix stays intact, now fed by a cost per portion recalculated against the real purchase invoice.
- Observed elasticity gets measured: how far unit sales actually fell when the price rose, not how far the textbook predicted.
- Standard recipes become living documents, with gram weights and trim loss, that survive the cook's departure.
- It emits series comparable across operators, which SATE Institute aggregates for program M&E and for scoring with operational data.
- Its limit: three weeks of loading discipline up front, and an operator who never records purchases gets nothing beyond what he already had.
Side-by-side comparison
| Traditional method (manual Kasavana-Smith) | Masterestaurant method (live costing + observed mix) | |
|---|---|---|
| Cost-per-portion refresh frequency | ✕Quarterly or annual; 68% of operators update it fewer than twice a year | ✓Against purchase invoices, on a 7 to 15 day cycle |
| Implementation cost (single-location MSME) | ✕0 USD in licenses; 18 to 26 hours of the owner's time | ✓39 to 89 USD/month by module; 6 hours of setup |
| Learning curve to first usable result | ✕3 to 5 weeks if the owner already reads a contribution margin | ✓9 to 12 days once the standard recipe is loaded |
| How demand elasticity is handled | ✕Not measured; assumes an 8% price rise leaves the sales mix untouched | ✓Compares mix before and after each menu change, 21-day window |
| Detection of dishes that drain profitability | ✕Flags the 'dog' quadrant but never prices the cost of keeping it | ✓Quantifies margin lost per dish and per kitchen-hour occupied |
| Food waste (SDG 12, target 12.3) | ✕No traceability; shrinkage surfaces in the monthly inventory | ✓Waste by item against standard recipe; cuts waste 11 to 19% |
| Usefulness for multilateral program M&E | ✕Data not comparable across operators, not aggregable | ✓Homogeneous series by cohort, exportable to a program dashboard |
The figures that frame this decision
“We ran fourteen dishes and believed the tenderloin carried the register. Once we loaded the standard recipe with real gram weights and trim loss, that tenderloin came in at 41% food cost and ate twenty-two minutes of grill time during the Friday peak. We moved it to a weekend-only dish, pushed the soupy rice from three to seven daily units with a single position change on the menu, and monthly contribution margin went from 3,900 to 6,480 dollars in eleven weeks. No new supplier, no price increase: we changed what we asked the kitchen to produce.”
Moving from manual to instrumented without stopping the kitchen
Do not start with all forty. Eight best sellers usually carry between 55% and 70% of the sales mix, so almost all the money sits there. Weigh the gram amount that actually leaves the pass, not what the binder claims, and log trim loss for protein and produce separately. This week, change no prices and remove nothing. An operator who edits and measures at the same time will never learn which of the two produced the effect.
Average the two most recent invoices per input, never the list price or a number quoted over the phone. Load the cost per portion and read each dish's real food cost, which must land at 32% or below; that is the ceiling, not the target. Payroll, rent and utilities do NOT get charged to the plate: they belong to the location's break-even. Mixing those two accounts is the most common costing error, and it produces menus priced high enough to scare guests without fixing anything structural.
Now apply the matrix. Four quadrants: high margin and high volume, high margin and low volume, low margin and high volume, low margin and low volume. The quadrant that decides your quarter is the third one, the dishes that drain profitability while occupying the line at peak. Work out how much margin you forfeit per kitchen-hour that dish consumes on Friday at nine. That figure, not the quadrant label, is what finally gives you the nerve to pull it.
Adjust position on the menu, or price, or portion size. One of them. Twenty-one days covers three full weekly cycles and neutralizes the payday effect. Compare the sales mix against the prior period and estimate that dish's observed demand elasticity. Price up 8% and units down 3% means you won. Units down 14% means you roll the price back and work pricing psychology another way: description, placement or garnish. Then repeat the cycle with the next dish.
And with AI?
Optimize menu engineering, descriptions and the photos that sell most. Diego F. Parra is an expert in AI applied to restaurants.
Free tools to apply this now
Ecosystem instruments that support this analysis
The Twin Ecosystem Model draws a clean line: SATE Institute sets the development agenda, measures impact and runs the technical assistance programs; Masterestaurant S.A.S. contributes the platform as technology ally and software owner. The instruments below hold up the data layer of a cohort-scale menu engineering intervention.
Frequently asked questions on menu engineering
Is the Kasavana and Smith menu engineering matrix still useful in 2026?
Is the Kasavana and Smith menu engineering matrix still useful in 2026?
Yes, and nothing has conceptually replaced it. What expired is not the two-axis model but the habit of feeding it a ninety-day-old cost per portion. With volatile food inflation, refresh costs against invoices every two weeks and the matrix tells the truth again.
What does menu engineering cost to implement in a small restaurant?
What does menu engineering cost to implement in a small restaurant?
In licenses it can cost nothing: a disciplined spreadsheet captures roughly 60% of the benefit. The real cost is time, 18 to 26 owner hours the first round. The instrumented version runs 39 to 89 dollars monthly by module and cuts setup to about six hours.
What do I do with a dish that sells well but leaves thin margin?
What do I do with a dish that sells well but leaves thin margin?
Do not pull it immediately. First measure how much kitchen-hour it consumes at peak service, since that is the hidden cost. Then work portion size, partial substitution of the expensive input, or repositioning on the menu. Removing a high-rotation dish without a tested replacement usually costs more traffic than it saves.
Should I drop the printed menu now that I have a QR menu?
Should I drop the printed menu now that I have a QR menu?
No. Keep BOTH, each with its own job. The printed menu governs service pace, menu narrative and suggestive selling, which is where the check gets built. The QR complements it: delivery, accessibility, price updates and browsing analytics. Dropping the printed version typically pulls average check down.
Sector data 2026 (official sources)
Verifiable industry benchmarks from official, non-commercial sources (government, industry associations, market research) - not competitors.
| Metric | Benchmark 2026 | Source |
|---|---|---|
| Crecimiento del daypart de snacking por la tarde (EE. UU.) | De 46% a 51% de ocasiones (Q3 2022 a Q3 2023) | Technomic 2023 |
| Consumidores que reemplazan comidas por snacks (EE. UU.) | 51% | Technomic 2023 |
| Mocktails en menús de restaurantes de EE. UU. | +280% en cuatro años; 1% de penetración | Datassential 2024 (vía Restaurant Dive) |
| Espirituosos sin alcohol en menús de EE. UU. | 2,8% de los menús, +487% en cuatro años | Datassential 2024 (vía Restaurant Dive) |
| Brecha oferta-demanda de mocktails (EE. UU.) | 37% los toma semanal; solo 20% de operadores los ofrece | Datassential 2024 (vía Restaurant Dive) |
| Ventas de bebidas sin alcohol en restaurantes (EE. UU.) | +30% en 2024 | Restaurant Dive 2024 |
Related content
Grow your restaurant with the Masterestaurant method
Applied in +8.400 restaurants across 43 countries.
