Dutchie POS Route Optimization with SuiteFleet

1. Start with the Dutchie POS delivery order

Open the delivery order D-01842 for Alex Morgan and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains ACC-100 | Storage case | 1 EA and ACC-200 | Cleaning kit | 2 EA.

Confirm the order is a delivery order for the correct store, and complete the store’s release checks before assigning its driver and route. Keep the delivery allocation linked to the original POS order.

Dutchie separates delivery preparation, route start, skipped deliveries, and checkout. Guestlist statuses can be configured, so map the store’s actual events rather than assuming one universal status list. Dutchie delivery setup.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Use the store origin, approved delivery area, driver assignment, and receiving slot. Retain manifest and reporting ownership in the authorized POS process.

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.

Dutchie separates delivery preparation, route start, skipped deliveries, and checkout. Guestlist statuses can be configured, so map the store’s actual events rather than assuming one universal status list.

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.

A skipped stop must preserve its reason and route relationship. Do not close the order or create a second sale merely because the driver needs another delivery attempt.

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 Dutchie POS

Return the delivery outcome to the linked order record and complete checkout through the authorized POS workflow. A delivery event must not tender payment or close the sale without the configured checks. Dutchie delivery setup.

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.