Infor CloudSuite Distribution Route Optimization with SuiteFleet

1. Start with the Infor CloudSuite Distribution sales order

Open the sales order 510482-00 for Prairie Electrical Supply and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains EL-100 | Cable connector | 4 BOX and EL-200 | Panel fastener | 6 BOX.

Open the stock order and confirm the order number, suffix, warehouse, ship-to, and picked quantities. Release shipping through Sales Shipping Feedback Entry or the configured warehouse process.

Distribution SX.e distinguishes Ordered, Picked, Shipped, Invoiced, and Paid stages. Retain the suffix because short shipping can move remaining quantities to a subsequent allocation. Infor processing stages.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Resolve Warehouse to a SuiteFleet departure hub and Ship To to the stop. Requested Ship Date remains a warehouse planning input; use a confirmed arrival date and window for routing.

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.

Distribution SX.e distinguishes Ordered, Picked, Shipped, Invoiced, and Paid stages. Retain the suffix because short shipping can move remaining quantities to a subsequent allocation.

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 customer 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 customer delivery. Monitor failed, rescheduled, and completed stops during execution. A route application must not post inventory, close an order, or trigger billing by itself.

When shipped quantity is lower than ordered quantity, reconcile the remainder to its suffix or remaining line. A receipt for suffix 00 cannot complete an outstanding suffix 01.

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 Infor CloudSuite Distribution

Read back Stage 3-Shipped after the authorized shipping process. Store SuiteFleet receipt evidence separately; delivery completion must not force Stage 4-Invoiced or Stage 5-Paid. Infor processing stages.

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.