Cluster picking sorts items into order-specific containers at the point of pick, letting one picker complete several orders in a single pass through the warehouse. For operations juggling many small-to-mid orders with overlapping SKUs, it typically cuts walking time and raises throughput. The catch: it demands a capable WMS or orchestration layer, real configuration work, and trained pickers, so it is not a fit for bulky items or low-volume, low-overlap SKU mixes.
TL;DR:
Table of Contents
What Is Cluster Picking and How Does the Workflow Run?
Picture a picker pushing a cart with a dozen totes instead of one. That is cluster picking. A batch of orders gets grouped into a “cluster,” either by the system based on rules you define or by a supervisor building the batch manually, and the picker works a single route that satisfies every order in that cluster at once.
The mechanics play out in a fixed sequence:
Compare that to discrete picking, where a picker completes one order start to finish, or zone picking, where each picker owns a fixed area and orders pass between zones. Cluster picking sorts items into order-specific containers during the pick, which is exactly what eliminates the sorting stage that batch picking still requires after the pick is done.
Cluster Picking vs. Batch, Zone, or Discrete Picking: Which Wins?
The right method depends on four variables: order volume, how much your SKUs overlap across orders, average item size, and the throughput you actually need. Get the mix wrong and you will add complexity without adding speed.
Retailers with e-commerce order profiles, dozens of small items per order, tend to see the strongest lift from cluster picking.
Configuring Cluster Profiles: The WMS Settings That Actually Matter
Cluster picking lives or dies on how you configure the cluster profile in your WMS. Get these fields wrong and pickers either walk too much or make sorting errors that erase your time savings.
Configuring cluster profiles correctly means setting positions, break rules, sort verification, mobile device menu items, and location directives before a single cluster ever hits the floor. System-directed cluster picking can auto-generate clusters up to the profile’s position limit, which is worth enabling once your SKU data is clean enough to trust the algorithm.
Pro Tip: Start every new cluster profile at half your cart’s physical capacity. Once error rates settle below your target for two full weeks, scale positions up incrementally rather than jumping straight to full capacity.
Process by Location vs. Process by Position: Two Very Different Flows
These two strategies change what a picker’s screen shows and how verification happens, and picking the wrong one creates friction you will feel every shift.
The choice is not cosmetic. It determines how much cognitive load you are asking pickers to carry per stop.
What Your WMS and Hardware Need to Support Cluster Picking
Cluster picking is not a training tweak, it is a technology decision. Before rolling it out, confirm your WMS actually supports the workload you are about to hand it.
Odoo’s cluster picking module requires enabling package tracking and assigning a dedicated destination package per order inside each batch, which is a useful reference point if you are evaluating whether your current WMS handles this natively or needs an orchestration layer bolted on top.
Pro Tip: If your WMS lacks real-time cluster reassignment, an orchestration layer sitting above it can often add that capability without a full WMS replacement.
Rolling Out Cluster Picking Without Wrecking Your Error Rate
Every operation that switches to cluster picking sees a temporary spike in errors. The question is how big and how long it lasts.
Practical experience shows initial error rates rise when verification and training lag the rollout, which is exactly why the pilot phase matters more than the go-live date.
Measuring ROI: The Metrics That Tell You If Clustering Is Working
Five numbers tell you almost everything: picks per hour, walking time per order, order cycle time, error rate, and labor cost per order. Track them before and after your pilot, not just after full rollout, or you will have no baseline to prove the change worked.
Cluster size is your biggest tuning lever. A modeling example using twelve-order clusters with forty-eight total items showed measurable walking-time savings against single-order picking, which is a useful reference point for sizing your own test batches before committing to a permanent cluster profile.
Watch error rate and cycle time together, not separately. A cluster size that boosts picks per hour while pushing error rate past your threshold is not a win, it is a hidden cost waiting to surface in returns and rework.
Review cluster performance on a set cadence, weekly at minimum during rollout, and adjust cluster size the moment SKU mix or order volume shifts meaningfully.
How Dynamic Orchestration Pushes Cluster Picking Further
Static clusters, built once at the start of a shift and left alone, run into the same problem every time: they cannot react to a rush order, a congested aisle, or a picker falling behind. Dynamic orchestration solves that by continuously re-evaluating cluster membership against live signals like deadlines, aisle congestion, and worker proximity, rather than locking a cluster’s contents in at creation time.
Lully applies that logic across the picking floor, and the company reports efficiency gains of 1.5 to 2 times standard throughput alongside labor cost reductions of up to 50% when orchestration replaces static wave and cluster scheduling. Those figures come from Lully’s own platform data, so treat them as a vendor benchmark to validate against your own pilot results rather than a guaranteed outcome.
Static clusters answer “what should this picker do right now.” Dynamic orchestration answers “what should every picker do right now, given everything changing at once.”
The implementation pattern is straightforward: keep your WMS as the system of record, layer orchestration on top for real-time reassignment, and measure the same KPIs you tracked in your pilot to confirm the lift holds at scale.
When Cluster Picking Actually Moves the Needle
Cluster picking earns its complexity when you have real scale and real SKU overlap. Under a few hundred orders a day with little overlap, the setup cost rarely pays back. Above that threshold, especially with e-commerce-style small item mixes, it consistently outperforms discrete picking.
My honest read: most operations underinvest in the pilot phase and overinvest in the technology purchase. Buy the orchestration layer after you have proven the workflow, not before. Start small, measure against a control group, then integrate orchestration once you know your cluster sizes and verification method actually hold up under real volume.
— Michael
See Dynamic Clustering in Action
Static cluster profiles get you partway there, but they still leave throughput on the table once conditions change mid-shift. Lully layers on top of your existing WMS to reassign cluster membership in real time, factoring in deadlines, congestion, and where your pickers actually stand on the floor, without asking you to rip out and replace the system you already run.
That approach is why operations running Lully report efficiency gains of 1.5 to 2 times alongside labor cost reductions of up to 50%, without adding robotics or physical automation to the floor. If your cluster picking pilot has proven the workflow but plateaued on throughput, the next step is worth taking: request a demo of the Lully orchestration platform and see how it performs against your own order data before your next peak season hits.
Where to Verify the Exact Setup Steps
For hands-on configuration, the Dynamics 365 cluster picking setup guide covers cluster profiles field by field, while the system-directed cluster pick documentation details auto-generation logic. Odoo’s cluster picking docs show an alternative batch-based approach, and WAPI’s explainer offers a clear conceptual overview for teams still evaluating the method.