Restaurant KPIs: The Metrics to Track for Every Branch

Restaurant KPIs are the handful of numbers that tell you four things about every branch: whether it is selling enough, whether it spends the right amount to do it, whether it runs smoothly, and whether guests come back. They fall into four groups: sales, cost, operations and customers. You do not need all of them on one screen. An owner needs six to eight that summarise every branch; a branch manager needs a slightly different set they can act on in their next shift. Above all, every branch must calculate each KPI the same way, or the numbers cannot be compared.

Sales KPIs: is the branch selling enough?

Sales KPIs tell you how much came in, from how many guests, through which channels, and how much was given away along the way.

• Net sales: what you actually keep from sales after discounts, comps, voids and refunds, excluding VAT. Formula: gross sales − discounts − comps − voids − refunds − VAT.
• Average check (average ticket): how much each order or guest spends. Formula: net sales ÷ number of transactions, or ÷ covers for dine-in.
• Covers and transactions: covers count the guests you served, transactions count the orders. Track both, because a table of four on one bill is one transaction and four covers.
• Sales per seat and sales per hour: how hard your space and your opening hours are working. Formula: net sales ÷ number of seats, and net sales ÷ trading hours.
• Channel mix and delivery share: how sales split between dine-in, takeaway, drive-through and delivery apps. Formula: channel net sales ÷ total net sales × 100. Read delivery after the commission the apps keep, not the headline figure.
• Discounts and voids %: how much revenue is given away or cancelled. Formula: (discounts + voids) ÷ gross sales × 100. A rising figure in one branch is often the first sign of a training or control gap.

Cost KPIs: is the branch spending the right amount to sell it?

• Food cost %: the cost of ingredients consumed as a share of food sales. Formula: (opening inventory + purchases − closing inventory) ÷ food net sales × 100.
• Labour cost % of sales: wages plus employer costs for the hours actually worked, as a share of net sales. Formula: labour cost ÷ net sales × 100.
• Prime cost %: food and labour together, the two costs you can change week to week. Formula: (food cost + labour cost) ÷ net sales × 100.
• Waste %: the value of food thrown away or spoiled as a share of food cost. Formula: recorded waste value ÷ total food cost × 100. It is only as reliable as the waste log behind it.

You will find target ranges for these KPIs quoted everywhere online. Treat them as rough rules of thumb at best: a coffee concept, a burger chain and a fine-dining room have very different cost structures, and the right target for each branch is the one you set from its own history and its own menu. If food cost is the number that worries you, the gap almost always traces back to a small set of causes, each worth investigating on its own.

Operations KPIs: is the branch running smoothly?

• Table turnover: how many times each seat or table is used in a period. Formula: covers served ÷ number of seats, or parties seated ÷ number of tables.
• RevPASH (revenue per available seat hour): combines how full you are with how much guests spend. Formula: net sales ÷ (seats × hours open).
• Speed of service: the time from order to food on the table, or to handover for takeaway, drive-through and delivery. Formula: average of (handover time − order time), tracked separately per channel.
• Order accuracy: how often an order goes out exactly as ordered. Formula: (orders − orders with a complaint, remake or refund) ÷ orders × 100.

Customer KPIs: are guests coming back?

• Repeat rate: the share of guests who order again within a period. Formula: returning customers ÷ total identified customers × 100. You need a loyalty programme, an app or a phone number to recognise a returning guest.
• Guest satisfaction and reviews: average rating and review volume per branch across the platforms you use, plus the themes guests keep mentioning. Formula: average rating per branch per period, and the number of reviews raising the same issue.

Which KPIs go on the owner's dashboard, and which on the manager's

The owner and the branch manager ask different questions. The owner asks which branch needs attention. The manager asks what to change on the next shift. Give each a short list instead of the full set, and make sure both lists use exactly the same definitions.

The owner's dashboard: seven KPIs across every branch

• Net sales against target, by branch
• Prime cost %, by branch
• Food cost % and labour cost %, to see which side of prime cost moved
• Average check and transactions, to tell a traffic problem from a spending problem
• Delivery share, to see how the channel mix is shifting
• Discounts and voids %, as a control check
• Guest rating, to catch a service problem before it shows up in sales

The branch manager's dashboard: what they can act on this week

• Net sales by daypart and by channel
• Labour cost % by shift, against the planned rota
• Covers and table turnover, or RevPASH, for dine-in
• Speed of service and order accuracy, by channel
• Waste % and the most-wasted items
• Discounts and voids, by cashier
• New reviews and the issues they raise

How to compare branches fairly

A branch ranking is only useful if it compares like with like. Three rules keep it honest.

• One definition everywhere. Net sales must mean the same thing in every branch: before or after VAT, with delivery commission in or out, with staff meals counted the same way. One branch recording comps as discounts and another recording them as voids is enough to make the ranking meaningless.
• Like-for-like periods. Compare the same days of the week and the same weeks across branches, and line up Ramadan, Eid, school holidays and the seasons year on year by the event itself, not by calendar date. Leave newly opened branches out of growth comparisons until they have a full year of history.
• Normalise for size. A large mall branch will always outsell a small neighbourhood one. Compare sales per seat, sales per labour hour and RevPASH rather than raw totals, and group branches by format: dine-in, drive-through, food court and delivery-only kitchens.

How often to review each KPI

• Daily: net sales, transactions, average check, labour cost %, discounts and voids, plus any order accuracy or review issues. These are the numbers you can still change this week.
• Weekly: food cost % against what your recipes say it should be, prime cost %, waste %, channel mix, speed of service and the branch ranking. A week is long enough to separate a pattern from one bad day.
• Monthly: actual food cost from the full inventory count, repeat rate, guest satisfaction trends, sales per seat and RevPASH by branch format, and the targets for the month ahead.

Common mistakes with restaurant KPIs

• Tracking everything. Thirty KPIs on one screen means nobody knows which one to act on. Start with the short list and add a KPI only when a decision needs it.
• A different definition in each branch. If every branch manager builds their own report, you end up with as many versions of net sales as you have branches.
• Reading percentages without the totals behind them. Labour cost % can fall simply because sales jumped on a busy weekend, while hours stayed well above plan.
• Ranking branches on raw sales. The biggest branch tops the list every time, and the ranking teaches you nothing.
• Waiting for month-end. A KPI reviewed once a month describes problems that started weeks earlier.
• Treating a number as an answer. A KPI tells you that something moved. You still need to know why, and what to do about it.

“A KPI is only useful if every branch calculates it the same way and someone knows what to do when it moves.”

How DataGrid helps

DataGrid brings your point-of-sale, delivery app, scheduling and purchasing data together so every branch sits in one place, with ready-made restaurant dashboards and no data team needed to build them. Each KPI is calculated once, with one agreed definition, so net sales in your first branch means exactly what it means in your fiftieth. The numbers are updated automatically every day, and the AI Advisor explains what changed, why it changed and what to do next: for example, which branch's labour cost rose and which shifts drove it. Your team makes the call. Book a demo to see your own branches on one screen.

Frequently asked questions

What are the most important KPIs for a restaurant?

If you can only watch a few, watch net sales, average check, transactions, food cost %, labour cost % and prime cost %. Together they tell you whether you sold enough and whether you kept enough of it. Add delivery share and guest rating if you run several channels or several branches.

What is the difference between a KPI and a metric?

A metric is any number you can measure. A KPI is one of the few metrics you have tied to a target and a decision. Sales per seat is a metric; it becomes a KPI when you set a target for it and someone is responsible for moving it.

How do I track KPIs across several branches without spreadsheets?

Connect your systems once, agree a single definition for each KPI, and let the numbers calculate themselves for every branch. Spreadsheets break at the definitions step, because each person who builds one makes slightly different choices. A shared dashboard built on one set of definitions removes that problem and frees your managers from rebuilding reports by hand.