Vero -- Tools for Restaurant Operators
A monthly prime cost calculation tells you what went wrong. A weekly prime cost tracker tells you when it started -- and gives you time to act before it repeats three more times. This page walks through the exact four numbers to collect each week, why the weekly cadence is the only one that catches problems in the period they happen, and how a single spreadsheet makes the habit easier to maintain than it looks.
Most operators learn their prime cost percentage once a month, at the close of period. The number arrives after the fact: a scheduling decision that pushed labor from 28% to 34% happened in week one, ran unchecked for the remaining three weeks, and is now baked into the month-end figure as a single aggregate. The problem is gone; the cost has already compounded.
Weekly tracking changes the feedback loop. A spike in week two labor cost -- caused by a full-staff shift call during a day that turned out slow -- shows up as a one-week anomaly rather than a hidden drag on the monthly number. A delivery week with high wastage registers immediately. An extra part-time shift added during a school holiday appears in that week's data, not three weeks later when the invoice arrives.
The goal is not to create more reporting work. It is to shorten the gap between the decision and the consequence so corrections happen in the same period as the mistake. Four numbers, thirty minutes on Sunday evening, once a week -- that is the minimum viable prime cost tracking system for any restaurant or bar.
Set a fixed time to collect these -- Sunday evening or Monday morning, before the new week begins. Consistency matters more than precision at first. An approximate weekly count is more actionable than a perfect monthly one.
| Number | What it is | Where to get it | Common error |
|---|---|---|---|
| Gross sales | Total revenue before any deductions | POS daily report or cashbook | Using net sales after platform fees or discounts -- this inflates prime cost artificially |
| COGS | Opening stock + purchases received this week minus closing stock | Physical count Sunday evening + purchase invoices | Using purchase invoices alone -- stock sitting in the walk-in is not sold yet |
| Total labor cost | All wages, salaries, allowances, employer contributions for the week | Payroll records or weekly wage sheet | Excluding owner salary or draw, which makes the number look better than it is |
| Prime cost % | (COGS + Labor) / Gross Sales x 100 | Calculated from the above three | Calculating it once and not tracking the trend -- one number is a snapshot, four consecutive weeks is a pattern |
A single week's prime cost percentage is a data point. Four consecutive weeks is a pattern. Eight weeks is actionable intelligence.
The most valuable signal in a weekly prime cost tracker is direction, not level. A prime cost that sits at 61% for six weeks and then moves to 65% over two consecutive weeks is a system sending a clear message: something changed. It might be a new aggregator agreement reducing the effective gross sales denominator. It might be a kitchen hire that added labor without a corresponding revenue lift. It might be a supplier price change that has not yet been reflected in menu prices. None of these show up as clearly in a monthly figure because the monthly figure averages them away.
The second most valuable signal is variance. A business with consistent 60% prime cost is different from one that swings between 53% and 68% week to week. High variance means the business depends on which week you happen to measure it in. Low variance means the cost structure is predictable and the operator understands what drives it. A weekly tracker is the only way to know which kind of business you are running.
| Week | Gross sales | COGS | Labor | Prime cost % | Signal |
|---|---|---|---|---|---|
| Week 1 | 2,80,000 | 75,600 (27%) | 84,000 (30%) | 57% | Baseline established |
| Week 2 | 2,10,000 | 63,000 (30%) | 84,000 (40%) | 70% | Labor fixed while sales dropped -- investigate scheduling |
| Week 3 | 2,50,000 | 67,500 (27%) | 70,000 (28%) | 55% | Labor adjusted; sales recovered partially |
| Week 4 | 2,90,000 | 78,300 (27%) | 78,300 (27%) | 54% | Strong week; prime cost in target range |
The week 2 spike to 70% would have been invisible in a monthly calculation -- it would have appeared as a slightly elevated 59% average across four weeks. In a weekly tracker, it stands out immediately as a scheduling problem (labor cost stayed flat while a slow trading week cut revenue by 25%). The correction in week 3 is also visible: labor came down to match the lower revenue, and the week closed at a healthy 55%.
This is the operating value of weekly tracking. Not the number itself, but the contrast between weeks and the ability to match each deviation to a specific decision made that week.
A spreadsheet with five columns (week ending date, gross sales, COGS, total labor, prime cost %) and a chart of the prime cost percentage over time is all the structure you need. The discipline is in showing up every Sunday evening to collect the four inputs. The insights come from the chart.
For a bar or restaurant tracking food cost, labor by department, aggregator fees, and GST separately, the calculation gets more involved. A P&L tracker that separates revenue by channel (dine-in, delivery, events) and costs by line (food, beverage, staff, platform fees) gives a more accurate prime cost figure and shows exactly which revenue mix or cost category drove any given week's movement.