Cycle Count Strategy for High-Value, Actively Modified Items

Summary:

We are currently using the "CC Location By Items" task type to perform cycle counts on a defined list of high-value items. While this task type effectively restricts the items included in the count, our customers have a specific requirement: they only want to cycle count those items from this list whose inventory has been actively modified (e.g., received, shipped, adjusted) within the current day. The goal is to focus cycle count efforts on items experiencing recent activity, thus ensuring accuracy where inventory changes are most frequent.

Content (please ensure you mask any confidential information):

Our initial attempt to achieve this involved incorporating a condition based on "location modified timestamp" within the cycle count task configuration. However, this approach has proven ineffective. We've observed that receiving and putaway activities, which inherently modify an item's inventory at a specific location, do not consistently update the "location modified timestamp." Consequently, our cycle count tasks are not being triggered for these actively modified items as intended.