How Do I Use the Menu Engineering Feature Effectively?

Menu Engineering isn't just a one-time diagnostic, it's most valuable as an ongoing habit. Here's how to build it into your routine.

Always Filter by Category First

Before drawing any conclusions, make sure you're filtering Menu Engineering down to a specific category or sub-category (e.g., Main Course, Pasta, Soup) rather than viewing everything at once. Performance only means something when compared apples-to-apples, a beef main course and a soup have completely different price points, popularity patterns, and cost structures, so comparing them directly will give you a misleading picture. Always compare items within the same category.

Review Monthly, Not Just When Something Looks Wrong

Make a monthly Menu Engineering review part of your regular routine, not something you only check when a number in your PnL looks off. Reviewing month-on-month lets you catch a slow decline early, before an item drifts from Satisfactory into Unsatisfactory or Replace territory.

Don't Just Focus on "Replace"

It's tempting to only look at items flagged Replace, but the real opportunity is often in your Satisfactory and Unsatisfactory items. These are your "almost there" dishes, often just one adjustment away (a recipe tweak, a price change, a repositioning on the menu) from becoming genuinely strong performers. A monthly review of these tiers is where you'll usually find the most actionable, lowest-effort wins.

Use the Radar Chart to Pinpoint the Actual Issue

Once you've identified an item worth investigating, click into it to see its radar (spider web) chart. This breaks the item down across multiple performance dimensions at once, so instead of just knowing an item is underperforming, you can see exactly where it's weak (e.g., strong on Popularity but weak on Profitability), pointing you directly to the right fix rather than guessing.

Use It Before You Design a New Menu

Before creating a new menu, run a full Menu Engineering review of your current one. This tells you, with evidence rather than instinct, what's actually working (keep and feature these), what's borderline (worth reworking rather than dropping), and what's genuinely underperforming (safe to cut). Designing a new menu without this step risks removing a quiet high-performer or keeping a dish that was never pulling its weight.

Track Closely After a New Menu Launches

Once a new menu goes live, don't wait for the next monthly cycle, review Menu Engineering weekly for the first several weeks. New items need time to establish a real sales pattern, and catching an early problem (a dish that's not landing with guests, or costing more than expected) within the first few weeks gives you time to adjust before it's had a lasting impact on the period's numbers.