If you're responsible for EV chargers — as a charge point operator, a fleet manager, a workplace, or a local authority — you'll quickly meet a wall of acronyms: CPMS, CSMS, backend, back office, platform. They all point at roughly the same thing, used inconsistently by every vendor.
This guide cuts through it: what a charge point management system actually does, where the real differences between products lie, and the questions that separate marketing from capability.
The plain-English definition
A charge point management system (CPMS) — also called a charging station management system (CSMS) or simply "the backend" — is the software that connects to your chargers and turns them from isolated hardware into an operated network.
The chargers themselves speak OCPP (the Open Charge Point Protocol), an open standard that lets hardware from different manufacturers talk to any compliant backend. The CPMS is the other end of that conversation.
What a CPMS actually does
Every credible CPMS covers a core set of jobs:
- Connectivity and monitoring. Maintain connections to every charger, track status in real time, and alert when something goes wrong.
- Session management. Start, stop and record charging sessions, capture meter readings, and produce the data that billing depends on.
- Access control. Decide who can charge — RFID cards, apps, plug-and-charge, open access — and enforce it.
- Remote operations. Restart chargers, unlock cables, change availability and update configuration without a site visit.
- Reporting. Utilisation, energy delivered, revenue, uptime — the numbers your finance team and your funders ask for.
That's the baseline. If a product can't do all of the above across multiple hardware brands, it's not a CPMS; it's a single vendor's companion app.
Where the real differences lie
The gap between a basic CPMS and a strong one shows up in five places:
1. Multi-vendor, multi-version OCPP support. Fleets are mixed in practice — different brands, different firmware, chargers speaking OCPP 1.6 alongside 2.0.1 and 2.1. A strong platform makes those differences invisible to your team. (Our engineering write-up on running mixed-version fleets explains why this matters more each year.)
2. Firmware and configuration management. Chargers are computers in car parks; they need updates. Platforms differ enormously here — from "email the manufacturer" to staged, audited rollouts with automatic rollback. If you'll ever own more than a handful of chargers, this is where operational cost hides.
3. Uptime evidence, not uptime claims. UK public charge point regulations set a 99% reliability bar for rapid networks, and tenders increasingly ask you to prove reliability. Look for connector-level availability tracking and exportable evidence — and ask vendors how their platform's reliability is measured and published. (We publish ours, continuously, on a public performance page.)
4. Intelligence. The difference between "the charger is red" and "this connector's failure risk is rising, schedule maintenance before Friday" is the difference between monitoring and operational intelligence. As networks grow, reactive operations stop scaling.
5. API access. Sooner or later you'll want charging data in your own systems — billing, CRM, asset management, a customer app. If the platform's answer is CSV exports, walk away. The honest test: can your developers do everything the dashboard does, through a documented API?
CPMS vs eMSP: a distinction worth knowing
You'll also meet the term eMSP (e-Mobility Service Provider) — the driver-facing side: apps, payment cards, roaming agreements. A CPMS manages chargers; an eMSP manages drivers. Some companies do both; the roles are distinct, and roaming protocols like OCPI connect them. When a vendor says "end-to-end platform", ask which of the two roles they actually perform, and how the other one connects.
Questions that expose the difference
Take this shortlist into any vendor conversation:
- Which OCPP versions do you support in production today, and with which hardware brands have you proven it?
- How do firmware updates work — and what happens when one fails?
- Show me connector-level uptime for a real network. How is it calculated?
- What's in the API, and what's dashboard-only?
- Can I white-label the driver experience and portals under my brand?
- What happens to my data and my chargers if I leave?
That last question matters more than it seems: because OCPP is an open standard, a well-configured fleet can be repointed to a different backend. A vendor who makes leaving difficult is telling you something about how they intend to keep you.
AmpNexus is a CPMS built for mixed fleets: OCPP 1.6–2.1 connectivity, staged firmware rollouts, predictive intelligence and a full API. Book a demo or start with the platform overview.