Skip to main content
A stock count compares what you physically have against what Bumara says you have, and corrects the difference. It is the discipline that keeps your inventory records worth trusting.

Types of count

Cycle counting is usually the better discipline. Counting a few items each week catches problems early and avoids the disruption of shutting down for a full count.

Running a count

1

Create the count

Inventory → Counts → New count. Select the location and the type.
2

Choose the items

A full count includes everything at that location automatically. A partial or cycle count needs you to select the items.
3

Start the count

Bumara takes a snapshot of the current system quantities. From this moment, the count is measured against that snapshot.
4

Count physically

Go and count. Enter quantities as you go, by typing or by scanning.
5

Complete the count

Every item must have a counted quantity. Variances are calculated.
6

Review the variances

Before posting anything. See below.
7

Post the count

Balances are corrected to what you counted, and variance movements are recorded.

Entering counts

By scanning

Scan an item’s barcode and its counted quantity increases by one. Scan five units, get five. Rapid scans are batched, so scanning quickly gives the right total. The row you scanned is highlighted briefly and the grid scrolls to it, so you can see what registered. Only items with a barcode can be scanned. See Scanning.

By typing

Type quantities directly into the grid. Tab or Enter moves to the next row. Entries save automatically as you go, and there is a save button if you want to force it.

Reviewing variances

This is the part that matters. Do it before posting.
1

Sort by variance size

Largest first, by value rather than by quantity.
2

Recount anything large

Big variances are recount candidates before they are investigation candidates. Miscounts are more common than theft.
3

Look for pattern

Everything in one category short? Everything in one aisle over? A pattern points at a process problem rather than an item problem.
4

Check for pending operations

An unposted transfer or a draft adjustment explains a variance without any mystery.
5

Investigate what is left

Genuine unexplained losses need attention beyond the count.
Posting a count writes off every variance in it. Do not post a count with large unexplained differences — you are recording a loss without understanding it, and the underlying cause carries on.

Count statuses

What posting does

1

Variance movements are created

One per item with a non-zero variance. Zero variances produce no movement.
2

Balances are set to the counted quantity

Exactly what you counted becomes the new balance.
3

The count is sealed

It cannot be edited afterwards, only voided.

Practical advice

Before opening or after closing. Counting during trading gives you a number that was never true at any single moment.
Two counts running at the same location produce conflicting snapshots. Bumara allows it but warns you — take the warning.
Shelf by shelf, aisle by aisle. Wandering means missing things and counting others twice.
One counts, one records. Materially fewer errors than one person doing both.
A count posted a week later has been overtaken by a week of trading, and the variances no longer mean what they meant on the day.

How often

Voiding a count

An administrator can void a posted count. This reverses the variance movements and returns balances to what they were before. The count stays visible, marked void. Void only when the count itself was wrong — counted at the wrong location, or entered against the wrong items. If the count was right but you subsequently discovered why the variance occurred, that is an adjustment, not a void.
Related: Scanning for barcode entry during counts, and Adjustments.
Last modified on August 4, 2026