Shopify Route Optimization with SuiteFleet

1. Start with the Shopify order

Open the source order #1048 for Lakeside Outdoor Co. 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.

Select an open order with eligible unfulfilled physical items. Check payment or credit policy, fraud review, fulfillment holds, and assigned location before release. Do not dispatch a held, canceled, or not-yet-due scheduled fulfillment order.

Shopify can split one order into several fulfillment orders and locations. Preserve the fulfillment-order line IDs and explicit quantities when creating a fulfillment. Moving work between locations or splitting it after export changes the assignment; the connector must reconcile that change before dispatch. Shopify order statuses.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Use the assigned fulfillment location as the planning origin. Split locations into separate tasks or shipments as required, and do not silently move a fulfillment order simply to make a route look shorter.

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.

Shopify can split one order into several fulfillment orders and locations. Preserve the fulfillment-order line IDs and explicit quantities when creating a fulfillment. Moving work between locations or splitting it after export changes the assignment; the connector must reconcile that change before dispatch.

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.

One fulfilled shipment must not hide another unfulfilled group in the same order. If only 4 of 10 units are released, keep the other 6 outstanding and retain a separate task and fulfillment relationship for the later shipment.

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 Shopify

Reconcile the appropriate fulfillment and its tracking information. A Fulfilled order reflects shipped items, while a delivered event describes customer receipt. Store proof metadata through the supported integration and verify each fulfillment before concluding the whole order is delivered. Shopify order statuses.

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.