Direct Replenishment

• Direct replenishment is triggered when a picker performs a pick denial using an exception code. This exception code is configured to map to the internal exception code "REPL."
• Direct replenishment can only be carried out in scenarios involving fixed storage bins.
• You may also define the exception codes "Full pick denial + Replenishment" and "Partial pick denial + Replenishment," which are mapped to the internal codes "BFRP" and "BPRP," respectively.

Picker Driven Replenishment: Direct replenishment can be executed by the picker, and the created Warehouse Task (WT) is displayed as the subsequent WT, enabling the picker to start work on it immediately. Once the direct replenishment task is complete then picker can resume the earlier replenishment as stock is available in the source by direct replenishment.

• If 'Picker Driven' is not selected in the settings, the system will not display the Work Task (WT) as the next item for the picker. Instead, it will be displayed to a different resource or according to the queue.
• Picker driven replenishment is only possible in the RF environment scenario.

Where Fits

Picker‑Driven Replenishment is a subtype of Direct Replenishment, which is triggered during a bin denial—when the picker cannot pick the required quantity from the picking bin.

• Can be performed by the picker (picker-directed replenishment)
• It is used in fixed bin storage types where min/max quantities are defined.
• The system calculates the replenishment in accordance with the maximum and minimum quantities.
• It assumes that the quantity in the storage bin is zero.
• Only possible in radio frequency scenarios.

When to Use Picker‑Driven Replenishment

• Picking bins frequently run empty during peak operations.
• Reserve storage is physically close to picking areas (reduces forklift travel).
• You want real‑time replenishment instead of batch‑driven replenishment.
• You operate in high‑velocity picking environments (e‑commerce, retail, pharma).