Acumatica Route Optimization with SuiteFleet

1. Start with the Acumatica order

Open the source order SO 004812 for Summit Industrial Supply and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains two lines with quantities 4 and 6 in the units shown.

Use an SO order with shipment processing enabled. Confirm its approval, credit, stock, and shipping rules before creating the shipment. Keep Order Type with Order Nbr.; the visible number alone is not the complete business key.

Sales Orders is SO301000 and Shipments is SO302000. One shipment may include multiple orders for the same customer, so the correlation must preserve every participating order line. Lot or serial splits and warehouse details must survive any aggregation into one delivery stop. Acumatica Sales Orders reference.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Map Warehouse ID and shipment address explicitly to the planning origin and destination. Requested On and Ship On have different meanings; receiving windows should not be inferred from either date alone.

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.

Sales Orders is SO301000 and Shipments is SO302000. One shipment may include multiple orders for the same customer, so the correlation must preserve every participating order line. Lot or serial splits and warehouse details must survive any aggregation into one delivery stop.

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 confirmed shipment of selected quantities can leave other order lines outstanding under the configured shipping rules. Do not use Complete Order merely to remove a delivery exception from the queue.

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 Acumatica

Attach delivery details to the shipment or a related customization. Confirm Shipment and sales-order completion belong to Acumatica’s shipment workflow; a shipment’s Completed status can involve invoice release. Do not force native statuses from a Delivered task. Acumatica Sales Orders reference.

Read back the linked record and review every outstanding allocation before marking the full order delivered. 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.