1Document how things work today

Before introducing any system, it helps to describe in simple terms how deliveries are coordinated today: who receives the calls, how couriers are notified, where deliveries are recorded and how you get basic numbers such as “how many deliveries did we do yesterday”.

2Use the Simple plan as a digital logbook

The first step is often the Simple plan: stores log deliveries in one place and couriers manually accept jobs from the Driver app. There is no GPS or complex assignment logic yet – but there is history and traceability.

3Add GPS and availability rules where it makes sense

As volume grows and you need better visibility, the Basic plan adds GPS and availability rules: couriers receive requests based on where they are and whether they are available, and they accept routes manually, while you keep real‑time visibility of what is happening in the fleet.

4Move to Semi-Auto when proposals save time

For fleets with many orders per hour, the Semi-Auto plan helps the dispatcher avoid starting every route from scratch. The system proposes bundled routes, while the human still decides which ones to approve or adjust.

5Use Auto when SLAs and scale demand it

The Auto plan makes sense when you have clear SLA targets (for example 90% of deliveries in less than 30 minutes) and a fleet big enough that a human cannot realistically make every assignment decision. The engine handles assignments but leaves a full audit trail of how each decision was made.

6Small steps with measurable outcomes

At each stage you can track basic metrics: average delivery time, deliveries per courier, how much buffer you have in each shift. If these improve, the transition is paying off; if not, you can tweak settings without going back to pen and paper.