How to Manage EV Charging Across Sites with Different Hardware Brands

Quick Answer

Managing EV charging across multiple hardware brands requires a hardware-agnostic Charge Point Management System built on OCPP that can connect to any compliant charger regardless of manufacturer. The core operational challenge is that different hardware brands implement OCPP differently, producing error codes, firmware behaviours, and session flows that vary across vendors. Operators running mixed fleets need a platform that normalises this variation, provides unified visibility across all charge points, and handles vendor-specific edge cases without requiring custom integration work for each hardware brand added to the network. 

Most EV charging networks do not start out with a hardware strategy. They start with a site, a procurement decision, and a charger brand that made sense at the time. As the network grows through new sites, acquisitions, and partnerships, the fleet diversifies. By the time an operator is managing twenty or thirty sites, it is common to find chargers from three or four different manufacturers, each with its own firmware behaviour, error reporting logic, and OCPP implementation. 

This is the reality that multi-site operators work with, and it shapes every part of how the network is run. Our guide to EV charging network operations covers how hardware diversity fits into the broader operational picture, alongside fault management, utilisation, and billing. 

Why managing a mixed hardware fleet is harder than it looks 

OCPP is the protocol standard that governs communication between charge points and management platforms. In principle, any OCPP-compliant charger should connect to any OCPP-compliant platform. In practice, the standard allows enough implementation latitude that the same OCPP version can behave quite differently across manufacturers. 

Some of this variation is minor. Different charger brands use different internal naming conventions for error codes, which means that a fault surfaced on a charger from one manufacturer looks different in the platform logs from an identical fault on a charger from another. An operator trying to identify a recurring error pattern across a mixed fleet may be looking at the same underlying problem described in four different ways. 

Some of the variation is more consequential. Session start and stop flows, load management commands, and firmware update behaviour all differ across manufacturers and firmware versions. A platform that handles these flows correctly for one hardware brand may encounter edge cases with another that require configuration adjustments, workarounds, or in some cases direct involvement from the hardware manufacturer to resolve. 

The operational burden this creates compounds with scale. Each new hardware brand added to the fleet introduces a new set of behaviours that the management platform and the operations team need to understand and account for. 

What OCPP compatibility actually means for operators 

OCPP certification from a hardware manufacturer confirms that a charge point communicates using the OCPP protocol. It does not guarantee interoperability in every deployment context, and it does not mean that the charger will behave identically to other OCPP-certified hardware when connected to a specific management platform. 

For operators evaluating hardware or platforms, this distinction matters. The relevant question is not whether a charger is OCPP-certified in isolation, but whether it has been tested and validated against the specific platform the operator is running, and whether the platform has experience handling that hardware brand's particular implementation at scale. 

Platforms that have processed large volumes of sessions across many hardware brands build up a body of operational knowledge about how each manufacturer's firmware behaves in practice. That knowledge is operationally valuable in ways that formal certification alone does not capture. 

How to maintain visibility across a mixed hardware fleet 

Unified visibility is the operational foundation of managing a mixed fleet well. When chargers from different manufacturers report status, errors, and session data in different formats, the default outcome is fragmented information that requires manual reconciliation to make sense of. Operators trying to assess network health across a mixed fleet without unified monitoring spend disproportionate time comparing data from systems that were not designed to talk to each other. 

A hardware-agnostic platform normalises this variation at the software layer, presenting a consistent view of socket status, session activity, errors, and utilisation regardless of which manufacturer's hardware is generating the data. The practical effect is that an operations manager can review the health of the entire network, including sites running chargers from three different vendors, in a single view without switching between systems or translating between different reporting formats. 

Data Insights provides this across eMabler-connected networks. Socket availability, session success rates, utilisation trends, and recurring error patterns are visible at the network, site, and charger level, across all connected hardware, in one place. For operators managing a mixed fleet, that unified view is what makes site-level diagnosis and network-level pattern recognition practical rather than theoretical. 

How to avoid vendor lock-in in EV charging hardware procurement 

Vendor lock-in in EV charging happens when the management platform is tightly coupled to a specific hardware manufacturer, either through proprietary protocols, commercial agreements, or integration architecture that makes switching hardware impractical without also replacing the platform. 

The consequences show up in procurement. An operator locked into a single hardware vendor loses the ability to negotiate on commercial terms, because the alternative is not just a different charger but a different platform and a network migration. Hardware quality, pricing, and support terms all become harder to contest when the cost of switching is high enough to make it a realistic option. 

A hardware-agnostic CPMS built on open standards preserves procurement flexibility as the network scales. Operators can evaluate hardware on commercial and technical merit, add new brands to the fleet without custom integration work, and make hardware decisions independently of platform decisions. That separation becomes increasingly valuable as the network grows and hardware requirements evolve. 

What to look for in a platform built for mixed hardware management 

Not all hardware-agnostic platforms handle mixed fleets with the same depth. The difference between a platform that is technically compatible with multiple hardware brands and one that manages them well in production shows up in a few specific areas. 

The first is the breadth and depth of validated hardware integrations. A platform that has run large volumes of sessions across many hardware brands in production has encountered and resolved the edge cases that arise from OCPP variation. One that lists hardware compatibility based on protocol certification alone may encounter those edge cases for the first time in a live deployment. 

The second is error handling and fault diagnostics across hardware brands. A platform that can detect, classify, and respond to errors from chargers across multiple manufacturers, in a consistent way, significantly reduces the operational complexity of running a mixed fleet. The alternative is an operations team that needs to maintain separate diagnostic logic for each hardware brand in the fleet. 

The third is the ease of onboarding new hardware. Adding a new charger brand to the network should not require a lengthy integration project. A platform built for mixed fleet management should be able to connect a new OCPP-compliant hardware brand with configuration work rather than custom development. 

Conclusion 

Managing EV charging across multiple hardware brands is an operational reality for most multi-site networks, and the complexity it introduces is real. OCPP provides a common language, but the variation in how manufacturers implement it means that unified management requires more than protocol compatibility. It requires a platform that has been built and validated across a wide range of hardware in production, that normalises reporting across vendors, and that preserves the procurement flexibility operators need as their networks grow. 

The hardware decisions operators make today shape how much operational freedom they have as the network scales. A platform layer that abstracts the complexity of mixed hardware makes that scaling significantly more manageable. 

eMabler is a charging management platform for EV charging operators across Europe. 

If you are managing or planning a multi-site network with more than one hardware supplier and want to understand what unified hardware management looks like in practice, we are happy to talk.