Function · Picking
openWCS already plans the pick — allocation, cubing and batch planning are Built. The operator-facing execution layer is Roadmap: planned and designed, not yet implemented.
⚑ Pick execution is planned — not yet implemented. Pick planning below is live today.
Built today
Before anyone touches a tote, the hard decisions are made: what stock to commit, how it fits a container, and how to group lines into efficient work.
Orders are allocated to specific stock, respecting availability and the location model — so each line points at a real, reachable unit before work is released.
Lines are fitted into containers across multiple carton/tote sizes, so the planner knows how many of which size a set of orders needs before it hits the floor.
Batch-pick planning groups order lines into efficient pick work, the basis for wave / batch picking — the planning that execution will later drive against.
On the roadmap
The execution layer — confirming picks, guiding operators, running goods-to-person stations — is designed but not built. Framed honestly so you know exactly where the line is.
Planned: operator and goods-to-person pick confirmation that closes out a planned line against what was physically taken. Not yet implemented.
Planned: pick-by-light, pick-by-voice and RF-gun guidance so operators are directed line-by-line. Designed for, not yet built.
Planned: the full GTP-station workflow — presenting HUs, capturing the pick, releasing the carrier — on top of the ASRS retrieval that already brings units to the station.
At a glance
order ─► allocate → cube → batch-plan (built)
│
▼
┄┄┄ roadmap ┄┄┄ confirm · light/voice/RF · GTP station
Open & honest
The planning that feeds picking is the same engine behind slotting and ASRS retrieval. Execution is tracked in the open.