Overview
A cycle count is a fundamental inventory auditing process that ensures the inventory data in Logiwa IO matches the physical inventory in your warehouse. This guide provides a comprehensive, end-to-end overview of the entire cycle count process, from the initial plan creation to the final inventory update. It is designed for both warehouse managers who will oversee the process and warehouse operators who will perform the counts on a mobile device.
The Cycle Count Lifecycle
The cycle count process in Logiwa IO follows a structured lifecycle designed for accuracy, automation, and control. Understanding this flow is key to effective inventory management.
Plan: The process always begins with a Count Plan. A plan defines the scope of the audit, specifying whether to count by Location or by SKU. A plan can be created for a one-time, ad-hoc count or as the basis for a recurring, scheduled count.
Learn more: Create a Count Plan
Configure Automation (Job Types & Waves): Before a job can be created, you must have a Job Type configured. This acts as a template, defining the rules for the count, such as the mobile screen workflow. For recurring counts, you create a Wave Rule that automatically generates jobs based on a schedule (e.g., daily, weekly).
Learn more: Create a Job Type for a Cycle Count
Learn more: Create Wave Rules for a Cycle Count
Create Job: A Job containing the specific count tasks is created. This can happen in two ways:
Automatically: A scheduled Wave Rule runs, evaluates the criteria, and creates the job.
Manually: A user creates a job directly from a Count Plan.
Execute Count (Mobile): An operator selects the job on their mobile device and performs the physical count, scanning locations/products and entering the counted quantities.
Review Discrepancies: A supervisor reviews the submitted counts in the Logiwa IO web interface, comparing the physical count quantities against the system's records and analyzing any discrepancies.
Approve & Update Inventory: Once the count is verified, a supervisor approves the results. A final Complete Count action adjusts the system's inventory records to match the physical count, ensuring data accuracy.
Managing Count Plans and Jobs
The Count Plan screen is the central hub for monitoring the status and progress of all cycle counts.
Monitoring Progress:
From the Count Plan grid, you can see the status of each plan (Pending, Ready to Count, Count Started, Inventory Updated, Cancelled). This allows managers to track active counts and review historical ones.
Pending: The count plan has been created, but no job has been generated for it yet.
Ready to Count: A job has been created from the plan, and the tasks are now available for operators to start on their mobile devices.
Count Started: An operator has started at least one task within the associated count job.
Inventory Updated: The count has been completed, reviewed, and a supervisor has executed the final "Inventory Update" action to update the system's inventory records.
Cancelled: The count plan has been manually cancelled and can no longer be used to create jobs.
Manual Job Creation
While wave rules are best for automation, you can trigger a job manually from a count plan at any time. This is useful for ad-hoc or priority counts.
Navigate to the Count Plan screen.
Select the plan you wish to start (it must be in
Pendingstatus).Click the Create Job button. A configuration pop-up will appear.
Select Job Type*: Choose a pre-configured Count Job Type from the dropdown. The settings from this job type will be applied to the job you are creating.
Batch Size: Enter the maximum number of locations to be included in a single job. For example, if your count plan has 100 locations and you set the Batch Size to 50, the system will create two separate jobs. If you leave it at 0, a single job will be created for all 100 locations.
Assign To: Choose how the job(s) will be assigned to your team.
Job Pool (Not selecting any user): The job will be unassigned and available for any authorized user to select from the mobile app.
User: The job will be assigned only to the specific user you select.
Click Save. The system will generate the job(s) and the Count Plan status will update to "Ready to Count".
Executing Counts on the Mobile App
Warehouse operators will use the Logiwa IO mobile app to perform the physical count tasks.
1. Selecting a Count Job
From the mobile app home screen, navigate to the Count module.
The job list screen will display jobs assigned to you under Your Jobs and unassigned jobs in the Job Pool.
Select a job to begin counting.
2. Performing a Location Count
When you select a location-based count job, the app will direct you to a specific location to audit all inventory within it.
Step 1: Scan the Location Upon arriving at the correct location, scan its barcode. This will take you to the Location Detail screen.
Step 2: Choose Count Method The Location Detail screen gives you two options for counting products:
Count Products on an LP: Select this if items are in a container with an LP barcode (e.g., a pallet or tote).
Count Products without LP: Select this if items are stored loosely on a shelf or bin.
Step 3: Count the Products
If you selected "Count Products on an LP":
Scan the LP barcode you wish to count.
Scan the product barcode on that LP.
Enter the counted quantity and confirm.
Repeat for all other products on that LP.
When finished with the LP, you must tap the Complete LP button to finalize its count.
If you selected "Count Products without LP":
Scan the product barcode.
Enter the counted quantity and confirm.
Note: If you need to recount a completed LP, you must scan it again. The app will prompt you to Reset Count for This LP. This is the only way to re-count a previously completed LP within the same count plan.
Step 4: Complete the Location Count Once all items and LPs within the location have been counted, tap the Complete Location Count button to finish the task for this location and move to the next.
If you need to start over, use the Reset Location Count button.
3. Performing a SKU Count
When you select a SKU-based count job, the app will direct you to count a specific SKU across all locations where it is stored.
The app will display the target SKU and the first Location to visit.
Scan the Location barcode. You cannot scan a location that is not part of the assigned task.
Scan the target Product barcode.
The app will then present the same choice as a location count: Count Products on an LP or Count Products without LP. Follow the relevant steps described above to count the SKU within that location.
After completing the count for the SKU in the first location, the app will direct you to the next location on the list until the count for that SKU is finished.
4. Handling Common Scenarios During Product Scans
When you scan a product barcode during any count, the system may ask for more information to ensure accuracy.
Shared Barcodes (Multiple Products): If a barcode is used for multiple products (for the same or different clients), a bottom sheet will appear, asking you to select the correct product from a list.
Shared Barcodes (Multiple Pack Types): If a product has multiple pack types sharing the same barcode, a bottom sheet will appear for you to select the correct pack type (e.g., "Each" or "Case").
Note: If a product has both multiple SKUs and multiple pack types for a barcode, you will always be asked to select the product first, then the pack type.
Attribute Tracking (Lot/Expiry/Production Date): If the product you scanned is tracked by Lot Number, Expiry Date, or Production Date, the app will require you to scan or enter this information before you can enter the quantity. This is a mandatory step because counts are a blind process, and the system needs to verify the exact inventory being counted.
Reporting Damaged Products: If you discover damaged items during a count, you can mark them directly in the app.
After scanning the product, tap the three-dots menu.
Select Report Damaged Product.
Enter the quantity of damaged items and select a Damage Reason from the dropdown. (Note: Damage reasons are configured in the Data Setup screen).
Confirm the action. The system will record the damage, which will be visible to the supervisor during the review phase.
5. Quantity Entry: Standard vs. One-by-One Count
Your job type determines how you enter the final quantity.
Standard Count: After all selections (product, pack type, attributes) are made, you will be prompted to manually enter the total counted quantity.
One-by-One Count: You must scan each individual unit. Every scan increases the counted quantity by one. This method is used when the "One by One Count" toggle is enabled in the job type setup. If attribute tracking is also enabled, you must confirm the attribute before every single scan.
Reviewing and Approving Counts
After operators complete their count tasks, a supervisor must review the results, approve the count, and update the system inventory.
1. Reviewing Discrepancies
Navigate to the Count Plan screen and click on the plan you wish to review.
Go to the Location Details or SKU Details tab.
Here, you can see a line-by-line comparison of the system inventory versus the physical count.
See our article xx:
2. Approving and Updating Inventory
Once you have reviewed the results and are confident in the physical count's accuracy, you must update the system.
On the Web UI: From the Count Plan details screen or on the Location/SKU Details screens, select the lines you wish to approve and use the Inventory Update action. This action creates a "Count" transaction that can be viewed in the Transaction History Report.
On the Mobile App (for authorized users): For location counts, users with the proper permissions can use the Update Inventory After Location Count feature directly on their mobile device to instantly update inventory levels after completing a location's tasks. This streamlines the process by reducing the need for supervisor intervention for every count.
Couldn’t Find What You Were Looking For?
Visit our Help Center to search for more documents!