Overview
A replenishment job type is the rulebook a replenishment wave follows. It sets the strategy (Static or Dynamic), the order source stock is taken in, how operators execute tasks on mobile, and which locations, products and LPs are in scope. Every setting works with both strategies; where one behaves differently, this article says so.
When to use it
Create or edit a replenishment job type when:
You're setting up Static or Dynamic Replenishment for the first time.
You need a different execution flow, quantity tolerance or scope for part of the warehouse.
You want to utilize various replenishment functionalities such as turning on LP Swap or enabling pack type conversion for a replenishment process.
Step-by-step
Navigate to Job Types and click Create New Job Type.
Choose Replenishment.
On General, fill in:
Name and Description (required).
Warehouse (required).
Replenishment Algorithm: FEFO (earliest expiry first) or FIFO (earliest receiving date first).
Click Next. On Settings, choose the Replenishment Type and configure the settings described below.
Click Next. On Conditions, optionally narrow the scope (see "Conditions" below).
Click Save. The job type is listed on Job Types.
Add the job type to a replenishment wave rule. Jobs are created only when that wave runs.
Settings & Parameters
Replenishment Algorithm
Sets the order source stock is taken in. FEFO (default) takes the earliest expiry date first; FIFO takes the earliest receiving date first.
Ties are broken by the source location's walking path priority.
See How Replenishment Chooses Source Stock for more details.
Example: Location R-01 holds a pallet expiring in March and R-02 a pallet expiring in June. With FEFO, the task takes the March pallet from R-01. With FIFO, it takes whichever pallet was received first.
Replenishment Type
Static replenishes each location up to the capacity defined on it. Dynamic replenishes based on open orders and the product's replenishment levels. See Understanding Replenishment: Static vs. Dynamic.
Example: Bin A-01 has a capacity of Min 10 / Max 50 boxes. A Static job type tops it up to 50 when it drops below 10. A Dynamic job type ignores that capacity and looks at the product's inventory at all target locations, open orders and Min/Max replenishment levels instead.
Batch Size
Maximum amount of work in one job. Static counts target locations; Dynamic counts products.
Example: Batch Size is 5. A Static wave finds 12 locations to replenish, so the tasks are split into jobs of up to 5 locations each. A Dynamic wave with 12 products to replenish creates jobs of up to 5 products each.
Zone Based Replenishment / Location Group Based Replenishment
Keeps each job within a single zone or a single location group. Only one of the two can be enabled.
Example: With Zone Based Replenishment on, tasks for locations in Zone A and Zone B are always placed in separate jobs, so one operator never has to cross between zones within a job.
Replenishment Flow
Pick & Put is two steps: the operator picks to an interim location or cart, then puts to the target.
Direct Put is one step: the operator picks and places stock at the target in a single scan sequence.
Example: A task moves 20 boxes from R-05 to A-01. With Pick & Put, the operator picks the boxes onto CART-1, and a put task from CART-1 to A-01 is created.
With Direct Put, the operator scans R-05, the product and quantity, then A-01, and the task is done.
Allow Exceed Task Quantity / Exceeding Percent %
Lets the operator pick more than the task quantity, up to the set percentage. Applies to picking only; a put can't exceed what was picked.
Example: The task is 10 units and Exceeding Percent % is 20. The operator can pick up to 12 units. Entering 13 is rejected.
Update Task Quantity If Less Picked
If the operator picks less than planned, the pick task completes with the smaller quantity. When off, the pick task is expected to be completed for the full quantity. If damaged or missing stock is reported, or the source location doesn't have enough quantity, a new pick task is created for the remainder. Applies to picking only; a short put always leaves a new put task for the remainder.
Example: The task is 10 units and the operator picks 7.
On: the task completes at 7.
Off: the task completes at 7 and a new pick task for 3 units is created, because damaged or missing stock was reported or the source location didn't have enough quantity.
Pick Full Pack
Applies when source stock is in a different pack type than the quantity needed.
On: the quantity is rounded up to whole packs.
Off: packs that would have to be broken are skipped.
Example: 30 units are needed and the source holds cases of 12.
On: the task takes 3 cases (36 units).
Off: the task takes 2 cases (24 units). The remaining quantity can be replenished with Units if available. (So it would be 2 cases + 6 units)
Allow Higher Pack Type Conversion to UOM
Converts higher pack types (for example, cases) to the UOM pack type when the pick is completed.
Example: A task picks 3 cases of 12 for a unit pick face. With the setting on, 36 units arrive at the target. For the pick and put flow, cases are converted once the pick tasks are completed. For the direct put flow, cases are converted at the single pick/put step, together with placing the stock at the target.
Only Replenish Full LPs
Replenishes whole single LPs only, as long as everything on the LP fits within the need. In Dynamic, the whole LP is given one target location; if none is found, all of that LP's tasks are removed.
Example: 100 units are needed. LP-1 holds 80 units and LP-2 holds 150. LP-1 is taken whole. LP-2 is skipped because it holds more than is needed.
Allow Scanning Another Put Location
Lets the operator put stock to a location other than the planned target.
Example: The task's target is A-01, but A-01 is blocked. With the setting on, the operator scans A-02 and completes the task there. With it off, scanning A-02 is rejected.
Allow Suggest Another
Lets the operator ask the system for a different target location.
Static offers another location that has a capacity for the same product and pack type and still has room: first one that can take the full task quantity, otherwise the one with the most room.
Dynamic runs the dynamic replenishment algorithm again, skipping locations already tried.
Example: The target A-01 is full.
In Static, the system offers A-07, which has a capacity for the same product and enough room.
In Dynamic, the algorithm suggests the next best location and won't suggest A-01 again.
Enable LP Swap
Lets the picker replace the assigned source LP with another LP of the same product at the same source location, as long as the new LP has inventory in the range of defined threshold. The target location doesn't change.
Example: The task says to take LP-100 from R-05, but LP-100 is behind another pallet. The picker scans LP-200, which holds the same product at R-05, and the task continues with LP-200.
Receiving Date Swap Threshold (FIFO) / Expiry Date Swap Threshold (FEFO)
Shown when Enable LP Swap is on. Number of days (±) the substitute LP's date may differ from the original LP's. 0 means the dates must match.
Example: A FEFO job type has a threshold of 5. The original LP expires on 10 January. A substitute expiring on 14 January or 8 January is accepted; one expiring on 20 January or 3 January is rejected.
Conditions
Conditions limit what the job type covers. All are optional, and wave rule conditions apply on top of them.
Condition group | Narrows down | Static vs. Dynamic |
Target Location Conditions | Which target locations are replenished | Static only. Disabled for Dynamic, where the dynamic replenishment algorithm decides the target |
Source Location Conditions | Which locations stock can be taken from | Same |
LP Conditions | Which LPs can be used, by LP type attributes | Same |
Product Conditions | Which products are replenished | Same |
To add one, click Add Condition under the group, choose the field, select the values and click Add Filter. Hover over a filter to see it, or click X to remove it.
Common questions
Can one job type run both Static and Dynamic? No. Each job type has one Replenishment Type. Create one job type per strategy and add both to the same wave rule if needed; they run in the order listed on the wave.
Do setting changes affect tasks that already exist? Settings apply to tasks created after you save. Tasks already created keep the settings they were created with.
Why don't I see Grouping? Grouping is only available for picking job types.
