Restaurant · 6 min read

How do I use my restaurant POS sales data to fix the menu?

The short answer

Pull four months of item-wise sales from your POS, work out the profit each dish leaves after its food cost, and sort the menu into dishes that sell well and earn well, sell well and earn little, sell little and earn well, and sell little and earn little. Push the first group, fix the price or portion of the second, move the third to a better place on the menu, and cut most of the fourth. Match what you keep to the capacity of the kitchen, because a long menu is slow and costly.

Not sure about your case? Ask an expert, free ↓

The curry that sold twice a week

A family restaurant has a menu of 140 dishes, printed on eight pages. The owner is proud of it. When the POS report is pulled at last, fifty-one dishes sold fewer than ten times in a month. Three of those need a special masala that the cook makes in a separate pan, and one needs paneer that is bought in a separate bulk pack and goes off. The cook has complained for a year, and the owner had no numbers to answer him.

A POS records every sale, discount and cancellation. Most owners look only at the day's total. The item report is where the menu's problems and profits show up. A chef quoted in our research called menu engineering a common failure point and said to match the menu to the kitchen's capacity; the report tells you what that means for you.

Four reports to pull

A method of our own, drawn from how POS vendors and operators describe menu reviews.
ReportWhat it showsWhat to look for
Item-wise sales for 3 to 4 monthsHow many of each dish sold, and the sales valueThe top twenty dishes and the bottom thirty; dishes that sell only on weekends or only for one group
Contribution by dishSelling price less food cost, times the number soldDishes that bring the most rupees, not just the most plates
Sales by hour and by dayWhen the kitchen is busy and when it is idleDishes that jam the kitchen in peak hours; a lunch that deserves its own short menu
Discounts, voids and cancellationsWhat was given away, removed or cancelled, and by whomA dish with many cancellations is slow or wrong; heavy discounts by one user need a conversation

Four months, not four weeks, because a dish sold in a festival month or a wedding season can mislead. Compare the same days of the week, since a weekend dish looks poor in a weekday average.

Sort every dish into four groups

The standard menu-engineering method, in plain words; thresholds are yours to set.
GroupSells well?Earns well?What to do
StarsYesYesProtect them: keep the recipe and portion fixed, put them where eyes land, never run out
WorkhorsesYesNoRaise the price a little, trim the portion or change the recipe to cut the cost; do not drop them, they bring people in
PuzzlesNoYesMove up the menu, give the captains a line to recommend them, rename or add a photograph; give them a quarter to prove themselves
Dead weightNoNoCut most of them, except dishes that a regular group cares about or that anchor the menu

An illustration with made-up dishes: butter chicken sells 400 plates a month at a ₹120 contribution each, so it brings ₹48,000 and is a star. A chilli paneer sells 380 plates at a ₹60 contribution, ₹22,800, and is a workhorse worth a small price rise. A prawn curry sells 20 plates at a ₹200 contribution, ₹4,000, and is a puzzle; if the prawns spoil, it is dead weight. These are example figures, not benchmarks.

To work out the contribution you need the food cost of each dish. Reported food cost for an efficient restaurant is 28–35% of sales of sales across the menu, but dishes differ widely, so cost the top twenty from your recipes; see inventory and accounting tools.

Fixes that follow from the data

  • Cut the bottom, in steps. Remove ten to twenty dishes at a time, starting with those that need a special ingredient or a separate station. Tell the cook first.
  • Shorten the menu for lunch. If the hour report shows the lunch crowd ordering ten dishes, give them a lunch menu of ten, with a fixed price. See filling empty weekdays.
  • Move dishes within stations. If the tandoor is jammed at 9 pm and the curry station is idle, shift items that can be made at either.
  • Reprice carefully. A small rise on a star that is under-priced often costs no sales. Do it for one dish at a time and watch the next two weeks.
  • Bundle slow dishes with fast ones. A combo of a strong dish with a weak one raises the average bill and moves stock.
  • Watch the cancellations. A dish that is voided often is a signal about the kitchen or the recipe, not just the guest.
  • Check the weekend dishes. Some dishes only make sense on weekends; take them off the weekday menu to cut prep and wastage.

Fewer dishes also help the wait times covered in how long a table should wait, cut the spoilage that makes up 4–10% of purchases of purchases in Indian restaurants and make training easier.

Look for leaks in the same data

  • Discounts by staff member. A cashier with ten times the discounts of the others needs a conversation.
  • Voids after the bill is printed. A pattern of late voids can mean cash being taken and the sale cancelled.
  • Items sold below cost. A dish priced before a rise in oil, gas or paneer may now lose money.
  • Payment-mode gaps. A day where cash sales are far below the pattern.
  • Aggregator sales against the dining room. If delivery grows while dine-in falls, see what delivery apps really cost.

For the wider routine of theft and leakage, see the restaurant running chapter once it is published.

If you are small, if you are large

Small. A thali or tiffin place has a short menu already, so the report tells you which side dish or sweet is wasted and which lunch combination sells most. Do it every quarter on a sheet of paper.

Large or with a bar. The report is a monthly meeting: kitchen head, bar head, manager and owner, with the top and bottom dishes on the table, bar items listed separately from food items and a rule for what gets cut and what gets one more quarter.

What usually goes wrong

  • Never looking at the item report.
  • Judging a dish on plates sold and ignoring its contribution.
  • Cutting a dish a core group of regulars loves.
  • Using one festival month as the data.
  • Raising every price at once and not knowing which rise hurt.
  • Keeping dishes that need a separate prep for two orders a week.

Apply it to your restaurant

If you want help reading your report, send us the item sales with the dish prices and your food costs for the top twenty and we will help you sort the menu. A related question is how many dishes to keep; the menu pages in the library cover that.

Questions people ask

How many dishes should a restaurant have on its menu?

As many as the kitchen can make well at the busiest hour. Many Indian restaurants carry more than they sell. Let the item report decide which to keep.

What is menu engineering?

A way of sorting dishes by how well they sell and how much profit each leaves, into stars, workhorses, puzzles and dead weight, and then acting on each group.

How often should I review the menu?

Quarterly for a small place and monthly for a large one, using at least three months of data so that a festival or season does not mislead you.

Can I remove a dish a few regulars love?

Check who orders it. If it is a regular's favourite, keep it or offer it on request, even if it sells little. Cutting it may cost you more than the dish earns.

Where these numbers come from

  1. Food cost for an efficient Indian restaurant: 28–35% of sales (India; benchmark 30. Compare food.food-cost-percentage). Reported: Restromark, restaurant COGS calculator, ideal rent, salaries, opex, checked 14 November 2026.
  2. Share of purchased food wasted: 4–10% of purchases (India restaurants; 2-4% of revenue; plate waste about 70% of restaurant waste). Reported: Restaurant India, from waste to wealth (28 July 2026), checked 14 November 2026.

Fees, rates and rents change. Check the official source before you pay or sign anything.

Tools and software · Restaurant

More on tools and software for a restaurant

5 pages on this. You are on number 4.

  1. Which POS and billing software should a restaurant use, and what does it cost?
  2. Do I need KOT printers, tablets or QR ordering in my restaurant?
  3. Which inventory and accounting tools connect with a restaurant POS?
  4. How do I use my restaurant POS sales data to fix the menu?
  5. Cash, UPI and card fees, a reservation system and CCTV: what does a restaurant need?
The tools and software page →

Reading about it is one thing; doing it in your restaurant is another. If you'd like a hand choosing and setting up your tools, tell us where you are and a person will reply, free.

Get help with this ↓

What now?

Next question · 4 of 5 in Billing and toolsCash, UPI and card fees, a reservation system and CCTV: what does a restaurant need? →

Where are you?

One tap, and we point you to the right next step.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert