
We run doorstep clothing collections for several UK charities, with multiple drivers covering hundreds of addresses a week, and OptimoRoute is the backbone of that operation. The route optimisation handles our mixed rural and urban postcodes well, and the driver app makes it easy for the team to log proof of collection and notes at each stop.
The API is the real standout for us. Bookings from our website go straight into OptimoRoute automatically, and custom fields let us carry the charity, collection ID and customer details through to each order. Afterwards we pull completion details back out to build weight and collection reports for each charity partner, which used to be a manual spreadsheet job. That end-to-end flow, from online booking to charity report, has saved our office a lot of admin time and made our reporting far more reliable. Review collected by and hosted on G2.com.
In the driver app, some fields can't be copied. Our drivers often need to take details like an address, phone number or What3Words reference from a stop and paste them into another app, and having to retype them is slow and leads to errors on the road. Making all order fields copyable would be a simple but genuinely useful fix.
The API is powerful but the documentation could go further. Getting full order and completion data back out takes several chained calls, and some endpoints behave in ways that aren't obvious from the docs. For example, searching orders with order data included can fail without a clear error, which cost us debugging time. Custom fields also can't be filtered server-side, so we have to pull everything and filter on our end.
None of this is a dealbreaker, but copyable fields in the driver app, clearer API error messages and server-side filtering on custom fields would make day-to-day use and integrations much smoother. Review collected by and hosted on G2.com.