Walk the aisle once
Run a wave for one site
Why this step
A wave is the other shape: part of many orders, together, because they are all going to the same tower on Thursday. It is how you load a lorry by destination rather than by paperwork.
What this does
Wave picking splits the lines of many orders into targeted runs: one wave collects everything from the cutting area, another everything for tomorrow's route, regardless of which order each line belongs to. It is the finer-grained sibling of batch picking — and like batch picking it is not enabled on this system: waves are part of the same uninstalled Batch Transfers module (they appear as an extra setting once batches exist). No wave menus or actions exist here today, so this page describes the capability honestly instead of walking through absent screens.
What enabling it would add
- Wave Transfers: pick individual order lines — not whole transfers — and group them into a wave by product, by location, or by whatever cut your floor plan needs.
- Automatic wave creation rules alongside the batch rules on the operation type.
- The same one-document workflow as batches: one responsible, one printed list, one validation for the wave.
In the meantime
The un-waved workflow is per-transfer picking, ordered by the transfer list's filters: group the Deliveries list by scheduled date or source document, work top to bottom, and let the removal strategy decide which units each line takes. It is less optimal walking, not less correct picking.
Asking for it
Waves come with the same module as batch transfers and are switched on as a second step after it. If line-level runs (all glass first, all hardware second) would genuinely change your floor's day, ask your WindoorERP administrator for batch transfers with wave picking enabled — they are one installation decision, taken fleet-wide.
Checkpoint
A single wave gathers everything going to one site on one day, across several orders.