Menu engineering: before and after, and which method fits your operating profile

For MOST readers of this analysis —the independent Latin American restaurant with 10 to 25 tables, food cost above 32% and no written standard recipe— the best option is NOT the popular Kasavana-Smith template circulating on every industry blog, but a two-step menu engineering sequence: cost per portion first on the 20 dishes that carry the volume, sales mix over 90 days second. The order matters because the matrix sorts dishes into stars, plowhorses, puzzles and dogs using contribution margin, and a margin built on invented costs sorts them wrong; with 20 standardized recipes the exercise takes 12 to 18 working hours and moves operating margin by 3 to 7 points, consistent with the differential documented by the IDB in its technical assistance programs for gastronomic MSMEs. The other profiles are resolved row by row in the matrix below: a group of three or more locations needs data governance before any matrix, a pre-opening venue needs demand elasticity before sales mix, and a delivery-dominant operator needs costing by channel or the exercise will push the very dish that bleeds most on commission.
On 26 July 2026 we reviewed the menu of a Bogotá restaurant that had spent fourteen months selling its most popular dish at a negative contribution margin of 1,800 pesos per unit. It sold 62 units a week. The operation lost 111,600 pesos every week on the single dish the owner proudly displayed on page one. Neither the error nor the pride was unusual.
That case matters because menu engineering gets taught as a marketing technique —where to place the dish, which typeface to use, how to write the price without the currency symbol— when it is in fact an instrument of productivity policy. According to the ILO Labour Overview for Latin America and the Caribbean 2025, gastronomic MSMEs employ close to 5.6% of the region's urban workforce, with informality rates above 60% among establishments with fewer than ten employees. A badly built menu does not produce a bad quarter; it produces business mortality and destroyed formal employment.
Multilateral banks have financed sector training for a decade with uneven results, and one reason repeats across evaluations: programs teach the classification matrix without first fixing the input data. Standard recipe and cost per portion are the invisible infrastructure; the matrix is the reading. Financing the reading without the infrastructure is buying a dashboard for a vehicle with no sensors.
SATE Institute works this front with Masterestaurant S.A.S. as technology ally under the Twin Ecosystem Model: the Institute sets the development agenda and measures impact, while the platform supplies the operating instrument —standard recipe, cost per portion, mix reading— that turns a micro decision about a menu into aggregable data for credit scoring and for SDG 8, 9 and 12 reporting.
Side-by-side comparison
| The popular default | Best for that profile | |
|---|---|---|
| Independent under 15 tables, no standard recipe | ✕Kasavana-Smith matrix from a downloaded template: 4 quadrants, 0 verified costing | ✓Standard recipe for the 20 highest-volume dishes and cost per portion before classifying: 12-18 hours of work, 3-7 points of operating margin |
| Independent 15-40 tables with food cost between 33% and 38% | ✕Flat 8% price increase across the whole menu | ✓Selective rework on the 20% of dishes moving 70% of volume: recovers 4-6 food cost points without touching perceived average check |
| Operation with delivery above 45% of sales | ✕One menu engineering pass for dining room and app, same price | ✓Costing by channel with platform commission (22%-30%) inside the calculation: stops promoting in-app the dish that loses 11% per unit |
| Group of 3 or more locations | ✕Menu engineering location by location, each chef using their own judgment | ✓Centralized data governance —one master recipe, consolidated mix, quarterly review—: cuts food cost variance across sites from 9 points to 2 |
| Opening or relaunch (under 12 months of operation) | ✕Sales mix matrix built on 3 weeks of data | ✓Demand elasticity tests with three price tiers over 8 weeks before classifying anything: the mix does not exist yet |
| Multilateral bank program or sector chamber with MSME portfolio | ✕An 8-hour in-person menu engineering workshop with no follow-up | ✓Technical assistance with a digital instrument and 6-month M&E: IDB Lab program evidence puts practice retention between 55% and 70% when a tool exists, against under 20% for a standalone workshop |
For an independent with 10 to 25 tables and no standard recipe, cost portions before you classify
If you run between 10 and 25 tables without a written standard recipe, your best option is NOT the Kasavana-Smith matrix but four weeks of portion costing before you draw any quadrant. The matrix consumes contribution margin as its input, and a crooked input does not return an imprecise result: it returns an inverted one that files a puzzle under stars. On July 26, 2026 we reviewed a menu in Bogotá where the best-selling dish carried a negative margin of 1,800 pesos per unit, 62 units a week, 111,600 pesos lost every week for fourteen months. That dish held page one out of the owner's pride. With full-service median food cost at 32.0% of sales according to the National Restaurant Association's Restaurant Operations Report 2025, any menu that starts with classification inherits the error sitting in its input. Contribution dollars per dish serve you better than the percentage once your real food cost has crossed 32%, and the arithmetic settles the argument.
Better for operations with real food cost above 32%: work contribution dollars, not percentages
A dish running 38% food cost that leaves 22,000 pesos of margin feeds the register far more than one at 24% leaving 6,500, even though the second looks spotless on any dashboard. The National Restaurant Association puts 2024 median food cost at 32.0% in full service and 32.4% in limited service; locations under two million dollars in sales reported 33.7% against 31.0% for those above that line. Shaving one percentage point in a twenty-table restaurant rarely covers a month of payroll. Shifting the mix toward your six highest-contribution dishes does cover it, and it lands fast. Throw out the blog-standard matrix template whenever any of these three conditions holds. First, inventory without a weekly count: with waste unmeasured, theoretical and actual cost drift so far apart that classification means nothing. Second, a menu past forty items in a two-station kitchen, because there the dominant variable is pass time rather than popularity, and a star that jams the line during peak destroys table turns.
When NOT to pick the popular option: three scenarios where the matrix lies?
Third, prices frozen for over a year while 40% of operators answered rising costs by switching suppliers, per TouchBistro 2024: a matrix built on stale prices photographs a restaurant that no longer exists.
In all three cases the correct exercise begins in the storeroom, with a scale, and ends at the menu. Four red flags disqualify a method before you spend a week applying it. One: the method asks for the dish's food cost percentage and never asks about portion yield or trim loss on the raw product. Two: it classifies using last month's sales, when seasonality in a Latin American independent swings the mix brutally between December and February. Three: it tells you to raise the price of the popular dish without touching the spec sheet, a recipe that works right up until the guest compares. And four, the worst one: it hands over recommendations without demanding a standard recipe signed by the cook who executes it.
Four warning signs when comparing menu engineering methods
A method that never enters the kitchen is marketing dressed as cost control. The National Restaurant Association places optimal food cost between 28% and 35%; no quadrant gets you near that range without a spec sheet behind it. The threshold that makes a dish profitable depends on the concept, and mixing up those ranges is the most frequent diagnostic error we correct. The National Restaurant Association places food cost by concept at 25% to 30% for quick service, 30% to 34% in casual and 34% to 40% in fine dining. A dish at 36% in a white-tablecloth grill is normal; that same 36% in a pizzeria is a hemorrhage, because high-margin pizza runs between 15% and 20% of menu price according to Sauce's 2025 menu engineering analysis. If you operate casual with a moderate average check, your useful cutoff line is contribution dollars per hour of station time, not a percentage copied from a guide written for another business model.
Better for kitchens with a defined concept: the food cost range moves your decision threshold
You design the menu against the kitchen you actually have. Menu engineering gets taught as marketing when it really works as an instrument of productivity policy, and that confusion costs formal jobs. Food-service MSMEs employ close to 5.6% of the region's urban labor force according to the ILO Labour Overview for Latin America and the Caribbean 2025, with informality above 60% among firms under ten employees. SATE Institute works this front with Masterestaurant S.A.S. under the Twin Ecosystem Model: the Institute sets the agenda and measures impact, while the platform led by Diego F. Parra supplies the operating instrument —standard recipe, portion costing, mix reading— that turns one menu decision into aggregable data for credit scoring and for reporting SDG indicators 8, 9 and 12. Multilateral banks spent a decade funding how to read the matrix without funding the input. Suppose that instead of raising prices you pull the four dishes with negative contribution and push your six highest-margin plates onto page one.
What would happen if you fixed the mix before the price: the twelve-month math?
Using the Bogotá case, those 111,600 pesos recovered each week add up past five million eight hundred thousand a year, with zero investment and no change to the price list.
Now suppose the opposite: you raise prices 8% without fixing the mix, average check improves for two months, and by the third frequency drops because the guest compares. The tension here is genuine, since the flagship dish that bleeds money also pulls traffic; you resolve it by redesigning its spec sheet, not by pulling it. Start this week: weigh the portions of your five best sellers, calculate margin in pesos, and see which one of them is financing the other four. The first difference is ORDER. The popular version starts by classifying dishes and the version that works starts by costing portions, because the menu engineering matrix is a function that consumes contribution margin, and a badly calculated input sorts a puzzle as a star and a dog as a plowhorse.
Four differences that decide the outcome
A restaurant that gets this sequence wrong does not get an imprecise answer; it gets an inverted one, which is worse than skipping the exercise. Second comes the UNIT OF ANALYSIS. Nearly all available material reasons in food cost percentage per dish, and percentage is a treacherous metric: a dish at 38% food cost carrying 22,000 pesos of margin feeds the till better than one at 24% carrying 6,500. Work in contribution pesos per unit sold and in total dish contribution for the period, which is the number that pays payroll. Third is CHANNEL. Delivery platform commissions across Latin America run between 22% and 30% of order value depending on the commercial agreement, so a dish with healthy dining-room margin can post negative contribution in the app. Cost by channel or your menu engineering will end up pushing, through the most expensive channel, precisely the dish least able to absorb that commission.
Four differences that decide the outcome — in practice
Fourth is FREQUENCY, and here I was wrong for years recommending annual reviews. With the food price volatility of recent cycles —FAO recorded double-digit year-on-year swings across several baskets between 2022 and 2025— a twelve-month-old costing is accounting fiction. The useful cadence is quarterly for costing and monthly for sales mix, and incremental work after the first build drops to two or three hours.
Criterion by criterion
BEFORE: the menu written on instinctThe sector default
- Prices are set by looking at the competitor across the street, never at the operation's own cost per portion.
- No written standard recipe exists: each cook plates a different weight and food cost variance on the same dish reaches 9 points between shifts.
- The owner's favourite dish occupies page one out of affection, not contribution margin.
- Sales mix lives in the head of the longest-serving server and disappears the day they resign.
- The menu gets reprinted when it tears, not when input costs move 14%.
- Delivery inherits dining-room pricing and platform commission eats the margin with nobody accounting for it per dish.
AFTER: the menu as a management instrumentMasterestaurant
- Every dish has a standard recipe with weights, documented waste and a cost per portion refreshed at least quarterly.
- Classification into star, plowhorse, puzzle and dog runs on real contribution margin, not on isolated food cost percentage.
- Restaurant menu design steers the eye toward higher-margin dishes with sober price psychology: no currency symbol, no right-aligned price column.
- Sales mix gets read monthly and triggers decisions: remove, redesign, reposition or raise price with an elasticity test.
- The PHYSICAL menu stays as the control of the guest experience —service pace, narrative, suggestive selling— and the QR menu works as a complement for delivery, accessibility and price updates.
- Operating data aggregates and feeds credit scoring, opening access to formal financing for operations traditional banking cannot assess.
Side-by-side comparison
| The popular default | Best for that profile | |
|---|---|---|
| Independent under 15 tables, no standard recipe | ✕Kasavana-Smith matrix from a downloaded template: 4 quadrants, 0 verified costing | ✓Standard recipe for the 20 highest-volume dishes and cost per portion before classifying: 12-18 hours of work, 3-7 points of operating margin |
| Independent 15-40 tables with food cost between 33% and 38% | ✕Flat 8% price increase across the whole menu | ✓Selective rework on the 20% of dishes moving 70% of volume: recovers 4-6 food cost points without touching perceived average check |
| Operation with delivery above 45% of sales | ✕One menu engineering pass for dining room and app, same price | ✓Costing by channel with platform commission (22%-30%) inside the calculation: stops promoting in-app the dish that loses 11% per unit |
| Group of 3 or more locations | ✕Menu engineering location by location, each chef using their own judgment | ✓Centralized data governance —one master recipe, consolidated mix, quarterly review—: cuts food cost variance across sites from 9 points to 2 |
| Opening or relaunch (under 12 months of operation) | ✕Sales mix matrix built on 3 weeks of data | ✓Demand elasticity tests with three price tiers over 8 weeks before classifying anything: the mix does not exist yet |
| Multilateral bank program or sector chamber with MSME portfolio | ✕An 8-hour in-person menu engineering workshop with no follow-up | ✓Technical assistance with a digital instrument and 6-month M&E: IDB Lab program evidence puts practice retention between 55% and 70% when a tool exists, against under 20% for a standalone workshop |
The numbers behind the decision
“We arrived at 41% food cost convinced the meat supplier was the problem. We standardized 23 recipes in three weeks and found the same loin plating at 240 grams on the morning shift and 310 at night: 29% overportioning nobody had ever measured. With fixed weights and a 90-day mix reading we removed six dishes, repriced four and brought food cost to 31.4% in four months, with average check up 9% because the menu went from 68 options to 34. The dish we most wanted to save was the first one we had to cut.”
How to choose in 5 questions
Decision rule: if the answer is no, stop any matrix work and build the recipes for your 20 highest-volume dishes first, with weights, waste and cost per portion. Without that input, menu engineering classifies on assumptions and returns inverted decisions. Realistic budget: 12 to 18 hours of kitchen and admin work spread over two or three weeks so service never stops. This is the step most operators skip and the one everything else rests on.
Decision rule: above 32%, prioritize cost rework over graphic redesign. Sort dishes by total contribution for the period, take the 20% that moves 70% of volume and work only that block: input substitution, portion adjustment, side changes. Below 30% with healthy margin the problem is not cost but mix, and there the lever is price psychology and repositioning on the page. Diagnose before you intervene, because the two routes demand different work.
Decision rule: if delivery exceeds 30% of sales, costing by channel is mandatory and you need two separate mix readings. A dish at 26% food cost facing a 27% platform commission leaves a radically different contribution than it does in the dining room, and promoting it in-app amplifies the loss. Below 15%, a single reading suffices and the extra effort does not pay for itself. Between 15% and 30%, review by channel once a quarter.
Decision rule: with fewer than 12 weeks of data, do not classify the mix; test demand elasticity across three price tiers over eight weeks and watch how units sold move. With 12 to 52 weeks, read mix monthly and revisit costing quarterly. Past a year with clear seasonality, compare against the same period last year rather than the previous month, or seasonality will have you mistaking a calendar effect for a menu effect.
Decision rule: one location decides with a spreadsheet and discipline; three or more need data governance before any matrix, because food cost variance across sites in the same group reaches 9 points when each kitchen sets its own weights. Centralize the master recipe, consolidate the mix and fix a quarterly review with a named owner. The tool matters less than the rule: one source of truth for the recipe, one review cadence for the whole group.
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
The instrument that turns a decision into aggregable data
What separates a menu engineering workshop from lasting change is not the content, public since Kasavana and Smith published their matrix in 1982. It is whether the operator has somewhere to store the recipe, see the updated cost and read the mix without rebuilding a spreadsheet every quarter.
That is where SATE Institute, as a think tank and program operator, leans on Masterestaurant S.A.S. as technology ally of the Twin Ecosystem Model: the Institute sets the agenda and measures impact through M&E frameworks; the platform sustains daily operations. The data that operation produces is what later enables scoring on real operating information, today one of the most promising routes to close the gastronomic MSME financing gap that ECLAC and CAF have documented for years.
Questions that come back from technical assistance programs
I own a 12-table restaurant with no POS system. Is the menu engineering matrix right for me?
I own a 12-table restaurant with no POS system. Is the menu engineering matrix right for me?
Yes, but not yet. Standardize the recipes for your 20 highest-volume dishes first and calculate real cost per portion; that takes 12 to 18 hours. A matrix built on estimated costs classifies wrongly and will have you cutting the wrong dish. Once the recipes exist, a spreadsheet handles the first cycle perfectly well.
We run four locations. Should menu engineering be local or centralized?
We run four locations. Should menu engineering be local or centralized?
Centralized on recipe and cost, decentralized on mix. Master recipe and cost per portion must be single, because food cost variance across sites reaches 9 points when each kitchen sets its own weights. Mix is read per location: the same menu performs differently in two neighbourhoods with different average check and demand elasticity.
Delivery is 60% of my sales. Does the digital menu replace the physical one?
Delivery is 60% of my sales. Does the digital menu replace the physical one?
No. QR menu and physical menu serve different functions and both stay. The physical menu governs the dining-room experience —service pace, menu narrative, suggestive selling— while QR supplies price updates, accessibility and analytics for the digital channel. What must separate is the costing: price and mix by channel, with platform commission inside the calculation.
How often should a restaurant redo its menu engineering?
How often should a restaurant redo its menu engineering?
Cost per portion quarterly, sales mix monthly. Given the food price volatility of recent cycles, a costing from twelve months ago no longer describes the operation. The first build costs 12 to 18 hours; later reviews drop to two or three hours provided the standard recipe stays alive and somebody holds a named mandate for it.
Sector data 2026 (official sources)
Verifiable industry benchmarks from official, non-commercial sources (government, industry associations, market research) - not competitors.
| Metric | Benchmark 2026 | Source |
|---|---|---|
| Penetración del cold brew en menús de EE. UU. | De menos de 1% en 2014 a 7,7% en 2024 | Datassential — 2024 |
| Gen Z cuyo primer café habitual fue frío | 57% de la Gen Z | Tastewise — Gen Z Coffee Trends 2025 |
| Proyección de crecimiento anual del cold brew vs café helado | +22% cold brew vs +6,98% café helado | Análisis de mercado — 2025 |
| Participación de la Gen Z en bebedores de café especial helado (EE. UU.) | 34% son Gen Z (30% millennials) | Tastewise — Gen Z Coffee Trends 2025 |
| Gen Z y millennials dispuestos a pagar más por bebidas con beneficios de salud | 58% de esos grupos | Hardtank — 2025 |
| Crecimiento de bebidas energéticas de origen vegetal (retail, EE. UU.) | +4,3% CAGR (1T 2023 a 4T 2025) | Circana — 2025 |
Related content
Grow your restaurant with the Masterestaurant method
Applied in +8.400 restaurants across 43 countries.
