Stocktakes
A stocktake reconciles what Fast2Task thinks you have with what’s actually on the shelf. It’s organised around count sheets (printable lists that counters work through), and finishes by posting adjustments so the system matches reality.
The stocktake lifecycle
- Draft: set up the count sheets and decide what’s being counted
- Start Stocktake: counting is underway
- Complete Stocktake: counting finished, review the variances
- Finalise Stocktake: adjustments are written to stock and the stocktake is posted
Setting up count sheets
A count sheet is one counter’s list, typically one sheet per location or area. Build them how you like:
- Add a Count Sheet and add products to it by hand
- Bulk Add Sheets by Location: one sheet per stock location, pre-filled with the products expected there
- Bulk Add Products: pour a set of products across sheets, with assignment rules to control which sheet each lands on
Each sheet can be printed for clipboard-style counting, and records who performed the count.
Counting
Each line shows the product, unit of measure and expected quantity, with space for counted. Counters enter what they actually find, including the actual location when goods turn up somewhere other than their expected location. That mismatch is worth recording: it fixes future picking, not just the numbers.
Reviewing variances
As counts come in, the stocktake totals up:
- Total expected vs total counted
- Variance per line and overall
- Variance cost: what the discrepancy is worth in dollars
Big variances deserve a second count before you post; a miskeyed digit is cheaper to catch now than to “correct” into your stock records.
Finalising
Finalise Stocktake writes the count to stock. For every product it sets the quantity on hand to what was counted, and where a counter recorded a different actual location, the stock is cleared off the location it was expected in and lands where it was actually found. Each change is written as a Physical Inventory Count stock transaction, so the adjustment shows up in the product’s history.
Before it runs, Fast2Task warns you about lines counted as zero that were expected to hold stock. A count of zero looks exactly like a line nobody got to, so these are worth a second look — finalising will write them down to zero. You can tick leave zero-counted lines alone to skip them instead.
A progress dialog tracks the adjustments as they’re applied. If any fail (a dropped connection, say), nothing is posted and you can simply finalise again — adjustments that already went through are recognised and won’t be applied twice.
Once finalising completes the stocktake is posted: it becomes a permanent record of the count — who counted what, where, and what changed — and can no longer be edited.