Restaurant Theft: How to Identify Losses Using Data
Contents
- How to detect restaurant theft by tracking ingredient usage
- Which data signals to check first
- Why write-offs without documentation hide losses
- Which receipt voids and discounts you need to check
- How to run an inventory audit you can trust
- What a variance audit looks like using a hypothetical example
- What analytics misses with product mismatches and unrecorded transactions
- What to automate for cash register and inventory control
- What to do after discovering a shortage
- Frequently asked questions
Suppose you run an inventory count and milk comes up short. The chef blames a miscount, while the floor manager attributes discounts to regular guests. You suspect restaurant theft, but so far you only see inventory discrepancies and disputed transactions. Where do you start your audit to reconstruct what happened?
We examine POS records, inventory, and write-offs. You will get a reconciliation procedure, a table of red flags, and an example of how to investigate a shortage. Numbers help you decide what to check. On their own, they do not prove an employee's guilt. Drawing conclusions requires source documents and an investigation of the specific event.
In brief:
- Calculate usage based on recipe cards and compare it to actual consumption from balances and inventory movements.
- Back up write-offs with documentation, and check units of measurement, yields, and document dates.
- Match voids, discounts, and partial receipts against inventory usage and payment confirmations.
- Supplement scheduled inventory counts with unannounced spot audits.
- Assign an owner to every unresolved discrepancy and verify the outcome once the root cause is fixed.
How to detect restaurant theft by tracking ingredient usage
Start with a single product and a closed period. Compare the recipe card standard against actual usage. The standard tells you how much should have been used for registered sales. Inventory balances and movements show the total stock removed. Gather supporting documents for non-sale usage separately.
Calculate theoretical usage. Multiply the number of portions sold by the ingredient quantity in the active recipe card. For past sales, use the recipe version from that period. Check modifiers and substitutions if they affect usage and appear in the available data. Confirm the calculations with the kitchen.
Calculate actual usage. Add receipts and incoming transfers to the starting inventory balance. Subtract the ending balance, vendor returns, and outgoing transfers. Convert packages, kilograms, and portions into consistent units of measurement. Save the conversion factors so the manager can replicate the audit.
Account for non-sale usage. Collect waste logs for spoilage, menu testing, staff meals, and other approved reasons. These amounts are already reflected in total inventory usage. Display them separately when comparing against theoretical standards. Adding them to actual usage a second time will inflate your consumption numbers.
For any remaining discrepancy, check prep yields, invoice dates, inventory counts, and undocumented usage. Record every explanation you find along with its documentation. Formulas in currency and percentages are explained in the guide on how to calculate food cost.
Which data signals to check first
Use this table as a working checklist for the manager. Select an event, inspect the source data, and record the audit findings. For recurring variances, compare different periods and operating conditions. This helps you move from an aggregate loss total to specific operational events.
| Data signal | What could be behind it | What to check |
|---|---|---|
| Actual usage exceeds theoretical standards | Errors in prep yield or units, or undocumented usage | The recipe card, balances, stock movements, and write-off logs for the same period |
| Inventory shortages without write-off logs | Staff meals, menu photo shoots, or recipe testing without documentation | The reason for issue, product, quantity, and responsible employee |
| Recurring spoilage of the same product | Overpurchasing or storage issues | Purchases, stock balances, reasons, and timing of write-off filings |
| Receipt voided after payment | Guest refund or an unauthorized cancellation | Original receipt, payment receipt, timestamp, void reason, and refund record |
| Only part of the order was entered into the POS | Some served items bypassed registration | Order composition, receipt line items, and fulfillment confirmation |
| Discounts are applied frequently | Promotional terms or unauthorized discounts for personal benefit | Justification, discount amount, timestamp, and manager approval |
| Food cost for a single category spiked sharply | Higher raw ingredient prices, recipe changes, write-offs, or product mismatches | Ingredient valuation, recipe cards, yields, and write-offs for the category |
| Category totals appear balanced, but individual product stock levels diverge | A premium product is served under the name of a cheaper one | Stock balances for specific items and actual kitchen prep |
Why write-offs without documentation hide losses
If ingredients were used for staff meals, menu shoots, or recipe testing, log a document. Without it, you will face a shortage and have to reconstruct events based on staff recollections. Auditing usage history is much easier when the justification is recorded at the moment of consumption.
Establish a clear logging procedure. Include the following details in each document:
- Reason for disposal.
- Product and quantity.
- Date.
- Responsible person.
- Approval in line with restaurant policy.
Agree on when the chef logs usage during peak kitchen hours. Set a clear deadline and check compliance. This allows the manager to link ingredient usage to a specific shift and document while the staff still remembers the circumstances.
Analyze the breakdown of write-offs. If the same product spoils repeatedly, examine purchasing volumes and storage conditions. For end-of-shift write-offs, review the stated reason and entry timestamp. After introducing the procedure, documented write-offs may increase. Compare how much of your previously unaccounted-for usage now has proper paperwork.
Require prompt logging and explanations. A rigid goal of "zero write-offs" can encourage staff to conceal spoilage or delay filing reports. Use verified causes to decide how to adjust purchasing, storage, and recipes. Then evaluate the outcome during the next period.
Which receipt voids and discounts you need to check
Check partial order entries, voids after payment, and discounts applied for personal benefit. Such schemes are described in Kontur.Market's review. Reconstruct the sequence of events, including the operational rationale for each action. Analysis of cash register fraud in food service
Void after payment. Retain the original receipt, payment details, void timestamp, and reason. Verify confirmation of the guest refund and check how it was recorded in accounting. To track cash movement accurately, match the entire history against the POS register log.
Partial receipt entry. Compare order items, receipt lines, and available fulfillment records. The sales report shows what was officially registered. To verify the remaining items, you will need the original order details and actual dispatch records. Keep them alongside your reconciliation results.
Recurring discounts. Check the justification, amount, time, and approval. Consider promotion rules and order items. When comparing employees, choose comparable conditions. An employee working during promotion days may have more discount transactions for legitimate operational reasons.
Kaspi payments. Match receipts against confirmed incoming payments using your standard process. Check settlement dates and refunds. Log every discrepancy with the source document, inquiry, response, and review outcome. That way, you can address recurring variances using accounting data.
Request available event logs, permissions, and export granularity from your iiko, r_keeper, or other system vendor once. Include POS event history and delivery data in your request. After reviewing a sample, determine which operations you can audit and automate.
How to conduct an inventory audit you can trust
Close all documents first. Close all checks at the register, post write-offs, and process supplier invoices. If a product was physically received but the receipt is not yet in accounting, fix this gap before analyzing kitchen usage. This procedure is described in the inventory article. First inventory count breakdown
- Record the exact time. Record the moment of the count and the operations included in the period. Track ongoing stock movement separately according to an agreed rule.
- Check units and storage locations. Count products in all designated storage areas. Account for prep items separately. Record how you count open packages.
- Preserve original values. Keep the revision history when recounting. Specify what was updated, on what basis, and how it changed the result.
- Analyze stock movements. Find missing receipts, transfers, write-offs, and duplicates. Record the explained portion of the variance and open questions separately.
- Repeat the check. Supplement scheduled inventory counts with surprise spot checks of problem item groups. Check whether discrepancies persist after corrections.
Apply a uniform procedure to comparable locations. For example, a cafe in Almaty counts milk by the carton, while a coffee shop in Astana tracks the volume of opened containers. Agree on the method first. Consider rent and staffing when evaluating overall location performance, but compare identical units and time periods to reconcile milk.
What variance verification looks like using a hypothetical example
Suppose a coffee shop was expected to use 40 liters of milk in a week based on sales and recipe cards. Based on stock balances and incoming shipments, actual consumption was 50 liters. All numbers in this example are hypothetical and rounded to explain the verification procedure.
The initial variance is 10 liters. Locate documentation for non-sale inventory reductions. In this example, there are write-off records for 4 liters used for staff meals and recipe tastings. These quantities are already part of the actual 50 liters. Accounting for them leaves 6 liters of unexplained consumption.
During the check, the manager finds a 2-liter counting error in open packages. After a confirmed correction, actual consumption is 48 liters. The unresolved variance is 4 liters. The calculation looks like this.
48 minus 40 minus 4 = 4 liters.
Check actual drink preparation against recipe cards, milk substitutions, and internal transfers. Align the time period with POS events. For shifts, account for differences in guest volume and responsibilities, then review specific transactions with the responsible staff.
Record action items based on the audit results.
- Clarify the method for counting open packages.
- Verify recipes and usage during preparation.
- Conduct a follow-up audit.
In the next period, check whether the variance persists. Compare original data with post-correction documents. For any remaining difference, record what confirmation is still missing and who will continue the review.
What analytics misses during stock mismatches and off-the-books transactions
When stock mismatches occur, check specific products. An expensive ingredient might be dispensed under the name of a cheaper one. The portion count and POS total will still appear consistent. Compare detailed stock balances with actual preparation. The overall kitchen total can conceal discrepancies between individual items.
Selling personal goods through the venue and settling personal orders with surplus inventory leave few traces. Tracking products and money that bypassed accounting requires additional data. Use dispatch controls, source documents, and surveillance cameras within your established audit procedure.
For delivery, reconstruct history across available systems. Match Wolt, Glovo, and Yandex Eda orders against POS data and settlement documents. Verify cancellations alongside payments, order handoffs, and all other available events. Record any history gaps that prevent completing the reconciliation.
When check counts drop and complaints appear on 2GIS, inspect service quality. To investigate product shortages, look for a concrete link to operations. Discuss with the manager which data relates to consumption and which explains guest behavior. This keeps your investigation focused.
What to automate for POS and inventory control
Check data completeness first. Make sure all days were exported, duplicates are absent, and products are mapped. If a file is missing, display the source status. After restoring the data, rerun the calculation and only then send the discrepancy for review.
- Daily POS events. Collect available cancellations, refunds, and discounts along with their reasons and source documents. Align the alert threshold with your venue format and operating conditions.
- Usage of problem items. Connect sales, recipe cards, inventory, and write-off records. Show standard usage, documented disposals, and the remaining variance. Label the calculation as preliminary until documents are closed.
- Documentation timing. Highlight documents entered after period close and retroactive changes. Save the reason for recalculation so the manager can explain changes in the totals.
- Investigation tasks. For each alert, assign an owner, a deadline, and a review outcome. During review meetings, close explained events and check open questions.
Choose the right tool to reconcile available documents from your POS and 1C. You can start with a spreadsheet or a POS report. The frequency of reconciliation and the volume of manual work will indicate when you need a dedicated system.
Selection criteria are detailed in our comparison of analytics tools. The overall metric framework is in the restaurant analytics guide.
What to do after discovering a shortage
Preserve the source data. Record the report generation time, save data exports and documents. Grant access to review participants. Discuss specific transactions with responsible staff routinely, keeping records for follow-up reconciliation.
Verify that all records are complete and recalculate. Ask the employee about the transaction. What was the justification for the write-off? Where is the refund confirmation? Which recipe was active? Compare the response with documentation and recount if necessary.
Separate established facts from assumptions. Correct unit-of-measure errors in the counting rule. Process missing write-off documents according to your standard procedure. Escalate recurring violations to management for further review. Preserve the justification for every adjustment and the updated total.
Adjust the workflow that allowed the situation to occur. Check discount approvals, cancellation permissions, product dispensing, and shift closeouts. Evaluate the results in the next period. Decisions about payroll deductions and liability require an established review procedure and verified evidence.
Frequently asked questions
How to detect restaurant theft on your own?
Choose a closed period and a problem product. Check balances, receipts, and units of measurement. Calculate usage from recipe cards, factor in write-off logs, and find the remaining discrepancy. Compare it against voids, discounts, and payments. Repeat with a control recount and record the verified causes.
What should you do if actual usage exceeds theoretical standards?
Check balances, stock movements, recipe cards, and non-sale disposals. Keep supporting documentation for every explanation. Calculate the unexplained discrepancy and run another check on the product. Then review preparation and order handoff together with the responsible staff.
How often should you conduct a control inventory count?
Choose a scheduled frequency based on products, turnover, and accounting workflow. Supplement it with unannounced spot counts for high-risk categories. Use the same procedure each time and close all documents before reconciliation. That way, you can compare results across periods.
Can you see voids and discounts in iiko or r_keeper?
Check available reports, change logs, and permissions in your system setup. To investigate, you need events with timestamps and stated reasons. Review a sample export to see what data you already get and what you need to track separately in your workflow.
Should you track losses in products or in tenge?
First, calculate quantities in comparable units. This lets you verify physical usage separately from purchase costs. Then convert the verified discrepancy into tenge using an agreed-upon formula and prioritize what to audit next.
