Understanding Cycle Counting Roles
Cycle counting involves three key roles, each with distinct responsibilities and needs:
Warehouse Manager / ICQA Lead
Responsibilities:
Creates and oversees cycle counts for designated locations
Configures auto-adjustment thresholds at the organization level
Bulk-assigns counts to warehouse associates
Reviews and approves or rejects adjustments that exceed configured thresholds
Generates accuracy reports for clients and internal quality programs
Key Needs:
Systematic count creation and assignment capabilities
Threshold configuration for variance handling
Comprehensive reporting and audit trails
Warehouse Associate
Responsibilities:
Executes counts on the warehouse floor
Scans location barcodes to identify counting areas
Enters physical quantities for each product found
Records findings in real time via scanner or tablet
Key Needs:
Clear visibility of assigned counts
Scanner-optimized workflow for speed and accuracy
Simple, fast quantity entry process
Ecommerce Brand Inventory Manager
Responsibilities:
Receives fulfillment services from your warehouse
Reviews inventory accuracy reports
Monitors adjustment notifications
Key Needs:
Transparency into inventory accuracy
Notification of adjustments made to their inventory
Confidence in system records and fulfillment operations
Setting Up Cycle Counts
Creating Cycle Counts
As a warehouse manager, you create cycle counts to systematically verify inventory accuracy for specific warehouse locations. This structured approach allows you to:
Define scope – Select which warehouse locations will be counted
Establish baseline – Create a snapshot of expected inventory at the time of count creation
Plan systematically – Organize counting work rather than responding reactively to discrepancies
Avoid operational disruption – Counts run alongside normal warehouse operations
When you create a cycle count, you specify the locations to be counted. The system captures the current system-recorded quantities for those locations, which serve as the baseline for comparison against the physical counts your associates will record.
Bulk Assigning Cycle Counts
Once cycle counts are created, distribute them to your team using bulk assignment. This approach ensures:
Fair distribution – Counting work is evenly spread across warehouse associates
Clear accountability – Each associate knows exactly which locations they are responsible for
Complete tracking – All assignments are logged for audit purposes
Efficient workflow – Associates can immediately begin counting their assigned locations
Bulk assignment saves time compared to assigning counts individually and ensures no locations are missed or double-assigned.
Configuring Auto-Adjustment Thresholds
Understanding How Thresholds Work
One of the most powerful features of cycle counting is the ability to configure auto-adjustment thresholds at the organization level. This configuration determines how variances are handled automatically versus requiring human review.
Minor Variances (Within Threshold):
Automatically corrected in the system
No manual review required
Processed immediately
Typical use case: Small counting variations due to rounding or minor shrinkage
Significant Discrepancies (Exceeding Threshold):
Escalated for human review
Require approval from ICQA lead before inventory is updated
Logged for investigation
Typical use case: Large quantity differences that may indicate theft, damage, or data entry errors
Setting Your Threshold
When configuring thresholds, consider:
Your business tolerance – How much variance is acceptable before requiring review?
Product value – Higher-value items may warrant lower thresholds
Historical data – Review past discrepancies to set realistic thresholds
Operational efficiency – Balance automation with oversight needs
Example threshold configuration: You might set a threshold of 5 units or 2% variance—whichever is smaller. This means a location with 100 units can auto-adjust for discrepancies up to 5 units, but a location with 200 units would auto-adjust only up to 4 units (2% of 200).
Executing Cycle Counts on the Floor
Scanner and Tablet Workflow
Warehouse associates perform cycle counts using an optimized scanner or tablet interface designed for speed, accuracy, and real-time data capture.
Step-by-Step Execution Process
1. View Assigned Counts
Associates access the cycle count module on their scanner or tablet and see a list of all locations assigned to them. Each location displays the expected inventory based on current system records.
2. Navigate to Location
Associates physically move to the first assigned location and locate the barcode for that location.
3. Scan Location Barcode
Associates scan the location barcode using their scanner. The system confirms the location and displays all products expected to be in that location, along with system quantities for reference.
4. Enter Physical Quantity
For each product in the location, the associate counts the physical items and enters the actual quantity found into the scanner or tablet. The system records the count immediately.
5. Record Findings
Once all products in a location are counted, the count is submitted. The system captures:
What was counted
Who counted it
When the count occurred
The physical quantities recorded
6. Move to Next Location
Associates proceed to their next assigned location and repeat the process for all assigned locations.
Best Practices for Floor Execution
Count during consistent times – Perform counts when warehouse activity is predictable (e.g., early morning before picks begin)
Verify barcodes – Ensure location barcodes are clean and readable
Double-check quantities – Associates should verify their count before submitting
Report issues – If a location barcode is damaged or missing, report it immediately
Complete assignments – Finish all assigned locations before the count period ends
How the System Handles Concurrent Warehouse Activity
Accounting for Picks, Moves, and Other Transactions
A key strength of ShipSidekick's cycle count system is its ability to account for concurrent warehouse activity during a count. This means:
Normal operations continue – You don't need to halt picks, moves, or other inventory transactions during a count
Variance calculation is accurate – The system factors in all transactions that occurred during the count period
No artificial discrepancies – Inventory movements are properly accounted for, so you only see true discrepancies
How It Works
When the system calculates variances, it:
Captures the physical count recorded by the associate
Identifies all inventory transactions (picks, moves, receipts) that occurred during the count window
Adjusts the expected quantity to account for these transactions
Calculates the true variance between adjusted expected quantity and physical count
This approach ensures that a pick that occurred during the count doesn't create a false discrepancy.
Reviewing and Approving Adjustments
ICQA Lead Review Process
Adjustments that exceed your configured thresholds require review and approval from an ICQA lead before inventory quantities are updated in the system.
Examining Discrepancy Details
When a discrepancy exceeds the threshold, the ICQA lead receives notification and can:
View the location and products involved
See the system-recorded quantity
Review the physical count recorded
Check the calculated variance
Review who counted and when
Investigating the Root Cause
The ICQA lead should:
Determine if the discrepancy is justified
Look for patterns (e.g., recurring issues at specific locations)
Check for known issues (e.g., damaged products, recent moves)
Review transaction history during the count period
Making an Approval Decision
Approve the Adjustment:
The system updates inventory to match the physical count
The adjustment is logged with the ICQA lead's approval
The change is recorded in the audit trail
Clients can be notified if configured
Reject the Adjustment:
The system does not update inventory
The location is flagged for recount
The associate may be asked to recount the location
Investigation notes are recorded
Audit Trail
Every approval or rejection creates a permanent record showing:
Who made the decision
When the decision was made
What adjustment was approved or rejected
Any notes or comments
The reason for the decision
This complete audit trail supports compliance, quality programs, and dispute resolution with clients.
Generating Reports and Tracking Accuracy
Accuracy Reports
Cycle counts produce comprehensive accuracy reports that serve multiple purposes.
For Internal Quality Programs:
Track inventory accuracy trends over time
Identify problem locations or product categories
Measure team performance
Monitor the effectiveness of your cycle counting process
For Client Communication:
Demonstrate inventory accuracy to clients
Show the frequency and nature of adjustments
Provide transparency into your quality controls
Build confidence in your fulfillment operations
Report Contents
Typical accuracy reports include:
Count summary – Total locations counted, total products verified
Variance metrics – Number of discrepancies, percentage accuracy
Adjustment details – What was adjusted, by how much, and why
Trend analysis – Accuracy over time, seasonal patterns
Location performance – Which locations have the most discrepancies
Associate performance – Counting accuracy by team member
Audit trail – Complete history of all counts and approvals
Using Reports for Improvement
Use your accuracy reports to:
Identify training needs for associates
Pinpoint locations with recurring issues
Adjust thresholds based on actual variance patterns
Demonstrate compliance to clients
Plan targeted retraining or process improvements
You can share these reports with clients to demonstrate the effectiveness of your cycle counting process and build confidence in your fulfillment operations.
Important Considerations and Constraints
Location Property Updates Don't Affect Counts
If you update location properties using the location upload template—such as making a location non-pickable—your inventory counts at those locations will not be affected. The inventory quantities remain unchanged when you modify location settings. This allows you to adjust location configurations without disrupting your cycle counting process.
Handling Discrepancies with Allocated Orders
When you discover inventory discrepancies after orders are already allocated, special care is needed:
The Problem:
Orders may be allocated to locations that don't have enough stock based on corrected counts
Simply refreshing a mission won't automatically update allocations to reflect moved inventory or corrected counts
The Solution:
Unallocate affected orders – Remove them from their current allocation
Reallocate based on corrected inventory – Reassign them to locations with available stock
Contact support for bulk operations – If you have many affected orders, support can assist with bulk reallocation
This ensures that your allocation system stays synchronized with your actual inventory.
Parent-Level Cycle Counting: Current Limitations and Future Plans
Current State:
Cycle counts must be performed at the individual organization level
You cannot currently perform cycle counting at a parent organization level
Why This Matters: If you manage multiple customer organizations within ShipSidekick, you must switch between individual organizations to create and manage cycle counts for each one. This means you cannot perform cycle counting across multiple organizations simultaneously or from a consolidated parent-level view.
Future Improvements: Improvements are being developed to address this limitation:
A parent-level inventory view is planned
Enhancements to the location-based counting workflow are in development
The ability to move and recount from the search by location view is planned
Check with your account team for the latest timeline on these features.
Frequently Asked Questions
General Cycle Counting
Q: Do I need to stop warehouse operations to perform a cycle count?
A: No. One of the key advantages of cycle counting is that it runs alongside normal warehouse operations. The system accounts for concurrent picks, moves, and other transactions during the count period, so you don't need to halt operations. This allows you to maintain fulfillment velocity while verifying inventory accuracy.
Q: How often should I perform cycle counts?
A: This depends on your business needs and accuracy requirements. Some warehouses perform cycle counts daily for high-value or fast-moving items, weekly for general inventory, or monthly for slower-moving items. Review your accuracy reports to determine the optimal frequency for your operation.
Q: Can I count specific products instead of entire locations?
A: The cycle count system is designed around location-based counting, where you count all products in a specific location. This approach is more efficient and reduces the risk of missing items. If you need to count specific products across multiple locations, you can create multiple cycle counts for the locations where those products are stored.
Setup and Configuration
Q: How do I create a cycle count?
A: As a warehouse manager, you create a cycle count by selecting the warehouse locations you want to count. The system captures the current system-recorded quantities for those locations as the baseline. You can then bulk-assign the cycle count to warehouse associates.
Q: How do I set auto-adjustment thresholds?
A: Configure auto-adjustment thresholds at the organization level. These thresholds determine which variances are automatically corrected (minor variances within the threshold) and which require human review (significant discrepancies exceeding the threshold). Consider your business tolerance, product value, and historical variance data when setting thresholds.
Q: Can I assign cycle counts to specific associates?
A: Yes. You can bulk-assign cycle counts to warehouse associates. This distribution ensures that counting work is evenly spread across your team and that each associate knows which locations they are responsible for.
Execution and Workflow
Q: What information do associates see on their scanner when executing a count?
A: Associates see their assigned locations and the system-recorded quantities for products expected to be in each location. They scan the location barcode, then enter the physical quantity for each product. The system records all findings in real time.
Q: What happens if an associate makes a counting error?
A: If a significant discrepancy is detected (exceeding your threshold), it will be escalated for ICQA lead review. The ICQA lead can reject the adjustment and request a recount. For minor variances within the threshold, the system auto-corrects, but you should monitor for patterns that might indicate training needs.
Q: How does the system handle inventory transactions during a count?
A: The system accounts for all concurrent warehouse activity (picks, moves, receipts) that occur during the count period. When calculating variances, it adjusts the expected quantity to reflect these transactions, ensuring that only true discrepancies are flagged.
Approval and Adjustments
Q: Who approves adjustments that exceed the threshold?
A: An ICQA lead reviews and approves or rejects adjustments that exceed the configured threshold. The ICQA lead examines the discrepancy details, investigates the root cause, and decides whether to approve the adjustment (updating inventory) or reject it (flagging for recount).
Q: What happens if I approve an adjustment?
A: When you approve an adjustment, the system updates the inventory quantity to match the physical count. The adjustment is logged with your approval, recorded in the audit trail, and can be communicated to clients if configured.
Q: What happens if I reject an adjustment?
A: When you reject an adjustment, the system does not update inventory. The location is flagged for recount, and the associate may be asked to count it again. Investigation notes are recorded for future reference.
Q: Can I see an audit trail of all cycle count activity?
A: Yes. The system maintains a complete audit trail showing who counted, when they counted, what they found, who approved or rejected adjustments, and when those decisions were made. This information is available in your accuracy reports and activity logs.
Inventory and Orders
Q: Will updating location properties affect my cycle counts?
A: No. If you update location properties (such as making a location non-pickable) using the location upload template, your inventory counts at those locations will not be affected. The inventory quantities remain unchanged when you modify location settings.
Q: What should I do if I discover inventory discrepancies after orders are already allocated?
A: You should unallocate the affected orders and then reallocate them based on the corrected inventory quantities. Simply refreshing a mission won't automatically update allocations to reflect moved inventory or corrected counts. Contact support for assistance with bulk reallocation if you have many affected orders.
Q: Can I perform cycle counts at the parent organization level?
A: Parent-level cycle counting is not currently available. You must perform cycle counts at the individual organization level. However, improvements are being developed, including a parent-level inventory view and enhancements to the location-based counting workflow. Check with your account team for the latest timeline.
Reporting and Quality
Q: What information is included in accuracy reports?
A: Accuracy reports typically include count summaries, variance metrics, adjustment details, trend analysis, location performance, associate performance, and complete audit trails. These reports can be used for internal quality programs and shared with clients to demonstrate inventory accuracy.
Q: How can I use cycle count data to improve my operation?
A: Review your accuracy reports to identify training needs, pinpoint locations with recurring issues, adjust thresholds based on actual variance patterns, and plan targeted process improvements. Use the data to demonstrate compliance to clients and build confidence in your fulfillment operations.
Q: Can I share accuracy reports with my clients?
A: Yes. Cycle count accuracy reports are designed to provide transparency into your inventory accuracy and quality controls. You can share these reports with clients to demonstrate the effectiveness of your cycle counting process and build confidence in your fulfillment operations.
Summary
Cycle counting is a table-stakes warehouse management feature that enables you to maintain inventory accuracy without operational disruption. By systematically creating counts, configuring smart thresholds, bulk-assigning work to your team, and leveraging real-time scanner workflows, you can identify and correct discrepancies quickly while maintaining full visibility and compliance documentation.
The combination of automated variance handling for minor discrepancies and human review for significant ones ensures that your inventory stays accurate while respecting your team's time. Complete audit trails support compliance, quality programs, and client communication. As you implement cycle counting in your warehouse, monitor your accuracy reports and adjust your approach based on actual performance data to continuously improve your inventory accuracy and operational efficiency.