Overview
Static Replenishment keeps each picking location stocked within a capacity you define on the location itself. When a replenishment wave runs, Logiwa IO checks every target location that has a capacity and creates a task to top it up whenever its stock has dropped below the minimum. The target is always the location that holds the capacity, so stock goes back to the same slot every time.
When to use it
Use Static Replenishment when:
A product always lives in the same dedicated picking location.
You want each slot kept within a fixed Min/Max, regardless of upcoming orders.
You replenish whole LPs (pallets, totes) into locations sized for a set number of LPs.
If you need replenishment driven by open order demand across several picking locations, use Dynamic Replenishment instead.
Prerequisites
Products, with the pack types you want to replenish in, are set up.
For LP capacity: LP types are created for your warehouse.
You can edit Locations, Job Types and Wave Rules.
How Static Replenishment works
What is evaluated
Each wave run checks every capacity on locations whose Replenishment Location Type is Target. A location can have more than one capacity, and each capacity is evaluated on its own. There are two kinds:
Capacity | Defined by | Measured in |
Product capacity | Product + pack type + Min Qty / Max Qty | Quantity, in the capacity's pack type |
LP capacity | LP type + assigned product + Min Qty / Max Qty | Number of LPs containing the matching product |
Static uses only the Min Qty and Max Qty of a capacity.
Product capacity calculation
Current Qty: Free Qty at the location + Open Replenishment Qty to the location
Trigger: Current Qty < Min Qty
Task Qty: Max Qty − Current Qty (Min Qty − Current Qty if no Max is set)
Free Qty is the on-hand quantity of the product and pack type at the location, minus anything allocated to shipment orders.
Open Replenishment Qty is the quantity on Pending or Started replenishment tasks already headed to this location.
Min is the gate. If Current Qty is at or above Min Qty, no task is created, even when it is below Max Qty.
If a capacity has only a Max Qty (Min Qty is 0), a task is created whenever Current Qty is below Max Qty.
Source stock in the capacity's pack type is used first. Other pack types can be utilized in the absence of the matching pack type.
Example: A bin has a product capacity of Min 10 / Max 50 boxes. It holds 10 boxes, 4 of them allocated to orders, so the Free Qty is 6. Another 2 boxes are already on an open replenishment task. Current Qty is 6 + 2 = 8, which is below 10, so a task is created for 50 − 8 = 42 boxes.
LP capacity calculation
Current LPs: LPs of the capacity's LP type holding the assigned product at the location + Open LP replenishment tasks to the location
Trigger: Current LPs < Min Qty
LPs to move: Max Qty − Current LPs (Min Qty − Current LPs if no Max is set)
Only full, single-SKU LPs of the assigned product are moved, one LP per task.
Example: A pallet location has an LP capacity of Min 3 / Max 5 pallets. It holds 2 pallets and 1 more is on an open task. Current LPs is 2 + 1 = 3, which is not below 3, so nothing is created. If that open task were not there, Current LPs would be 2, and the wave would create tasks to move 5 − 2 = 3 pallets.
For how the source location and stock are picked, see How Replenishment Chooses Source Stock.
Step-by-step setup
1. Set up source locations
Navigate to Locations and open the reserve location you replenish from.
Set Replenishment Location Type to Source.
Click Save. Repeat for each source location.
2. Set up target locations and capacities
Navigate to Locations and open the picking location.
Set Replenishment Location Type to Target.
Add a capacity:
Product capacity: Under Product Capacity, click Add Capacity, select the Client, Product and Pack Type, then enter Min Qty and Max Qty.
LP capacity: Under LP Capacity, click Add Capacity, select the LP Type, enter Min Qty and Max Qty as a number of LPs, then under Assign Product for this LP select the Client and Product.
Click Save.
3. Create a Static job type
Navigate to Job Types and click Create New Job Type.
Choose Replenishment.
On General, enter Name, Warehouse and Description, and choose the Replenishment Algorithm (FEFO or FIFO).
On Settings, set Replenishment Type to Static and configure the remaining settings (see Create a Job Type for Replenishment).
On Conditions, optionally limit which target locations, source locations, LPs and products this job type covers.
Click Save.
4. Create a replenishment wave rule
Navigate to Wave Rules, click Create New and choose Replenishment.
On General, enter the Rule Set Name and Warehouse, and add your Static job type. If you add several job types, they run in the order listed.
On Selection, optionally add conditions for target locations, source locations, LPs, products and shipment orders.
On Schedule, choose the days and times the wave runs.
On Assign, choose Add Pool, Assign to User Roles or Assign to Users.
Click Save.
5. Confirm it works
Open the wave rule and click Run.
Check the created jobs. Each task's target should be the location that holds the capacity.
Job Settings that work differently in Static
All job type settings work with Static. Please see Create a Job Type for Replenishment article for full details.
These two behave in a Static-specific way:
Setting | In Static Replenishment |
Batch Size | Maximum number of target locations in a job. Jobs are grouped by source location |
Allow Suggest Another | Offers another location with a capacity for the same product and pack type that still has room: first one that can take the full task quantity, otherwise the one with the most room. No putaway algorithm is used |
Common questions
Do open shipment orders affect when Static triggers? No. Only the location's own Free Qty and open replenishment are compared to its capacity. Allocated stock is excluded from Free Qty, but order demand elsewhere isn't considered.
Does Static Replenishment use the putaway algorithm? No. The target is always the location holding the capacity. Even Allow Suggest Another looks only at other locations with a capacity for the same product and pack type.
Can one location have several capacities? Yes. Each product or LP capacity on the location is evaluated separately.
Why wasn't a task created for a location that looks low? See Why Wasn't a Replenishment Task Created?