OCPP EV chargers + FleetERP
Depot charger sessions, scheduling and energy cost per kilometre.
How it works
FleetERP talks OCPP 1.6J and 2.0.1 to depot charging infrastructure, so charging becomes a scheduled operational activity with a cost attached rather than an untracked overnight event.
OCPP 1.6J or 2.0.1 WebSocket connection to the charge point management system.
FleetERP has no commercial relationship with hardware vendors and earns nothing on devices. If you later switch away from OCPP EV chargers, your history, reports and workflows stay exactly where they are.
What flows across
What OCPP EV chargers data lights up in FleetERP
Integration data is not stored in a separate silo — it feeds directly into the operational modules that use it.
OCPP EV chargers integration FAQ
Do we need to replace our OCPP EV chargers setup to use FleetERP?
No. FleetERP is device-agnostic and does not sell hardware. Your existing OCPP EV chargers deployment stays exactly as it is — oCPP 1.6J or 2.0.1 WebSocket connection to the charge point management system.
What data does FleetERP receive from OCPP EV chargers?
Charging session start, stop and kWh delivered; Charger availability and fault status; Smart charging schedules and load balancing; Tariff slab and session cost.
How long does the OCPP EV chargers integration take to set up?
Standard integrations are connected during week three of a normal 30-day rollout, alongside device onboarding. Most take a few hours of configuration rather than a project.
Sensors, video & ADAS
Fuel, temperature, pressure, load and camera feeds normalised into the same event timeline.
Already running OCPP EV chargers? You're most of the way there.
Book a demo and we will show you your own device data flowing into the platform during the call.
No per-user pricing · No hardware to buy · Deploy on your VPS or ours
Prefer to write? sales@fleeterp.in