FAQ
Questions operators ask
Straight answers about the fleet operating system: hardware, data, permissions, pricing, onboarding and the work behind a live delivery operation.
RideControl fleet OS
One operating record for vehicles, people and hubs.
Product and integrations
RideControl brings vehicles, couriers, service and cost per vehicle into one operating system. It is brand-agnostic, works with mixed e-mopeds and e-bikes, and offers a REST API plus webhooks for operational events.
- Vehicles from different manufacturers can run side by side.
- API covers vehicles, couriers, trips, service requests and billing.
- Webhooks cover events such as zone exit, service due and battery alarm.
- Delivery platforms and accounting tools connect through the API.
Operations and people
Groups model countries, hubs, fleets and client accounts. Roles follow that structure, so people see the work they are responsible for. Service Flow keeps repairs moving, while keyfobs and handovers make physical access accountable.
- Unlimited users on every plan.
- Hub, country and partner permissions.
- Phone-friendly maintenance kanban.
- Keyfob blocks and courier offboarding with a record.
Data and onboarding
Data is hosted in the EU, and you own it. Import the fleet and current service history from CSV; a typical onboarding takes two weeks. Keep the spreadsheet read-only for a few weeks while the team trusts the new record.
- CSV import and export.
- DPA for courier data.
- Retention and deletion requests from the panel.
- No lock-in or export fee.
Frequently asked questions
Related
See it on your own fleet
Book a 30-minute walkthrough. We open the panel with your vehicle types, hubs and countries in mind — no slides.
Book a demo