Batch pick vs multi-order picking — what is live today
Batch picking in Dark Store Systems uses OrderPickBatch jobs and pick flow 3 to group work across orders — fully implemented in the WMS. Multi-order pick appears as a pick-method label, but the distinct multi-order admin screen is currently mock. Buyers should evaluate batch pick and bundle pick as production paths.
What is batch pick in Dark Store Systems?
Batch picking groups pick work across multiple orders in a single walk. The WMS uses OrderPickBatch jobs and Orders_BatchPick* backend operations — pick flow 3 in the live system.
Operators on a batch walk collect items for several orders at once, then sort or place into order-specific totes depending on site configuration. Batch pick shares infrastructure with bundle pick: pick routes sequence the walk, pick-face validation gates release, and exception handling (skip, part-pick, DNP) applies the same way.
Batch pick is the live multi-order mechanism in the WMS. When procurement asks "can you pick multiple orders in one walk?" — the answer is batch pick, backed by real job names in the codebase.
What is multi-order picking — and is it live?
"Multi-order pick" appears in the admin app as a pick-method hint (multi_order_pick) and on marketing feature pages. However, the dedicated multi-order picking admin screen — with optimised grouping and customer-based batching UI — is currently mock. Mock screens carry footer disclaimers in the admin app.
This guide exists because buyers confuse mock UI with production capability. Dark Store Systems would rather tell you what ships today than oversell a roadmap screen.
| Mode | What it is | Live in WMS |
|---|---|---|
| Batch pick | OrderPickBatch jobs across orders (pick flow 3) | Yes — fully implemented |
| Bundle pick | Zone pick-work units per order (pick flow 1) | Yes — default scanner walk |
| Multi-order admin screen | Grouping UI with optimised/customer views | No — mock with disclaimer |
| Cluster picking | Industry term; one picker, multiple orders in cart cluster | No — no WMS backend mode |
When should I use batch pick instead of bundle pick?
| Factor | Bundle pick | Batch pick |
|---|---|---|
| Best for | Multi-zone orders; parallel zone pickers | High-volume single-zone or shared-SKU waves |
| Pick flow | Pick flow 1 (pick-then-pack) | Pick flow 3 |
| Work unit | Zone-grouped OrderBundles |
OrderPickBatch across orders |
| Consolidation | Common for multi-bundle orders | Sort-to-tote during or after walk |
| Live in WMS | Yes | Yes |
Neither mode is kit or BOM pick-as-one-SKU. Both remain line and product-instance based. See product bundles vs pick bundles for catalog kit naming.
Release timing from the order pool affects both modes — do not flood the floor before pick queue validity checks pass.
What should I evaluate next?
- Bundle picking — zone pick-work units in detail
- Multi-order picking feature page — roadmap context (mock UI clearly labelled)
- Warehouse picking hub — full capability map including paper pick
- Cluster picking myths — honest guide to industry terms not built in the WMS
For procurement security review, see Security.
Frequently asked questions
What is batch pick in Dark Store Systems?
Batch pick uses OrderPickBatch jobs and pick flow 3 to group pick work across multiple orders in one walk. Backend operations include Orders_BatchPick*. It is fully implemented in the live WMS — not a demo screen.
Is the multi-order picking screen live?
No. The dedicated multi-order picking admin screen with optimised grouping is currently mock UI with footer disclaimers. Batch pick is the live multi-order mechanism. Evaluate batch pick and bundle pick as production paths.
When should I use batch pick instead of bundle pick?
Use bundle pick when orders span multiple zones and parallel pickers improve throughput. Use batch pick when high-volume waves share SKUs and a single walk across orders is more efficient. Both paths use pick routes and pick-face validation.
Is batch pick the same as cluster picking?
No. Cluster picking (one picker, multiple orders in a cart cluster) is common industry terminology but is not implemented as a WMS backend mode in Dark Store Systems. Batch pick groups work via OrderPickBatch — a different execution model. See the cluster picking guide.