Skip to main content

Settings and permissions

Zoned cycle counts​

Permissions​

Below you can find a summary of the permissions related to zoned cycle counts. You can use these to finetune users' ability to create, edit or view the cycle counts.

  • CycleCountZoneGroups
  • CycleCountZones
  • CycleCounts
  • ZonedCycleCounts
  • DeactivateZonedCycleCounts
  • ManageZonedCycleCounts
  • ZonedCycleCountAllowManualCorrections
  • ZonedCycleCountPlans
  • InitialCycleCounts

Settings​

There's several settings influencing your zoned cycle counts. These can all be found in your Settings chapter individually, but the following related settings can all be set simultaneously by using the SetCycleCountSettings service.

  • GenerateCycleCountAfterNASC
    • After a NASC (negative stock auto correct) is created, a cycle count will be generated
  • MaxCycleCountsPerShop
    • The max number of active cycle counts per shop
  • MaxCycleCountsPerShopPerDay
    • The max number of cycle counts to create per day per shop
  • CycleCount:OnlyCreatePastDue
    • Generate only cycle counts for products when the interval is expired
  • CycleCount:DaysOfWeek
    • On which days cycle counts should be generated
  • CycleCount:StockLabels
    • Which stock labels should be counted

The following settings can be set additionally.

  • CycleCount:ProductLimit
    • The max number of products to be included in a cycle count
  • UserTasks:CreateCycleCountOnNoStockPartialPickCompletion
    • If you were expecting to be able to pick during a SFS flow, but instead perform a partial pick due to the reason NoStock, then this will create a cycle count (if set to true)
  • CycleCountAfterReservationOrderLineCancelled
    • This setting will automatically trigger a cycle count whenever products are being cancelled from a reservation task. It should be set to true on the pickup organization unit. The setting defaults to false.
    • Note that even when it's enabled, it will only trigger when there hasn't been a stock mutation between the placing of the order and the time of cancellation.
  • StockReplenishmentTasks:AutoGenerateCycleCountZoneReset (edge-case setting)
    • Context: It is possible to disable replenishment for products (or for it not to be configured at all for a product);
    • You can activate replenishment for these kinds of products when cycle counting them in specific zones, which you specify in this setting
    • This is also dependent on the setting StockReplenishmentTasks:AutoGenerate, which when set to true will generate replenishments via the proces mentioned here above (while false will generate replenishments when products are shipped)

Stock mutation threshold​

Using a setting called CycleCount:LastStockMutationThreshold and an integer value that represents number of days, you influence the search criteria/filtering of products that would be included in a cycle count. The setting value represents the considered number of past days, where a stock mutation has occurred, that would be included in the cycle count.

Example: A value of 14 for the setting implies that generated cycle counts will include products that have had a stock mutation in the last 14 days in the specified organization unit and assortment i.e. any older stock mutations would not be part of the cycle count.

A few things to keep in mind when using this setting:

  • Execution on OU level: The search criteria/filtering performed by the cycle count task is executed on the respective organization unit configured on the task. This means that only the assortment and mutations of the respective organization unit are taken into account for the cycle count.
  • Manually created Zoned Cycle Counts: The setting does not impact manually created Zoned Cycle counts. It would however, impact scheduled zoned cycle only (if configured).
  • Default value: If not set, the default value of the setting is 7 (days). The default does not impact manully created cycle counts. It would however, impact scheduled zoned cycle counts only (if configured).
Prerequisites

There are some prerequisites to keep in mind like assortments and mutations, otherwise cycle counts will not trigger. More on this here.