A recount happens when a second user counts a SKU to confirm a discrepancy found during an initial cycle count. ShipHero flags these items until two consecutive counts confirm the same variance, which keeps inventory accuracy high.
For an overview of cycle counting and how to create a cycle count, see Understanding Cycle Counting in ShipHero.
Table of Contents
- How Cycle Count Recounts Work
- Enabling Cycle Count Recounts
- Types of Recounts
- Creating Cycle Count Recounts with the ShipHero Public API
How Cycle Count Recounts Work
If the expected quantity of a SKU in a location is 10, but a user counts 8, ShipHero records a discrepancy of 2. With the Cycle Count Recount setting enabled, ShipHero assigns a different user to count that SKU in the same location.
ShipHero compares the discrepancy amount (the variance), not a fixed number, between the two counts. This lets warehouse teams keep picking, packing, and shipping orders without disrupting the recount, even if the on-hand quantity changes between counts.
Recount Example Scenario
- Initial State: Expected amount is 10. User counts 8. The discrepancy is -2.
- Warehouse Activity: 3 units are picked and shipped. The new expected amount becomes 7.
- Recount Execution: The second counter finds 5 units remaining. ShipHero confirms the discrepancy of -2 (7 minus 5 = 2 variance).
- Result: ShipHero closes the recount and updates the inventory balance, because the variance stayed consistent despite the change in total stock.
If the second count does not match the first discrepancy, ShipHero keeps the SKU flagged for another recount until two consecutive counts agree.
Enabling Cycle Count Recounts
By default, inventory variances do not require a recount by a second user. Enable this setting to flag all discrepancies for verification.
Types of Recounts
| Recount Type | Description & System Action |
|---|---|
| Unit Discrepancy | Occurs when the physical count does not match the expected quantity in ShipHero. This triggers a mandatory second count. |
| Unexpected SKU in Location | When counting by location, any item found that isn't assigned to that bin triggers a recount. ShipHero prompts a counter to check all locations associated with that SKU. Does not apply to SKU-based counts. |
| Lot Discrepancy | Occurs when the identified lot ID does not match the system record. ShipHero flags the item, and a manager must manually verify and transfer incorrect lots. |
Creating Cycle Count Recounts with the ShipHero Public API
You can create an Items Flagged for Recount cycle count through the ShipHero Public API using the cycle_count_recount_create mutation. This is useful for triggering recounts automatically as part of an external inventory workflow.