Skip to main content

A Guide to Managing and Executing Cycle Counts

An overview of the cycle count process in Logiwa IO, with links to each step and a reference for count plan, line and job statuses.

Overview

A cycle count checks that the inventory in Logiwa IO matches what is physically in your warehouse.

  • Who does what: supervisors plan counts, review the results and update inventory in the web app; operators count on the Logiwa IO mobile app.

  • What you count: by Location (all inventory in the selected locations) or by SKU (one SKU in every location where it is stored).

  • When you count: as a one-time, ad-hoc count or as a recurring, scheduled count.

Each step has its own article:

The cycle count lifecycle

Step

What happens

Learn more

1. Plan

A Count Plan defines the scope: count by Location or by SKU, for a one-time count or as the basis for a recurring count.

2. Job type and waves

A Job Type must exist before a job can be created. It is the template for the count, for example the mobile screen workflow. For recurring counts, a Wave Rule creates jobs on a schedule (for example, daily or weekly).

3. Create job

A job with the count tasks is created automatically when a scheduled wave rule runs, or manually from the count plan.

4. Count

An operator selects the job on the mobile app, scans locations and products and enters the counted quantities.

5. Review

A supervisor compares counted and system quantities in the web app. Lines with large differences can be recounted.

6. Update inventory

A supervisor clicks Update Inv. in the web app to adjust inventory to the count. An authorized operator can also do it on mobile (Complete Count & Update Inventory), and lines with no difference are updated automatically when Auto-Update No-Difference Count Lines is on in the job type.

When to use it

  • Count locations or SKUs on a recurring schedule, with wave rules creating the jobs.

  • Run a one-time, ad-hoc or priority count by creating the job manually.

  • Check all inventory in a set of locations (Location Count), or one SKU wherever it is stored (SKU Count).

  • Track the progress of a count and check what a plan, line or job status means.

Prerequisites


Monitoring count plans and statuses

The Count Plan screen is the central place to track active counts and review past ones. The buttons above the Count Plans grid are Import, Create New Count, Filter, Cancel, Update Inv., Create Job and Export As Excel.

Count Plan grid

Column or option

What it does

Counted Locations / Counted SKU

Shows how many lines of the plan are counted (in Count Completed or Inventory Updated). Compare with Number of Location (Location Count) or Number of SKU (SKU Count) to see progress. Hidden by default: turn them on in the Column Chooser. Included in Export As Excel.

Job Code

A plan split into several jobs shows all of its job codes.

Other columns

Other columns include Number of Location, Number of SKU, Count Object, Count Operation Type, Count Started Time, Count Completed Time, Inventory Updated Date Time, Inventory Update User, Created By and Created Time.

Filtering

Click Filter above the grid to filter the plans, for example by status. The column headers have no filters.

Sorting

Columns can't be sorted. Plans are shown in the default order.

Count plan statuses

Plan status

Meaning

Pending

The plan is created, but no job has been generated for it yet.

Ready to Count

A job has been created and its tasks are available to operators on mobile.

Count Started

An operator has started at least one task in the job.

Inventory Updated

All actionable lines are resolved and at least one line had its inventory updated: by a supervisor with Update Inv., by an operator on mobile, or by Auto-Update No-Difference Count Lines.

Cancelled

The plan was cancelled, or all of its lines were cancelled. It can no longer be used to create jobs.

Count line statuses

Each location (Location Count) or SKU (SKU Count) in a plan is a count line with its own status, shown in the Status column of the Location Details and SKU Details screens.

Line status

Meaning

Pending

The line exists but no job has been created for it yet.

Ready to Count

A count task exists in a job and is waiting for an operator.

Count Started

An operator has started counting the line on mobile.

Count Completed

The operator has completed the count. The line is waiting for review and an inventory update.

Inventory Updated

Inventory has been adjusted to the counted quantity. This cannot be undone.

Recount Created

A recount was created for the line. The line is kept as a record of the first count, and a new line in Ready to Count is added for the recount.

Cancelled

The line was cancelled individually, by cancelling the plan, or by Update Inv. on the Count Plan screen. It is not counted or updated.

Count job statuses

Jobs created from a count plan are listed on the Job Management screen with their own status.

Job status

Meaning

Pending

The job is created and no count has been submitted yet.

Started

The first count in the job has been submitted on the mobile app.

Completed

All non-cancelled tasks in the job are counted.

When Update Inv. is used on the Count Plan screen, the plan's jobs are closed and tasks that were not counted are cancelled. When a count plan is cancelled, its jobs are removed from Job Management (see Creating and Cancelling Count Jobs).

Automatic status transitions

Logiwa IO changes the plan status automatically once all actionable lines are resolved:

Plan lines

Plan becomes

All Cancelled

Cancelled

All Inventory Updated

Inventory Updated

A mix of Inventory Updated and Cancelled, with at least one Inventory Updated

Inventory Updated

  • Lines in Recount Created are excluded from the evaluation. They are passive records showing that a recount was triggered; the new lines created by the recount are evaluated instead.

  • So filtering the Count Plan screen by Count Started (with Filter) shows only plans that still have counting work left: at least one line in Ready to Count, Count Started or Count Completed.

  • The status is re-evaluated after every line cancel or inventory update: from the Count Plan, Location Details or SKU Details screen, from the mobile app, or through the Open API.

  • Lines updated by Auto-Update No-Difference Count Lines count as Inventory Updated. While any line is still in Count Completed, the plan stays in Count Started.

  • If all lines are resolved but the plan still shows Count Started, clicking Update Inv. on the Count Plan screen corrects the plan status (see Reviewing Counts and Updating Inventory).

💡 Instant Count: while an Instant Count session is active, the plan stays in Count Started even if its locations are completed and inventory-updated, so the operator can keep adding locations. The status is evaluated when the operator taps Complete Instant Count. If no line has been inventory-updated at that point, the plan becomes Cancelled. See Using Instant Count on the Mobile App and Reviewing and Approving Instant Count Plans.


Common questions

Why does my plan still show Count Started? At least one line still has counting work left: it is in Ready to Count, Count Started or Count Completed, for example a line waiting for an inventory update. If all lines are resolved and the plan still shows Count Started, click Update Inv. on the Count Plan screen.

How can I see how far a count has progressed? Turn on Counted Locations or Counted SKU in the Column Chooser of the Count Plan grid and compare it with Number of Location or Number of SKU.

Where are the rules that can block a count? Rules for creating jobs are in Creating and Cancelling Count Jobs. Rules for scanning LPs, SKUs and locations are in Counting on the Mobile App. The check run when you update inventory is in Reviewing Counts and Updating Inventory.

Did this answer your question?