Sana Commerce Route Optimization with SuiteFleet

1. Start with the Sana Commerce webstore order

Open the webstore order WEB-01842 for Cedar Building Products and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains BLD-100 | Door hardware kit | 4 EA and BLD-200 | Cabinet hinge | 6 EA.

Open the webstore order and identify the corresponding ERP sales document. Confirm ERP release, shipment quantities, and shipping destination before exporting the delivery allocation.

Sana displays order and shipment information from the connected ERP. Shipment creation remains an ERP responsibility; avoid creating a second operational order merely to populate the webstore. Sana sales documents.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Use the ERP ship-from location and actual delivery address. Map shipping methods explicitly; a customer’s selected method does not define the driver’s physical origin.

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.

Sana displays order and shipment information from the connected ERP. Shipment creation remains an ERP responsibility; avoid creating a second operational order merely to populate the webstore.

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.

An order may have several ERP shipments. Expose each tracking reference and remaining quantity accurately instead of presenting the first delivered shipment as the full order.

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 Sana Commerce

Return tracking and delivery evidence through the supported ERP integration, then verify the customer’s shipment view. Keep the ERP shipment number and tracking reference consistent across both views. Sana sales documents.

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.