Odoo 19 Batch or Wave Picking? Choose What to Group
Compare whole-transfer batches with split-line waves in Odoo 19, using a quantity example and a warehouse decision worksheet.
Applicability
Odoo 19 Inventory with Batch, Wave & Cluster Transfers, Storage Locations and Multi-Step Routes enabled. Warehouse configuration access is required. Barcode hardware and third-party warehouse extensions are outside this guide; confirm app availability in your subscription and deployment.
Research method
Official Odoo 19 batch and wave documentation research, with an invented allocation example and editorial decision checklist; no new Odoo warehouse test.
Choose batch when you want to group whole transfers. Choose wave when you need selected parts of transfers grouped separately. A wave is not simply a warehouse zone or a custom route. This distinction matters more than a promise to save a fixed percentage of walking time.
Contents
- Compare the unit of work
- Work through three orders
- Prepare the documented workflow
- Check stock and sorting
- Choose a first approach
Compare the unit of work
The batch documentation groups transfers into a picking list and describes sorting goods into orders afterwards. The wave documentation splits transfers before grouping selected lines. A wave can only combine lines from the same operation type.
| Decision | Batch | Wave |
|---|---|---|
| What is selected? | Whole transfers | Selected transfer lines |
| Practical starting point | Similar orders you can pick and sort together | A subset needs a different release time or grouping |
| Main control to plan | Separate picked goods back into orders | Track both selected and remaining lines |
These starting points are editorial choices, not measured performance claims. Both need a clear sorting and packing plan.
Work through three orders
Invented example, not an Odoo test: three orders are reserved for the same picking operation type. Product A is a cable; B is an adaptor.
| Order | A | B |
|---|---|---|
| HK001 | 2 | 1 |
| HK002 | 3 | 0 |
| HK003 | 1 | 2 |
| Total | 6 | 3 |
If all transfers are ready together, a batch can group the three transfers. Your packing worksheet still needs to allocate A as 2/3/1 and B as 1/0/2. Collecting six A items and three B items does not prove each order was packed correctly.
If you choose to handle A first, a wave can select the A lines. The B lines still need their own follow-up. Your worksheet should show:
A wave: 6 collected -> HK001:2 + HK002:3 + HK003:1
B pending: 3 -> HK001:1 + HK002:0 + HK003:2
Do not mark HK001 or HK003 complete merely because their A lines are finished. In a small Hong Kong warehouse sharing one packing bench, label the order containers before pooled goods arrive; otherwise saved travel can become extra sorting work.
Prepare the documented workflow
With configuration access, enable Batch, Wave & Cluster Transfers, Storage Locations and Multi-Step Routes in Inventory → Configuration → Settings. Confirm your actual picking and shipping route; enabling settings alone does not define your packing process.
For a batch, the operation card menu provides Prepare Batch. Choose the operation type and transfers, then confirm. Processing is separate: check quantities and validate the transfer. Confirm is not proof that picking has finished.
For a wave, use Prepare Wave from the relevant operation card menu, select the required lines, then Add to Wave. The official guide also documents automatic grouping by product or product category. It does not require the old article's duplicated zone routes or developer-mode propagation recipe.
Check stock and sorting
The batch guide distinguishes demand, reserved stock and completed quantities. A product missing from detailed operations may have no reserved stock; compare the full operations list and check availability. Incomplete processing can lead to a backorder decision. Do not treat a confirmed batch as a stock-availability guarantee.
For either method, keep a release sheet with order reference, expected quantity, picked quantity, packing container and remaining quantity. Assign one person to explain differences before dispatch.
Choose a first approach
- Take a representative set of orders and complete the allocation table above.
- Choose whole-transfer batching unless a specific split-line requirement justifies waves.
- Decide who sorts goods and where remaining lines are recorded.
- Record picking time, sorting time and errors separately when you evaluate the process in your own operation.
APAA has not measured savings for this example. For help defining the route and grouping rules, discuss your workflow with APAA.
Sources
- Odoo 19: Batch picking
Whole-transfer grouping, preparation, processing and backorders.
Source checked
- Odoo 19: Wave transfers
Split-line grouping, same-operation-type restriction and manual or automatic waves.
Source checked