How to Choose an EV Charging Management System

Portability is the one to test

A platform that supports OCPP in principle but has only been tested against a handful of charger models will struggle with yours. Ask which models are proven, and ask to connect one of your units during evaluation rather than after signature.

Diagnostics separate platforms more than features do

When a session fails, can you see the message exchange, or only that it failed? Platforms that expose the protocol layer let your team resolve problems. Platforms that hide it make you dependent on their support queue for every incident.

This single difference determines your operating cost more than any feature on a comparison sheet.

Check the exit before the entry

• Whether chargers can be repointed to another backend without vendor involvement
• Whether historic session data exports in a format another system can ingest
• What notice period applies and what happens during it
• Whether driver accounts and RFID credentials transfer
• Whether any hardware becomes unusable on exit

Our disclosure

RIOD builds charging management software, so we are one of the options this page teaches you to evaluate. The criteria above are the ones we would want applied to us, and the portability and exit tests in particular are ones we build for.

Why we stopped reselling a shared platform

We learned this one the expensive way, so it is worth being direct about it.

We used to put customers onto a third-party white-label platform. It carried each customer's brand, and underneath it was one system serving all of them. That arrangement is fine until you want a change. Then it is not fine, because the change either cannot be made or it lands on everybody at once. A request that is reasonable for one operator is a regression for the four sitting next to them on the same platform.

Eventually a change became unavoidable. The only way to make it was to send people out to every charger and do it physically, unit by unit, in the field. That is the point at which a software decision made years earlier becomes a software change that requires a visit to every site.

Charger360 exists because of that. It lets a charger move between management platforms without anyone visiting the site. If a platform is discontinued, if its terms change, or if it simply stops being the right one, the fleet switches remotely. Changing a backend should not require a visit to the site.

Choose for the exit as much as the features

Feature comparison is how platforms are usually chosen and it is a reasonable way to pick between them. It is not a good way to avoid the expensive outcome, which is being unable to leave.

Ask, before anything else, how the fleet moves to a different platform. If the answer requires touching each charger, price that into the decision, because it is the cost we actually paid: a change we could not make on a shared platform was eventually deployed by sending people to every unit in the field.

The features you compare today will all be matched within two years. The migration path will not change at all.

How we would work through this with you

We build a platform, so we are competing for this decision and you should weigh our advice accordingly.

The one thing we would press regardless of who you choose is the exit question. Ask every candidate, including us, how your fleet moves to a different platform without anyone visiting a charger. We ask ourselves that because we once could not answer it, and the answer cost us a great deal of driving.