Function · Replenishment Built
Replenishment keeps forward pick faces stocked from reserve. openWCS works min/max with the right urgency, tops faces off opportunistically in off-peak windows, and skips reserve entirely with direct-to-pick when inbound can go straight to the face.
How it works
Fixed pick faces carry a SKU+UoM with a minimum and a maximum. openWCS watches the level and chooses how — and how urgently — to refill.
Drop below min and a refill is raised — emergency if the face is empty and blocking picks, scheduled otherwise so routine refills don't jump the queue.
In quiet windows every face is topped up to max, so disruptive hot replenishments during peak are avoided and the floor starts each rush full.
If a forward face has headroom below its max, inbound is routed straight there — skipping a reserve put-away and a later replenishment trip entirely.
Refills carry a priority so an empty, picking-blocked face is served ahead of a face that is merely below min — work is sequenced by what actually hurts throughput.
Replenishment draws from reserve and automated blocks, reusing the same movement layer as put-away — one mover network, not a separate pipeline.
Min, max and the off-peak window are configuration per face, so you set the trade-off between carrying buffer and trip count yourself.
Step by step
At a glance
inbound (SKU, HU) ─► forward face has headroom? ── yes ─► direct-to-pick (cross-dock)
│ no
▼
reserve put-away
face below min ─► replenishment ── empty? ─► EMERGENCY
└─ else ──► SCHEDULED
off-peak window ─► top every face up to max
Configurable & open
Replenishment shares the slotting engine's location model and the conveyor/ASRS movers. Read the slotting deep dive for how those faces are chosen in the first place.