Nothing to build: it is done, tested and has over 300,000 deliveries on it. It is a switch, not a project. And it does not replace your delivery service: you test it in one location, against what you have, and decide with the numbers.
The customer gets a link by email and sees the map with no account. At the end they rate, and the rating stays on the order, with the driver and the branch. No app to install.
It comes in and sits in a list until a person checks who is free. The minutes that matter most are lost there.
Neither do you nor the customer. The only way to know is to call, and the one calling is the customer, to your branch.
How long it takes, what each delivery costs, who delivers well. Known by feel, not by number.
When the order comes in, it finds the nearest driver within the authorised fleets and offers it. Real street distance, with straight-line distance as fallback if the network fails: a network problem never stops a dispatch.
Your drivers and an external fleet live in the same system. You authorise the fleets you want, under contract, and it distributes among them.
A link by email, no account: where the order is, who brings it and when it arrives. At the end they rate, and the rating stays on the order.
Times, payouts, efficiency. Each branch sees its own; the region sees everything. And the driver has an app, with their orders and their settlement.
| An outsourced delivery service | Delorean | |
|---|---|---|
| Who assigns | A dispatcher, looking at a list | The system, to the nearest driver, instantly |
| Whose fleet it is | Theirs. Change provider, change everything | Own, third-party or mixed, in the same system |
| What the customer sees | Nothing, until it arrives | The map, the driver and the time, via a link with no account |
| What you know about the delivery | That it left | Every status with its time: offered, taken, picked up, delivered |
| The cost | Per order, theirs | Per delivery, at the rate you agreed with each fleet |
| Reports | Whatever the provider sends | Yours: times, payouts and efficiency per branch and per driver |
| Trying it | You sign a contract | One location, against your current service, decided with numbers |
| When a delivery goes wrong | You call | Reassigned with one tap, and it records who and when |
Written from each product's public documentation. They are mature tools and this page says where they are still better. No prices here: they change on their own and the page would end up lying without anyone touching it.
Switched on in one branch with your current fleet or a third-party one. The other branches stay as they are.
Times and cost per delivery of the switched-on branch against the rest. That is the number you decide with.
The branches that make sense, with the regional board. And the third-party fleet for the peaks your own does not cover.
No. It is an option, not a mandatory replacement. You switch it on in one location to compare times and cost against what you have.
Yes. And a third-party one too, or both: you authorise the fleets you want and the system distributes among them.
The nearest within the authorised fleets, by real street distance. If the network fails it falls back to straight-line distance: it never leaves an order undispatched.
No. They get a link by email and see the map, the driver and the time. They rate from there at the end.
Their app: the orders assigned to them, the route and their settlement. With hours and earnings reports.
It is reassigned with one tap, to another driver or another branch, and it records who did it and when.
What you agree with each fleet. Quoted per delivery, visible in the payout report per branch.
They stay exactly the same until you decide. Each branch switches on separately.
Yes, via API: the order comes in from where you already have it and goes out dispatched. Not entered twice.
Yes, moved with this same system. It is not a new module: it is the one that has been running longest.