On this page
- How it works
- Core distinction: cluster vs batch picking
- WMS requirements and vendor landscape
- Benchmarks and productivity
- Cart configuration: the 6-tote sweet spot
- Volume thresholds and when to use cluster picking
- Cluster picking in fashion and apparel
- Picking technology: scan-to-tote vs voice picking
- Training considerations
- Robotics and automation context
- Key terms
Cluster Picking
Cluster Picking
Cluster picking is a warehouse order fulfillment method in which a single picker simultaneously collects items for multiple customer orders in one trip through the warehouse, depositing each item into its assigned tote on a multi-compartment cart as it is picked. The defining characteristic is that sorting occurs at the pick face during the pick walk — no separate sorting step is required after the pick is complete.
How it works
A WMS (Warehouse Management System) assigns multiple orders to a single cluster, allocates each order to a specific tote slot on the picker's cart, and generates an optimised pick route. The picker walks the route once, scans each item, and the WMS confirms which tote to place it in (scan-to-tote logic). When the cluster is complete, each tote contains a fully sorted, ready-to-pack customer order.
Cluster picking requires three WMS capabilities that distinguish it from simpler Batch Picking (ShipBob; DCL Logistics; r/wms, 2024-10):
- Scan-to-tote validation — WMS confirms the item-to-tote assignment at the pick face, not at a downstream sort station
- Intelligent cluster grouping — orders are grouped by proximity and SKU overlap to minimise travel distance
- Route optimisation — the WMS generates pick sequences minimising total walking distance across all orders in the cluster
Microsoft Dynamics 365 Supply Chain Management supports cluster picking natively via configurable cluster profiles specifying position count, cluster break conditions, and sequencing/verification logic; putaway clusters are a separate D365 feature (picking multiple license plates for different putaway destinations in a single trip), distinct from pick clusters. (D365 Advanced Warehouse Management, YouTube, 2025-02-02)
Core distinction: cluster vs batch picking
Terminology inconsistency: ShipBob's blog states "cluster picking is another term for wave picking," treating them as synonymous [https://www.shipbob.com/blog/cluster-picking/]. Optioryx, Pulpo WMS, and the r/wms practitioner community treat them as distinct: wave picking is temporally scheduled (orders dispatched in time-based waves) while cluster picking is spatially organised (orders grouped by cart proximity) [https://www.optioryx.com/blog/cluster-vs-batch-picking; https://blog.pulpowms.com/cluster-pick]. The conflation appears to be imprecision in ShipBob's framing rather than industry consensus.
The structural separation that matters in practice is cluster vs batch:
| Dimension | Cluster picking | Batch Picking |
|---|---|---|
| When sorting occurs | During the pick walk (at pick face) | After the pick (at put wall or sort station) |
| Physical infrastructure | Multi-tote cart only | Requires Put Wall, conveyor sorter, or staging area |
| WMS complexity | Higher (scan-to-tote, cluster grouping) | Lower (SKU grouping only) |
| Capital cost | Low (carts + totes + WMS config) | Higher (put wall infrastructure) |
| Best for | High-SKU-diversity, 1–5-item orders | High-SKU-commonality; very high volume (15,000+ orders/day) |
r/supplychain practitioners summarise this as "moving sort" (cluster) vs "fixed sort" (batch): "cluster picking = sort at the cart (moving sort). Batch picking = sort at a fixed location (fixed sort). The physical infrastructure requirements follow from that." (r/supplychain, 2023-12, comment score 12)
The r/supplychain "moving vs fixed sort" framing is from December 2023. The distinction is definitional rather than market data — low drift risk. Included because no newer source covers this angle more clearly.
Amazon nomenclature: an ex-Amazon industrial engineer confirms Amazon calls its cart-with-totes system "batch picking" internally but describes it as operationally cluster picking: "What Amazon calls 'batch picking' is operationally cluster picking — you're sorting to totes during the pick walk, not after. Amazon uses the term 'batch' generically to mean 'multiple orders at once' which isn't the standard industry definition." (r/AmazonFC, 43-upvote post, comment score 31, 2024-07)
r/supplychain (21-upvote post, 2024-10) confirms the terminology is inconsistent across industry: "a lot of operations use the terms interchangeably, which causes confusion... In practice, many operations that call themselves 'batch picking' are doing what academics would call cluster picking, and vice versa."
TGW Logistics (YouTube, 2026-04-27) adds a practical constraint of pure batch picking that cluster picking avoids: in a batch environment, orders are interdependent, making it difficult to prioritise urgent orders during the pick walk without disrupting the entire batch.
WMS requirements and vendor landscape
r/wms practitioners (31-upvote post, 2024-08) rate WMS cluster picking support as follows (as-of 2024-08):
| WMS | Cluster picking capability |
|---|---|
| Manhattan Active WM | Excellent — native scan-to-tote, sophisticated configurable grouping |
| Blue Yonder | Adaptive clustering adjusting in real-time to pick progress; "variant similarity" flag for fashion |
| Körber | Solid but more basic grouping logic |
| SAP EWM | Cluster grouping described as "fairly rigid" — one of SAP's weaker areas |
| Deposco | Mid-market; good for <~5,000 orders/day |
Mid-route exception handling: Manhattan Active WM and Blue Yonder can dynamically reassign affected orders to a new cluster or discrete pick when a mid-route stockout occurs. Körber and Deposco create a pick exception requiring supervisor intervention. (r/wms, comment score 14, 2024-08) These are vendor-sourced self-described capability claims — independent verification not found.
A r/wms comment highlights that cluster grouping algorithm quality can create a 20–30% pick rate difference: "Naive implementations just fill a cluster until it hits a limit. Smarter implementations run optimisation across order SKU overlap to minimise picker travel." (r/wms, 2024-10)
For fashion specifically: Blue Yonder has a "variant similarity" flag natively that prevents orders requiring similar-style/colour items from appearing in the same cluster (reducing visual confusion mis-sorts). Manhattan Active WM requires custom configuration to achieve this constraint. (r/fulfillment, comment score 15, 2024-10)
Benchmarks and productivity
[!unverified] ShipBob reports cluster picking increased picking speeds "tenfold" for client Earthley (ShipBob blog, vendor claim — potential conflict of interest; no independent verification found). [https://www.shipbob.com/blog/cluster-picking/]
Practitioner-reported benchmarks (as-of 2024-11, r/warehouse IE analyst, 38-upvote post — highest-signal dataset in this research run):
| Method | Pick rate (picks/hr) | Walk time share | Mis-sort rate |
|---|---|---|---|
| Discrete / single-order | 80–120 | 40–60% of pick time | Low |
| Cluster (4–6 tote cart, optimised) | 180–240 | 15–25% of pick time | ~0.8% (apparel DC) |
| Batch to put wall (effective combined) | 180–200 | — | ~0.3% |
An apparel 3PL manager (r/wms, 2024-10) reports a 35% improvement vs discrete after 6 months: ~190 picks/hour for cluster pickers vs ~140 discrete; experienced cluster pickers reach ~220/hour.
A DC manager (r/warehouse, comment score 22, 2024-11) notes measurement differences: some sites count "order lines per hour" rather than individual picks. Cluster picking yields 45–55 order lines/hr; at an average of 3 items per order, this translates to 135–165 individual picks/hr.
The core efficiency mechanism: travel time accounts for 50%+ of total picking time in traditional discrete operations (Getproductiv; multiple sources). Cluster picking amortises travel cost across multiple orders simultaneously. An IE analyst (r/warehouse, 2024-11) reports walk time drops from 40–60% of pick time (discrete) to 15–25% with a 6-tote optimised cluster.
A 2024 MDPI Sustainability journal study found that increasing SKU density by ~28% from a base of 5.55% nearly doubles pick distance performance in ecommerce warehouses, confirming that Slotting Optimisation directly amplifies or dampens cluster picking efficiency. [1]
CognitOps notes that pick rate benchmarks range from 60–300 picks/hr depending on operation type, product mix, layout, and method — making cross-operation comparisons misleading without context. (CognitOps, as-of 2026-07-05)
Picking operations account for approximately 50–65% of total warehouse labour costs (Getproductiv; Episode 4 YouTube, 2026-03-29), making pick method selection one of the highest-leverage operational decisions.
Cart configuration: the 6-tote sweet spot
r/warehouse practitioners confirm 6 totes as the sweet spot: "We tested 4, 6, and 8 tote configurations. 6 totes was our sweet spot — at 8 totes we saw 12% higher mis-sort rate and the pickers slowed down because managing the cart in narrow aisles was harder." (r/warehouse, comment score 19, 2024-11, corroborated by IE analyst in same thread at score 16)
Cart orders per trip: DCL Logistics cites 8–12 orders per cluster picking trip for experienced pickers [https://dclcorp.com/blog/inventory/cluster-picking/] VS Interlake Mecalux states up to 6 orders simultaneously in pick-to-tote setups [https://www.interlakemecalux.com/blog/cluster-picking] VS Optioryx says 6–12 totes. The discrepancy likely reflects cart design and order line-count differences rather than a fundamental disagreement. Neither DCL nor Mecalux figure is sourced from a controlled study.
A r/wms commenter identifies cart physical design as an under-discussed mis-sort contributor: "Pickers need to be able to see the tote labels clearly while moving. We had issues with totes positioned too far back on the cart — pickers were mis-sorting because they couldn't easily read which tote was which. Colour-coded totes + clear label positioning reduced our mis-sort rate by about 40%." (r/wms, comment score 4, 2025-06)
Volume thresholds and when to use cluster picking
Practitioner-reported volume guidance (as-of 2024–2025):
| Volume | Recommended method |
|---|---|
| < 800–1,000 orders/day | Discrete picking — cluster picking overhead not yet justified (r/wms, 2025-06, score 6) |
| 800–~20,000 orders/day | Cluster picking — lower capex than put wall; efficiency advantage clear (r/wms, 2024-10, score 9) |
| ~15,000–20,000+ orders/day | Batch + automated sorter begins winning on throughput (r/warehouse, 2024-11, score 13) |
Crossover volume: r/wms 3PL practitioner puts cluster advantage at "under 20,000 orders/day" (score 9, 2024-10) VS r/warehouse large-FC practitioner puts the batch+sorter crossover "around 15–20K orders/day" (score 13, 2024-11). The range is consistent; the lower bound is disputed. No controlled study found.
r/supplychain practitioners (34-upvote post, 2024-08) note a key cluster picking flexibility advantage over batch + put wall: "cluster picking throughput can flex up or down with headcount. During seasonal peaks, cluster picking scales more gracefully — just add pickers and carts, no infrastructure change needed."
Order profile guidance: cluster picking works best for orders of 1–5 items. Where a significant portion of orders have 10+ items, batch + put wall handles those better. For operations with 60%+ of orders at 1–3 items, cluster picking is the clear recommendation. (r/supplychain, comment scores 19 and 19, 2024-08)
Hybrid routing is common in mature operations: small orders (1–5 lines) → cluster picking; large orders (10+ lines) → discrete or zone picking; WMS routes automatically by order profile. (r/wms, 2025-06, score 5)
Cluster picking in fashion and apparel
Apparel fulfillment presents specific cluster picking challenges due to size/colour/style variant complexity.
Mis-sort rates and costs (as-of 2024-10): a r/fulfillment apparel ops practitioner (27-upvote post, 2024-10) reports mis-sort cost of £12–18 per incident including return shipping, restocking, and customer satisfaction impact; 1% mis-sort on 5,000 daily picks = ~£750/day in recoverable cost.
r/warehouse DC reports 0.8% cluster mis-sort rate vs 0.3% batch + sorter — cluster's mis-sorts are caught at packing (item in wrong tote), while batch picking misses can propagate further before detection. (r/warehouse, comment score 11, 2024-11)
Practitioner-reported mitigations (as-of 2024-10):
- Mandatory barcode scan at tote drop, not just at pick — reduced mis-sort rate from ~4% to ~0.7% (r/fulfillment, comment score 21 — highest-signal mitigation in dataset, 2024-10)
- WMS cluster grouping rule: never assign two orders requiring the same style/colour combination to the same cluster unless both orders are the same size
- Physical tote colour-coding by size range — reduces picker cognitive load at pick face
Cart sizing for fashion: practitioners recommend capping cluster size at 4–5 totes for fashion (vs 6 for general merchandise). Mis-sort cost in fashion is reported as 5–10x higher than general merchandise. (r/fulfillment, comment score 10, 2024-10)
Size curve and sparse routes: fashion SKU distribution follows a bell curve (more M and L than XS and XXL). Cluster pick routes for popular sizes are densely routed; rare sizes have sparse pick locations. The WMS must handle sparse pick routes efficiently or rare-size orders slow down the whole cluster. (r/fulfillment, comment score 9, 2024-10)
Ghost inventory risk: returned items placed back into active pick locations before quality checking create ghost inventory — WMS records the location as stocked but the returned item may be damaged or mislabelled. Mitigation: quarantine zone with quality check and label verification before returning to active pick. (r/fulfillment, comment score 17, 2024-10)
Seasonal replenishment collisions: new-season arrivals disrupt cluster routes if the WMS does not handle mid-shift replenishment gracefully. Practitioner mitigation: morning shift = steady-state picking; afternoon shift = pick + replenishment in separate zones. (r/fulfillment, comment score 12, 2024-10)
GXO + KNAPP automation case (fashion DTC Tilburg, Netherlands):
Published approximately 2022. No updated quantitative results (2024–2025) found publicly.
GXO Logistics deployed the KNAPP Pick-it-Easy Robot at its fashion ecommerce DC in Tilburg, Netherlands — described as an industry-first application for automated pocket induction in apparel logistics. AI vision identifies each product and optimal grip point before placing items into a pocket conveyor for sorting, grouping, and routing to packing stations. A patent-pending retry process handles misaligned apparel items — the robotic arm re-locates garments that slip on the conveyor. [2]
Picking technology: scan-to-tote vs voice picking
| Technology | Speed | Accuracy | Best for |
|---|---|---|---|
| Scan-to-tote (handheld) | Baseline | ~0.4% errors after training | Apparel and size variants |
| Voice picking | 15% faster initially; 8% slower after training | ~1.2% errors in noisy environments | High-velocity, uniform items |
| Ring scanner | Slightly faster than handheld | Similar to scan-to-tote | General purpose |
Source: r/warehouse DC tech lead trial (22-upvote post, 2025-01). Single-facility outcome — not a controlled study.
A practitioner hybrid approach: voice for high-velocity, uniform items (accessories, books) where item confirmation is less critical; scan-to-tote for apparel and size variants where the barcode provides definitive item confirmation unavailable with voice. (r/warehouse, comment score 16, 2025-01)
Vision-based confirmation (emerging, 2025): camera on the cart confirms item SKU before tote assignment is confirmed in WMS. Described by an r/warehouse IE consultant as "not mainstream yet but worth watching as a trend for the next 2–3 years." (comment score 14, 2025-01)
Training considerations
r/warehouse and r/fulfillment practitioners report cluster picking requires approximately 2–3x longer training than discrete: competency in discrete picking takes ~1 week; cluster picking requires ~2–3 weeks due to the cognitive load of managing cart layout, tote assignments, and scan-to-tote confirmation habits. Experienced discrete pickers can be harder to train to cluster picking than new hires due to ingrained single-order mental models. (r/warehouse, comment score 14, 2024-11; r/fulfillment, comment score 10, 2024-09)
Common picker errors (r/fulfillment training manager, comment score 17, 2024-09):
- Placing item in tote without scanning to confirm — most common and highest-impact error
- Forgetting to check tote colour/number before placing
- Moving to the next pick before confirming the current one is registered in the WMS
- Not managing cart orientation — tote position on the cart should be consistent throughout the pick walk
Robotics and automation context
AI-powered piece-picking robots can handle millions of unique SKUs and reach 1,200 picks/hr in optimised deployments (PatSnap tech landscape, 2026). These compete with or complement cluster picking by automating the sortation step cluster picking performs manually.
Global piece-picking robots market: USD 1.7 billion in 2025, projected USD 2.58 billion by end 2026, forecast USD 20.78 billion by 2031 at 51.78% CAGR — driven by labour shortages, ecommerce parcel growth, and AI accuracy improvements. (Mordor Intelligence, 2025, as-of 2025)
Goods-to-Person (GTP) systems eliminate the unproductive walk time that consumes 50%+ of a picker's shift in traditional operations — solving the same travel-time problem as cluster picking but through automation rather than route optimisation. (NetSuite)
Key terms
| Term | Meaning |
|---|---|
| Scan-to-tote | WMS-driven confirmation that an item has been placed in the correct order tote at the pick face |
| Cluster | A set of customer orders grouped by the WMS for simultaneous picking in one cart trip |
| Moving sort | Informal term for cluster picking — sorting happens as the picker moves (vs fixed sort for batch) |
| Fixed sort | Informal term for batch picking — sorting happens at a stationary put wall or sorting station |
| Cluster profile | WMS configuration object (e.g., in D365) specifying cluster size, break conditions, sequencing logic |
| Zone-cluster hybrid | Cluster picking operated within a defined warehouse zone |
| Pick face | The storage location where an item is physically retrieved during picking |
| Ghost inventory | Stock the WMS records as available but that is physically absent, damaged, or mislabelled |
References
- MDPI, 2024-07, peer-reviewed [ — www.mdpi.com/2071-1050/16/14/5953]
- Covariant / KNAPP, approx. 2022 [ — covariant.ai/insights/gxo-solves-apparel-picking-challenges-with-the-knapp-pick-it-easy-robot-powered-by-the-covariant/]