Transport & logistics EV & energy Smart charging

EV fleet charging management

Appfront builds custom charging management platforms for electric fleets, for leasing companies, transport firms, couriers, municipal vehicle fleets and public transport operators. Under the hood: OCPP 1.6 and 2.0.1, ISO 15118 for V2G, proprietary optimisation models for smart charging and load balancing, and integrations with charge point vendors and energy markets. On the surface: an API and dashboards that fit seamlessly with your planning, telematics and accounting.

Fabian van Dijk Business Developer · Appfront

What is an EV fleet charging management platform?

An EV fleet charging management platform is the orchestration layer between your electric vehicles, your charge points, your scheduling and your energy contract. Rather than separate apps per charger supplier and manual spreadsheets of charging sessions, you get a single environment that controls every charge point via OCPP, tracks vehicles through telematics and adjusts charging schedules in real time to match your planning, grid capacity and energy prices. The software is brand-agnostic: the same dashboards manage Allego rapid chargers, TotalEnergies depot units, Fastned, EVBox and Wallbox units, and private wallboxes at drivers' homes.

For most fleets, this is a logical next step once the first EVs are on the road. The business case for electric driving doesn't rest on the purchase, but on how smartly you charge. Shifting charging into the cheap night-rate window between 02:00 and 05:00 can cut the energy bill by tens of percent, provided the schedule accounts for a hundred vehicles at once without exceeding the grid connection. That kind of optimisation is exactly what a charge management platform does, and what a standalone charger vendor app cannot do once you have several brands on site. This fits our wider work on custom transport software, where charge management is often tied into the planning and TMS layer.

Appfront designs these platforms so they don't become black boxes. The optimisation objectives, OCPP profiles, model versions and evaluation metrics can be inspected by your own mobility manager and IT team. Integrations run over standard REST, webhooks and OCPP, documented to the OpenAPI standard, so new charger brands, a different energy contract or a new eMSP partner can be plugged in quickly. You can read more about this approach on our page on smart API integrations, where we explain the OCPP, OCPI and ISO 15118 landscape.

Smart charging rather than plug-and-pray

The platform schedules when and at what power each charging session runs, based on departure time, the required end charge, energy peaks and grid capacity. Drivers plug in and the software handles the rest, without tripping the grid connection or hitting the peak rate.

Load balancing across the grid connection

The depot's grid connection has a fixed power ceiling. The platform dynamically distributes the available power across active sessions, prioritises vehicles that need to leave first and scales back as a peak approaches, without costly grid upgrades.

V2G and grid services

With ISO 15118-20 hardware and proprietary optimisation models, vehicles can feed electricity back into the grid, for instance during imbalance price spikes or as emergency power. The platform manages the schedules and handles the financial settlement with BSPs connected to TenneT.

Our development process for a fleet charging platform

A good charge management platform doesn't start with OCPP libraries, but with the operation on the depot. We work alongside your mobility manager, planners and first drivers to understand how charging really runs today: which vehicles are at which chargers and when, where peaks already occur, what agreements have been made with drivers, and which energy contracts and grid connections are in place. Only then do we choose the architecture, the OCPP versions and the first set of integrations. This way you get a platform that is not only technically sound, but also trusted in day-to-day practice by everyone who works with it.

1
Discovery at the depot

We map the charging landscape: vehicle types, charge points per brand, grid connection, energy contract, planning flow and driver habits. Without that context, any smart charging algorithm gets stuck in week one.

2
Architecture & OCPP selection

We define the OCPP profile (1.6 + 2.0.1 where needed), the eMSP and CPO role split, ISO 15118 where relevant, and the data model for vehicles, sessions and tariffs. OpenAPI contracts are agreed before a single line of code is written.

3
Implementation & pilot

Iterative build with automated tests and a pilot at one depot or in one region. The smart-charging algorithm runs in shadow mode alongside the existing set-up, so you can compare results before it takes control.

4
Rollout, monitoring and further development

Phased rollout per depot, with monitoring of charging costs, peak-shaving effect, ETA errors in range planning and exception rates. This is followed by ongoing management, charger expansions and support for new models.

What a charging platform concretely delivers

Every charge management platform is tailored to the type of fleet, the kind of transport and the existing systems. Below are the components we consistently see, which can be combined depending on your scenario. What appears on this page aligns with our broader work on custom energy software, where smart charging and V2G meet trading systems, balance responsible parties and grid operators.

Smart charging & peak shaving

For each vehicle, a charging profile is calculated based on departure time, required final state of charge, grid capacity and hourly prices. The platform sends OCPP commands to charge points to ramp power up or down, avoids grid peaks and makes use of cheap off-peak hours, applied uniformly across every type of charger.

Dynamic load balancing

The grid connection has a hard ceiling: exceeding it means fines or blown fuses. The platform dynamically distributes available power across active sessions, giving priority to vehicles that need to leave first. It scales back automatically as a grid peak approaches.

V2G & vehicle-to-building

With ISO 15118-20 hardware, vehicles can feed energy back to the building or the grid. The platform manages schedules, safeguards minimum battery levels for the next journey, and settles accounts with BSPs using TenneT balancing prices or imbalance exposure.

Charging session billing & reporting

Every kWh is recorded, linked to the vehicle, driver, customer or cost centre, and passed on to accounting, the eMSP partner or the customer portal. Flat-rate amounts, dynamic hourly tariffs and home-charger allowances for drivers all run in one flow.

Charging forecasts & AI optimisation

An AI model predicts, based on scheduling, historical trips, weather and seasonal patterns, how many kWh each vehicle will need each night. The platform then applies the optimal schedule, aimed at lowest cost, lowest CO₂ or highest self-consumption of PV. Our approach to these kinds of models is outlined under AI development.

!

Anomaly detection in charging behaviour

A charger suddenly delivering 30% less power, a session stopping abruptly, a vehicle that doesn't plug in after a trip: the platform detects these deviations and proactively alerts mobility managers. Faulty units become visible before drivers arrive at a depot that isn't working.

Typical scenarios in practice

A fleet charging platform looks different for each type of fleet. We see a number of scenarios recur structurally, and for each we have a recognisable approach that takes into account the specific rules, restrictions and systems common in that market. Much of this runs alongside the wider planning challenges we cover on transport planning API, where route optimisation and charging schedules are linked together.

Transport companies with electric fleets

Distributors and couriers who make hundreds of stops a day with e-vans and e-trucks from one or more depots. The platform handles overnight charging on tariff, range validation against the schedule, and dispatches extra charging at fast chargers between rounds when needed — without dispatchers having to chase drivers by phone.

Leasing companies with EV portfolios

Leasing companies that lease electric cars and want to pass on charging costs transparently: home-charger allowances for business drivers, public charging costs via an eMSP card, and depot charging at the employer. The platform consolidates all sessions per lease car, links them to the lease invoice, and gives drivers insight into their usage through their own portal or app.

Public transport operators with electric buses

City transport operators and regional transport concession holders replacing diesel buses with electric buses. A tight schedule applies here: buses must leave the depot on time. The platform calculates which bus belongs to which charger, how much power is needed now given the grid connection, and raises an alert as soon as a vehicle won't reach the planned SoC.

Municipal fleets and ZE zones

Municipalities with service cars, home-care EVs and enforcement vehicles that must operate within zero-emission zones. The platform takes account of ZE city-centre restrictions, prioritises EVs for inner-city routes, and ensures the municipal connection at fleet or parking locations doesn't become overloaded by peak charging.

Last-mile couriers & taxi organisations

Hubs full of small electric vans or e-taxis that alternate between driving and charging. Turnaround time is critical here: a driver who spends too long at the charger is lost revenue. The platform schedules fast-charging stops between trips, selects the right charge point based on the current queue, and ensures the depot connection doesn't exceed the contract.

Public charging networks & eMSP partners

CPOs (charge point operators) and eMSPs that want to offer their public charging infrastructure to fleet customers. The platform acts as a white-label back office — session routing between networks via OCPI, dynamic tariffing, roaming handling and detailed reporting per partner.

Technology we use

We align the technology stack with your scale, your type of fleet and your existing IT landscape. We use open standards where possible and our own models where they add value. The software is built in a language and framework that your own team can continue to manage — no vendor lock-in, no secret sauce. For the integration layer, we build on our experience with smart API integrations, where OCPP, OCPI and ISO 15118 receive the same attention as REST and webhooks.

OCPP 1.6 & 2.0.1 OCPI between CPO & eMSP ISO 15118-2 / 15118-20 (V2G) SteVe & CitrineOS reference Allego / Total Energies / Fastned APIs EVBox & Wallbox connectors EPEX Spot & APX day-ahead TenneT imbalance prices Webfleet / Geotab / MiX telematics Python (FastAPI) / Node.js PostgreSQL + TimescaleDB Redis & RabbitMQ MQTT for chargers with legacy backbones XGBoost / LightGBM for charging forecasts Azure West Europe / AWS Frankfurt OpenAPI 3 / Swagger GitHub Actions / GitLab CI Grafana + Prometheus monitoring

Why choose Appfront for your charging platform?

Appfront combines experience in OCPP development, energy market integrations and optimisation models, with a clear preference for custom work that fits what you already have. We know that a charge management platform only works if drivers trust it, that a smart-charging algorithm only adds value if it is based on your own energy contract and grid capacity, and that a platform only keeps running if the OCPP integrations are properly documented for future charger brands. That is why we always start at the depot and with your existing systems, not with a blank OCPP manual.

For every integration, we write clear documentation and OpenAPI contracts so that your own team, or a future partner, can understand and manage what is running. No black box around smart-charging rules, transparent model versions for charging forecasts, and clear agreements on OCPP profiles, monitoring and management. That way you remain independent and can keep control of your charge management at all times, a requirement that is becoming increasingly important legally under the AI Act for algorithms that steer driver behaviour or vehicle deployment.

You work with a fixed point of contact who understands the OCPP side, the energy market side and the integration side. This keeps lines short, prevents miscommunication between charger supplier, energy supplier and your own IT, and speeds up decisions when choices need to be made during the build around data models, tariffs or OCPP profiles.

See also our broader overview of the integrations we build and how we approach transport & logistics as a whole. Charge management is often a specific layer on top of the planning and TMS layer.

  • OCPP 1.6 and 2.0.1 implementation experience
  • ISO 15118-20 for V2G and plug-and-charge
  • Energy market integrations (EPEX, APX, TenneT)
  • Telematics integrations with Webfleet, Geotab, MiX
  • Multi-vendor charger support (Allego, Fastned, EVBox, Wallbox)
  • Custom charging forecast models based on your historical data
  • Smart charging and peak shaving at connection level
  • OpenAPI 3 contracts, no undocumented endpoints
  • Secure by default: API keys, scoped permissions, rate limiting
  • EU-resident hosting (Azure West Europe, AWS Frankfurt, Dutch cloud)
  • AI Act preparation for charging algorithms
  • A fixed point of contact, no account managers passed around
  • Ongoing management, OCPP tracking and model renewal

Security, GDPR, AFIR and AI Act

Charging data is sensitive: a charging session reveals where a vehicle was parked, at what time, and therefore indirectly where a driver was. This falls under the GDPR and, for public charging infrastructure, under the European Alternative Fuels Infrastructure Regulation (AFIR). The algorithms that act on this data also fall under the AI Act. Appfront builds according to the OWASP ASVS and explicitly determines for every charging platform which personal data is required, who has access and how long it is retained.

We host by default within EU residency — Azure West Europe, AWS Frankfurt or a Dutch cloud of your choice — and encrypt data in transit and at rest. We document the data flows between charging points, telematics, energy suppliers, eMSP partners and accounting so that your record of processing activities is complete and you can demonstrably comply with the GDPR. For public charging points, we support the AFIR-mandated open data publication of availability, prices and payment methods, without any driver data ending up in it.

For the AI components — charging forecast models, optimisation algorithms and anomaly detection — we deliver model cards, a description of training data provenance and evaluation metrics. This allows you to demonstrate under the AI Act that decisions are transparent and explainable. For algorithms that steer driver behaviour — for example, assigning routes based on charging availability — we include an impact assessment and human oversight steps. See also our information security policy and CVD policy.

  • GDPR-compliant processing of charging sessions and location data
  • EU residency: Azure West Europe, AWS Frankfurt or Dutch cloud
  • AFIR-compliant open data for public charging infrastructure
  • AI Act: model cards, dataset provenance, evaluation metrics
  • Impact assessment for charging-behaviour algorithms affecting drivers
  • Encryption in transit (TLS 1.2+) and at rest
  • Mutual TLS for OCPP connections where supported
  • API key rotation and role-based access
  • Rate limiting and DDoS protection
  • Audit logs with traceable charging session history
  • Monitoring and alerting for OCPP anomalies
  • Documentation for your record of processing activities

Frequently asked questions about EV fleet charging management

Answers to the questions we are asked most often about custom charging management platforms for electric fleets.

An EV fleet charging management platform is a software layer that orchestrates the charging of an entire electric fleet. Rather than each driver or dispatcher deciding where and when a vehicle is plugged in, the platform links charge points, vehicles, scheduling and energy contracts together via OCPP and its own integrations. It optimises when charging takes place (smart charging), distributes power across multiple chargers (load balancing), monitors range against the schedule, and delivers charging sessions to accounting and eMSP platforms for settlement.

SaaS platforms from charge point suppliers work well for a single hardware brand and standard office fleets. They struggle once you mix several charger suppliers (Allego, TotalEnergies, Fastned, EVBox, Wallbox alongside your own depot chargers), once V2G or multi-level dynamic load balancing comes into play, or once scheduling, the TMS, the energy contract and billing need to operate on a shared logic. A custom platform gives you a vendor-neutral OCPP layer, control over the optimisation objectives, and a data model that aligns with your own fleet and planning systems.

We work with both OCPP 1.6 and OCPP 2.0.1. The majority of current charge points still run on 1.6, while 2.0.1 is needed for smart-charging profiles, ISO 15118 plug and charge and V2G. Our platforms support both versions in parallel, with an abstraction layer that sits above the version differences. For V2G (vehicle-to-grid) we implement ISO 15118-20 once the hardware supports it. For back-office integrations with other systems we use OCPI between CPOs and eMSPs.

For fleets on a dynamic energy contract, we pull hourly prices from EPEX/APX every day and align charging schedules to them. For fleets on a fixed contract, we work with grid capacity limits and peak shaving to reduce transport costs. For fleets with their own solar panels or battery buffers, we also connect that data and choose between direct consumption, grid injection or storage. You set the optimisation goal yourself: lowest energy costs, lowest CO₂, or highest self-consumption of PV.

For planners, range is the biggest practical problem: a route that was simple with a diesel bus now needs a stop at a fast charger or a vehicle swap. Our platforms connect vehicle telematics (State of Charge, real-time consumption) to planning and give planners proactive alerts when a route isn't feasible. We also model zero-emission zones in cities such as Amsterdam, Rotterdam and The Hague, so vehicles are allocated to keep diesel vans out of ZE zones and EVs are used for critical deliveries there.

Yes. Charging sessions contain location data, timestamps and links to a driver or vehicle, which falls under the GDPR. We host within EU residency, encrypt data in transit and at rest, keep charging session data only as long as needed for billing and reporting, and provide documentation for your record of processing activities. For public charging infrastructure covered by the Alternative Fuels Infrastructure Regulation (AFIR), we support the mandatory open data publication and payment methods. For algorithms that steer driver behaviour, we deliver model cards and human-oversight steps in line with the AI Act.

Yes. Appfront regularly takes over or extends existing charge point management systems. We review the OCPP implementation, the business rules for smart charging, the eMSP/CPO role allocation, the billing flows and the monitoring. We then draw up an improvement plan and can take care of extensions (V2G, dynamic tariffs, new charger types, additional integrations) and ongoing management.

A custom charging management platform makes most sense when you plan multiple vehicles across multiple charging points and standard tools no longer cover it. Typical profiles: leasing companies with EV portfolios, transport companies with electric distribution or last-mile fleets, couriers, taxi organisations, public transport operators with electric buses, municipal fleets with service cars and home-care EVs, and public charging networks. For a few vehicles on a handful of wallboxes, a standard app from the hardware supplier is often enough.

Talk to us about your fleet charging platform

Tell us what your fleet looks like today: which vehicles, which chargers, which energy contracts, and which planning and TMS layer sits around them. Let us know what you would like to automate, such as smart charging, load balancing, V2G, charging session billing, range planning or mixing chargers from multiple brands. We are happy to help you think through scope, priorities, data model and alignment with your existing suppliers. A no-obligation first conversation will give you a clear picture of what is achievable for your situation.

Edit content