Busy riders. Thin drops.
You run Tookan to dispatch your riders, or you are about to. We follow one drop from the order to the last stop and set your dispatch system to what that drop earns you.

Where one drop's money goes
A sample drop dispatched through Tookan: assigned, driven, attempted and closed. Every figure is a sample. Yours come from your own files.
- What the drop earns you1.250
- Rider time on the drop0.520
- Idle rider time0.200
- Vehicle and fuel0.240
- Failed attempts0.130
- Manual dispatch and re-assignment0.100
- What you keep0.060
Four numbers, one each
Each stop the drop makes through your dispatch system has one number that tells you how it is doing. A sample operator, read the way we read you.
Sample
- Rider
Orders per rider hour
YOU 2.1PAR 3.0
Between peaks your riders stand still on your payroll. Those hours sit inside the cost of every drop.
- Dispatch
Drops assigned without a dispatcher's hand
YOU 46%PAR 90%
Your dispatchers override the rules every day because the rules do not match your zones. Each override is a minute you pay for.
- Attempt
First-attempt success
YOU 82%PAR 94%
A failed drop costs you the ride, the fuel and a second ride. You cannot fix a failure you cannot name.
- Assign
Minutes from order to rider assigned
YOU 11PAR 3
Your customer waits while the order sits unassigned. Slow assignment costs you the drop, or a rider at the wrong end of town.
You will know these
- Your dispatchers override automatic assignment every day.
- A failed drop is a free-text note, so you cannot count why.
- Your Tookan export does not match your orders or your ledger.
- You pay riders from one sheet and track them in another.
Four moves on one drop
We set your dispatch rules to the drop
Assignment, zones and rider teams follow what a drop earns you, not only the nearest rider.
We record why a drop fails
Every failed or returned drop carries a coded reason. You count the reasons and fix the largest first.
We tie each task to an order
Each Tookan task matches an order, a rider payment and a cash on delivery entry in your books.
We train your dispatch and finance teams
Your teams run the set-up themselves. We keep it current with you as you add zones and cities.
On your desk
- A dispatch design: assignment logic, zones, rider teams and escalation.
- Task and status templates that record the reason for every failed drop.
- A map of the Tookan fields that feed rider pay, delivery cost and cash on delivery.
- Your set-up tied to your order system and your ledger.
- A handover pack and training for your dispatch and finance teams.
What owners ask us
- Can you fix a Tookan set-up I already run?
- Yes. We read your account against what one drop earns you, list what is out of line and change the settings with your administrator. See Tookan implementation and onboarding.
- What do I send you?
- A month of Tookan exports, your rider pay sheet and your order list. We tell you which settings we read first.
- What changes once the set-up is right?
- More of your drops are assigned without a dispatcher's hand. Failed drops carry a reason you can count, and each task matches an order and an entry in your books.
- Should I set up Tookan before my first rider goes out?
- Yes. We set your rules on the cost of one drop first, so your first rider is dispatched the way your numbers need.
- Who owns the Tookan account?
- You do. The Tookan account is in your company's name, and you hold the subscription and the contract with the vendor directly.
We set dispatch by the drop
Our founder set the money logic behind a last-mile fleet of about 1,000 vehicles at BaladiMart, part of Al Baladi Group. We test every setting in your dispatch system against what it does to the cost of your drop and to your cash.
Related
- Delivery cost optimizationWhat one successful delivery costs you, zone by zone, and which costs to change first.
- Dispatch and assignment workflow definitionThe written rules for assignment, priority and exceptions, set so every dispatch choice protects the group's margin.
- Delivery management system integrationDispatch connected to orders, customer messages and the ledger so every delivery becomes usable operating and financial data.
Bring last month. Leave with a score.
Sit down with Qasim Abbas. One table, your numbers, and a clear read on where you stand against par.