How I track food cost cleanly every day

A daily number should be practical, not performed as perfection

I track food cost daily in two layers: first as a same-day target cost based on maintained recipes and that day’s sales, and second as an actual view that I check regularly with counted stock and purchases. For daily management, that is better than pretending I can recount the entire storeroom every night without fail. If I wait for perfect precision, I usually get no reliable steering number at all. If I run the same short routine properly every day, I tend to spot pricing mistakes, portion drift, or shrinkage after two or three days instead of meeting them only at month end, when the cause is already harder to trace back to one shift or one prep habit.

Take a hypothetical bistro day. At lunch we sell 38 bowls, 24 soups, and 41 coffees, and in the evening another 19 pasta dishes. I do not want to discover only after the monthly count that the bowl margin has been slipping all week. So I treat daily food cost like a weather report: not the final annual balance sheet, but good enough to guide decisions today. The monthly inventory still matters, yet my daily figure must be fast, comparable, and honest above all. That is how I notice whether a price, a portion, or a purchase rhythm is currently moving out of line, while there is still time to correct it before the next ordering cycle.

Your recipes decide whether the daily figure is worth anything

The key preparation is not counting but recipe maintenance. If my curry is stored only as “chicken, rice, sauce,” no report will give me a usable cost basis. I therefore assign every sales-relevant ingredient with quantity and purchase cost, and for prepared components I also maintain yield. That is exactly where I use BonZumo’s recipes and base recipes: ingredients and quantities are linked to a product, while material costs and yield feed into recipe cost. That does not complete daily tracking automatically, but it gives the daily number a foundation I can actually defend when a chef, buyer, or shift lead asks why the percentage changed.

The difference is very practical. A tomato soup does not cost “around €1.20”; it may be €0.34 tomatoes, €0.09 onions, €0.12 cream, €0.05 oil and spices, plus €0.18 from a prepared vegetable base. If I maintain that structure cleanly, I can react precisely when a supplier changes one line price instead of guessing across the whole dish. A common trap is the forgotten garnish. Croutons, parmesan, herbs, lemon oil, or a spoon of crème fraîche look minor, yet at high volume they distort the daily figure quickly. Those small details decide whether my daily food cost percentage is credible enough for action or merely sounds tidy in a meeting.

I deliberately separate daily target, daily actual, and real variance

Many teams get stuck because they expect one single number to explain everything. In practice, I need three views. The daily target asks what today’s sold dishes should have cost according to recipe. The daily actual view asks what I really bought today or consumed from stock. The variance asks why those two do not match. Only that separation makes the analysis fair. Otherwise service, kitchen, and purchasing all get thrown into one pot and the result is called food cost control, even though the causes behind the number are completely different. That distinction keeps the discussion factual instead of turning a cost issue into vague blame across departments.

In my routine, the shift lead never writes down only “food cost 31 percent” but also where the figure comes from. For example, the target may sit at 28.4 percent, while same-day purchases seem to push cost to 35 percent, yet that delivery already includes stock for the weekend. Then the kitchen is not the problem; my view is. The reverse happens too: a day with very low purchasing can look healthy even while portions in production were too generous. This clearer language matters for staff fairness. People should not be held responsible for a number that actually comes from ordering rhythm, a stock build-up before Saturday, or an invoice that landed on the wrong day.

What my daily routine looks like between kitchen, stockroom, and closing

I set the same short process every day, ideally right before or right after daily closing. First, the responsible person checks which dishes, drinks, or components were especially relevant that day, such as anything involving fish, meat, avocado, cream, or fresh berries. Then only those sensitive items are counted or recorded as production usage. At the same time, I review the day’s sold quantities and compare them with recipe costs. In BonZumo, I use recipe costs from inventory management and the sales context from closing under Understand the day's activity before you close up. That gives me one operational thread instead of separate notes, memory, and loose invoices.

One extra detail matters more than many operators expect: a fixed time. If I count today at 10:10 p.m. but tomorrow not until 12:40 a.m., I compare different stock situations and create noise myself. In my example operation, the late shift counts every evening exactly after the last delivery has been put away and before any new pack is opened for the next day. That keeps the cut-off clean. A common mistake is “just topping up quickly” before counting. If tomorrow’s milk is already brought up from the cellar, today’s consumption looks artificially low. So my routine also includes a rule for when transfers, refill boxes, and freshly opened backup packs are allowed to move.

I count daily only the items where variances become expensive

A full daily stocktake makes sense in almost no restaurant. I work instead with a core list of 15 to 40 items that are expensive, shrinkage-prone, or especially high-volume. Typical examples are beef fillet, salmon, burrata, open wine, spirits, coffee, cream, frying oil, and seasonal peak items. I revise that list with the menu. In BonZumo, inventories can be recorded in a structured way by item and unit, which helps only if my team also uses the same packs and measures everywhere. If one person counts in liters and the next in bottles, or one counts opened bags while another counts kilos, we create fake variances ourselves before any real waste has even happened.

In the hypothetical bistro, I count avocados, chicken breast, burrata, and flat white beans every day. Why those four? Avocados fluctuate in purchase price, chicken drives major dishes, burrata is expensive and perishable, and coffee runs in high volume from morning to late afternoon. By contrast, I do not count dry pasta every evening, only weekly, because the variance is usually small and the effort is higher than the insight. The skill is not collecting the maximum amount of data but choosing the right bottlenecks. That is what keeps the routine feasible in roughly twelve minutes, which matters because a perfect process that takes thirty-five minutes usually stops happening after the second busy Friday.

Purchasing and stock movements must follow the same logic

Daily food cost becomes useless if deliveries, returns, and in-house prep all happen without structure beside one another. I need a clear movement path per product group: who ordered it, who accepted it, where it was stored, when it was opened, and what was transferred into production. BonZumo supports that with item data, stock movements, inventory, suppliers, and purchasing orders as one shared structure; it is not a magical automation that fixes weak habits by itself. The benefit appears only when my team consistently uses the same item names and units instead of meaning “crate of tomatoes” one day and “6-kilo tomatoes” the next, depending on who is typing or receiving the goods.

A frequent trap sits in prep work. If 8 kilograms of tomatoes are cooked into a sauce in the morning, that is not missing stock but a conversion into a base recipe. I make that intermediate step explicit so daily usage does not appear twice: once as raw goods gone and then again as sauce costed a second time. In practice, I set a short handover routine for such components. The kitchen reports produced quantity and yield, and the shift lead checks whether the figures look plausible for the batch size and planned service. That turns a plain stock movement into understandable cost information instead of a late argument about supposed shrinkage that was really just undocumented prep.

What I do with the numbers so the daily effort actually pays off

The point of daily tracking is not a pretty report but a faster decision. If my daily target cost for pasta suddenly jumps from 26 to 32 percent, I check three things first: did a purchase price change, did the portion get larger, or was an ingredient quietly substituted? If recipe costs are maintained in BonZumo, I can see faster which component is driving the shift. For the costing foundation itself, I rely on Understand what goes into every dish on your menu. The decision still remains mine as the operator, because the system gives me structure and visibility, while portion policy, plating rules, and menu pricing are management choices I have to make and explain fairly to the team.

In the example, I find that burrata pasta is not becoming more expensive because of the pasta itself, but because half burrata portions often end up plated as a full ball in practice. The right solution is not automatically a price increase. A different mise en place step may be enough: portion burrata in advance, label the tray with the target weight, and adjust the plating picture so the expected amount is visually clear. Another day may show rising coffee cost because the grinder was reset and each shot suddenly uses two grams more. That is where daily food cost control proves its value: finding small causes early, while the correction is still simple, instead of turning them into an expensive monthly surprise.