Restaurant Inventory Count, Variance & Backup Guide

Use physical counts as verification, investigate variance, protect transaction history, and keep a recovery path.

A count is a verification event

• The physical count tells you what is actually present. The system balance tells you what should be present based on recorded changes. The difference is the variance that deserves explanation.
• Do not erase the trail by casually overwriting balances. Preserve the count, the prior balance, and the correction reason.

Investigate variance in a useful order

• Check unit-of-measure mistakes, missed receiving, transfers between locations, unrecorded waste, duplicate transactions, skipped storage areas, and count-entry errors before assuming theft or misconduct.
• If the same item or location repeats, improve the process that creates the variance rather than correcting the number forever.

Protect data integrity

• Reject impossible values such as negative balances where the workflow does not permit them, invalid costs, duplicate IDs/barcodes, orphaned location references, and malformed restore files.
• When a save or restore fails, preserve the last known valid state instead of partially applying a change.

Backup is part of closing the loop

• Create backups on a routine schedule and before major changes or upgrades. A backup is only useful if the restaurant knows where it is and can successfully restore it.
• Review & Backup is the final step of the inventory workflow because reliable records require both operational accuracy and recoverability.

Next step

Use this guide on its own, or move into Gravity Inventory Center when you need to build, record, verify, or maintain the work.