Delivery software normally assumes you already have the fleet. In practice the harder problem for many companies is the one before that: agreeing with a carrier who does what, at what price, in which zone, and having that agreement signed by both sides. Delorean's logistics module has two sides — the company that needs deliveries and the one that does them — and starts at the agreement.
| Onfleet | Delorean | |
|---|---|---|
| Route optimisation | Yes, that is the core of it | Not included |
| Live tracking for the customer | Yes, with notifications and ETA | Not included |
| Fleets and zones | Yes | Yes, defined by the company that does the delivering |
| Drivers | App for the driver | The driver is not a Delorean user or an employee — they get their own access |
| Contracting a carrier | Outside the product | A two-signature agreement: the client and the carrier |
| Orders and dispatch | Yes, complete | The client loads the order, it is offered, and it gets dispatched |
| Delivery metrics | Deep | Not yet — real delivery times are on the roadmap |
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.
For a company that needs to organise who delivers what and under which agreement, yes. For optimising routes and giving the end customer live tracking, Onfleet is specialised and Delorean is not.
Route optimisation, live tracking with ETA for the recipient, proof of delivery flows and deep delivery analytics.
It covers the step before: finding, agreeing with and signing a carrier, with the agreement, the orders and the money in the same place as the rest of the company.
They are not Delorean users and not employees of the company using it — they get their own access to what they need.
It has two signatures: the client who needs the deliveries and the carrier who will do them. Neither side can claim afterwards that it was never agreed.
Yes, the company doing the delivering defines its fleets and zones.
The client loads it, it is offered, and it is dispatched to whoever takes it.
Not yet. Real metrics — deliveries completed and how long they took — are pending, and they will feed the rest of the module.
Yes. The module has both sides: you can be the one who needs deliveries, the one who does them, or both.
It is in the same product as the money, so what was delivered and what is owed are not in two different systems.