Your pickers walk the whole warehouse for one order

Watch your warehouse for an hour and you will see the waste. A picker takes an order, walks to the far aisle, grabs one item, walks back, packs it, then takes the next order and walks to the same far aisle again. The picking itself - reaching for the product - takes seconds. The walking takes minutes, and you pay for it on every single order. At a handful of orders a day it does not matter. At D2C volume it is the reason your team is flat out and still behind. Odoo already has the tools to fix this. Most brands just never turn them on.

The real cost is the travel, not the pick

In any warehouse, the time to fulfil an order splits into travel and everything else. Travel - walking to the location, walking back - is usually the largest single share, and single-order picking maximises it, because every order is a fresh round trip. Two orders that both need a product from aisle 12 mean two separate walks to aisle 12. Three orders, three walks. The pattern scales badly exactly as your volume grows.

The fix is simple to state: fetch for more than one order per trip. If a picker collects the items for ten orders in one pass through the aisles, they walk the floor once instead of ten times. Same stock, same products, a fraction of the steps. That is the whole idea behind batch, wave, and cluster picking, and it is why moving off one-order-at-a-time is the highest-leverage change most growing warehouses can make. It builds directly on getting scanning right in the first place, which we cover in Odoo barcode scanning for warehouse operations.

Batch, wave, and cluster - what each one actually is

These three terms get used loosely, but in Odoo they are distinct methods for distinct problems. Pick by the problem you have.

• Batch picking. Group several orders into one batch and send a picker to collect everything on the list in a single trip. They fetch the total quantity of each product across all the orders, then the orders are separated at packing. Best when many orders share the same items - the classic D2C case where one hero SKU is in half the day's orders.
• Wave picking. Release orders to the floor in planned waves grouped by a rule that matters to you - a carrier cut-off, a delivery deadline, a warehouse zone, a priority customer. Wave picking is about timing and sequencing: making sure the orders that must ship on the next van are picked before it leaves, not whichever ones a picker happened to reach.
• Cluster picking. A picker carries several orders at once on a trolley of bins and, as they walk, drops each item straight into the bin for its order. Picking and sorting happen in the same pass, so there is no separate sortation step afterward. Strong for many small orders with few lines each - again, the typical D2C profile.

These are not mutually exclusive. A common setup waves the day's orders by carrier cut-off, then cluster-picks within each wave so the picker sorts as they go. The right combination depends on your order profile and your floor, which is the part worth thinking through before you touch settings.

Setting it up in Odoo

None of this needs custom development - it is configuration of the Inventory app plus the Barcode app. The pieces you work with:

• Operation types and a two-step flow. Move from pack-at-pick to a pick-then-pack flow so picking and packing are separate operations. That separation is what lets one picking operation serve many orders that are then packed individually.
• Batch transfers. Odoo groups multiple pickings into a batch transfer that a picker works as one list. You can build batches by hand or by a rule, and the picker sees a single consolidated set of items to collect.
• The Barcode app. On a scanner or phone, the picker scans each location and product as they go, which keeps stock accurate in real time and guides them along the batch. Scanning is what makes batch and cluster picking trustworthy - without it, collecting for ten orders at once is error-prone.

Because the whole flow runs on Odoo's own inventory engine, stock stays correct across every channel you sell on - the same accuracy that matters for a multi-channel inventory sync across Shopify, Amazon, and Flipkart. And once the flow is set, you can let Odoo build the day's batches automatically on a schedule rather than a manager assembling them each morning, using the approach in scheduled actions and automation rules.

Which method fits your volume

There is no single best method - there is the one that fits your order profile. If a few SKUs dominate your orders, batch picking gives the biggest instant win, because one trip to the popular aisle covers many orders. If your pain is missing carrier cut-offs and late dispatches, wave picking fixes the sequencing so the urgent orders go first. If you ship many small orders with one or two lines each - the everyday D2C shape - cluster picking removes the separate sorting step and usually wins on throughput.

The mistake is copying another brand's setup without checking your own numbers. Pull your real order data - lines per order, SKU concentration, how orders cluster by carrier and deadline - and let that choose the method. Getting this right is core to the warehouse management and inventory management work we do, and it usually pays back inside the first peak season. When the flow needs to reach beyond stock into orders and channels, it ties into a full Odoo implementation rather than a one-off tweak.

Frequently asked questions

Do I need the Odoo Barcode app for batch picking?

You can run batch picking on paper lists, but you should not at any real volume. Collecting items for many orders in one trip is where mistakes creep in - the wrong quantity, the wrong order - and scanning each product and location as you go is what keeps it accurate. The Barcode app also updates stock in real time, so your counts stay right while the picker works rather than after a later reconciliation.

What is the difference between wave and batch picking, simply?

Batch is about grouping orders to save walking - collect for several at once. Wave is about timing - releasing the right orders to the floor at the right moment so deadlines and carrier cut-offs are met. Batch answers "how do we walk less"; wave answers "which orders do we pick next". They solve different problems and are often used together.

Will this work with my existing Odoo without a custom module?

In most cases yes. Batch transfers, operation types, and the Barcode app are standard Inventory features. A custom module only comes in if you have an unusual routing rule or a specific device workflow the standard flow does not cover. The bulk of the value is configuration and training, not development.

How much faster is multi-order picking, realistically?

It depends entirely on your layout and how much your orders share items, so treat any single number with caution. The mechanism, though, is reliable: you are replacing many round trips with one, and travel is the largest slice of pick time. The denser your aisles and the more your orders overlap, the bigger the gain - which is exactly why measuring your own order profile first tells you what to expect.

The short version: if Odoo is picking one order per trip, your team is walking far more than they need to, and at D2C volume that walking is your throughput ceiling. Batch, wave, and cluster picking are already in Odoo - the job is choosing the mix that fits your orders and your floor, then setting it up with the Barcode app and batch transfers. Do that and the same team ships more, the cut-offs get met, and peak season stops being the thing you dread.