Workday Inventory Route Optimization with SuiteFleet

1. Start with the Workday Inventory inventory stock request

Open the inventory stock request ISR-01842 for Northside Service Center and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains SUP-100 | Examination gloves | 4 CASE and SUP-200 | Surface wipes | 6 CASE.

Open the inventory stock request and confirm its transfer type, source site, destination site, and reserved quantities. Create the appropriate picking lists and release only the quantities ready for shipment.

Workday Inventory supports issues to users or par locations and transfers between inventory sites. This example is a site-to-site transfer; the receiving site’s put-away is a separate step after transport. Workday inventory fulfillment.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Use source and destination inventory-site addresses. Respect receiving-dock hours, site access instructions, and internal transfer priorities when assigning routes.

3. Select eligible stops and available drivers

Open Workbench for the intended date and filters. Inspect task, driver, and hub layers; resolve tasks without a location before optimization. Use geographic selection to choose the intended area, then confirm the selected task set contains only released work.

Choose Plan & Optimize when assigning eligible tasks across drivers, or Optimize Existing Routes when retaining assignments and improving stop sequence. Review enabled drivers, shift windows, departure hubs, and the displayed task-capacity limits. Do not assume those limits represent weight or volume.

Workday Inventory supports issues to users or par locations and transfers between inventory sites. This example is a site-to-site transfer; the receiving site’s put-away is a separate step after transport.

4. Review objectives, constraints, and results

Choose the supported objective: Fastest Completion, Shortest Distance, Fewest Vehicles, or Balanced Workload. Review Respect Time Windows, Reassign Assigned Tasks, and Time Per Stop before running the preview. Select the objective that matches the dispatch plan and confirm which routing constraints are enabled.

Inspect the returned driver assignments, stop sequence, projected completion, and every unassigned task. Check stop times against driver shifts as well as receiving team windows; confirm that the proposed schedule is feasible. Missing locations and conflicting requirements need explicit resolution.

Review the Dallas–Fort Worth planning example, with distances in miles and local receiving times. Dispatchers should check stop sequence, road access, and unresolved work before applying a plan.

5. Execute the route and process actual outcomes

Keep assignment and planned arrival separate from receiving team delivery. Monitor failed, rescheduled, and completed stops during execution. A route application must not post inventory, close an order, or trigger billing by itself.

Zone picking can produce multiple picking lists for one stock request. Preserve their shipment relationships and reconcile shortages before marking the entire request delivered.

After a stop completes, match its task ID to the source shipment, review required proof, and reconcile accepted quantities. Record actual event time and a separate sync outcome. If the source changes after planning, compare the change with the dispatched allocation before overwriting operational data.

6. Verify the result in Workday Inventory

Record delivery evidence against the inventory shipment relationship. The destination team completes the configured put-away process; a SuiteFleet Delivered event must not silently perform that inventory action. Workday inventory fulfillment.

Read back the linked record and review every outstanding allocation before reporting the full delivery requirement complete. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.