Quick answer
Use picking routes when a supervisor needs to turn eligible orders into route-based picking work. Start from a saved Fulfill Orders view when you want a specific order set, or from Batch Orders / Picking routes when Logentic should create routes from the setup values you enter.
Use this when
A supervisor is preparing route-based picking work for associates.
A saved Fulfill Orders view already represents the orders your team wants to route.
You need to control the order count, bin count, route method, and assignment before work starts.
Before you start
Confirm the correct workspace and warehouse.
Confirm the order set is ready for route picking.
Use whole numbers in order count and bin fields.
Do not generate routes at scale if the setup screen, counts, route method, or selected orders do not match the work you intended.
Video walkthrough
Watch the full route workflow, then use the step-by-step guide below. The video links inside the steps open the same walkthrough at the relevant moment.
Steps
Access route creation
To create routes from a specific order set, open Handling > Fulfill Orders, choose the route-ready tab or saved view, select the eligible orders, then choose the route creation action.
To let Logentic create routes from setup values, open Handling > Batch Orders > Picking routes, or use Quick Actions when your workspace shows a route-generation shortcut.
Video: Watch route creation and setup.
Select or confirm the orders to include
For a saved view, select only the orders that should be routed together.
For automatic route generation, confirm the order queue and count before generating the route.
Make sure the selected orders match the batch, lot, priority, or work queue your team intends to process.
Review the route setup
Confirm the workspace and warehouse.
Review the number of orders to include.
Review the number of bins or totes needed for the route.
Choose the route ordering method your team expects, such as alphanumeric order or shortest distance when those options are available.
Generate the route
Select Generate Routes or the route-generation action shown in your workspace.
Wait for Logentic to finish creating the route before leaving the page.
Do not send associates into route work until you have confirmed the route was created and appears in the route queue.
Check how many orders were actually included
Compare the number of orders selected with the number of orders included in the generated route.
If fewer orders were included than expected, check whether excluded orders were already started or already had picking activity.
Do not recreate a second route blindly for orders that may already be in active work.
Adjust the route before final validation
Review the orders and stops included in the route.
Remove any order that should not be part of the route before finalizing, when Logentic gives you that option.
Validate the route only when the route contents match the work your team intends to complete.
Assign the route to the right associate
If Logentic shows an assignment step, choose the associate who should complete the route.
Assign the route to yourself only if you are the person completing it.
Confirm the assignment before expecting the associate to open or start the route.
Video: Watch route assignment.
Start the route or open the route overview
If the route is assigned to the person using the iPad or workstation, they can start route work from their assigned route queue.
If several routes were created, open Pick (All Routes) to review all active routes before dispatching the work.
Monitor route progress
Use the route overview to see routes that are not started, in progress, or already started.
Review order count, SKU count, unit count, assigned associate, created date, and last updated date.
Use these values to understand workload and decide which route needs attention first.
Video: Watch route monitoring.
Reassign if needed
If a route is assigned to the wrong associate, reassign it from the route overview before work starts.
If an associate sees an access or assignment error, check assignment before treating it as a scan, device, or permission problem.
Common blockers
If this happens | What it usually means | What to do next |
Fewer orders are included than expected. | Some selected orders may already have picking activity, route activity, or work that has already started. | Check the excluded orders before creating another route. Route only eligible orders that are not already in active work. |
The route action is missing. | The action may depend on selected orders, browser width, workspace configuration, or role/access. | Bulk-select the intended orders first. If the action still does not appear, capture the saved view, selected count, role, browser width, and screenshot. |
The associate cannot open the route. | The route may be assigned to a different account. | Confirm assignment in Pick (All Routes) before retrying on the associate device. |
Route generation fails or returns to the queue without confirmation. | The route may not have been created or the app may have hit an unclear generation error. | Stop and contact Logentic with the route source, setup values, selected count, timestamp, and screenshot. |
What good looks like
The route setup matches the intended workspace, warehouse, order set, bin count, and route method. The generated route appears in the route queue, the included order count makes sense, and the route is assigned to the right associate before picking starts.
Tips for supervisors
Use Pick (All Routes) to see route workload across the floor.
Use order count, SKU count, and unit count to identify heavier routes.
Use the last updated time to spot routes that may be active, delayed, or stuck.
Assign the route before sending the associate to pick; assignment issues can look like access or scanning problems.
Stop and contact support if
The route action returns you to Fulfill Orders without a setup screen, progress indicator, success message, route queue redirect, or new route confirmation.
Routes do not appear where expected after the success message.
The route count or order count does not match the work you selected.
A route-generation error appears, or a numeric field accepts a value you did not intend.
The associate dropdown is missing or does not show the expected person.
An associate cannot open a route that should be assigned to them.
What to include
Workspace and warehouse.
Where you started: Fulfill Orders queue/view, Batch Orders, or Quick Actions.
Saved view name, selected order count, generated route count, bin count, and route method.
Whether an associate was assigned and which route queue was checked.
Approximate timestamp and screenshot of the setup, route queue, assignment, or error.