Overview
A replenishment task is only created when a wave runs, the location or product actually needs stock, eligible source stock exists and, for Dynamic, a target location is found. If any of these fails, there's no task. Work through the checks below in order; most cases are solved in the first two sections.
1. Check the wave rule
Check | Why it matters | What to do |
Has the wave run since stock dropped? | Tasks are only created when a wave runs. Stock isn't watched between runs | Click Run on the wave rule, or add more times on its Schedule |
Is the job type on the wave rule? | Only job types listed on the wave rule are processed | Add the job type on the wave's General tab |
Is it the right warehouse? | A wave only runs for its own warehouse | Check the wave rule's Warehouse |
Was another wave running? | Only one replenishment wave runs per warehouse at a time | Run the wave again once the other has finished |
2. Check the conditions
Check | Why it matters | What to do |
Do wave or job type conditions exclude the location, product or LP? | Both sets of conditions apply, and everything must match | Review Selection on the wave and Conditions on the job type |
Does the wave have Shipment Order conditions? | Only products on an open shipment order matching all of them are considered | Check the product is on a matching order, or remove the condition |
Example: The wave has Order Status = Shortage. SKU-1 is low in its bin but isn't on any shortage order, so it gets no task.
3. Check the source stock
Check | Why it matters | What to do |
Is there stock in a Source location? | Only locations with Replenishment Location Type = Source supply stock | Set the reserve location's Replenishment Location Type to Source |
Is the stock free? | Stock allocated to shipment orders isn't used. Damaged and missing stock isn't used either | Check allocations and inventory status at the source |
Do source conditions exclude it? | Source Location conditions on the wave and job type limit which locations supply | Review the conditions |
Is Only Replenish Full LPs on? | Only whole LPs that fit within the need are taken. A bigger LP is skipped | Turn it off, or keep LPs that fit the need in reserve |
Was the stock used by another task in the same run? | Stock is never assigned to two tasks in one run | Check other tasks created by the same wave |
See How Replenishment Chooses Source Stock for more details.
4. Static Replenishment: Check the target location
Check | Why it matters | What to do |
Is the location a Target with a capacity? | Static only checks locations with Replenishment Location Type = Target and a product or LP capacity | Set the type and add a capacity |
Does the capacity match the product and pack type? | A product capacity is for one product and pack type | Check the capacity's Product and Pack Type |
Is Current Qty below Min? | Free Qty plus open replenishment to the location must be below Min Qty | Check open tasks to the location. Allocated stock doesn't count, but open replenishment tasks do |
LP capacity: is there a full single-SKU LP of the assigned product? | LP capacity only moves whole LPs holding only the assigned product | Check Assign Product for this LP and the LPs in reserve |
Do wave or job type Target Location conditions exclude it? | They limit which target locations Static replenishes | Review Selection on the wave and Conditions on the job type |
Example: A bin with Min 10 holds 9 free boxes, and a task for 5 boxes is already open. Current Qty is 9 + 5 = 14, so no new task is created.
5. Dynamic Replenishment: Check the product and demand
Check | Why it matters | What to do |
Is the product's Min. Replenishment Level above 0? | Products with Min 0 are skipped | Set the level on the product |
Per Warehouse: is this warehouse listed? | With Per Warehouse, warehouses not listed are skipped | Add the warehouse on the product's Replenishment Level section |
Is Demand greater than Supply? | A task is only created when Open Order Qty + Min Level is greater than Target Location Free Qty + Open Replenishment Qty | Check the Dynamic Replenishment Report for the product |
Are the orders counted? | Only unallocated quantity on Open and Shortage orders counts | Check order statuses and allocations |
6. Dynamic Replenishment: Tasks created, then removed
Dynamic tasks are created without a target, then the dynamic replenishment algorithm assigns one. If it can't, the task is removed straight away, and so is any job left empty.
Check | Why it matters | What to do |
Does any algorithm rule apply to this stock? | A rule's conditions must match the stock being replenished | Review the dynamic replenishment algorithm's rules |
Do target locations have room? | The rule's actions, such as capacity checks or empty-location rules, may leave no candidate. If the rule uses Suggest a location with the selected replenishment type = Target, only Target locations are considered | Free up or add target locations, or relax the rule |
Are there empty locations the rule can't use? | A rule without Suggest an empty location only considers locations that already hold inventory, so empty locations are never suggested by it | Add a rule with Suggest an empty location |
Is soft allocation on? | Locations targeted by other open tasks count as occupied, so suitable locations can run out faster | Turn off Enable Soft Allocation for Dynamic Replenishment on the wave, or add target locations |
Is Only Replenish Full LPs on? | The whole LP needs one target. If none fits, all its tasks are removed | Check that a target can take the whole LP |
Common questions
A task was created, but for less than I expected. Why? Open replenishment tasks already count toward stock, so the task only covers what's still missing. There may also not be enough eligible source stock. In Dynamic, if target locations with a product capacity can't hold the full quantity together, the task is reduced to what fits.
Where can I compare a product's need with what was created? For Dynamic, use the Dynamic Replenishment Report. For both strategies, the Replenishment Task Details screen shows the tasks that exist.