Restaurant Labour Cost in India: What It Should Be

Quick answer

Indian restaurants run labour at roughly 18 to 25 percent of revenue, not the 30 percent US benchmark, so the real cost is attrition rather than overstaffing.

Labour in an Indian restaurant typically runs 18 to 25 percent of revenue. Search for a benchmark and you will be told 30 percent, sometimes 35, because almost every article on restaurant labour cost is written for the United States, where the wage structure is completely different. Borrowing that number is not just inaccurate. It sends you after the wrong problem, because the expensive thing about Indian restaurant labour is not how many people you employ. It is how fast they leave.

Key takeaways

How to calculate it

Labour cost percentage is total employee cost divided by revenue for the same period, times 100.

Labour cost % = total employee cost ÷ revenue × 100

Total employee cost is not just salaries. Include staff meals, PF and ESI contributions where applicable, bonuses, uniforms, and the cost of accommodation if you provide it, which many Indian restaurants do for kitchen staff. Leave those out and you will flatter your number by several points.

On ₹10,00,000 of monthly revenue, employee costs of ₹2,20,000 give you a labour cost of 22 percent. That is a normal, healthy figure for an Indian full-service restaurant.

Why the 30 percent benchmark does not apply

Look at where the numbers come from and the gap explains itself.

American sources are consistent with each other. ChowNow puts a good labour cost at 20 to 30 percent of sales, Restaurant365 suggests 28 to 32 percent, Toast says around 30, and Rezku breaks it down by segment from 25 to 30 percent for quick service up to 35 to 40 percent for fine dining. They agree because they are all describing the same market.

That market pays a line cook a multiple of what an Indian restaurant pays, and it schedules hourly staff who can be sent home when the room is quiet. Neither is true in most Indian kitchens, where staff are salaried monthly, often live on or near the premises, and are not sent home at 3pm because service is slow.

So the Indian number lands lower. Industry reporting puts employee costs at roughly 18 to 25 percent of restaurant revenue, and that matches what shows up in real P&Ls.

A lower percentage sounds like good news. It is mostly a different problem wearing a smaller number.

The number that actually matters: attrition

Here is the part the imported advice misses entirely.

The same industry reporting cites the National Restaurant Association of India putting attrition in food service at 10 to 40 percent per month, with nearly 75 percent of QSR employees staying less than three years in a role. India's hospitality sector overall sees more than 50 percent annual turnover, and hourly staff attrition often runs past 70 percent.

Read that monthly figure again. At the middle of that range, a twenty-person restaurant is replacing several people every month, permanently.

That is where Indian restaurant labour money actually goes, and almost none of it appears on the salary line:

A restaurant running 22 percent labour with 30 percent monthly churn is in worse shape than one running 26 percent with a stable team, and the P&L will tell you the opposite.

Why the standard advice misfires here

Search for how to reduce restaurant labour costs and you will get the same list every time: forecast demand better, schedule smarter, cut overtime, hire part-time staff, avoid split shifts.

That advice is written for an operation with hourly staff, week-to-week scheduling flexibility, and overtime rules that bite. It is genuinely useful in that context.

In a typical Indian restaurant with monthly-salaried staff, most of those levers barely move. You cannot send a salaried cook home for three hours on a slow Tuesday and save money. Trimming the roster below what a Saturday rush needs just means a worse Saturday, which is the night that pays for the week.

So the honest version of "reduce labour cost" in India is not "employ fewer people for less time". It is two different things: keep the people you have, and get more revenue out of the same team.

Keeping the people you have

Retention is a labour cost strategy, and it is usually cheaper than the churn it replaces.

Pay at market, not below it. The saving from underpaying is smaller than the cost of replacing someone twice a year. Check what comparable restaurants nearby actually pay rather than what you paid last year.

Fix the roster before the salary. Predictable days off and shifts that end when they are supposed to are worth real money to staff, and they cost you nothing.

Train deliberately, not by osmosis. Staff who understand the menu sell more of it, which pays for the training directly. It is the same mechanism behind upselling that actually works: a server who has tasted the dish recommends it with conviction.

Promote from inside where you can. A commis who can see the path to becoming a cook stays longer than one who cannot.

Getting more from the team you have

The other half is revenue per staff hour, and this is where the room's design does more than the roster does.

If your servers spend the rush walking between tables taking orders, that is time not spent serving, reading tables, or selling. Removing the order-taking trip lets the same team cover more covers on the night that matters. That is the argument behind improving table turnover, and it is a labour argument as much as a speed one, since more covers on the same payroll is a lower labour percentage without anybody losing a shift.

It also protects you against churn in a specific way. When the suggestion to add a side or a second round is built into how the order is taken, your average ticket stops depending on whether the person carrying it has been there three years or three days. That consistency is the whole point of AI upselling, and in a 30-percent-monthly-churn environment it matters more in India than almost anywhere else.

We build one of these, so weigh that accordingly. The underlying point stands without us: in a high-attrition market, systems that do not depend on staff tenure are worth more than they are in a stable one.

Where labour sits in the whole picture

Labour is one line. Food is the bigger one, rent is the one that decides your fate, and channel mix is the one that swings hardest.

Watch food and labour together as prime cost, which should sit under roughly 60 to 65 percent of revenue. At 32 percent food and 22 percent labour you are at 54 percent, which leaves room for everything else. At 35 and 28 you are at 63 percent and the rest of the P&L has almost nothing to work with.

We put the full line-by-line build in restaurant profit margin in India, and the food side in food cost percentage.

FAQ

What is a good labour cost percentage for a restaurant in India?

Roughly 18 to 25 percent of revenue for a full-service restaurant, which is well below the 28 to 35 percent quoted by American sources. Judge it alongside food cost as prime cost, which should stay under about 60 to 65 percent combined. A low labour percentage with high attrition is not the good result it looks like.

How do you calculate restaurant labour cost?

Divide total employee cost by revenue for the same period and multiply by 100. Include staff meals, PF and ESI where applicable, bonuses, uniforms, and accommodation if you provide it, not just salaries. Leaving those out understates the number by several points and makes benchmarking meaningless.

Why is restaurant attrition so high in India?

The National Restaurant Association of India reports attrition of 10 to 40 percent per month in food service, driven by low barriers to switching, migration, and competition for trained staff. Nearly 75 percent of QSR employees stay under three years. The cost shows up in rehiring, retraining, and service quality rather than on the salary line.

Is it cheaper to cut staff or improve retention?

Improving retention is almost always cheaper in India, because the salary saving from a thinner roster is small next to the cost of constant replacement and the revenue lost to slower, less confident service. Cutting the roster below what your busiest shift needs also damages the nights that carry the week.

What is prime cost in a restaurant?

Prime cost is food and beverage cost plus total labour, as a share of revenue. It is the number to manage weekly because it is the largest and most controllable block of spending. Under about 60 to 65 percent leaves enough room for rent and overheads to still produce a profit.

What to do next

Work out two numbers for last month: labour as a percentage of revenue, and how many people left. If the first is inside 18 to 25 percent and the second is more than one or two, your labour problem is retention, not headcount, and no amount of roster trimming will fix it. Fix the roster predictability and the training first, then look at whether your team spends the rush serving or just taking orders. Book a short dineomai demo if you want to see what happens to covers per server when the order-taking trip disappears.

See it on a real table

A 15-minute demo: watch dineomAI take an order, speak five Indian languages, and upsell the right pairing. No hard pitch.

Book a 15-minute demo →