Physical stock taking and cycle counting — annual, quarterly, perpetual

What physical stock taking is

Physical stock taking is counting what is actually on the shelf and comparing it against the book quantity the system carries. For each item — or each lot, where batch control applies — at a location, the count records the system quantity, the physically counted quantity, and therefore the variance between them. In a well-designed inventory system the count records that variance only: correcting the book is a second, separate step done through a stock adjustment.

Counting is the feedback loop of stock control. Every other discipline — reorder alerts, valuation, promising stock to a customer — assumes the book quantity is right. The count is how you find out whether it is, and by how much it is not.

The three count types — annual, quarterly, perpetual

Fast Inventory Software's physical stock taking supports three count types, which between them cover how real businesses count:

These are complements, not competitors. The mature pattern is perpetual cycle counting through the year — so accuracy is maintained and problems surface within weeks of appearing — plus the annual count the statute and the auditor expect. A store that counts only annually discovers in March what went wrong in June, nine months too late to find the cause.

The variance-only principle

The single most important design property of a stock-taking module is what happens when the count is saved. There are two schools:

• The wrong one: saving the count sets stock to the counted figure. Fast to operate — and fatal to control. A double-scanned carton or a missed rack corrupts the balance with no trace; there is no variance record to investigate, no approval step, and no distinction between "counted wrong" and "book was wrong."
• The right one: saving the count records system quantity, physical quantity and variance — and nothing else. Stock is untouched. Reconciliation happens through a separate adjust-increase or adjust-decrease document, each posting its own row in the immutable stock ledger.

Fast Inventory is built on the second model, and it is worth insisting on when evaluating any system: counting and correcting are different acts, done by different people, at different times, each leaving its own record. The variance sheet becomes a management report in its own right — accuracy by location, by counter, by item class — instead of vanishing into silently rewritten balances. The pillar guide places this rule inside the wider stock-commit principle: stock changes only at documented commit points, and a count is not one of them.

The count procedure, step by step

Investigating and reconciling variances

The discipline after the count matters as much as the count itself. The rule: investigate first, adjust second. A large share of variances are process errors, not physical losses — and a process error is fixed by posting the missing document, not by adjusting:

• An unposted movement. The receipt sits on a desk; the issue went out on a verbal okay. Post the document and the variance disappears the honest way.
• Stock in the wrong place. The quantity exists — in another store or bin. That is a stock transfer, net zero, not a loss and a gain.
• A counting error. Recount before you adjust — especially when the variance is suspiciously round or suspiciously large.
• A genuine physical difference. Damage, spillage, theft, historical error — only this category earns an adjustment, posted with a reason and, for meaningful values, an approval. The stock adjustment guide covers that flow in depth.

Scheduling cycle counts with ABC

Cycle counting needs a schedule, and ABC analysis supplies it. Count A items — the small set carrying most of the inventory value — most often, monthly in many operations; B items quarterly; C items once or twice a year. The arithmetic is persuasive: a store with 2,000 items might have 150 A items, and counting seven or eight of them per working day covers the whole A class every month with one person-hour a day. Layer on event-driven counts — negative balances, empty-bin reports, variances on neighbouring items — and accuracy problems get caught in days rather than at year-end.

Preparing for a clean count

Most bad counts are lost before the first item is scanned. The preparation checklist — general good practice, straightforward to run:

• Post everything first. Every pending receipt, issue, return and transfer must be in the system before counting starts, or the book quantity being compared against is already stale.
• Freeze movements in the counted area. Counting a location while goods flow through it produces variances that are timing artefacts, not truths.
• Tidy physically before counting. Same item consolidated, cartons labelled, damaged goods segregated — half of counting pain is housekeeping pain.
• Count blind where stakes are high. For sensitive items, have the counter enter the physical quantity without studying the book figure first — it removes the temptation to "confirm" the system.
• Use barcodes. Scanning the item (or lot) label eliminates the commonest count error of all — counting the right quantity of the wrong item.

Common counting mistakes

• Counting only once a year — accuracy decays continuously; an annual-only regime means eleven months of decisions on drifting numbers.
• Adjusting without investigating — every unexplained adjustment teaches the team that variances are normal and hides the process fault that caused them.
• Ignoring lot detail — counting a batch item as a single quantity leaves expiry data wrong even when the total is right; count at lot level where lots exist.
• No variance follow-up — the variance report is a diagnosis of your processes; filing it unread wastes the whole exercise.
• Tools that overwrite stock on save — the design flaw this whole guide argues against; walk away from it in any evaluation.

How Fast Inventory Software implements counting

In Fast Inventory Software, physical stock taking runs as annual, quarterly or perpetual/cycle counts. The operator picks the counting user and location, scans or selects the item — or the specific lot — sees the system quantity, and enters the physical quantity; saving stores a numbered count document with header and detail lines and produces the book-vs-counted variance report. The count changes nothing else: reconciliation is done by raising the matching adjust-increase or adjust-decrease document, which updates the running stock balance and writes its row in the immutable ledger.

Because counting sits on the same platform as everything else, the supporting pieces are already there: item and lot barcodes for scan-based counting, ABC classes from the reports layer to drive the cycle schedule, and the valuation view to price every variance before it is approved.

Frequently asked questions