Pick routes — sequenced warehouse walks
Pick routes define the sequence operators follow through warehouse bays. Dark Store Systems maps bays to routes, assigns routes to zones, and sorts pick jobs by PickRoutesMapping order during Picking_SortPickJobs. Admins create and reorder routes in the pick routes screen; the handheld walk follows that sequence automatically.
What are pick routes in Dark Store Systems?
A pick route is the ordered path a picker follows through warehouse bays. Instead of ad-hoc location order, the WMS resolves each bay to a route position and presents jobs in that sequence on the handheld.
Routes are configured in the admin Pick Routes screen (PickRoutesPage). Data lives in PickRoutes and PickRoutesMapping tables. Zones link to routes so each zone's bundle pick work inherits the correct walk order.
Pick route sequencing applies to bundle picking and batch picking walks — wherever Picking_SortPickJobs runs before the operator starts moving.
How does pick route sequencing work?
- Create a route — Admins define a named route in the pick routes screen. Each route is a ordered list of bays the picker will visit.
- Map bays to positions —
PickRoutesMappingstores bay-to-sequence relationships. Reordering bays in admin updates the walk order for future jobs. - Assign routes to zones — Zones reference a pick route. When an
OrderBundlebuilds for a zone, it inherits that zone's route for job sorting. - Sort jobs before the walk —
Picking_SortPickJobsorders pick jobs by route mapping position. The handheld presents the next bay in sequence — not database insert order. - Operator follows the handheld — The picker confirms each line at the sequenced location. Exceptions (skip, part-pick, DNP) do not break route order for remaining lines.
Route sequencing sits downstream of pick-face validation and upstream of consolidation or packing handoff.
Why does walk order matter on the warehouse floor?
Every unnecessary backtrack costs walk minutes. When fast movers sit early in the route and slow movers cluster logically, pickers complete more lines per hour without rushing.
In our experience, sites that treat route design as ongoing maintenance — not a one-off setup task — see fewer aisle crossings and less congestion at peak. Pair route sequencing with zone management so each zone's route reflects how stock actually sits on the floor.
Pick routes do not replace pick-face gates. A perfectly sequenced walk to an empty bay is still a wasted walk — validation blocks release before assignment.
What should I evaluate next?
- Bundle picking — zone pick-work units that consume route sequencing on the handheld
- Warehouse picking hub — full picking capability map
- Pick queue — supervisor control surface for releasing sequenced work
- Batch pick vs multi-order picking — batch pick also uses route sorting
For procurement security review, see Security.
Frequently asked questions
How do zones link to pick routes?
Each warehouse zone references a pick route in admin configuration. When bundle work builds for that zone, Picking_SortPickJobs sorts jobs using the zone's assigned route and PickRoutesMapping bay positions. Changing a zone's route affects future walks — not walks already in progress.
Can I reorder bays on an existing route?
Yes. Admins edit bay order in the pick routes screen. Updated PickRoutesMapping positions apply to newly sorted jobs. Operators on active walks continue their current sequence until walk exit.
Does pick route sequencing apply to batch pick?
Yes. Picking_SortPickJobs sorts jobs for batch pick walks (pick flow 3) as well as bundle pick (pick flow 1). Route configuration is shared — zones and bays map the same way regardless of pick mode.
Do pick routes optimise themselves automatically?
No. Routes are admin-configured walk sequences — not an autonomous AI picker. The zone management and layout tools help plan the floor; pick routes translate that plan into handheld job order.