Sage Intacct Route Optimization with SuiteFleet

1. Start with the Sage Intacct order

Open the source order SO-10482 for Cedar Grove Medical Center 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 the configured Order Entry transaction definition and approval rules to release eligible Sales Order lines. In this example, convert the released quantities to a Shipper before delivery execution. Pending is a transaction-conversion state, not a promise that stock or driver capacity is available.

Order Entry transaction definitions determine the conversion path. A document called Shipper is a configured workflow choice, not a universal Intacct fulfillment endpoint. Preserve the original transaction and line relationship when converting only part of an order. If line-level ship-to contacts are enabled, group tasks by the actual line destination instead of blindly using the header contact. Sage Order Entry conversion.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Separate Need by date from Ship by date. The receiving date and window should drive the customer stop, while the warehouse departure deadline remains a different planning input.

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.

Order Entry transaction definitions determine the conversion path. A document called Shipper is a configured workflow choice, not a universal Intacct fulfillment endpoint. Preserve the original transaction and line relationship when converting only part of an order. If line-level ship-to contacts are enabled, group tasks by the actual line destination instead of blindly using the header contact.

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 for 10 cases can produce a Shipper for 4 and leave 6 for later conversion. A delivered task for the first Shipper must not advance the remaining lines or create a sales invoice by assumption.

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 Sage Intacct

Record the delivery result against the linked Shipper or a related custom delivery record. Converting the source order does not itself prove customer receipt. Keep partially converted lines outstanding and use the configured document conversion, rather than forcing an arbitrary order status. Sage Order Entry conversion.

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.