Cycle counting in a warehouse that keeps shipping

A picker removes stock while another worker counts the same location. A receipt is physically placed in the bin before its scanner message reaches the WMS. By the time the count is reviewed, the screen balance has changed again.

Cycle counting can work in an active warehouse, but the count needs a defensible boundary. Decide which stock is being observed and how movements around that observation will be handled. The goal is to compare the physical observation with the expected quantity at the same point, not with whichever balance happens to be visible later.

Choose a counting method the operation can sustain

A short location-level pause is often the clearest control where movements can be stopped safely and without disrupting critical work. Release the location when the count and necessary checks are complete. Do not assume a WMS counting task automatically blocks every relevant movement; demonstrate the installed behaviour.

Where pausing is impractical, use a movement-aware method with a clearly recorded count window and reliable event capture. A system cannot reconstruct an exact snapshot from vague notes such as “picked during the count”. If the movement evidence is unreliable, use a smaller scope or a controlled recount.

Microsoft documents that open cycle-count work does not itself block the location's stock from reservation and outbound processing. Difference review also depends on user settings and deviation limits. Establish any required movement control explicitly in the installed process. Microsoft Dynamics 365 — Cycle counting.

Reconcile movements around the observation

Consider this illustrative example for one owner, SKU, bin and stock status. The expected balance at the start of the controlled window is 70 units. A confirmed 12-unit pick and an eight-unit receipt both physically affect the bin before observation begins. No further movement affects the bin while its 65 units are counted, so the observation has a common comparison point.

The expected physical quantity is 70 − 12 + 8 = 66. The one-unit difference remains unresolved. Comparing the observation with the original 70 would suggest five missing units; comparing it with a later balance could produce another answer.

Now suppose the receipt message was entered after the count, while the cartons were placed before it. The event belongs in the physical comparison even though its posting time is later, provided its timing is supported. If the receiver cannot establish when the units entered the bin, recount under a controlled boundary rather than choosing the timestamp that makes the numbers agree.

Continuous counting requires more than summing all movements inside a time window. A receipt placed into a compartment already counted will be absent from the observation; the same receipt placed into a compartment counted later may be included. Record where the movement occurred relative to the observation, then bring each component to the agreed comparison time. Where that evidence is unavailable, pause the affected scope and recount.

Also distinguish a physical pick from a reservation. A reservation does not remove units from the bin. A confirmed pick into a trolley does remove them from this bin's count, even if they remain in the warehouse's overall custody.

Preserve the observation independently of the expected answer

A blind count records what the worker sees without encouraging them to copy a displayed expected quantity. Capture the item, owner, location, unit, status, observer and time. Where lots or handling units distinguish stock, preserve those dimensions too.

A recount should be another observation, with its own scope and evidence. Do not overwrite the first count. If the second count agrees with the system but the first does not, the supervisor still needs to understand whether stock moved, the unit was misunderstood or the initial observation was wrong.

For packaged goods, record the counting basis. Five sealed cases and two loose units need a verified case conversion. Treating five cases as five units can create an apparent loss that no amount of recounting will explain.

Give each decision an owner

Tolerance should determine review effort under an approved policy, not erase unexplained losses automatically. A small repeated variance may reveal a pack conversion or process problem even if each individual difference sits below a financial threshold.

Check the count through the next movement

After an approved correction, confirm that open picking or replenishment work remains consistent with the new balance. A count is not complete if the next task immediately recreates a negative quantity or allocates held stock.

Follow the process through an exception: planned count → controlled observation → expected-at-snapshot comparison → recount or event investigation → approved adjustment → confirmed operational balance. If evidence is insufficient, keep the count unresolved and schedule a controlled follow-up.

Measure recount frequency, repeated variance by location, cause-resolution time and the operational effect of the counting window. State the denominator of any accuracy measure: counted records, counted units and financial value answer different questions. A convenient sample should not be presented as proof of accuracy across the whole warehouse.

Trust the boundary as much as the number

The count becomes useful when another reviewer can reconstruct what should have been present at the observation time. Movement controls and a preserved decision trail make that possible while the rest of the warehouse continues working.

Next actions

1. Select a small set of active locations and define the counting dimensions.
2. Decide where to pause movements and where reliable movement reconciliation is possible.
3. Test a count with a nearby pick, late-posted receipt and pack conversion.
4. Separate observation, recount and adjustment permissions.
5. Review repeated causes before increasing count frequency.

A counting-process assessment can begin with one active zone and a variance whose movement history cannot be reconstructed.