Quick answer
Choose the simplest picking method that matches the work your team needs to complete. Use regular picking for straightforward picking, pick/pack when one operator is picking and packing, route picking when route planning matters, and batch picking when similar orders can be grouped.
Safe stop/escalate checklist
Start here: Start in Fulfill Orders or the picking queue your supervisor assigned.
Do this first: Confirm the warehouse, merchant, order set, and whether the job needs regular picking, pick/pack, route picking, or batch picking.
Stop if you see these states/errors: Stop before creating route or batch work if the order set, browser action visibility, role permission, or expected method is unclear.
Who owns the blocker: Associate: follow the assigned queue. Supervisor: choose the method and approve route/batch work. Support: investigate missing actions or unclear blocker evidence. Product/Engineering: clarify route/batch action semantics and UI visibility issues.
What evidence to send: Warehouse, merchant, queue or saved view, intended picking method, order count, example order IDs, visible action state, screenshot, timestamp.
Common use cases
Warehouse lead: Decide which picking method to train or use for a shift.
Picker: Understand why a queue is regular, route, batch, or pick/pack work.
Support: Help an operator avoid starting the wrong workflow.
When to use this
A team is deciding how to process a group of ready orders.
Operators see several pick-related tabs and are not sure which one to use.
You are preparing a repeatable fulfillment process for a merchant or warehouse.
Before you start
Confirm the warehouse and merchant context.
Confirm whether the work needs route planning, batching, or one-order-at-a-time handling.
If a workflow may create live picking, route, or batch work, review the order set before starting.
Steps
Use regular picking when orders are ready to pick and do not need route optimization or batch grouping.
Use pick/pack when the operator is picking products and building the package in the same activity.
Use route picking when the warehouse wants route-based work for a specific order set.
Use batch picking when similar orders can be grouped operationally.
Use saved Fulfill Orders views when the same filtered order group will be reused.
If unsure, start with the least specialized workflow and ask support before creating routes or batches at scale.
Screenshots
Screenshot: Use Fulfill Orders to compare pick, route, batch, and pick/pack queues before choosing a workflow.
Screenshot: Use Tote Manager context when your workflow depends on tote setup, labels, or tote scanning.
What good looks like
The team chooses a workflow that matches the operational job and avoids creating route or batch work when a simpler pick flow would be safer.
Common issues and next actions
If this happens | What to do next |
The team sees too many pick tabs. | Start by asking whether the work needs route planning, batch grouping, or pick/pack. If not, use regular picking. |
The route or batch action is not visible. | Check browser width and role/access, then contact support with the view and screenshot if the action is still missing. |
The team is unsure whether grouping orders is safe. | Pause before creating batch or route work and confirm the warehouse process. |
Contact us when
Contact support when the team cannot identify the right picking method, an expected action is missing, or choosing the wrong workflow could affect live fulfillment work.
Send us this information
Warehouse and merchant.
Visible queue or saved view name.
Picking method you expected to use.
Order count and one or two example order IDs.
Screenshot with private customer data masked.