Restaurant Food Cost Creeping Up? These Are the Four Leaks

Food cost rarely explodes. It crawls.

January it was 31%. March, 33%. By June it is somehow 37% — and there is no single event you can point at. The menu did not change, the suppliers are the same, the kitchen looks normal. But on monthly sales of Rp150 million, that 6% gap is Rp9 million evaporating every month. Over a year, more than Rp100 million — a renovation, or two full salaries.

Food cost is hard to control precisely because the leak is never one big hole. It is four small ones, all dripping at once.

Leak one: portions that drift

The recipe says 120 grams of chicken per serving. Reality in the kitchen: the senior cook plates 130 because he feels generous, the new hire plates 140 because she has not memorized it yet, and during the rush everyone eyeballs everything. Fifteen extra grams per plate sounds trivial — until you multiply by 200 plates a day.

The cure is boring but effective: written recipes with gram weights, a scale at the prep station, and random portion spot-checks once a week. Not daily — random is enough, as long as the kitchen knows a check can happen any time.

Here is the part most owners miss: portion drift shows up in no report at all unless you compare theoretical ingredient usage against actual usage. If your POS stores a recipe per menu item, every sale automatically computes what should have been consumed. Set that against the physical stock count at month end, and the gap is your drift plus waste plus shrinkage — quantified. Without the theoretical number, you are only guessing.

Leak two: waste nobody writes down

Tomatoes rot, rice burns and gets redone, a wrong order becomes staff lunch. All of it is normal. What is not normal is leaving it unrecorded, because unlogged waste blends into every other leak and can never be analyzed.

One simple sheet in the kitchen is enough: date, ingredient, quantity, reason. Tally it weekly. The pattern usually appears within two weeks — vegetables always spoiling on Mondays because Saturday’s shopping was oversized, or one particular dish getting remade too often. Then the decision is easy: shift the buying schedule, retrain one recipe.

Prep scraps count too. Chicken skin, bones, vegetable stems — kitchens that turn them into stock or staff meals cut waste with almost no effort.

Leak three: ingredient prices that rise quietly

Chili tripling before a festive season — everyone sees that coming. The dangerous ones are the unannounced small hikes: cooking oil up 5%, eggs up 8%, chicken up a few cents per kilo. Suppliers rarely send a formal notice; the invoice just slowly reads different.

If purchases live in a system rather than a shoebox of receipts, you can see the price trend per ingredient per supplier. Two immediate payoffs: you catch which supplier is quietly raising prices and can negotiate or compare, and you catch which menu items no longer make sense because their key ingredient keeps climbing. Those dishes are candidates for a price bump or a redesign — for how to decide which dishes deserve to stay, see menu engineering to lift profit.

Leak four: the one nobody likes talking about

Small theft. Not someone running off with the safe — a pack of cigarettes from the display, two liters of oil going home, a sale rung up nowhere with the cash pocketed. In most restaurants this is less about bad employees than about wide open opportunity: stock is never counted, cashiers can void transactions without a trace, the drawer is never reconciled.

You close this leak not by suspecting everyone but by making deviations visible: every void and discount logged with who and when, the drawer counted at every shift change, rotating stock takes by category instead of one giant annual count. On a modern POS like Tenavora, that audit trail is automatic — voids, discounts, and cash variances surface on their own, before suspicion ever has to.

The routine that makes it stick

The four leaks share one property: none can be patched once and forgotten. What works is rhythm.

• Daily: reconcile the drawer per shift, log kitchen waste.
• Weekly: spot-check portions, tally waste, glance at purchase prices that moved.
• Monthly: stock take, theoretical vs actual usage, real food cost per menu category.

It sounds like a lot, but once sales, recipes, and purchasing sit in one system, the monthly recap is an hour of work, not a week.

Start with a single number: this month’s actual food cost, computed honestly. This is where many owners get a shock — they assumed 30% and find 38%. The shock is useful. From next month on, every percentage point you claw back has a visible price tag.