Prime Cost (Labor + Food %) Tracker

$39.00

an operator who already watches food and labor, knows roughly where each sits, and wants them combined into the one ratio that actually decides whether the place makes money.

Local-firstNo telemetry — nothing phones homeNo lock-inNo migration

Feed it a weekly line of sales, food cost, and labor cost and it computes your prime cost as a percent of sales for every week, flags the ones over 60%, and lays them out as a trend so you catch the drift before the month-end P&L does.

$39 a month, flat. No per-seat charge and no contract. Cancel any day and the reports you already ran stay on your disk.

Your food cost is fine and you’re still not making money

You watch your food cost. It sits around 34%, right where it should be. Labor looks reasonable too, most weeks. And still the money doesn’t show up the way the individual numbers say it should.

That’s because the figure that governs a restaurant isn’t food cost or labor cost on its own. It’s the two together, against sales, week over week. Food at 34% and labor at 32% is a 66% prime cost, and 66% is the gap between a decent month and a frightening one. Watching the two separately hides the weeks they both crept up at once, and the P&L only catches it a month late, once it’s already spent.

One weekly export in, the trend out

  1. Keep a weekly CSV: the week, sales, food cost, and labor cost. One row per week.
  2. For each week it adds food and labor and divides by sales to get the prime cost percent.
  3. It flags every week over your target (60% out of the box) and lays the weeks out as a trend, so you see the drift, not just the latest point.

What the report shows

  • PRIME_COST.md: the average prime percent across your weeks, a count of the weeks over target, and a week-by-week detail table.
  • The weekly cadence is the whole point, since prime cost is a leading number you can still act on, unlike a P&L that lands after the period you’d have wanted to fix.
  • prime.csv, the raw trend line of week, prime percent, and whether it ran over, ready to chart.
  • prime.json for anything else you feed it into.

Who it’s for, and who it isn’t

Built for an operator who already lives in these metrics and wants food and labor combined into the single ratio that decides profitability. A restaurant, a bar, a hospitality room past the guessing stage.

Not for you if you only look at the numbers monthly off the P&L and that’s genuinely enough for how you run. This is for the operator who wants the weekly read. It also needs labor alongside food, so a food-cost-only view won’t fill it out.

What it replaces, and what those do better

A weekly spreadsheet you rebuild by hand, or the monthly P&L. The P&L is genuinely better as the number of record: reconciled, complete, and what your accountant and your lender go by.

What the P&L can’t be is early. It arrives weeks after the period, when the overspend is already gone. This computes the same prime ratio every week from four numbers, for a flat fee on your machine, so you see the drift while you can still cut a shift or renegotiate a case. Keep the P&L for the record. Use this to steer.

Your data, and where it stays

Your weekly sales, food cost, and labor cost read from disk and write back to disk at 0600 permissions, with no network call. What your labor and food actually run is the private core of a restaurant’s viability, and here it becomes a trend line without leaving the building.

$39 a month, and your first trend

Set the weekly CSV, an output folder, and your target percent in a .env, then run. First prime-cost trend in a couple of minutes. Add a row each week and the trend extends, so after a month or two the drift is obvious at a glance.

Flat monthly, cancel any day, and the reports stay on your disk.

Security and privacy

Handles client sales/food/labor exports (weekly P&L-adjacent figures). Security is designed in.

Principles
Local-first. WEEKLY_CSV is read from disk and never transmitted anywhere; nothing in this tool touches the network. Nothing is uploaded, no telemetry, no cloud dependency.
Non-destructive. The source CSV is only read, never modified or deleted.
Least privilege. Reads WEEKLY_CSV, writes only under OUTPUT_FOLDER.

Protections implemented (v0.1.0)
Path-traversal defense — every output filename is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so the report can’t be written outside OUTPUT_FOLDER.
Fail-fast config validation — clear errors for missing/invalid WEEKLY_CSV/OUTPUT_FOLDER/TARGET_PCT before any file is touched.
Restrictive permissions — the generated report (PRIME_COST.md, prime.json, prime.csv) is written 0600.
Defensive parsing — the CSV parser and currency parser never throw on malformed input (missing fields default to empty string, unparseable amounts default to 0); a bad row degrades the analysis rather than crashing it.
Secrets discipline.env and generated PrimeCost/ output are git-ignored; no secrets or client data in the repo.

Distribution / AV trust

Known limitations / roadmap
TARGET_PCT is a single flat threshold — no day-part or seasonal adjustment (e.g. holiday weeks running hotter on labor). Reviewers should sanity-check flagged weeks against known one-off events.
– Prime cost here is food_cost + labor_cost only; it does not separately net out employer payroll taxes/benefits from labor_cost — feed a fully-loaded labor figure if that’s the intended definition.
– No historical baseline/rolling average in v0.1.0 — each week is judged independently against TARGET_PCT, not against the location’s own trailing trend.

Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.

Frequently asked questions about Prime Cost (Labor + Food %) Tracker

What is prime cost software, and why does prime cost matter so much to a restaurant?

Prime cost is the single number that decides whether a restaurant lives or dies, and prime cost software exists to keep that number in front of an owner every week instead of once a year when the accountant adds it up. Prime cost is your food cost plus your labor cost, measured as a percentage of sales. Together those two are the largest controllable costs a kitchen has, and if they drift the wrong way the restaurant bleeds out quietly while the dining room still looks busy. This tool combines food cost and labor cost against sales to compute a weekly prime cost, flags the weeks that run over your target, and trends it so a problem shows up early rather than at year end.

The buyer is an independent restaurant owner who has been flying blind on this figure. Most owners feel when a month is off, but they cannot say whether food or labor caused it, or how bad it really got, because the number lives buried in a spreadsheet or in a report they only see long after the week is gone. The prime cost software puts it on a weekly clock, so the read arrives while you can still act on it.

The workflow is short. You import your sales, your food cost, and your labor cost. You set your prime-cost target, the percentage you are aiming to stay under. You get back a weekly prime-cost report that breaks the number into its food and labor halves, marks any week that ran over, and shows the trend across weeks. That is the whole loop, built to be run every week without turning it into a project.

Prime cost matters because it is where a restaurant is won or lost. A great concept with a beautiful room still fails if food and labor eat too much of every dollar that comes in. This is a food business, regulated for safety under the state and local rules modeled on the FDA Food Code, but no amount of good food safety saves an operation whose prime cost is out of control. Watching the number weekly is how owners catch the slide while a small correction still fixes it.

The reason weekly beats monthly is that a month is four chances to bleed before you notice. If labor crept up in week one, you want to know in week two, not after four weeks have compounded the damage. By flagging over-target weeks and trending the figure, the tool turns prime cost from a post-mortem into a live signal, which is the only version of the number that can actually change an outcome.

What you get is the one figure that makes or breaks the business, watched weekly and split so you can see which half is the problem. You can see how the weekly report is built on the Prime Cost Tracker product page, and see the other tools built for independent operators on the small business operators page. Import your sales, food, and labor, set a target, and let the tool tell you every week whether you are winning or slipping.

How does the tool calculate weekly prime cost and flag the weeks that run over target?

The math behind this prime cost software is simple on purpose, because a number you have to trust has to be one you can understand. Each week the tool takes your food cost and your labor cost, adds them together, and divides by your sales for the same week. That gives prime cost as a percentage of sales. You set a target percentage you want to stay under, and any week that lands above it gets flagged, so the report draws your eye straight to the weeks that need attention rather than making you read every row.

The sales figure at the bottom of that fraction has to be honest, and for most restaurants it comes off the register. Those recorded sales are also what appears on a IRS overview of Form 1099-K, the form third-party payment networks send for the card payments you take in for goods and services, so the denominator in your prime cost rests on the same real transactions your payment records already track. Feeding the tool accurate weekly sales is what keeps the percentage meaningful, because a prime cost measured against a wrong sales number is worse than no number at all.

The food and labor split is what makes the flag useful instead of just alarming. When a week runs over target, you do not only learn that something went wrong, you see whether food or labor drove it. A spike in food cost points you at waste, portioning, or a supplier price jump. A spike in labor points you at overstaffing or overtime. Without the split you would know the week was bad but not where to look, which is the trap a single blended number sets.

The trend line is the third piece, and it is where early warning lives. One over-target week can be noise, a slow week or a big delivery. Three in a row climbing is a pattern, and the trend makes that pattern visible before it becomes a crisis. By watching the direction rather than a single point, you catch a slow creep in labor or a gradual rise in food cost while a small change can still turn it around.

Because the calculation runs weekly, it stays close to what is actually happening on the floor. A monthly figure blends four different weeks into one average that can hide a bad stretch entirely. The weekly cadence keeps each week visible, so a problem does not get averaged away, and a good week does not paper over a bad one. That resolution is the whole point of tracking prime cost this often.

The result is a weekly number you can act on, split so you know which half to fix and trended so you see trouble coming. You can see how the flags and trend are built on the Prime Cost Tracker product page, and how the same weekly discipline runs through the other tools for independent operators on the small business operators page. Give the prime cost software honest weekly numbers, and it will tell you plainly which weeks slipped and why.

Where does my sales and payroll data live, and is it safe with this tool?

Your numbers stay with you. This prime cost software works from the sales, food cost, and labor cost you bring to it, and it does not require you to push your financials up to a shared cloud to get a weekly prime cost. For an independent owner that is the honest answer to a fair question, which is who else gets to see how my restaurant is really doing. Your sales, your margins, and your labor spend are sensitive, and here they stay in your hands.

That matters because prime cost data draws on some of the most sensitive information a business holds. Labor cost is downstream of payroll, which touches employee pay and personal details, and sales reveal exactly how the operation is performing. The FTC’s plain-language FTC guide Protecting Personal Information is built around a few simple ideas, take stock of what you hold, keep only what you need, lock down what you keep, and get rid of what you no longer use. A tool that works from your own figures instead of hoarding a copy on a distant server fits that thinking.

The tool keeps a record of the weekly reports it produced, so you can see what it did with the numbers you gave it. It works from summary figures, your weekly sales, food, and labor totals, rather than needing every employee’s pay stub, which keeps the most sensitive detail out of it in the first place. You feed it the totals, it returns the prime-cost read, and the underlying data stays yours to keep or clear as you decide.

It would be dishonest to claim that keeping data local makes it automatically safe. The machine you run this on still needs ordinary care, a password, current updates, and a backup so a hardware failure does not take your records with it. What the setup removes is the extra exposure of a third-party breach, because your sales and labor figures are not sitting in a shared system waiting to be caught up in someone else’s incident. The surface you have to protect is smaller and simpler, which is what a small operator can realistically manage.

The same discipline the FTC guide describes applies to the payroll detail behind your labor cost. Keep only what you truly need, store the sensitive parts where you can lock them, and clear out what has aged past use. Because this tool asks for labor totals rather than raw payroll, it helps you follow that thinking by keeping the rawest data out of the prime-cost workflow entirely.

If data location is what makes you hesitate, this is the point in the tool’s favor. You can read how the approach works on the Prime Cost Tracker product page, and see how it lines up with the way other independents run on the small business operators page. Your sales, your food cost, and your labor spend stay yours, and the prime cost software earns its keep without asking you to give that up.

How is it different from a spreadsheet or my POS back-office?

The difference is that this prime cost software is built to do one job every week without falling apart, where a spreadsheet and a POS back-office each fail at prime cost in their own way. A spreadsheet can compute prime cost, but only if someone keeps it fed and does not break a formula, and in a busy restaurant that discipline slips fast. A POS back-office tracks sales well but often treats prime cost as an afterthought buried behind features you pay for and rarely open. This tool does the weekly prime-cost read as its whole reason to exist.

Start with the spreadsheet. It is free and flexible, which is exactly why it is fragile. One wrong cell, one week nobody updated, and the number is silently wrong, and prime cost that is wrong is worse than none because it gives false comfort. A spreadsheet also tends to lose its own history, overwritten week after week until you cannot see the trend that matters most. Keeping a real record is part of running a business, and the IRS guidance on how long to keep records expects organized supporting documents behind your figures, which a tool that retains each weekly report serves better than a sheet you paint over.

Now the POS back-office. A register system is good at capturing sales, but food cost and labor cost have to come together honestly for prime cost to mean anything, and many back-office modules make you dig for that combined view or upsell it as a higher tier. You end up paying for a broad platform to reach one number it treats as secondary. This tool inverts that. Prime cost is not a buried report here, it is the product, computed weekly, split into food and labor, and flagged when it runs over.

There is also the matter of focus. Because the tool does only prime cost, it stays simple enough to actually run every week, which is the habit that makes the number useful. A platform with a hundred features invites you to check the prime-cost screen occasionally at best. A tool that opens straight to the weekly read makes the review a two-minute routine rather than a project you keep postponing.

What you give up by going focused is worth stating. You are not buying a full back office that also runs your floor, your ordering, and your accounting. If you need all of that in one place, a suite may fit you better. But if what you actually lack is a trustworthy weekly prime cost that you will genuinely look at, paying for a whole platform to get a number it buries is the expensive way around.

The prime cost software is the focused alternative for the owner who wants prime cost watched properly. You can compare how it fits your restaurant on the Prime Cost Tracker product page, and see where it sits among tools for independent operators on the small business operators page. One number, watched weekly, split and flagged, at a price a single restaurant can carry.

Does the tool handle payroll, or do I still need to keep my own labor records?

This tool tracks the labor side of prime cost, but it does not run your payroll, and you still keep your own labor records. The prime cost software takes your labor cost as an input, sets it against food cost and sales, and reports the combined prime-cost percentage. It is a measurement tool, not a payroll system. It does not cut paychecks, calculate withholding, or file anything, and it is honest about that line so you know what still sits with you.

Keeping payroll separate is deliberate, and it is safer that way. Payroll holds the most sensitive employee information a small business touches, and a prime-cost tracker does not need pay stubs or personal details to do its work, only your labor totals for the week. By asking for the total rather than the raw payroll, the tool measures what it needs while leaving the sensitive detail in your dedicated payroll process, which is one less place that information has to live.

The labor side also carries a real recordkeeping duty that no tracking tool removes. Under federal wage law, an employer must keep certain payroll records, and the DOL Fact Sheet #21 on FLSA recordkeeping sets out that employers must preserve payroll records for at least three years and the wage-computation records behind them for two years. That obligation stays with you whether or not you track prime cost, and it belongs in a proper payroll process that holds the underlying hours, rates, and pay, not in a prime-cost report.

Where the tool helps is in making that labor cost mean something week to week. Payroll tells you what you paid, but on its own it does not tell you whether you paid too much for the sales you did. By setting labor against sales alongside food, the tracker turns a raw payroll total into a labor percentage you can judge, and flags the weeks where it ran hot. That is the read a payroll system alone does not give you, because payroll is about paying people correctly, not about whether the staffing fit the week.

So the two work as a pair. Your payroll process keeps the detailed, legally required labor records and pays your team right. This prime cost software takes the resulting labor cost, combines it with food and sales, and tells you weekly whether your prime cost is where it needs to be. Neither replaces the other, and using both means your labor is both correctly recorded and actually managed against the sales it supports.

The short answer is that you keep your payroll where it is and add this on top for the read it cannot give you. You can see exactly what the tool asks for and what it reports on the Prime Cost Tracker product page, and see the other tools an independent operator might pair with it on the small business operators page. Run payroll properly for the records the law requires, and let the tracker turn those labor totals into a weekly prime cost you can steer by.

Attributes Value
Deployment

Cloud

Platform

Web

License Type

Subscription

Billing Period

Monthly

Target Customer

Small Business & Retail

Free Trial

Yes

Reviews

Be the first to review “Prime Cost (Labor + Food %) Tracker”

Your email address will not be published. Required fields are marked *