Detecting inventory loss: theoretical vs actual usage and ticket controls

Theft, waste and portioning leave the same footprint

Owners who suspect skimming usually start from a feeling: protein disappears faster than sales justify, or the bar's numbers drift. The difficulty is that several innocent causes produce exactly the same shortage on an inventory sheet. A cook who portions six and a half ounces instead of six, a case of greens thrown out without a waste-log entry, a family meal nobody rang in and a short delivery that was signed for as complete all look identical to product walking out the back door.

That overlap is why the most useful advice in owner discussions is about measurement and culture rather than cameras alone. In an r/restaurantowners thread on preventing skimming, commenters recommended reconciling theoretical inventory against physical counts weekly, ringing up everything including owner and staff meals, using clear trash bags, keeping key control and randomly checking portions; others warned against treating the whole team as suspects (Reddit discussion). Those are recorded excerpts of operators' opinions, not studies, but they point in the direction this article develops: separate the causes before naming a culprit.

Building a theoretical versus actual report for the items that matter

Theoretical usage is what you should have used: units of each menu item sold, from the POS product mix, multiplied by the recipe quantity of each ingredient. Actual usage is what you did use: beginning inventory plus purchases received minus ending inventory. The difference is variance. You do not need to do this for every ingredient. Start with five to ten high-cost or easy-to-remove items, such as proteins, liquor, wine and anything sold by the portion.

The report is only as good as its inputs. Recipes must reflect the quantity as purchased, or the report must account for trim and cooking yield. Purchases must be the quantities actually received, not invoiced. Counts must use consistent units and be taken at the same point in the week. And every item that leaves the kitchen must appear in sales somewhere, which is why the ring-everything policy below is part of the measurement system, not just a rule.

Counting weekly rather than monthly narrows the window in which a problem can hide and makes causes easier to recall. Commenters in the thread above attributed a claim about the cost savings of weekly reconciliation to a named restaurant accountant; that figure is secondhand and is not used here.

Worked example: chicken breast variance at a bar and grill

Hypothetical example, for illustration only. In one week the POS shows 410 chicken sandwiches at 6 ounces of raw chicken breast each and 120 chicken salads at 4 ounces each. Theoretical usage is 2,460 ounces plus 480 ounces, which is 153.75 pounds plus 30 pounds, or 183.75 pounds. The count shows 80 pounds on hand at the start, 200 pounds received and 70 pounds at the end, so actual usage is 210 pounds. Variance is 26.25 pounds, about 14.3 percent of theoretical. At an assumed $3.20 a pound, that is $84 for the week.

Now remove explainable causes. The waste log records 6 pounds of chicken discarded, leaving 20.25 pounds. Random portion weighing during two services shows sandwiches averaging 6.5 ounces instead of 6; across 410 sandwiches that extra half ounce is 205 ounces, about 12.81 pounds, leaving about 7.44 pounds unexplained. The manager then checks whether staff meals and comps containing chicken were rung, and finds several were not. Only after portioning is corrected and every meal is rung does the next week's report show whether any meaningful unexplained variance remains. In this example, portioning explained nearly half the variance (about 12.81 of 26.25 pounds) and logged waste another 6 pounds, so about 18.81 of 26.25 pounds, roughly 72 percent, had an operational explanation before anyone's honesty was in question.

Ring everything: making the POS a complete record

A theoretical report cannot see food that never touched the POS. That is why the practice of ringing every item, even if it is then discounted to zero, matters so much. In the same skimming thread, a highly upvoted commenter described feeding staff, ringing up everything including the owner's own meal, and allowing managers to comp when it benefits the business, so that waste and theft show up in inventory and product mix each week (Reddit discussion).

Set up the POS so comps, staff meals, spills, remakes and manager discounts each have their own reason code, and require a manager approval for each. That gives every item a ticket and turns the comp report into a useful document instead of a black hole. Providing a staff meal deliberately also removes one of the most common, and most understandable, sources of unrecorded usage.

• No food or drink leaves the kitchen or bar without a ticket, including owner, family and staff meals.
• Separate POS reason codes for comps, staff meals, remakes, spills and manager discounts.
• Manager approval required for comps and voids, logged with name and time.
• Waste log at each station, filled in when product is discarded, not reconstructed at close.
• Clear trash liners in prep areas and controlled access to high-value storage.
• Numbered keys or codes assigned to individuals, with access reviewed when staff change.

Reading cash tickets, voids and discounts for patterns

Inventory variance tells you something is missing; ticket data can tell you where. Look for patterns tied to the same employee, shift or tender type: cash tickets that consistently lack items commonly ordered together, voids or item deletions made after a check was printed or paid, checks reopened and closed for lower amounts, discounts applied mostly to cash payments, and frequent no-sale drawer openings.

In a widely upvoted r/restaurantowners post, an owner described noticing that one server's cash tickets lacked drink charges and then using unannounced test purchases to confirm whether drinks were being rung (Reddit discussion). That account is one owner's self-report from a recorded excerpt. It illustrates a sound principle: a data pattern is a reason to verify, not a conclusion. Test purchases, if used, should be part of a consistent, documented quality-and-controls program applied to all staff, and any employment action based on them should be reviewed with an employment lawyer or HR advisor familiar with your jurisdiction.

Investigating fairly once the explainable causes are gone

If variance persists after portioning, waste logging, receiving checks and ring-everything are in place, treat what remains as a question to investigate, not an accusation to make. Write down the pattern, the dates, the reports that show it and what has already been ruled out. Widen data before narrowing on a person: does the pattern follow one employee across shifts and stations, or one station regardless of who works it?

Cameras can help confirm or rule out a specific pattern at a specific time, but as commenters in the skimming thread noted, footage without a timestamped question to answer is rarely useful. Keep conversations with staff factual and private, let the employee explain, and record what was said. Rules on workplace recording, final pay, deductions and termination vary by jurisdiction; get advice before acting on suspected theft, and report suspected crimes to the police rather than attempting to recover money informally. Wrongly accusing an employee damages the team and can create legal exposure for the business.

Failure modes that hide the real cause

The most common failure is a report built on wrong recipes, such as using cooked weights for raw purchases, which produces a permanent variance that looks like theft. The second is inconsistent counting, where one manager counts open cases and another does not. The third is reacting to one bad week. Variance should be tracked over several weeks so a single delivery error or catering event does not trigger a confrontation.

Another failure is relying on controls without culture. Commenters in a separate owner thread described checking inventory and sales reports carefully while admitting there are not enough hours to investigate every discrepancy (Reddit discussion). That limit is real. Focus investigation time on the few items with the largest dollar variance and let routine controls handle the rest.

Weekly variance checklist and records to keep

This is an operational routine, not a legal standard. Keep its records together so trends and decisions can be explained later.

• Count the same five to ten high-value items at the same time each week, in consistent units.
• Pull POS product mix and calculate theoretical usage from current, yield-adjusted recipes.
• Calculate actual usage from counts and received quantities; record variance in units and dollars.
• Subtract logged waste; run random portion checks on items with high variance.
• Review comp, void, discount and no-sale reports by employee and tender type.
• Note what was ruled out each week and what changed in process.
• Escalate persistent, unexplained patterns to a documented review with HR or legal advice.