Flowhub Maui Route Optimization with SuiteFleet

1. Start with the Flowhub Maui delivery order

Open the delivery order FH-01842 for Taylor Bennett and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains ACC-310 | Storage pouch | 1 EA and ACC-410 | Cleaning cloth | 2 EA.

Confirm Delivery is enabled for the store and identify the available dispatch workflow. Review the Ready order, driver, vehicle, delivery zone, and required release steps before dispatch.

Flowhub’s newer Dispatch board is a limited-availability feature. It distinguishes pending routes, en-route work, and route closeout; confirm the store’s release before applying those controls to the connector design. Flowhub delivery.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Respect enabled delivery zones, delivery hours, selected time slots, and assigned vehicles. The shared Dallas map demonstrates SuiteFleet planning controls; the store example uses Sacramento.

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.

Flowhub’s newer Dispatch board is a limited-availability feature. It distinguishes pending routes, en-route work, and route closeout; confirm the store’s release before applying those controls to the connector design.

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.

If dispatch is incomplete or an order is not delivered, retain the route-stop identity and unresolved step. Do not create another order or replay already completed reporting actions.

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 Flowhub Maui

Reconcile the stop outcome first, then complete the store’s payment and route closeout steps through the supported workflow. Keep returned goods and unsuccessful stops visible to the dispatcher. Flowhub delivery.

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.