[Blog]()Inventory # Cycle counting while the warehouse operates: cutoff and adjustments Counting in sections lets the warehouse operate, provided each difference is compared with the correct point in time. **[Jonathan Perez]()**Co-founder · Design, product and sales October 8, 2026 · 8 min read **Short answer** Count a defined location or group, retain its physical cutoff and reconcile movements occurring before the difference is applied. Separate the counted result from adjustment authorization. Continued operation needs an agreed local hold or a verifiable movement record; repeating approval must not deduct the difference again. ## Cycle count cutoff and adjustment tests Record the cutoff and ten checks that prevent overwriting later movements. [Download CSV worksheet]() In this guide - [Which part of the warehouse will you count?]() - [Hold a zone or reconcile its movements?]() - [Worked example: count 98, then issue 7]() - [Who should review a difference?]() - [How do you prepare a useful demonstration?]() ## 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 **Synthetic exercise C01** TOR-B, location A-01, whole pieces. The system shows 100 at 10:00 and 98 are physically counted at that cutoff. Times and quantities are invented acceptance data. | Step |Recorded |Physical or expected |Difference | | --- | --- | --- | --- | | 10:00: count C01 |100 |98 counted |−2 | | 10:05: S07 issues 7 |93 |91 after the issue |Still −2 | | 10:10: authorized J01 adjustment |91 |91 |0 reconciled | | Repeat J01 |91 |91 |No extra adjustment | 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. ## Review a count that did not reconcile A free consultation can help define the cutoff, permissions and evidence for a location count. - The original count and any recount for one location. - Receipts and issues from that interval with references. - The applied adjustment and its approver. [Book a free consultation]()[Ask on WhatsApp]() Related - [Inventory management system]() - [Distribution management software]() ## Frequently asked questions ### Does cycle counting always avoid operational pauses? No. You can limit a pause to one zone or reconcile identified movements. Without sufficient evidence during counting, you need a controlled hold or recount. ### Should the counter see expected stock? A blind count helps prevent copying it. Decide who can compare it afterward, and preserve the initial result, recounts and responsible people. ### Can small differences be adjusted automatically? Only under an explicit, tested tolerance and permission policy. Repeated small differences may reveal a packaging or entry problem. ### What if goods arrive after counting? Identify the receipt as later than the cutoff and retain it in reconciliation. If its timing or quantity cannot be verified, request a recount before replacing the balance. ## Sources 1. [Cycle counting in Dynamics 365]()Microsoft Learn 2. [Inventory adjustments in Odoo 19]()Odoo Last updated: October 8, 2026 ## Keep reading [InventoryOct 8, 2026 ### Warehouse locations: find goods and record every movement]()[InventoryOct 8, 2026 ### Negative stock: when to block an issue and how to correct it]()[InventoryOct 5, 2026 ### Inventory migration from Excel: catalog, count and cutover]() --- Canonical: https://nightlysoftware.com/en/blog/warehouse-cycle-counting Updated: 2026-10-08 Description: Test location counts, movements during the cutoff, recounts and authorized adjustments with a reconciled example and a downloadable worksheet.