Quick answer
Use a saved Fulfill Orders view when a filtered order set should become route-based picking work. Confirm the warehouse, filters, saved view name, and visible order count, then bulk-select the orders you want to route. The Create picking route action appears after orders are selected because it is a bulk action.
Common use cases
Warehouse lead: Prepare a repeatable order subset for route work.
Operations manager: Review a filtered queue before creating operational route work.
Support: Collect the saved view and route evidence needed when route actions are missing or route creation fails.
When to use this
A saved Fulfill Orders view represents the exact orders that should be routed together.
The warehouse team wants route-based picking instead of regular picking.
The team needs to reuse the same filter set for repeated route preparation.
Before you start
Confirm the warehouse before saving or reopening the view.
Use a clear saved view name that describes the operational purpose.
Review the visible order count before creating route work.
Bulk-select only the orders that should be included in the route. The route creation action is tied to the selected orders.
Route actions may be hidden at narrower browser widths or for some role/access states. If you do not see the expected action after selecting orders, do not assume the view is invalid.
Creating a route may create operational warehouse work, so only continue when the view and selected orders are correct.
Steps
Open Handling, then choose Fulfill Orders.
Select the warehouse that should own the route work.
Use search, sort, and filters to isolate the orders that should be routed together.
Save the filtered result with a clear operational name.
Reopen the saved view and confirm the visible order count.
Bulk-select the orders you want to include in the route.
Select Create picking route from the available bulk action.
Review any route details, prompts, or assignment step shown by Logentic before confirming route creation.
After the route is created, go to Handling > Fulfill Orders > Pick (Routes) to find the route work.
If Logentic prompts you to assign the route, complete that assignment after generation. Assignment can be reviewed or changed later from Pick (Routes).
If the action is missing, route creation does not finish, or the route does not appear under Pick (Routes), contact support with the evidence below.
If fewer orders are included than expected
A saved view or selected queue can show more orders than the route finally includes. The route should only include orders that are eligible for new route work.
If this happens | What it usually means | What to do next |
You selected more orders than the route includes. | Some selected orders may already have picking activity, route activity, or work that has already started. | Do not recreate the route blindly. Check the skipped orders for existing picking activity, then route only the untouched eligible orders. |
The route action does not appear after opening the saved view. | The route action is tied to selected orders and can also be hidden by browser width or access state. | Bulk-select the intended orders first. If the action still does not appear, capture the saved view, selected count, browser width, role, and screenshot. |
The selected order set is not the same as the route queue. | The view may include orders that are not safe to add to new route work. | Compare the saved view count, selected count, generated route count, and any orders already started before sending associates into route work. |
Assign and monitor the route
After Logentic generates the route, assign it to the correct associate if an assignment selector appears.
Use the route overview, such as Pick (All Routes), to confirm route progress, order count, unit count, and current associate assignment.
If a route is assigned to the wrong associate, correct the assignment from the route overview before the associate starts picking.
If an associate cannot access the route they expect, check the route assignment before treating it as a scan or device issue.
What good looks like
The team can return to a known saved view, select the intended orders, create route work safely, assign or review the route when prompted, and find the route under Handling > Fulfill Orders > Pick (Routes).
Common issues and next actions
If this happens | What to do next |
The saved view is missing. | Confirm the warehouse, filters, permissions, and whether the view was saved under another account or role. |
The route action is not visible. | Bulk-select the intended orders first, then check browser width and role/access. Contact support with the saved view name and screenshot if the action is still missing. |
Route creation does not finish. | Collect the saved view name, warehouse, order count, route method if selected, and approximate time, then contact support. |
If route work opens with the wrong SKU or location
If the route or iPad view later shows a style/SKU that does not match the expected location, lot, bin, tote, or container, stop route work and use What to do when a SKU is in the wrong storage location or container. Include the saved Fulfill Orders view/filter in the evidence packet so Support can connect the route back to the source order set.
Contact us when
Contact support when the saved view is missing, route actions are hidden after bulk-selecting orders, route creation fails, assignment cannot be completed, or the route does not appear under Handling > Fulfill Orders > Pick (Routes).
What to include
Warehouse selected in Fulfill Orders.
Saved view name.
Expected order count and visible order count.
One or two example order IDs.
Route action, method, or assignment prompt selected, if visible.
Approximate time route creation was attempted.
Screenshot of the selected orders, route action, assignment prompt, or Pick (Routes) tab with private customer data masked.