A full house is not the same as a good night. A restaurant can be packed, the kitchen slammed, the tips flowing — and still lose money on that exact shift. The tables were full; the margin wasn't. And most owners only find that out weeks later, when the accountant closes the month and the loss is already baked in.
The businesses that survive in food do one thing differently: they know the result of a shift by the time the doors close, not thirty days after. It comes down to three numbers — and once you watch them shift by shift, "were we busy" stops being your measure and "did we earn" takes its place.
The three numbers that decide a restaurant
Almost everything about a restaurant's profitability lives in three costs, and their relationship to sales:
| Number | What it is | Healthy range* |
|---|---|---|
| Food cost | Ingredients as a % of sales | ~28–35% |
| Labor cost | Kitchen + floor wages as a % of sales | ~25–35% |
| Prime cost | Food + labor together | keep under ~60–65% |
*Ranges vary by format — a bakery and a fine-dining kitchen live in different worlds. The point isn't a magic number; it's watching your numbers move.
Prime cost is the one that matters most, because it combines the two biggest levers you actually control. If food and labor together eat more than roughly two-thirds of sales, there's little left for rent, utilities, and profit — no matter how full the room was.
Why "once a month" is too late
A monthly close tells you the average of thirty shifts. But restaurants don't fail on averages — they bleed on specific nights: the over-scheduled Tuesday, the promo that priced dishes below cost, the week a supplier quietly raised prices.
- A good month can hide bad shifts. Strong weekends mask weekday losses you never see.
- By the time you know, it's history. You can't re-staff a Tuesday that already happened, or unsell a dish you sold at a loss all week.
Watching prime cost per shift turns those invisible losses into something you can act on tomorrow — not next month.
"I always looked at the month. When I started seeing food and labor cost per shift, I found that two weekday evenings were quietly losing money every single week. Cutting one line cook on those shifts turned the month around."
What to watch, shift by shift
You don't need a controller to do this — you need three quick reads after service:
- Sales for the shift — what came in.
- Food cost — roughly, what the sold dishes cost you.
- Labor — who worked and what it cost.
Put those together and the shift tells you the truth in one line: prime cost as a share of sales. Over a couple of weeks a pattern appears — which shifts earn, which drain — and staffing, prep, and promos start getting decided by numbers instead of by "it felt busy."
How this works in Finmap
Finmap pulls your sales and expenses together so the shift result isn't a spreadsheet exercise. Connect your POS and accounts, and revenue, supplier payments and payroll land in one place, categorized — so food cost and labor cost are visible against sales without you re-typing anything.
Because it's live, you don't wait for a monthly close: after a shift you open Finmap and see whether that service actually earned. If a location or day is dragging, it shows — and you fix the schedule or the menu price while it still matters. The month stops being a surprise and becomes the sum of shifts you already understood.
📌 Stop judging a shift by how busy it felt. Try Finmap free for 14 days: bring sales, suppliers and payroll into one place, and see food cost, labor cost and the real result after every shift — while you can still change tomorrow's.
Frequently Asked Questions
It depends on format, but under ~60–65% of sales is a common healthy ceiling. More important than hitting a benchmark is watching your own prime cost trend — a creeping number is a warning long before it's a crisis.
A POS tells you what you sold; it rarely shows what that selling cost once suppliers and wages are counted. Bringing sales, supplier payments and payroll together is what turns "revenue" into "did we earn."
Weekly catches most patterns; per-shift catches the specific bad nights inside a good week. Start weekly if that's easier — the habit of comparing cost to sales is what matters most.
You don't need perfect nightly inventory to start. Track supplier spend against sales over the shift or week; it's directional but honest — and far better than finding out a month later.
