Quick answer

Use this article to move from route preparation to route picking without over-assuming what the app has completed. After route work is created, review it from Handling > Fulfill Orders > Pick (Routes). Confirm the route source, selected orders, assignment, and accepted scan codes before training operators or retrying failed route generation.

Common use cases

Warehouse lead: Prepare route work from Batch Orders or a saved Fulfill Orders view.
Picker: Find and work route tasks from Handling > Fulfill Orders > Pick (Routes).
Support: Collect the right evidence when route generation or route picking is blocked.

When to use this

The warehouse wants route-based picking work.
Route work is prepared from Batch Orders or a saved Fulfill Orders view.
A route exists or route generation was attempted and needs investigation.

Before you start

Confirm the warehouse and merchant.
Confirm the route source: Batch Orders or saved Fulfill Orders view.
Confirm route setup values or selected orders before generating route work.
If Logentic prompts for route assignment after generation, complete the assignment before expecting the route to be ready for the assigned operator.
Use Handling > Fulfill Orders > Pick (Routes) to review route work and adjust assignment when available.
Use the product barcode or scan code configured for the item. Do not assume the visible SKU is accepted for route picking.
If route generation returns an unclear technical error, pause and contact support instead of retrying repeatedly.
If route creation returns you to Fulfill Orders without a clear setup screen, progress indicator, success toast, route queue redirect, or new route confirmation, stop and contact support with the evidence below.

Screenshots

These screenshots show where route work is prepared, reviewed, and escalated when blocked. If route creation returns you to Fulfill Orders without a clear setup screen, progress indicator, success toast, route queue redirect, or new route confirmation, stop and contact support with the evidence below.

Before you start

Quick Actions menu showing route actions for route-based picking work.

Screenshot: Route actions live in Quick Actions. Use Create a picking route from views only when the saved Fulfill Orders view already represents the work you intend to route.

Fulfill Orders page showing the warehouse and filtered route-related order view.

Screenshot: Confirm the filtered view before creating route work. Check the warehouse and filters first so the route is created from the intended order set.

Route setup and queue review

Picking route setup screen showing order count, product limit, bin count, and route method fields.

Screenshot: Review route setup before generating route work. Confirm order count, product limit, bin count, and route method before continuing.

Batch Orders picking routes page showing route queue context.

Screenshot: Open Batch Orders / Picking Routes to review route work. Do not start route picking until the route and order set match the work your team intends to complete.

When route generation is blocked

Route generation error evidence screen for support escalation.

Screenshot: Stop on unclear route-generation errors. Capture the setup values, warehouse, merchant, route method, timestamp, and screenshot, then contact support.

Steps

Choose the route source: Batch Orders route generation or a saved Fulfill Orders view.
Confirm the warehouse, merchant, order count, and any route setup values.
For a saved Fulfill Orders view, bulk-select the orders before using Create picking route.
Review the route setup before generating or creating route work.
Complete any assignment prompt shown after route generation.
Open Handling > Fulfill Orders > Pick (Routes) to find the created route work.
Start route picking only when the route, assignment, and order set match the work your team intends to complete.
Scan totes, bins, products, or locations using the codes configured for your warehouse process.
If route work does not appear, route assignment cannot be completed, route generation fails, or a scan is rejected, collect the evidence below and contact support.

What good looks like

The team can explain where the route came from, which setup values were used, which orders were included, who it is assigned to when assignment is shown, and where the route stopped if support needs to investigate.

If the route screen does not match the expected SKU or location

Pause route work if the iPad or route screen shows a style/SKU that does not match the location, lot, bin, tote, or container the associate expects. Do not continue the route if the mismatch could cause the wrong product to be picked.

Save the route screen, route ID, handling order, and Fulfill Orders view/filter when available.
Capture expected versus actual style/SKU and expected versus shown location/container.
Ask a supervisor to confirm whether the location/container is expected to hold one SKU or multiple SKUs.
Escalate using the wrong storage location/container guide if setup or inventory state may be wrong.

Common issues and next actions

If this happens	What to do next
Route generation shows an unclear technical error.	Do not retry at scale. Capture warehouse, merchant, order count, product limit, bin count, route method, and timestamp.
Route actions are hidden or missing.	Check browser width and role/access, then contact support with the saved view, route source, and screenshot.
A product scan is rejected during route picking.	Scan the configured product barcode or scan code. Do not assume the visible SKU is the accepted scan value.

Contact us when

Contact support when route generation fails, route work does not appear under Handling > Fulfill Orders > Pick (Routes), route assignment is missing or wrong, route actions are hidden, or route picking rejects a tote, barcode, SKU, product, bin, or location code.