- Confirm the measurement basis
- Trace the possible movement causes
- Approve an explained resolution
A variance is a signal to investigate, not automatic proof of waste, theft or a software fault.
Illustrative decision process, not a product screenshot or customer result.When physical stock differs from the recorded balance, the restaurant needs an explanation before it needs a cleaner-looking number. The difference may involve timing, units, receiving mistakes, preparation yield, waste or an unrecorded movement. Calling every discrepancy “waste” hides useful information.
This guide provides a practical investigation order. It does not establish that Restrova calculates theoretical ingredient usage or supports every adjustment category automatically. Verify the actual records available in the proposed system.
Confirm that the quantities are comparable
Check the item identity, unit, storage locations and count time. A balance in bottles cannot be compared directly with a count in cartons. A receipt recorded after the count may also create an apparent difference if the report covers a later moment.
Resolve these basic measurement issues first. Otherwise the team may spend time investigating a loss that is actually a unit conversion or period mismatch. Retain the original count and the basis used for the comparison.
Calculate the simple expected balance
For an illustrative ingredient, opening stock is 30 kg, accepted receipts are 20 kg and recorded usage is 35 kg. With no other movements in this simplified example, expected closing stock is 15 kg. A physical count of 12 kg leaves a 3 kg difference to explain.
That calculation does not identify the cause. It also depends on what “recorded usage” includes. If authorised waste or transfers are tracked separately, incorporate them consistently and avoid subtracting the same movement twice.
Investigate distinct cause categories
| Possible cause | Evidence to inspect | Why the distinction matters |
|---|---|---|
| Timing | Count time and movement timestamps | May be a period mismatch rather than loss |
| Unit error | Pack and base-unit definitions | Can distort many records at once |
| Receiving error | Accepted quantity and supporting record | Expected goods may not have arrived |
| Waste | Approved record of discarded quantity | Identifies a specific operating event |
| Yield difference | Actual preparation output and agreed recipe basis | Usable quantity may differ from purchased quantity |
| Unrecorded movement | Staff meal, transfer or other authorised use | Missing records can look like unexplained loss |
Treat the categories as investigation prompts. The appropriate records and approval rules depend on the restaurant’s process.
Distinguish yield from waste
Yield concerns how much usable output results from a defined preparation process. Waste concerns an identified quantity discarded under the restaurant’s recordkeeping definitions. They may be related, but they should not be automatically treated as identical.
For example, a preparation process may have a documented expected output from a purchased ingredient. If actual output differs, review the measurement and process before adjusting every recipe or stock balance. Do not use an invented universal yield percentage for all kitchens.
Check recipe assumptions separately
If the proposed system calculates expected ingredient use from sales, inspect the recipe quantity, portion definition and event that triggers deduction. Then test a cancelled or corrected order. A theoretical calculation is only as useful as its configuration and recorded events.
If those capabilities are not verified, do not present a manual estimate as an automatic system result. The owner can still investigate movements using consistent receipts, counts and approved records, with the limitations stated clearly.
Keep the resolution explainable
Assign each material difference to a reviewer. Record what was checked, what was established and what remains unknown. If an adjustment is approved, link it to the reason and the relevant period.
Avoid assuming misconduct from an unexplained difference. Repeated patterns deserve investigation, but they can also reveal a persistent unit or receiving problem. The goal is an accurate operating record and an appropriate response supported by evidence.
Use findings to improve the next count
Choose a specific corrective action: clarify a pack conversion, require a receiving reference or record a transfer at both locations. Review whether that change reduces the same unexplained pattern in later counts.
Do not claim a percentage reduction in waste from this exercise unless a real measurement period and comparison support it. A worked example is not a customer outcome.
Discuss the process with Restrova
Review Restrova inventory management and the related stock demonstration. Bring the 3 kg example and your cause categories to a demo, asking which records and reports are available.
Use the weekly count guide, receiving checklist and permissions review to prepare the full workflow.
Variance questions
Is every stock shortage waste?
No. Review timing, units, receipts, transfers and other movements before assigning a cause.
Can I adjust the balance first and investigate later?
Follow the business’s approved process and preserve the original observation and explanation. An unexplained adjustment can make later review harder.
Does recipe-based deduction guarantee accurate stock?
No. Recipes, portions, recorded events and corrections must be maintained correctly, and physical checks still matter.
Related Restrova demonstration
This inventory introduction shows the starting product context for a stock discussion. Verify the particular unit, receiving, permission, counting or transfer requirements in this guide in a live demonstration.
Restrova Inventory Demo | Restaurant Inventory & Stock Management System
Restrova’s inventory demonstration introduces stock items and inventory-level monitoring for day-to-day restaurant supplies.
Watch this demonstration on YouTube · Published
Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.

