Overview

A Cycle Count Job Type acts as a reusable template for all count jobs created in your warehouse. It defines essential parameters, such as how jobs are batched and which specific locations or SKUs should be included.

Configuring a job type is a mandatory step before you can create cycle count jobs:

Cycle Count Waves: Count job types can be assigned to the cycle count waves and waves create count jobs based on the selected count job type
Count Plans: Cycle count jobs can be also manually created on the Count Plan screen, by selecting the count job type.

Created count job types can be used for both Location Count & SKU Count Plans.

Step-by-Step Guide

Step 1: Navigate and Create

Navigate to the Job Types screen. If you have trouble finding it, please use the main search bar.
Click Create New Job Type in the upper-right corner.
Select Cycle Count from the Operation Type sidebar.

Step 2: General Configuration

In the General tab, fill out the basic information for your job type.

Field	Description
Name*	Type the name for this job type. Required field.
Warehouse*	Select the warehouse where this job type will be used. Required field.
Operation Type	Selected on the previous screen. Cannot be edited here.
Allocation Algorithm	This field does not apply to Cycle Count job types and cannot be edited.
Description*	Provide a more detailed description for clarity. Required field.

Click Next to proceed.

Step 3: Configure Settings

The Settings tab allows you to define the operational behavior of the count jobs.

Batch Size: This defines the maximum number of locations to be included in a single job when jobs are created automatically by a Cycle Count Wave.
- For example, if a wave identifies 100 locations to count and the batch size is set to 25, the system will create four separate count jobs.
- If left at 0, one single job will be created for all locations.

Note: This setting only applies to automated job creation through waves. It does not affect jobs created manually from the Count Plan screen. This parameter is currently applicable only for location counts.

One by One Count: This toggle changes the counting method on the mobile app.

Enabled: The counter must scan each item individually. Every scan increases the counted quantity by one. This method is recommended for high-value or sensitive items where precise unit-by-unit validation is required.
Disabled: The counter scans the product once and is then prompted to manually enter the total counted quantity.

Click Next to proceed.

Step 4: Define Count Conditions

In the Loc. Count Conditions and SKU Count Conditions tabs, you can specify filters to ensure the job type only applies to certain locations or products. This is an optional step.
- Location Conditions: Use these filters for location-based counts. You can add conditions such as Location Zone, Aisle, Location Type, or custom fields to narrow down which locations are included in the count job.
- SKU Conditions: Use these filters for SKU-based counts. You can add conditions such as SKU, Product Group, or Client.

Note: Created count job types can be used for both Location & SKU Count plans. Therefore both location & SKU conditions can be selected for count job types.

However, location conditions and SKU conditions are mutually exclusive within a single count plan.

If this job type is used for a location count, only the Location Conditions will apply.
If this job type is used for an SKU count, only the SKU Conditions will apply.

Click Save to finalize the job type.

What's Next?

With your new job type configured, you are now ready to create count plans and jobs. You can use this job type to:

Manually create a job from a pre-made count plan. Learn more at Create a Count Plan.
Automate your counts by assigning this job type to a recurring wave. Learn more at Create Wave Rules for a Cycle Count.