Overview
Once a replenishment wave has worked out how much a location or product needs, Logiwa IO decides where that stock comes from. It looks only at eligible source locations and stock, ranks them by date, walking path and quantity, and assigns stock to tasks so the same units are never planned twice. The rules are the same for Static and Dynamic Replenishment, except where noted.
When this matters
Read this article when:
You want to understand why a task takes stock from a particular location or LP.
A task is split across several source locations.
You're deciding between FEFO and FIFO, or setting up source conditions.
Step 1: Which locations can supply stock
A location can supply stock only if:
Its Replenishment Location Type is Source.
It matches the Source Location Conditions on both the wave rule and the job type, if any are set (location group, zone, location type, area type, ABC code, custom fields).
The stock in it matches any Product and LP conditions on the wave rule and job type.
Example: The job type has the Source Location Condition Location Group = Reserve. Stock in bulk location B-10, which is in the Overflow group, is never used, even though B-10 is a Source location.
Step 2: Which stock can be used
Only free (unallocated) stock is used. Damaged and missing inventory isn't used.
Example: R-01 holds 40 units, 15 of them allocated to shipment orders. Up to 25 units can be taken from R-01.
Step 3: In what order stock is taken
Eligible stock is ranked in this order:
Date. Set by the job type's Replenishment Algorithm.
FEFO (default) takes the earliest expiry date first.
FIFO takes the earliest receiving date first.
Stock without a date is still considered.
Walking path priority. When dates are equal, the source location's walking path priority decides in ascending order, lowest walking path priority first.
Whole quantity. When still tied, a location that can cover the full quantity on its own is preferred over one that can only cover part of it.
Remaining locations. If no single location covers the need, it's filled from several locations in the same order.
Example (FEFO, 50 units needed, same walking path priority):
Location | Expiry | Free units |
R-01 | March | 20 |
R-02 | March | 60 |
R-03 | June | 100 |
R-01 and R-02 share the earliest expiry, so R-03 isn't used. Walking path priority is tied, so the location that can cover all 50 units wins. The task takes 50 units from R-02.
Step 4: LP and pack type rules
Rule | What happens | Example |
Matching pack type first (Static product capacity) | Stock in the capacity's pack type is used before other pack types | Capacity is in boxes. Boxes are taken before cases of the same product |
Other pack types | Converted to the needed quantity. With Pick Full Pack on, rounded up to whole packs; with it off, packs that would have to be broken are skipped | 30 units needed, source holds cases of 12. On: 3 cases (36 units). Off: 2 cases (24 units) |
Only Replenish Full LPs | Only whole single-SKU LPs that fit within the remaining need are taken | 100 units needed. An 80-unit LP is taken whole; a 150-unit LP is skipped |
Static LP capacity | Always moves whole single-SKU LPs of the capacity's assigned product | Capacity for 5 pallets of SKU-1: only full pallets holding only SKU-1 are used |
Step 5: No double-booking
Within one wave run, stock assigned to one task isn't offered to another.
Example: Two bins both need SKU-1, and R-02 holds 60 free units. The first bin's task takes 50 from R-02. The second bin can only get the remaining 10 from R-02, plus stock from the next location in order.
After the task is created
The source chosen at creation is what the operator sees on mobile. If Enable LP Swap is on for the job type, the operator can substitute another LP of the same product at the same source location. The source location itself doesn't change. See Understanding LP Swap in Replenishment.
Common questions
Why did a task take stock from a farther location? Date comes before walking path priority. With FEFO, an earlier-expiring pallet in a farther location is taken before a later-expiring one nearby.
Why is one task split across several source locations? No single eligible location had enough free stock to cover the full quantity, so the need was filled in ranked order across several locations.
Is stock without an expiry or receiving date ever used? Yes. It's still considered, ranked using walking path priority.
Can I stop replenishment from using certain locations? Yes. Add Source Location Conditions to the job type or wave rule, or change the location's Replenishment Location Type so it isn't Source.