What you will learn
- Live charger status, availability, and fault monitoring
- Session management: start, stop, energy delivered, and duration
- Driver authentication by app, card, or roaming partner
- Pricing engine with time-of-use, per-kWh, and session-fee models
- Payment processing with receipts and failed-payment handling
What a EV charging management platform is
A charger is not a standalone appliance once it belongs to a network. Drivers expect to find it, start a session, pay, and get support when it faults, while operators need to know which chargers are offline, which sessions failed, and how much revenue each site earned. The management platform is the system that makes a scattered set of chargers behave like one service.
The platform sits between three parties with different interests: drivers who want simple charging, site hosts who want revenue share and uptime, and the operator who bears support and maintenance costs. Pricing, access control, and settlement must therefore be explicit and auditable, or disputes between operator and host become routine.
Who uses it
Charge-point operators, site hosts, fleet managers, and support teams use it. Drivers interact through apps or cards, and finance teams reconcile session revenue and host settlements.
Core features
The features below are the ones buyers check first when evaluating a EV charging management platform.
- Live charger status, availability, and fault monitoring
- Session management: start, stop, energy delivered, and duration
- Driver authentication by app, card, or roaming partner
- Pricing engine with time-of-use, per-kWh, and session-fee models
- Payment processing with receipts and failed-payment handling
- Site-host revenue sharing and settlement reporting
- Remote charger actions: reset, firmware update, and configuration
- Utilisation and revenue reporting by charger, site, and period
How it is built
Build in this order, and do not skip the validation step at the end of each phase.
- Define the network model. Document charger types, site-host agreements, pricing models, and support responsibilities before building the operator tools.
- Build charger connectivity. Connect chargers through their standard protocol, and validate status, session, and metering messages against real hardware.
- Build session and payment flows. Implement driver authentication, session control, pricing, and payment, and test failure cases like interrupted sessions.
- Build operator monitoring and support. Provide live status, fault alerts, remote actions, and session history for support staff.
- Add host settlement and reporting. Calculate revenue shares, generate host statements, and report utilisation and revenue.
- Pilot on a small live network. Operate a handful of sites with real drivers for a full billing cycle, and resolve every session and settlement discrepancy.
Test against real chargers early, including failure cases. A session flow that works in a demo and fails on a faulty connector will generate the support calls that define your reputation.
Technology considerations
Charger protocol handling is the technical core. Chargers speak a standard management protocol, but implementations vary, firmware differs, and connectivity over mobile networks drops. The platform must handle delayed and duplicate messages, never double-bill a session, and keep a complete session record even when a charger goes offline mid-charge.
- Standard charger-protocol support with per-model quirks handled explicitly
- Idempotent session and metering processing to prevent double billing
- Offline-tolerant session records reconciled when chargers reconnect
- Payment handling with failed-payment and refund workflows
- Remote management for resets, configuration, and firmware
Challenges and how to handle them
Charging platforms fail on session accuracy and on charger uptime visibility. A driver billed for energy never delivered, or an operator learning about a dead charger from social media, damages trust faster than any feature gap. The second failure is pricing opacity: drivers who cannot predict the session cost will not return.
- Sessions billed on estimated rather than metered energy
- Charger faults visible to drivers before they are visible to operators
- Pricing that drivers cannot understand before starting a session
- Host settlements disputed because session data is incomplete
- Roaming sessions that fail on authentication at the charger
What to check before launch
Before launch, test every session flow against real chargers, including the failure cases: a driver unplugging early, a charger losing connectivity mid-session, a payment card declining, and a roaming credential that the charger does not recognise. Each case must produce a correct, explainable session record and a fair bill, because drivers judge the network on its worst session, not its best. Confirm that charger faults appear on the operator dashboard before drivers report them on social media, and that support staff can see session history, not just live status. Reconcile the first billing cycle's sessions against payment records and host statements completely; a single unexplained session in the pilot will multiply across a larger network.
What a good first version looks like
A good first version covers one charger family and a small network: live status, sessions, payments, host settlement, and support tooling. Roaming, fleet features, smart-charging optimisation, and grid integration follow once live sessions settle cleanly.
Costs and timelines vary with scope, integrations, and the number of sites or users involved. Treat any figure you see online as a rough range only, and confirm with a written quote for your specific requirements before committing budget.
Frequently asked questions
How do drivers start a session?
Typically through an app, an RFID card, or a roaming partner's credential. The charger authenticates the driver with the platform before energy flows, and the session is metered from that point.
What happens if a charger loses connectivity mid-session?
The charger records the session locally and forwards it when connectivity returns. Billing must wait for the reconciled record, not guess from the interruption.
Can pricing vary by time of day?
Yes. Time-of-use pricing is common, but the price in force at session start, and any change during the session, must be clear to the driver before and during charging.
How are site hosts paid?
Under the host agreement, usually a revenue share or fixed fee per session or per kWh. The platform calculates the share from metered sessions and produces a host statement.
What is roaming?
Agreements letting drivers from one network charge on another's chargers, with authentication and settlement handled between operators. It expands coverage but adds integration and reconciliation work.