How it works Compare Pricing Blog About Log in EN ⇄ FR

POS data & KPIs

Restaurant KPIs: the numbers your POS already tracks

Your till records every item, every void, every discount, every night — and most of it dies unread in a back-office menu. Here are the KPIs worth a daily look, the reports that pay, and the method that turns a POS full of data into decisions about your menu, your prices and your margin.

Try methodus free The method

14-day trial · No credit card · Cancel anytime

Definition

Restaurant KPIs (key performance indicators) are the handful of numbers that tell you whether the venue earned money and why: revenue against the same weekday, sales mix by item, voids and discounts, and the gap between the margin your recipes promise and the margin your sales delivered. Every one of them can be computed from data your POS already records.

Variance = actual food cost % − theoretical food cost %

The five KPIs worth a daily look

Not a forty-line report — five numbers, read in the time a coffee takes. Everything else is monthly.

Sales vs the same weekday — this Tuesday against the last four Tuesdays, not against yesterday; weekdays have personalities and comparing across them is noise
Sales mix — which items actually sold, because the menu earns item by item, not as an average
Voids, comps and discounts — the money that rang and then un-rang; small individually, a pattern in aggregate
Theoretical vs actual margin — what your costed recipes say the night should have earned, against what it did
Coverage — how much of what sold is matched to a costed recipe; every unmatched item makes the other four numbers softer

Two traps. Reading the month instead of the day — by the time a bad pattern shows up in a monthly report it has cost you thirty nights. And reading revenue alone — a record night selling your lowest-margin items can earn less than a quiet one selling the right ones. Revenue is the loudest number in the building and the least conclusive.

Theoretical vs actual: the one comparison that finds money

Every costed recipe is a promise: this dish, at this portion, at today's ingredient prices, earns this margin. Multiply each promise by what the till says you sold and you get the night's theoretical margin — what the venue should have earned. The actual number is what purchases and takings say really happened. The gap between the two is the most useful number in the building: it's over-pours, over-portions, waste, comps nobody logged, and prep loss no spec accounts for — leaks with names, findable one by one.

Neither side of the comparison lives in the POS alone. The till knows what sold but not what it cost to make; your recipes know the cost but not what sold. The comparison only exists when the two are connected item by item — which is exactly the connection most venues never build, because until recently it meant a spreadsheet and a Sunday.

The method

From till data to decisions, in four steps

No analyst, no BI project. One connection built once, then a daily glance.

1
Get the data out of the till
Every POS can produce an item-level sales report — export, print-out, or the report screen itself. Whatever yours produces is enough; the format matters less than the habit. If the data stays inside the POS's own back office, it will keep dying there.
2
Match items to costed recipes — once
Connect each POS item to the recipe it represents: 'Negroni' on the till to the Negroni spec with its real ingredient cost. It's a one-time pass with a few clicks a week of upkeep as the menu moves, and it's the step that turns sales rows into margin. A till that only knows prices can never tell you what a night earned.
3
Read the same five numbers every morning
Yesterday against the same weekday, the mix, the voids, theoretical vs actual, coverage. Five numbers, every morning, same order — the value is in the streak, because a leak shows up as three odd days long before it shows up in a monthly report.
4
Act on the mix, not the total
The decisions live item by item: the high-margin cocktail nobody orders needs a menu position, the bestseller earning nothing needs a price or a portion look, the item that sells only on weekends needs a weekday reason to exist. That's menu engineering — the mix is where POS data finally pays.

With methodus

Any POS, no integration required

methodus was built for the venue whose POS doesn't have an API — which is most of them:

Import any sales report

CSV or spreadsheet export, a photo of the printed report, or paste straight from the POS screen — the AI reads it either way. If your till can produce a sales report at all, methodus can ingest it.

Items matched to costed recipes

Each POS item links to its costed spec, so every sales row carries a real margin. methodus remembers your confirmations — the second import matches itself.

The dashboards, computed for you

Sales against the same weekday, sales mix, voids and discounts, theoretical vs actual margin — the daily five, on a dashboard instead of in a spreadsheet.

Lightspeed K-Series: automatic

On Lightspeed K-Series the till syncs daily on its own — no exports, no photos. Other POS systems flow through the report import.

The till keeps ringing exactly as before. The difference is that what it records stops being a receipts archive and starts being the morning's five numbers.

Try methodus free14-day trial · No credit card · Cancel anytime

The decisions the mix points to — prices, positions, portions — are the subject of the menu engineering guide → — where sales data turns into a better menu.

Go deeper on your POS data

FAQ

Restaurant KPI FAQ

Five numbers cover the day: sales against the same weekday (not against yesterday), sales mix by item, voids and discounts, theoretical vs actual margin, and how much of what sold is matched to a costed recipe. Everything else — labor percentage, prime cost, supplier price drift — is a weekly or monthly read.

Theoretical food cost is what your costed recipes say the period should have consumed, given what the POS sold. Actual food cost is what purchases and stock movement say really happened. The gap between them is waste, over-portioning, unlogged comps and prep loss — the leaks worth hunting, because each has a findable cause.

Start with the item-level sales report — it feeds sales mix, menu decisions and margin analysis. Add the voids and discounts report, and sales by daypart. The dashboard totals your POS shows by default are the least useful screen it has: revenue without margin flatters the wrong nights.

Lightspeed K-Series syncs automatically every day. Every other POS works through the sales report import: upload a CSV or spreadsheet export, photograph the printed report, or paste from the POS screen — the AI extracts the items and matches them to your costed recipes, and remembers your matches for next time.

Sales mix analysis breaks revenue down by item to show what actually sold — and, once items carry recipe costs, what each item earned. It's the basis of menu engineering: two nights with identical revenue can differ sharply in profit purely on mix, which is invisible in the totals your POS shows by default.

Who builds methodus

methodus is built by an operator. Nathaniel Gilliand, École hôtelière de Lausanne graduate, runs restaurants, bars and beach clubs. This is the tool he built to find the margin that was evaporating in his own P&L.

14-day trial, no credit card.

Start free

A till that finally talks

Import any sales report — file, photo or paste. Items matched to costed recipes, margins computed, the daily five on one dashboard.

Try methodus free