Wave, Batch & Zone Picking
Wave/batch/zone picking: order clustering, pick-list optimization, picker assignment, wave progress
Wave, Batch & Zone Picking turns a pile of individual transfers into organised, trackable picking waves. Define named warehouse zones with an explicit walking order, cluster eligible transfers into waves by hand or automatically, optimize each wave's pick path by zone and location, and balance workload across a pool of pickers, with wave progress tracked live as transfers complete.
Key Features
Warehouse picking zones
stock.warehouse.zone is a named, sequenced group of stock locations (each location keeps its own in-zone sequence too), giving pickers an explicit walking order; every pick line inherits its zone from its own source location, enforced with a one-location-one-zone constraint.
Create Wave and Auto-Cluster wizards
The Create Wave wizard groups selected or filtered transfers (by channel, carrier, priority, zone or operation type) into one wave; the Auto-Cluster wizard buckets every eligible, unassigned transfer at once by any combination of those criteria, with an optional per-wave size cap that splits an oversized cluster into several sequential waves.
Pure-python clustering and pick-path engine
services/wave_picking.py implements cluster_pickings, optimize_pick_path, compute_progress and assign_pickers as framework-free functions, unit tested without a database.
Pick-list optimization
action_optimize_pick_list re-sequences every pick line of a wave by zone order then in-zone location order, storing the result on each stock.move.line's pick_sequence field so the picker's list is walked in physical order, not raw creation order.
Picker assignment and workload balancing
A picker can be assigned to a wave directly (action_assign_picker), or the Balance Picker Workload wizard spreads a batch of draft, unassigned waves across a pool of pickers with a largest-job-first greedy balancing pass that accounts for each picker's already-assigned load.
Draft to in-progress to done lifecycle
Each wave moves through a draft, in_progress, done (and cancelled) lifecycle validated by validate_transition: starting a wave reserves its transfers and assigns the picker, and it can only be closed once every transfer is done or cancelled.
Live wave progress tracking
Every wave computes its transfer count, completed count and completion percentage live from the state of its underlying transfers via compute_progress.
Traceable cluster criteria
Each wave keeps the channel, carrier, priority and zone filter it was built or auto-clustered from, so it stays clear afterward why a set of transfers ended up grouped together.
Use Cases
Screenshots
03 Zone List
04 Zone Form
05 Wave Creation Wizard
06 Auto Cluster Wizard
Why Choose This Module
Because the clustering, pick-path optimization, progress and picker-balancing logic all live in a single framework-free, unit-tested engine, the same decisions that used to require a warehouse management system are available directly inside standard Odoo Inventory, with every wave, zone and pick sequence a plain, reportable Odoo record.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: stock
- Support: odoo@gencbaris.com
- Update date: 2026-07-13
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Discuss (mail) |
| Lines of code | 1171 |
| Technical Name |
wave_batch_zone_picking |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module