📘 Cycle Counting – Overview
Cycle Counting in Canary7 provides a flexible and controlled way to maintain inventory accuracy without the need for full physical stocktakes. It uses five core components that work together to define, generate, execute, and review counting tasks.
🔄 The 5 Components of Cycle Counting
1️⃣ Cycle Count Profile – Controls What Jobs Appear
The Cycle Count Profile determines how Cycle Counting jobs will behave and which jobs will be visible for generation.
Key elements:
Initiation Method: Choose whether jobs are triggered automatically or manually
Default Item UOM Determination Method: Set whether counters scan the UOM they see or pick from a pre-defined list
Job Zones and Job Types: Define which zones and types of jobs the profile can operate across
🔗 Used in: Job Creation
2️⃣ Cycle Count Job Creation – Defines the Job Parameters
Just like other job creation modules in Canary7, this is where the actual Cycle Count job is generated, using your chosen profile.
Tabs include:
General: Select the Job Type and configure Job Number assignment
Where: Apply filters to control the dataset
Group By: Define how jobs are grouped (e.g. by location, item)
Order By: Optimise the sequence in which jobs are executed (e.g. by pick path)
🔗 Leads to: Job Execution
3️⃣ Cycle Count Template – Configures Selection Rules
The Template defines the structure and rules that guide how the system selects items and locations for counting.
Includes options for:
Item and Location Selection
Count Validity (how long a count remains valid)
Maximum Location Counts per Job
Additional parameters to refine the job's scope and frequency
🔗 Used during: Job Creation
4️⃣ Cycle Count Enquiry – Run, Review, and Reconcile
The Enquiry screen provides visibility into all your planned and completed Cycle Count jobs.
From here you can:
Run planned jobs
View and analyse count results
Confirm counts or reconcile any variances
🔗 Used after: Job Execution
5️⃣ Cycle Count Job Execution – The Counting Process
This is the hands-on phase where warehouse users carry out the count.
Users scan or input quantities for each assigned item or location
Data is fed back into the system for review and reconciliation
🔗 Follows: Job Creation and feeds into Enquiry
✅ Summary
Each component plays a distinct role:
Component | Role & Function |
---|---|
Profile | Defines rules for which jobs are accessible, how Initiation/UOM is handled, and valid zones/types |
Job Creation | Generates the job using filters, grouping, and sequencing |
Template | Applies item/location selection rules and validity settings |
Enquiry | Allows users to run plans, view results, confirm or reconcile |
Job Execution | Where users complete the physical cycle counting tasks |