Cycle counting while the warehouse operates: cutoff and adjustments

Which part of the warehouse will you count?

Define location, product, lot, owner and unit before assigning a task. Counting “screws” without separating goods in receiving from goods already on a shelf creates artificial discrepancies. A small scope lets you investigate using recent documents. This exercise does not promise that every area will always remain open: it keeps the rest of the warehouse operating while a specific part is controlled.

Dynamics 365 describes task creation, mobile counting and difference review for its WMS solution. It also says open count work does not itself block inventory for reservations and issues. Choose a movement rule rather than assuming one. Cycle counting reference.

Hold a zone or reconcile its movements?

With a local hold, agree when it starts, who releases it and where incoming goods wait. Without a hold, every movement needs to fall before or after the physical count. Retain start, finish and reference time; a count taking half an hour does not automatically have one cutoff for every item. If you cannot reconstruct what moved during counting, request a controlled recount rather than approving an uncertain difference.

Odoo 19 warns that a counted quantity may no longer match the balance when movements happen before an adjustment is applied. That warning does not amount to automatic reconciliation. The demonstration must show how the configuration handles an old value. Adjustment documentation.

Worked example: count 98, then issue 7

Do not replace 93 with the old count of 98: that would create five nonexistent pieces. In this scenario the accepted difference is −2 and the final balance is 91. Before applying it, verify that S07 occurred after the cutoff and no receipts remain unrecorded. If S07 lacks a trustworthy time or sequence, the exercise cannot be resolved with that evidence and requires another count.

Who should review a difference?

Separate counting, investigation and approval when the impact justifies it. A blind count prevents someone from copying expected stock; a second count should preserve the first rather than erase it. Investigate incorrect units, open cases, pending receipts, unrecorded issues or goods in another location. The explanation should lead to a missing movement or a reasoned adjustment; labelling everything “inventory error” hides recurring causes.

• Normal: C01 records 98, retains its cutoff and applies one −2 difference after S07.
• Exception: another issue arrives during review; reconcile from the cutoff or request a recount without overwriting current stock.
• Retry: J01 loses its response; repeating its identity preserves balance 91 and lets the user check whether it was already applied.
• Permissions: the counter can submit a difference, but an unauthorized user must not apply J01 through another screen or import.

How do you prepare a useful demonstration?

Use the cycle count and cutoff worksheet for a location with actual movements. Attach receipts and issues from that interval, a count photo or signed count record and adjustment history. Record what remains unexplained. Do not infer warehouse accuracy from a single example: this test checks behavior rather than proving a percentage improvement.

The general inventory guide helps select frequency; the location guide distinguishes shelves and zones. An inventory management system should demonstrate the cutoff you agreed. If movement records are unreliable, address that issue before automating approval of count differences.