Choose min-max or wave-demand warehouse replenishment

The forward location contains 24 cartons. A released wave needs 30, while the warehouse holds another 50 in reserve. The total inventory looks sufficient, yet the picker stops six cartons short.

The decision is not whether stock exists somewhere. It is how much eligible stock must reach the pick face, by when, and under which trigger. Min-max and wave-demand replenishment address different timing questions. The right design often combines a maintained starting position with demand-driven work for exceptions.

Warehouse replenishment here means moving reserve stock into forward-picking locations. The method comparison assumes the inventory is already within the warehouse. Buying more stock or transferring it between depots is a different planning decision with different lead times and commitments.

Match the trigger to the work

Min-max replenishment responds to a defined stock position falling below a threshold and aims towards an agreed maximum. Demand replenishment responds to the stock needed for selected work. Microsoft documents these as distinct methods, with configuration governing how existing replenishment quantities are considered. Microsoft Dynamics 365 — Replenishment overview.

Choose the method by a representative operating pattern. A threshold based on yesterday's quiet shift may be inadequate during a peak. Conversely, filling every slot to its maximum can consume space and handling effort that current orders do not need.

Calculate the executable replenishment

Use this illustrative example. Forward stock is 24 cartons, wave demand is 30, reserve stock is 50 and the agreed replenishment multiple is 12 cartons. All 24 forward cartons are eligible for this wave, with no competing allocation or incoming move already counted.

The immediate shortfall is 30 − 24 = 6 cartons. A 12-carton move would bring the forward balance to 36 before picking, leaving six after the wave. That is feasible only if the location can hold 36, the 12 reserve cartons are eligible and the move finishes before the picks need them.

To see how the triggers differ, first assume a location capacity of 48 cartons and a simple on-hand min-max policy with minimum 18 and maximum 48. At 24, that policy creates no move, although the known wave is six short. If a 12-carton pick reduces stock to 12 before the next evaluation, a move of 36 would refill it to 48, subject to reserve eligibility. Wave-demand logic can instead expose the six-carton shortfall before that pick. Neither rule alone guarantees that the move arrives in time.

Now set the location capacity to 30. A 12-carton replenishment before any picking would overfill it. The planner must use an approved alternative: sequence picking and replenishment, use another eligible location or change the work plan. The system should not solve the conflict by ignoring capacity.

If 40 of the 50 reserve cartons are on hold, only ten are eligible. There may be enough loose cartons for the six-carton shortfall, but not enough for the stipulated 12-carton move. The authorised handling rule decides whether a smaller move is allowed. A stock-hold status cannot be removed just to make replenishment feasible.

Compare the methods in a repeatable stock replay

The Replenishment sheet in the illustrative review workbook uses the same 24-carton forward balance, 30-carton demand and 12-carton multiple. Its starting result is a candidate 12-carton wave-demand move and no current on-hand min-max move. These are alternative proposals to compare, not quantities to add together.

Change the held reserve to 40 cartons and the demand proposal becomes a reserve shortfall. Restore that input, then set both physical capacity and the min-max maximum to 30 cartons: the 12-carton demand move conflicts with the available six-carton headroom. The original example therefore remains useful when the stock total is sufficient but execution is not.

For a timing test, enter an existing 12-carton task expected at minute 855, or 14:15 IST, against the requirement at minute 840, or 14:00. It remains a task to resolve; the worksheet does not authorise a second move. If its eligible arrival is revised to 14:00, it covers the planning shortfall, but the warehouse still needs the actual destination confirmation before treating it as received stock.

Record the proposed quantity, constraint and supervisor's decision for each run. A numerical candidate establishes what to review. It does not prove that a WMS will enforce the intended capacity, eligibility or task-netting behaviour in its deployed configuration.

Account for work already in progress

Suppose an earlier task is moving 12 cartons to the same location. Creating another identical task could be unnecessary, but treating the first task as completed stock could also be wrong.

Record the task's source, destination, item, quantity, state and expected completion. Distinguish proposed, assigned, picked from reserve, in transit and confirmed at the destination where the system supports those states. The allocation logic needs a deliberate treatment of each state.

An inbound 12-carton task due at 14:15 does not cover picks that require the stock at 14:00. It may suppress a duplicate replenishment request while still leaving the wave blocked. Confirm that the incoming quantity is for the same item, owner and usable status, and has not already been assigned to another demand. Netting it twice is as misleading as ignoring it.

If a task is cancelled after stock leaves reserve, the process must explain where the stock physically remains. Releasing the reservation alone does not return the cartons to their original location.

Put blocked replenishment into the shift plan

The replenishment team needs to know which waves depend on a task. A queue sorted only by creation time may leave an urgent shortage behind work for tomorrow. At the same time, avoid treating every picker request as an emergency; repeated urgent work is evidence that thresholds, capacity or release timing need review.

Test the combined process

Use the same sample to compare manual supervision, native WMS replenishment and any proposed extension. Include a normal shortfall, blocked reserve, a half-finished task, a cancelled wave and a repeated scanner submission.

Control flow: identify demand or threshold breach → separate current eligible stock from timely assigned incoming work → check reserve, multiples and capacity → resolve conflicting or late tasks → create approved work → confirm arrival → release dependent picks. An infeasible move returns to the planner with the specific constraint. A raw threshold quantity must pass the same feasibility review as a wave-demand proposal.

Measure pick starvation, urgent moves, replenishment labour and overcapacity attempts together. Keep the demand scope and shift conditions comparable. Reducing one type of task is not useful if pickers spend longer waiting.

Replenish for the next executable action

The chosen trigger should make stock available where and when approved work can use it. Keeping planned supply distinct from confirmed stock prevents a good-looking inventory total from hiding an impossible pick.

Next actions

1. Select one forward-pick zone and compare demand with eligible stock and location capacity.
2. Document the current thresholds, case multiples and treatment of open tasks.
3. Test min-max, demand and combined methods on the same shortfall cases.
4. Give blocked work a visible owner and dependency on the affected wave.
5. Adjust the policy using starvation and total handling effort, not task count alone.

Use one repeated pick-face shortage to scope a replenishment assessment, with the current thresholds, arrival timing and capacity constraint.