Overview
After completing a cycle count, you may find significant discrepancies that require a second, more focused count to verify the results. The recount process in Logiwa IO allows managers to create a new, targeted count plan based on the results of an initial count. This ensures that any variances are thoroughly investigated before making final inventory adjustments, safeguarding the accuracy of your stock data.
A recount is essentially a new count job for an existing count plan, but it is specifically created to re-audit locations or SKUs that were identified with discrepancies in a previous count.
When to Create a Recount
A recount should be performed when:
A discrepancy found in a cycle count exceeds an acceptable tolerance
High-value items show any level of discrepancy.
You need to confirm a surprisingly large over-count or under-count before making a significant inventory adjustment.
Step-by-Step Guide to Creating a Recount
Step 1: Identify Discrepancies
Navigate to the Count Plan screen and select the completed count plan you wish to review.
Go to the Location Details or SKU Details tab.
Analyze the results, paying close attention to the Difference (%) column to identify the lines with the most significant variances.
Step 2: Initiate the Recount Job
Select the checkbox next to the single location or SKU line you wish to recount.
Click the Create Recount button.
The Create Recount pop-up will appear. Configure the new job by filling in the following fields:
Job Type: Select a pre-configured Count Job Type from the dropdown.
Batch Size(Location): This field will define how many locations are included per job if you are recounting multiple lines at once.
Assign to: Choose how the new recount job will be assigned (to the Job Pool or a specific user).
Click Save to create the new recount job.
Note: Create recount functionality is only possible for count plan lines that are in the "Count Completed" status.
Step 3: Understand the Changes on the Count Details Screen
After you create the recount job, the Count Details screen will update automatically to reflect the new tasks:
The original count line that you selected will have its Status changed from Count Completed to Recount Created. This archives the initial count result.
A new line for the same location/SKU will appear directly below the original. This new line will have a new Job Code and a Status of Ready To Count. This is the active task that needs to be executed.
Step 4: Execute and Review the Recount
The newly created recount job will now be visible in the mobile app for the assigned user or within the job pool.
An operator selects the job and performs the count tasks by following the standard mobile counting process.
Once the operator submits the count from the mobile app, the results populate the new recount line on the Count Details screen. The Counted Qty and other relevant fields will be updated.
After considering the results of the new count plan line, Update Inventory action can be used to finalize the process and trigger the definitive inventory adjustment in the system.
Important Note on Inventory Movements
It is important to understand that the Initial Stock Qty on the new recount line may be different from the Initial Stock Qty on the original "Recount Created" line. This happens if inventory transactions (such as picking, receiving, or transfers) occurred in that location after the original count was performed but before the recount job was created.
Logiwa IO correctly captures a new inventory snapshot when the recount job is created to ensure the recount is benchmarked against the most current system data, providing the highest possible accuracy.
Couldn’t Find What You Were Looking For?
Visit our Help Center to search for more documents!