Warehouse picking workflow: pick lists, scan checks and exceptions

GAO’s 2002 physical-count study documented picking errors among tracked variance causes, alongside receipt, location and shipping errors. A picking procedure defines how orders become tasks, how each pick is checked and what to record when the shelf differs from the task.

WarePulse builds a pick task per order with lines sorted by location, and on every plan batch picking groups orders into one walk. Each pick is verified by scanning the location and then the item, and for expiry-tracked stock the pick enforces the earliest-expiring lot, with an override that needs a reason.

Connect workflow fit to rollout context earlier.

WarePulse builds a pick task per order with lines sorted by location, and on every plan batch picking groups orders into one walk. Each pick is verified by scanning the location and then the item, and for expiry-tracked stock the pick enforces the earliest-expiring lot, with an override that needs a reason.

Warehouses whose picking errors come from look-alike SKUs.

Food and pharma warehouses that must ship the earliest-expiring lot first (all plans).

Teams moving from printed pick lists to handhelds.

WarePulse mobile app pick execution screen with active line progress and scan actions

Watch the floor app run the workflow

See receiving, task execution, picking, confirmations, and exception context move from the floor app into the operating view.

Compare related WarePulse options

Compare the next topics buyers usually review: implementation, pricing, trust, field evidence, and operating fit.

Plan the next warehouse step

Bring a day of orders and your location list, and we will run location-sorted, scan-verified picking on them with you.

Workflow steps

  • Release three orders and walk the location-sorted pick list.
  • Scan the wrong item at a location and see it refused.
  • Try to pick a later lot of an expiry-tracked item and read the request for an override reason on every plan.

Implementation planning

  • Label every location and item before go-live; scan verification needs a barcode at both.
  • The phone camera supports EAN, UPC, Code 128, Code 39, Code 93 and QR codes. Validate the hardware-scanner setup and supported formats on the devices you will use.

Questions to resolve

  • Do we need wave or zone picking? WarePulse offers batch picking on every plan; zone and cluster picking are not offered.
  • Will scanning slow pickers down? Test it on your own orders; a refused scan is an error caught before packing.

What WarePulse delivers inside this workflow

How WarePulse changes execution, handoffs, and reviewability inside this workflow.

Pick tasks per order with lines sorted by location.

On every plan, batch picking groups several orders into one walk, and allocation runs reserve stock for orders.

Each pick is verified by scanning the location, then the item, on iOS or Android, with an offline queue.

For expiry-tracked stock, the pick enforces the earliest-expiring lot; picking another lot needs a reason.

In the mobile ship-out flow, each line must be verified and exactly packed, and a tracking number is required before submission.

WarePulse mobile app task list and sync diagnostics for warehouse operators

What this workflow usually gets wrong

The process friction that quietly extends lead time, hides exceptions, and stretches labor.

1

Pick lists follow order-line sequence, so pickers walk back and forth across the building.

2

A look-alike item is picked because nothing checks the barcode.

3

Short picks are fixed quietly, so the record and the shelf drift apart.

Built for warehouses where this station is the bottleneck

The teams and roles this workflow impacts first.

Warehouses whose picking errors come from look-alike SKUs.

Food and pharma warehouses that must ship the earliest-expiring lot first (all plans).

Teams moving from printed pick lists to handhelds.

When the shelf does not match the task

A short pick, an empty location or the wrong item are the moments that decide record accuracy. Record the exception where it happened and count the location, rather than borrowing stock from another location without a trace. For expiry-tracked stock, WarePulse does not accept a later lot without a reason, so that exception is written down at the pick.

Sort pick lines by location before releasing them.

Scan the location and the item on every pick.

Count a location as soon as a short pick is found there.

Keep FEFO overrides rare and review their reasons.

How to roll it out

1

Allocate

On every plan, run allocation so stock is reserved for the orders being released.

2

Build the pick

Each order becomes a pick task with lines sorted by location; batch picking groups orders on every plan.

3

Scan each pick

Scan the location, then the item, and enter the quantity picked.

4

Handle exceptions

Record short picks and wrong-location finds where they happen, and count the location.

5

Verify at ship-out

In the mobile ship-out flow, every line is verified again and a tracking number is entered.

Frequently asked questions

Does WarePulse support wave or zone picking?+
Batch picking is available on every plan. Waves are used for FF&E project releases; zone and cluster picking are not offered.
What stops a picker taking the wrong item?+
The item scan: each pick is verified by scanning the location and then the item.
Can a picker take a later-expiring lot?+
Only with a reason. For expiry-tracked stock on every plan, the pick enforces the earliest-expiring lot.

Start with the station creating the most operational drag today.

Pick a day of orders with location-sorted lists and scan checks, then count the locations where you found short picks.

Plan the next evaluation step