Restaurant inventory counts: zero, uncounted, and variance

Expected inventory may be calculated from the previous balance and the activity recorded since then: purchases, usage, waste, transfers, or earlier adjustments. It gives the person counting a point of comparison. It does not prove what is physically present.

Counted quantity is different. It is the amount someone actually finds during the physical count. Keeping expected and counted quantities separate makes variance visible instead of allowing the system's estimate to replace an observation.

0 means counted and found zero. Uncounted means not counted yet. If both states are stored as zero, an unfinished count can look like a confirmed empty shelf and create an incorrect adjustment.

Fictional example: tomatoes are expected at 8 cases and counted at 0 cases, so their status is Counted. Chicken breast is expected at 12 packs but has no entry, so its status is Uncounted. The tomatoes may require review; the chicken still requires a count.

Restaurants receive, store, and count products in different units: case, bag, bottle, each, pound, or ounce. A person may count two cases while inventory is maintained in pounds. That conversion is useful only when the package and unit relationship is known.

Conversions should be understandable and reviewable. Some products do not have enough information for a reliable conversion, and variable-weight products may not fit a fixed assumption. In those cases, the gap should remain visible instead of being hidden behind a precise-looking number.

A full count rarely happens in one uninterrupted pass. The team needs to see what has been counted, what remains, where work stopped, and which entries need review. Saving progress also prevents a resumed count from turning blank items into accidental zeros.

Variance is the difference between the expected quantity and the counted quantity. It is an operational signal, not an explanation by itself. A difference may point to missing activity, a unit error, spoilage, portioning, theft, or a simple counting mistake.

Large or surprising differences deserve review. Check the count entry, unit, recent purchases, waste, and other recorded activity before deciding that the inventory record should change.

A completed count should not silently rewrite inventory. The restaurant should review the variance and explicitly post the approved adjustment. That moment separates observation from the decision to change the official quantity.

After posting, the adjustment should remain linked to the physical-count event. Later, an operator can see what changed, where it came from, when it happened, and which operational action caused it. History is a trust layer, not just a log.

The initial release of Venkoi Serve is planned to include numeric count entry, visible count units and conversions, saved progress, and expected-versus-counted review. The restaurant will explicitly post the reviewed adjustment, and insufficient conversion information will remain visible.