EV Charger, CMS and Technology Integrations

Charger to backend is the one that is never as done as it looks

OCPP support on both sides is a starting condition, not a working integration. Two compliant implementations can disagree on configuration keys, reconnection behaviour or meter value context, and the result is sessions that fail intermittently.

Business system integration is usually deferred and should not be

Operators frequently launch with manual export into finance and reporting, intending to automate later. At small scale this works. It becomes the operational bottleneck at exactly the point the network grows, which is the worst time to address it.

Every integration needs an owner

• Who is responsible when it stops working
• What happens when either side releases a new version
• Whether failures are visible, or silent until someone notices missing data
• Whether there is a retry and reconciliation path, or data is simply lost

Silent failure is the common one. An integration that stops without alerting anyone is discovered at month end, by which point the gap is large.

What we integrate

Charger to backend work is covered in detail under OCPP integration services. Platform-level integrations to payment, identity, energy and business systems are scoped per deployment rather than offered as a fixed catalogue, because the systems involved differ in every organisation.

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.

How we work with you on this

Integration work sits between two organisations who each blame the other when a session fails, so we try to be the party that owns the diagnosis rather than the party defending a boundary.

Our engineers work with your platform team and, where necessary, directly with the other vendor. Where the root cause is our hardware, we will say so first. That position costs us occasionally and it is the only way an integration relationship functions.