Before counting, choose the reason and scope
A count can investigate a suspected error, check a high-use area or maintain routine confidence in records. Name the purpose before choosing the list. Counting every product with the same frequency may spend time on stable shelves while the troublesome picking area remains unexamined.
Build a starting list from your own evidence: recent discrepancies, frequent handling, confusing variants and items that would stop important work if missing. These are practical prioritization criteria, not a universal scoring formula. Include a smaller sample from apparently quiet areas so the plan does not assume that unreported problems do not exist. Assign a person who can finish the work within the available window.
Set a boundary that stays still
Define the location, bins and products in scope, the count start time, and the movement rule. If the whole operation cannot pause, isolate a small area and route new arrivals or picks elsewhere until its count is complete. Everyone handling those products needs to know the boundary.
For example, a fictional workshop counts bins A1 through A6 before opening. A delivery arriving during the count stays in receiving until the count finishes. If a unit must leave urgently, record the movement and its exact timing so the reviewer can reconcile it. A count without a movement boundary can confuse a correct physical observation with an incorrect stock adjustment.
Separate counting from approval
Use a count sheet that identifies the product, unit, location and counted quantity. Consider a first count without showing the expected quantity, followed by a deliberate recount of differences. A blank entry should mean “not counted,” not automatically zero.
InFlow's web stock-count documentation supports multiple sheets, team coordination and review. It describes a snapshot and advises stopping order processing and inventory movement once counting starts. Its documented behavior also warns that later backdated orders do not update the completed count's system snapshot. Plan the operating cutoff around that limitation; do not assume a later edit will retroactively make the count consistent.
Configure a manageable count pattern and verify it
A suggested first experiment is one small area per working session, followed immediately by review of its differences. Change that cadence to fit the team's real capacity. A fictional stockroom with 120 bins might begin with ten troublesome bins, learn how long they take, and schedule the rest only after the process is understood.
Track completed and reviewed counts separately. Record unresolved differences and the owner of each investigation. If the same SKU repeatedly disagrees, inspect its transaction path rather than merely counting it more often. Paper can work when scope and ownership are clear; coordinated software sheets help as counters multiply. Your next action is to schedule one count with a named start, boundary and reviewer, then measure whether the team can finish that complete loop.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- inFlow: stock counts in the web app — Merchant documentation · inflowinventory.com · Merchant-controlled · checked 2026-09-24