Wave picking vs zone picking: when each one wins

Wave picking and zone picking solve different problems.

Operators that confuse them end up with the wrong workflow for the warehouse they actually run.

Here is the honest comparison and when each one wins.

Wave picking — the one-line definition

Wave picking groups orders into release windows ("waves") that get picked together, typically batched by carrier cutoff, dispatch route, or customer priority. A morning wave for next-day delivery orders. An afternoon wave for same-day. An evening wave for marketplace SLA. Each wave is released to the floor as a single picking job.

The defining shape: orders are batched by *time and constraint*, not by warehouse geography.

Zone picking — the one-line definition

Zone picking splits the warehouse into geographic zones with dedicated pickers in each zone, where each picker only walks their own zone. A single multi-line order gets split across zones — each picker grabs their portion, the parts get consolidated at pack.

The defining shape: pickers are batched by *geography*, not by order release.

When wave picking wins

• High order volume with multiple carrier cutoffs per day
• Mixed SLA mix — same-day, next-day, standard — needing different release timing
• Marketplace SLAs (Amazon, TradeMe, eBay) requiring tight cutoff handling
• Predominantly single-line or low-line-count orders (the picker walks the warehouse once per wave)
• Operators where time-based prioritisation matters more than walk distance

Wave picking is the default for ecommerce 3PLs running multiple carriers and SLA tiers. Most ANZ DTC operations above 500 orders/day land here.

When zone picking wins

• Large warehouse footprint where pick-path distance is the bottleneck
• Multi-line orders with high SKU diversity (consolidating at pack saves total walk time)
• High-value or hazmat zones requiring restricted access
• Specialised zones (chilled, frozen, ambient) that need different handling
• Operators where walk distance and zone specialisation matter more than release timing

Zone picking is the default for wholesale distribution, B2B operations, and warehouses with mixed temperature zones or specialised handling.

When you can combine them (zone-wave)

Large operations run both — pickers are zoned, but each zone releases waves on the same cutoff schedule. Zone-wave is common at enterprise scale (Manhattan, Blue Yonder defaults). For ANZ SMBs, picking one strategy cleanly usually beats running both.

Other strategies in the family

For completeness: batch picking picks multiple identical-SKU orders together, cluster picking picks 4–8 orders simultaneously into a tote rack, and discrete picking is one picker, one order — the simplest and slowest strategy. Wave and zone are the two that matter for picking-strategy decisions at the WMS layer.

How OpsUI handles this

OpsUI's Warehouse module supports wave, zone, batch, cluster, and discrete picking — chosen per pick run, not locked in at setup. The pick screen on the picker's phone (Bluetooth scanner attached) tells them which strategy is running and what to do next. The strategy is data, not code.