Replenishment Tasks Still Generated After Timer Disabled

Question:

Dear CSO,

In the PROD environment for INKLI001, the replenishment timer has already been disabled. However, we are still seeing replenishment tasks being generated.
Could you please help us check why the replenishment tasks are still being generated?

Is there any other timer or configuration that needs to be disabled to completely stop the replenishment task generation?

---

Answer:

The Demand Replenishment option can be disabled under Rules → Allocation Rule by unticking 'Replenish' option:

The behavior would be as follows:

1. Demand Replenishment unticked

• If there is insufficient stock in the pickface, the order will be partially allocated and no replenishment task will be triggered.
• Example: 15 qty ordered, 10 qty available in pickface
  → 10 qty allocated
  → Order becomes Partially Allocated
  → No replenishment task is triggered.

2. Demand Replenishment ticked

• The available stock will be allocated, and a replenishment task will be triggered for the remaining demand.
• Example: 15 qty ordered, 10 qty available in pickface
  → 10 qty allocated
  → Replenishment is triggered.

However, please note that the 'Standard' Allocation Rule is currently applied across all sites. Therefore, if we untick Demand Replenishment from the existing rule, it will disable Demand Replenishment for all sites, as all sites are currently using this same Allocation Rule.

If we only want to disable it for a specific warehouse/site, we would need to:

1. Create a separate Allocation Rule.

1. Assign the new rule to the SKUs used by that specific site.

The Allocation Rule can also be configured at the Customer/Goods Owner level. This would allow any new SKU under that Customer/Goods Owner to automatically inherit the specified Allocation Rule. But this does not update existing SKU to the new rule.

Please test this configuration in UAT and confirm whether it meets the requirement.

Ask project team to give advise

As discussed on WhatsApp, the replenishment task was not triggered by the timer because the replenishment timer has already been disabled.

If the replenishment task is triggered by the timer, it will be a Min-Max Replenishment.

In this case, the generated replenishment task is a Demand Replenishment. When the allocation is triggered, the replenishment task will be generated accordingly.