Replenishment in SAP Extended Warehouse Management moves stock from reserve or another suitable source location into a picking area when it is needed. Depending on configuration, it can be triggered by minimum stock levels, open warehouse requests, task confirmation or a picker exception. The goal is reliable picking availability, not purchasing new stock.
The reserve-stock versus pick-face problem
A high-bay storage location may contain hundreds of cases, but a forward picking bin used by associates holds only a small quantity. Order pickers cannot use warehouse stock efficiently if that bin runs empty during a wave. Replenishment connects the two locations through warehouse tasks and confirmations. It is distinct from supplier procurement or material requirements planning.
The main trigger patterns
SAP EWM supports planned replenishment based on configured minimum and maximum quantities. Order-related replenishment considers open warehouse-request quantities. Automatic replenishment can be triggered after warehouse-task confirmation. Direct replenishment can respond to a bin denial in supported fixed-bin and RF scenarios. The exact availability of options, apps and behavior depends on the deployed solution and configuration.
Example: an underfilled pick bin
Imagine a forward pick bin with a minimum of 20 units, a maximum of 80 and current stock of 12. A basic target-to-maximum calculation suggests 68 units are needed. Actual warehouse-task quantities may be rounded or constrained by minimum replenishment quantity, packaging, stock availability and bin capacity; SAP's planned and order-related algorithms have different rounding rules. Avoid treating the arithmetic alone as the system's final task quantity.
Execution and exceptions
The system identifies candidate source stock according to configured search and stock-removal rules, then issues or proposes movement work. A worker confirms the warehouse task when the physical movement is complete. If no suitable reserve stock exists, replenishment cannot manufacture inventory; planners must investigate stock status, replenishment settings, blocked stock or inbound supply. Physical quantity exceptions need recorded resolution.
How to evaluate a replenishment design
Check whether the operating goal is a stable min/max pick face or demand-driven staging, whether fast-moving SKUs have appropriate capacities, and whether task priorities interfere with picking. In a test, deliberately lower bin stock, run the expected trigger, inspect proposed tasks, confirm a movement and verify bin inventory. Measure missed picks and unnecessary movement rather than merely counting generated tasks.
Distinct from wave management and putaway
Wave management groups outbound demand for controlled release. Putaway decides where inbound stock should be stored. Replenishment specifically keeps the locations used for picking or staging adequately supplied. All three may interact but are not interchangeable functions.
Related Knowledge
wave management, warehouse tasks, stock removal strategies, putaway strategies. Return to SAP EWM.