Menu engineering with data for restaurants
The menu is the biggest profit lever a restaurant controls, yet many Indian restaurants change it based on chef instinct and complaints. This guide shows how to use sales analytics to build a menu that earns both volume and margin.
Why does menu engineering matter in India?
A typical casual dining or QSR menu in India has dozens of active SKUs across several categories. More options sounds like more choice and more revenue. The data usually says otherwise. A small share of dishes brings most of the revenue, and a long tail of slow items adds complexity, waste, tied-up stock and a slower kitchen.
Menu engineering uses sales, cost and preference data to decide which dishes to promote, reprice, remove or develop. With rising food costs, aggregator commissions and thin margins, profit per dish is a basic management practice and not a luxury.
What is the menu engineering matrix?
The framework was developed by Kasavana and Smith in 1982, and it is still the most useful tool for Indian operators. It sorts every dish on two scales: popularity (sales against the menu average) and profitability (contribution margin against the menu average).
What are stars?
Stars are popular and profitable. A well-placed biryani, a signature curry or a bestselling dessert made from low-cost ingredients at a premium price fits. Feature stars in physical and digital menus, and on Swiggy and Zomato place them in recommended sections and at the top of their category. Protect their quality and do not discount them without a reason.
What are plowhorses?
Plowhorses sell well but earn little per unit. Staples such as dal makhani, plain naan or jeera rice often land here, because they are priced low or cost more than expected. They are the easiest to act on. A small price rise, a better supplier rate or tighter portions can move them toward star status without losing volume.
What are puzzles?
Puzzles earn well when ordered but are not ordered often. They may be hard to see, poorly described or unknown. On delivery platforms, give them featured placement, better photos or a place in combos. A tandoori speciality with a strong margin that few guests order can become a real contributor if its order rate rises.
What are dogs?
Dogs take menu space, prep effort and stock for little return. Most should come off the menu. Use judgement in India. A regional speciality may stay for brand identity, and some apparent dogs are seasonal items judged on too little data. Investigate before you cut anything with strategic value.
How do you calculate contribution margin per dish?
The profitability axis needs contribution margin, not only gross margin. Contribution margin is the menu price minus the raw material cost per serving and, for delivery, the packaging cost per order. It isolates variable cost and leaves out fixed overhead.
You need a recipe costing database that links each item to its ingredients and standard portions, plus current purchase prices. In many chains this sits in an inventory system or a chef’s cost card spreadsheet. Bring it into your analytics next to POS sales volume and the full classification becomes possible at scale. In Restrologic POS, recipes and stock deduction are built in, which keeps these costs current.
Do dishes perform differently across regions?
Yes, and this matters for any chain in several cities. A North Indian chain that expands south may find that staples which are stars in Delhi are slow sellers in Chennai or Bengaluru. The dishes are fine. Local taste, familiarity and competing cuisines create different demand.
A single national menu strategy therefore underperforms one built from outlet-level data. For larger chains, build regional reports that group outlets by city or market and rank items by contribution within each group. Regional managers can then decide for their own markets.
How can you A/B test menu changes?
Delivery platforms let you test a change on some outlets before rolling it out chain-wide. Both Swiggy and Zomato allow menu edits at outlet level, so you can run different menus in different outlets and compare.
Choose two similar outlets (similar market, customers and baseline revenue). Change the menu at one and leave the other alone. Run the test for several weeks so day-of-week effects even out, then compare revenue per order, item volumes and average order value. Good things to test:
- a price rise on a plowhorse, to see whether volume falls by more than the margin gain
- featuring a puzzle in the recommended section
- moving desserts higher in the category order
What should you measure?
- item-level order volume for the changed items
- category-level volume, in case the change moved orders between categories
- average order value
- rating trends, if you changed portions or recipes
- revenue per outlet per day, the final test of whether the change helped
How do you plan the menu by season?
Seasonal demand in India is often managed by instinct. Mango dishes peak in summer and then fade. Soups and warm drinks rise in winter in the north and centre. The wedding and festival season drives party and large-format orders. Monsoon moves demand toward comfort food in Mumbai and Pune.
Analytics makes this planned. Look at item-level demand by month over past years, link it to calendar events and decide in advance what to feature, remove or introduce. A seasonality calendar built from two or more years of sales is one of the most useful exercises a chain can do, and it lets you time Swiggy promotions to the dishes in demand.
How does Restrologic help?
Our restaurant analytics includes a menu performance view that classifies your whole menu into stars, plowhorses, puzzles and dogs and refreshes it as sales flow in from your POS and aggregators. It uses your recipe costs for true margin-based classification, and for multi-city chains it adds regional breakdowns. See how it would look for your menu and get in touch.