Food cost

Restaurant Staff Meals and Prep Waste: How to Track and Cost Both

Curran Dye

September 23, 2026

Staff meals and prep waste inflating restaurant food cost, reported 34 percent versus a tracked 30 percent, on a Supy preview

Where Staff Meals and Prep Waste Actually Go

Staff meals and prep waste are stock that leaves the kitchen with no sale behind it. A staff meal is ingredients the team eats. Prep waste is the trim, offcuts and spoilage lost while getting product ready to serve.

Neither shows up as revenue. If you do not record them, the system never depletes the stock they used. That missing stock surfaces later as unexplained variance. It makes food cost look worse than the kitchen really ran.

This is why they matter more than their size suggests. Take an example kitchen buying $60,000 of food a month. Staff meals near 3% and prep and trim waste near 2% add up to about $3,000 of stock a month. Untracked, that $3,000 does not vanish. It lands in food cost as a mystery gap. A kitchen genuinely running at 30% can report 34%. The team then hunts a problem that is really just unlogged movement.

Two untracked leaks in an example kitchen: staff meals $1,800 and prep and trim waste $1,200 add up to $3,000 a month landing in food cost

Stop the Staff Button From Hiding Meal Costs

The most common way staff meals go missing is the flat-fee staff button on the till. It is rung as a fixed-price "staff meal" with no link to specific menu items. So it records a sale value but never tells the inventory system which ingredients were used. Stock is never depleted for what the team ate. Do that a few times a day across sites and the on-hand figures drift from reality.

There are two clean fixes, and both keep the stock ledger honest. First, ring staff meals through the till as the actual menu items the team ate. The point-of-sale link then depletes the right ingredients automatically. Second, where a meal is not a menu item, log it as a wastage entry against a dedicated staff-meal category. The ingredients still come out of stock. You can also switch on the setting that auto-converts a voided or cancelled ticket into a wastage record. A comped or cancelled staff order is then captured and costed with no re-keying.

How the staff meal is recorded	Does stock deplete?	Effect on food cost
Flat-fee staff button	No	Understates stock, inflates variance
Actual menu items through the till	Yes, automatically	Correct stock, cost sits in food cost
Staff-meal wastage category	Yes	Correct stock, separated from food cost

Log Prep and Trim Waste by Item, Not by Guess

Prep waste needs the same discipline. Record it the moment it happens, not at month-end. Log each loss by item, quantity, reason and waste type in seconds on mobile or desktop. Each entry deducts from stock and costs the loss at that day's ingredient price. It then feeds a live cost-impact breakdown by branch, period and category. Recipe-level losses decompose to their ingredients. A wasted batch deducts each component in proportion, not as one vague write-off. You can also attach a photo of spoiled goods before discarding them. Our guide to restaurant food waste tracking covers the wider setup.

One setup step comes first. Skipping it is how prep waste stays invisible. An item can only be wasted against if it exists in the catalog. So build your item master and prep recipes before the team logs against them. One operator generated significant waste during a tasting of more than forty new dishes. They could not record any of it, because the new ingredients had not been created yet. For recurring losses like daily trim, clone a previous wastage record to a new date. That removes the friction that makes people stop logging.

Four steps to log a prep or trim loss: pick the item, enter the quantity, choose the reason and waste type, and stock deducts and costs itself at the day's price

Keep Staff Meals Out of Your Food Cost Percentage

Logging staff meals fixes your stock counts. It also forces one decision about your food cost percentage. Is a staff meal a cost of selling food, or a staff benefit? Kept inside cost of goods sold, staff meals inflate the food cost percentage you report. Tagged to a dedicated staff-meal category or wastage-type expense flag, the usage still comes out of stock. But the cost is separated from cost of goods sold. Your food cost percentage then reflects what you actually sold. That single choice makes the cost appear in or vanish from food cost. Make it deliberately, not by accident.

Custom categories make this practical across a group. Two categories, Sales and Complimentary, are built in and fixed. Every other reason category you can add, rename or hide. So staff meals, prep, trim and spoilage each get their own line. Each line matches your own cost-centre breakdown. Read the cost-impact-by-category report and you see where staff meals and prep waste actually go. The report splits it by site and by period. They stop hiding as one unexplained lump in the food cost gap. Note one thing. A dedicated staff-meal cost centre is a common request, not a single named button. The mechanism above is how operators do it today, with categories that already exist.

Where you put staff meals decides food cost percentage: inside cost of goods sold reports 34%, in their own category reports 30%, a 4-point gap

Put a number on it before you change anything. Take a month of food purchases. Estimate the share going to staff meals and prep waste, then price it. In the $60,000 example, 5% is about $3,000 a month you cannot currently see. Then compare your reported food cost percentage against your own target for the site, not an industry average. Treat any gap wider than about 2 points as worth investigating. The example kitchen shows a 4-point gap, between a real 30% and a reported 34%. That is exactly what unlogged staff meals and prep waste create. Start logging both this week and tag them to their own categories. The gap either closes or points you at the next real problem.

Book a Demo with Supy - track staff meals and prep waste and see the cost by site

Get weekly insights and tips delivered straight to your inbox.

Ready to optimize your restaurant operations?

Book a demo



Blog

Our operational insights





No items found.

Your questions  answered

Everything you need to know about Supy — from setup to integrations, pricing, and daily use. If it’s not covered here, just ask.

How do I track staff meals in a restaurant inventory system?

Track a staff meal the same way you track a sale: by the ingredients it used. The cleanest method is to ring the meal through your point of sale as the actual menu items the team ate, so the system depletes the right stock automatically. Where the meal is not a menu item, log it as a wastage entry against a dedicated staff-meal category instead. Either way the ingredients come out of stock and get costed. Avoid a flat-fee staff button that records only a price, because it never tells inventory which items were used.

Why do staff meals make my food cost percentage look higher?

Staff meals raise your food cost percentage when their ingredient cost sits inside cost of goods sold but the meals produced no sale. You are dividing more cost by the same revenue, so the percentage climbs. The fix is a decision about where the cost belongs. If you treat staff meals as a staff benefit, tag them to their own category or a wastage-type expense flag, so the stock still depletes but the cost is separated from cost of goods sold. Your food cost percentage then reflects only what you actually sold to paying customers.

What is the difference between logging a staff meal as a sale and as wastage?

Both methods remove the ingredients from stock, but they land in different places on your reports. Logging the meal as a sale through the point of sale depletes stock and books it like any order, which suits meals that map to real menu items. Logging it as wastage against a staff-meal category also depletes stock, but records it as a non-sale loss you can separate from cost of goods sold. Choose the sale route when the meal is a menu item, and the wastage route when it is an off-menu plate or you want it kept out of food cost.

How do I stop the flat-fee staff button from causing inventory errors?

Replace the flat-fee staff button with a method that names the ingredients used. Ring staff meals as the specific menu items the team ate, so the point-of-sale link depletes the correct stock, or log the meal as a wastage entry against a staff-meal category. Both keep on-hand quantities accurate. If your till still uses a fixed-price staff button, switch on the setting that auto-converts voided or cancelled tickets into wastage, so those transactions are captured and costed automatically. The goal is simple: every staff meal should move real stock, not just record a price.

Can prep and trim waste be logged by item and costed automatically?

Yes. Log each prep or trim loss by item, quantity, reason and waste type in seconds from mobile or desktop. Each entry deducts the item from stock and costs the loss at that day's ingredient price, then feeds a cost-impact breakdown by branch, period and category. Recipe-level losses decompose to their ingredients, so a wasted batch deducts each component in proportion rather than as a single write-off. You can attach a photo of spoiled goods as evidence, and clone a recurring loss like daily trim to a new date instead of re-entering the same lines.

Should staff meals be included in cost of goods sold?

That is a policy choice, and both approaches are valid as long as you are consistent. Some operators keep staff meals inside cost of goods sold because the food genuinely left the kitchen. Others treat them as a staff benefit and separate the cost, so their food cost percentage measures only paying sales. What matters is that the stock is always depleted, so your counts stay accurate, and that you decide the treatment deliberately. Tagging staff meals to their own category lets you report either way from the same data, and see the cost by site and period.

What setup do I need before my team can log prep waste?

The main prerequisite is that every item exists in your catalog, because you can only record waste against an item the system already knows. Build your item master and prep recipes first, including semi-finished items, so batches can decompose to their ingredients. Set up the wastage reason categories you want, such as staff meals, trim and spoilage, so each loss lands on the right line. One operator could not log any waste from a forty-dish tasting, because the new ingredients had not been created yet. Create the items, then the logging takes seconds.