Replenishment Lanes
A Replenishment Lane describes one flow of stock inside a Warehouse: from a source area into a destination area, such as Reserve into Case Pick or Case Pick into Each Pick. The Lane owns the "where" of replenishment. Replenishment Policies attach to a Lane and own the "when" and "how much" for the SKUs they select. Splitting the two means several Policies can fill the same pick area with different thresholds, and a Warehouse with a multi-step flow can describe each step once.
Every Replenishment Policy belongs to exactly one Lane, and a SKU takes part in a Lane only when it matches an active Policy in that Lane. The Replenishment Report then shows one need per SKU per Lane.
Location Profiles name the areas of the Warehouse: where stock waits in reserve and where it is picked from.
How to Create a Replenishment Lane
- Navigate to System -> Operations -> Replenishment Lanes and click Create Replenishment Lane.
- Choose the Warehouse first. A Lane stays in the Warehouse it was created in, and changing it on a new Lane reloads the Profile and upstream Lane choices.
- Fill in the remaining fields (see the table below) and click Save Replenishment Lane.
| Field | Description |
|---|---|
| Name | A descriptive name, for example "Reserve to Each Pick". |
| Code | A short identifier using lowercase letters, digits, and hyphens. It must be unique within the Warehouse and appears beside the name on the Replenishment Report. |
| Active | Only active Lanes produce needs. Two active Lanes in the same Warehouse must not share destination Locations. |
| Destination Profile | The Location Profile whose Locations this Lane fills. Policies in the Lane measure coverage in these Locations. |
| Source Profile | Optional. The Locations stock is drawn from. Leave it empty to source from all eligible stock outside the destination. A source may not share Locations with the destination, because a Location cannot be both supply and demand for one Lane. |
| Upstream Lane | Optional. The Lane that feeds this Lane's source, for describing a cascade such as Reserve feeds Case Pick feeds Each Pick. A Lane cannot be its own upstream, and the chain cannot form a loop. |
| Sort Order | When a SKU matches Policies in more than one Lane, it produces a need only in the Lane with the lowest Sort Order. Ties are broken by the order the Lanes were created. |
Rules Between Lanes
ShipStream blocks a save that would leave two active Lanes fighting over the same shelves, or a Lane whose source overlaps its own destination. If a Location Profile is later edited so that overlap appears anyway, the next replenishment build suppresses the affected Lane and the Replenishment Report shows a Lane conflict advisory naming the Lanes involved until you correct the Profiles.
An active Lane that already has Replenishment Policies cannot have its destination changed. Deactivate the Lane or move the Policies first.
Reading the Grid
The grid at System -> Operations -> Replenishment Lanes lists each Lane's Code, Name, Warehouse, Active state, Destination Profile, Source Profile (shown as All eligible stock when empty), Upstream Lane, Sort Order, and Updated At. It is sorted by Sort Order so you can read the precedence between Lanes at a glance. Click a row to edit the Lane.
Deleting a Replenishment Lane
A Lane cannot be deleted while any Replenishment Policy uses it, while another Lane names it as upstream, or while it still appears in the Warehouse's published replenishment results. Remove those references, wait for the next publication if needed, then click Delete Replenishment Lane on the Lane's form.