USE CASE

Delivery route planning

Plan the day’s deliveries as trips, with drivers, vehicles and stops in one place.

The problem

Dispatch plans the day on a whiteboard and a phone call. Drivers leave without the address list, customers ask where their order is, and nobody can say which deliveries were actually completed until the driver is back.

The flow in Sundial

1. Start from what is ready. Take the submitted delivery notes for the day. Each one carries the customer, the address and the goods.

2. Create a delivery trip. Add the delivery notes as stops, set the departure time, and assign a driver and a vehicle from your records.

3. Order the stops. Arrange the stops in the order the driver should run them, with the contact and address for each.

4. Notify and dispatch. Send customers their delivery details from the trip and print or share the stop list with the driver.

5. Close the trip. As stops are completed, mark them; the trip shows what was delivered and what came back.

What the team sees

Dispatch sees every trip of the day, its driver, vehicle and stop list. Sales can answer “where is my order?” by opening the delivery note and following it to its trip.

Why it holds up

The trip is built from delivery notes that already exist, so addresses, contacts and goods are never retyped. Drivers and vehicles are records in Sundial, which means you can look back at who ran which route and when. The trip sits on top of the delivery chain; it does not replace it, so stock and billing stay correct regardless.

With AI (coming to Sundial)

Coming to Sundial: ask “which deliveries for Columbus are still open today?” in plain language, and an agent that drafts tomorrow’s trips from ready delivery notes for dispatch to approve.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us