Create & run pick batches

A pick batch turns a pile of open orders into one walk through the warehouse. You build it with filters, the app sorts it by bin location, and a picker works through it on the web or the iPad picker.

Build a batch

Open the picking page and set your filters. A live preview shows how many orders and fulfillable units match before you commit.

• Timeframe — how far back to pull orders.
• Order tags — isolate priority, wholesale, whatever you tag in Shopify.
• Couriers — batch by how it ships.
• Product types — keep bulky lines out of the trolley run.

Which orders are eligible at all is controlled by an org-level financial-status allowlist (paid, authorized, pending — your call, set in picking settings). It applies to every batch, created from web or iPad.

Pick routes

Items in a batch are sorted by bin code so the walk is short. Bin codes come from your products — point OrderOps at the Product field, Variant field, or a custom stock-name field in settings. If you have drawn a warehouse map and the batch's bins are on it, the pick order follows a planned walking route across the floor instead of plain alphabetic bin order. Completed batches keep their original pick order.

Completion

A batch completes itself the moment every unit is picked — nothing pending, nothing partial. If you have known shorts or substitutions, force-close it manually instead. Both work from web and iPad. Completed batches show a Pack link that jumps straight into the shipping flow.

The pack–pick interlock

Packing usually starts before picking finishes. The moment a label is created for an order in your batch, that order's units lock: pickers see them as picked and cannot reduce the count below the locked floor. Locks are computed live from active shipments — there is no separate bookkeeping to drift. Void the label and the lock releases on the next refresh. This is what stops the same unit being picked twice. See the pack bench for the other side of the handshake.