OCPP 1.6 Charger Compatibility: A Field-Proven Guide

Name: ELVO CPMS Standard Plan
Brand: ELVO
Availability: InStock

On this page

01 What OCPP 1.6 guarantees, and what it does not
02 How to check a charger’s OCPP compatibility before you buy
03 The traps a spec sheet will not show you
04 A real case: winning public tenders with a certified platform
05 How ELVO handles hardware compatibility
06 What NOT to trust on a datasheet
07 Questions to ask the charger vendor before you order
08 Prepare before your next hardware order
09 Frequently asked questions
10 In short
11 Read next and resources

Use this article if you:

are an installer or operator about to order charging stations and need them to work with your management platform
are taking over stations that someone else installed and have to bring them under your control
keep seeing “OCPP compatible” on datasheets and want to know what that phrase actually guarantees

A charger is compatible with a charge point management system (CPMS) when both implement OCPP 1.6, the open protocol released in 2015 and still the industry workhorse. Compatibility is decided by the protocol version and a configurable backend URL, not by the brand on the casing. ELVO runs 700+ station models in production as of July 2026.

The brand on the casing is also less stable than it looks. From where we sit operating a CPMS: new charger brands keep appearing that are really white-label versions of another manufacturer’s hardware. Brands get created, rebadged, and retired; the protocol underneath is what you buy on.

If a hardware order is on your desk this week, a 30-day free trial of ELVO lets you prove your models connect before you sign anything, with no setup fee and no sales call.

What OCPP 1.6 guarantees, and what it does not

OCPP 1.6, published by the Open Charge Alliance (OCA) in 2015, defines the messages a charging station exchanges with its management platform: authorization, transactions, meter values, status, firmware, and load management profiles. OCPP 1.6-J carries those messages as JSON over WebSocket. The protocol does not guarantee that a charger lets you change its backend URL.

OCPP 1.6 exists in two variants: OCPP 1.6-S uses SOAP, and OCPP 1.6-J uses JSON over a WebSocket connection. The J variant is what current backends expect, and its secure form runs TLS over wss. Compared to earlier versions, OCPP 1.6 added smart charging with load balancing and charge profiles plus local authorization list management, which is why the Open Charge Alliance still describes OCPP 1.6 as widely used while the industry moves toward OCPP 2.x. OCPP 2.0.1, released in 2020 and approved in its third edition as IEC 63584 in 2024, is not backward compatible with OCPP 1.6, and OCPP 2.1 was released in 2025. What a backend is and how to choose one is covered in our OCPP backend guide.

OCPP 1.6 guarantees the language both sides speak. It does not guarantee that the firmware exposes the backend URL for you to change, or that every optional feature profile is implemented with equal depth on every model.

What you need on day one	The OCPP 1.6 mechanism	What to check on the charger
Drivers charge without staff on site	Authorize, StartTransaction, StopTransaction	RFID reader on board; autostart supported
Billing-grade energy data per session	MeterValues reported during transactions	Built-in MID-class meter (EU metering directive) if you invoice
Power capped across many stations	SetChargingProfile, smart charging profiles	Smart charging listed as supported
Faults fixed without a site visit	Reset, UnlockConnector, ChangeConfiguration	Remote reset documented by the maker
Firmware kept current over the years	UpdateFirmware, FirmwareStatusNotification	Vendor publishes updates and an OCPP update path

How to check a charger’s OCPP compatibility before you buy

Five minutes with a datasheet answers most compatibility questions. Check the OCPP version and variant, confirm the backend URL is configurable, confirm TLS over wss, and find out whether the model connects directly or through a master unit. Then prove the answer with a live session on a trial backend.

Find the OCPP line in the datasheet. You want “OCPP 1.6” stated explicitly, ideally the J variant. Manufacturers publish this: MENNEKES lists professional units as compatible with OCPP 1.5s and OCPP 1.6s+j and states that station data can go to any OCPP-based backend.
Confirm the OCPP endpoint URL is yours to set. This is the single most important check. A charger that only talks to the manufacturer’s own cloud is locked no matter what the datasheet says. Wallbox documents OCPP activation and setup for its chargers, including endpoint configuration; that is the kind of page you want to find for your model.
Check transport security. Look for TLS over wss, the secure WebSocket connection defined by OCPP 1.6 Security. Without wss, station traffic crosses the network unencrypted.
Check how the model reaches the backend. Some models connect directly. Others connect through a master unit: KEBA KeContact P30 x-series dynamically controls up to 15 c-series wallboxes and acts as the OCPP communication hub toward the backend. Both designs work; know which one you are wiring and what fails if the master goes offline.
Ask for the OCPP implementation notes. A serious vendor can name the backends the model has run with in production and hand over configuration notes. go-e states its chargers are compliant with OCPP 1.6 and publishes a public explainer of OCPP charging.
Prove it before the purchase order. Connect one unit to a trial backend, run a live session, authorize with RFID, and read the meter values. Thirty minutes of evidence beats any brochure.

Q: Does “OCPP 1.6 compliant” on the datasheet mean the charger will work with any CPMS? A: Almost. The protocol side will connect. The practical risks are an endpoint URL you cannot change and optional profiles the model skipped, which is why the endpoint check and a trial session matter.

The traps a spec sheet will not show you

The three compatibility traps in the field are a printed OCPP logo with a locked backend URL, a new brand selling rebadged hardware with unknown OCPP fidelity, and models managed only from the maker’s phone app. All three connect, in theory. In practice they lock you to one vendor’s cloud or to no backend at all.

The locked endpoint is the most common trap. The firmware speaks perfect OCPP 1.6, but only to the manufacturer’s platform, and the setting to change the URL is hidden, dealer-only, or absent. The second trap: a young brand may be a white-label version of another maker’s charger, so the OCPP implementation and the firmware roadmap belong to a company whose name is not on the casing. The third trap is the wallbox managed only over Bluetooth from a phone app standing next to it, with no backend connection at all; fine for a driveway, useless for an operation.

None of this argues for buying only famous logos; it argues for buying on verifiable behavior: version, endpoint, wss, update path. If the stations are already on a wall and pointed at someone else’s backend, the checks are the same, and our migration guide covers repointing the OCPP endpoint in waves without downtime.

Q: A charger comes with a free platform included. Is that a compatibility problem? A: Often, yes. If the firmware accepts only the maker’s own cloud as its OCPP endpoint, the charger cannot join any other backend until that setting is opened. Ask for the endpoint setting in writing before you buy.

A real case: winning public tenders with a certified platform

One ELVO client, an installer, bids in European public tenders where charging stations and their management platform are offered together. The requirement in those tenders reads certified, not compatible: the platform the installer offers with the stations must hold an OCPP certification. A self-declared “OCPP compatible” backend fails that line, because there is no public record behind it. ELVO meets that line with a public record: a certificate ID anyone can open in the Open Charge Alliance registry. The installer wins those tenders. What to put in the software section of a tender is covered in our tender specification guide.

That is the whole difference: “compatible” is a datasheet word; “certified” is a public record anyone can check.

Q: Is “OCPP compatible” enough for a public tender? A: In tenders like these, no. Certification is the requirement: an OCPP certificate you can prove with a registry entry and a certificate ID. Self-declared compatibility has no public record to show.

How ELVO handles hardware compatibility

ELVO connects any station that implements OCPP 1.6 and runs 700+ station models in production, across AC and DC, as of July 2026. The list is field-driven: models join it when real deployments connect them. The Open Charge Alliance certifies ELVO for OCPP 1.6 Full and Security, with TLS over wss.

The honest version of “compatibility” first. ELVO does not run a hardware test lab, on purpose. Models are proven in production: when a client connects a station, that model joins the supported list, and if a model-specific quirk appears, support fixes it reactively. The list keeps growing instead of aging. It spans AC wallboxes and DC fast chargers, connector types from Type 2 and CCS to CHAdeMO and Schuko, and stations from Wallbox, Alfen, KEBA, ABB, and others, with no exclusive hardware partnerships. Etrel chargers, one inherited-fleet example, are connected to ELVO in production, as of July 2026.

Any OCPP 1.6-J compliant station auto-discovers over WebSocket, with no vendor SDK. If your model is not on the list yet, you define the model yourself and register the station the same way as any other, two steps, fully self-service. Certification is verifiable rather than claimed: the Open Charge Alliance lists ELVO with certificate OCA.0016.0336.CSMS for OCPP 1.6 Full, registered in April 2023, and certificate OCA.0016.1071.CSMS for OCPP 1.6 Full + Security, SW 1.6-J, registered in June 2025. The certified products registry is public, so you can run the same check on any backend vendor. Dynamic load management for EPBD Article 14 duties is included, covered in detail in our EPBD compliance guide, and the backend fundamentals live in the OCPP backend guide.

What six makers of OCPP 1.6 compatible chargers state on their official pages, checked in July 2026:

Manufacturer	What the official page states
Wallbox	”All new Wallbox chargers support OCPP 1.6j”
Alfen	Eve Single Plus spec lists backoffice communication over OCPP 1.6, with OCPP 2.0.1 also listed
ABB	Terra AC wallbox spec lists OCPP 1.6
MENNEKES	”Compatible with OCPP 1.5s and OCPP 1.6s+j”; data can go to any OCPP-based backend
KEBA	KeContact P30 x-series is the OCPP communication hub, as master or stand-alone
go-e	”go-e Chargers are compliant with OCPP 1.6”

Q: Is a 700+ model list a tested-in-lab list? A: No, and that is the point. The models on the ELVO list run in production at real deployments. A lab list ages the day it is published; a field list grows with every new site that connects.

What NOT to trust on a datasheet

Marketing words on a charger datasheet have concrete replacements. OCPP-ready means nothing until it names the version and variant. Works with any backend means nothing until an OCA-certified backend is named. Secure means nothing until TLS over wss appears. Certified means nothing until a registry entry can be opened.

❌ “OCPP-ready” → ✅ “OCPP 1.6-J, with the endpoint URL configurable by the operator”
❌ “Works with any backend” → ✅ a named, OCA-certified backend the model has run with in production
❌ “Enterprise-grade security” → ✅ “TLS over wss per OCPP 1.6 Security”
❌ “Certified” → ✅ an entry you can open in the Open Charge Alliance certified products registry

Questions to ask the charger vendor before you order

Six questions separate a compatible charger from a locked one: the exact OCPP version and variant, whether the endpoint URL is configurable, TLS over wss support, direct or hub connection, which backends the model has run with in production, and who manufactures the hardware behind a young brand.

Which OCPP version and variant exactly, J or S? “OCPP compatible” without a version is not an answer.
Can I change the OCPP endpoint URL myself? If the answer involves a dealer tool or a support ticket, price that friction in.
Is TLS over wss supported, and how are certificates handled? Unencrypted station traffic should be a dealbreaker on any public site.
Does this model connect directly, or through a hub or master unit? Both are fine; your wiring plan and failure modes differ.
Which backends has this model run with in production? A real deployment named beats a compatibility matrix.
Who actually manufactures this hardware? For a young brand, the OCPP firmware and update roadmap belong to the real maker.

Prepare before your next hardware order

Four habits keep every future purchase compatible: keep a one-line inventory per station, set OCPP 1.6-J with TLS over wss as your minimum purchasing spec, pilot one or two units on a trial backend before fleet orders, and document each model’s OCPP settings at handover.

Keep an inventory line per station: brand, model, OCPP version, endpoint URL, firmware version.
Write “OCPP 1.6-J minimum, TLS over wss, operator-configurable endpoint” into your standard purchasing spec.
Pilot one or two units of any new model on a live backend before the fleet order, with a real session and a real invoice.
At handover, leave the OCPP settings documented for whoever manages the site after you.

Frequently asked questions

Is my charger compatible with ELVO? If the charger implements OCPP 1.6, it can connect to ELVO. ELVO runs 700+ station models from mixed brands in production as of July 2026, across AC and DC. For a brand not yet on the list, compatibility is checked against the datasheet in minutes, with no integration project.

What is OCPP 1.6 and what does it guarantee? OCPP 1.6 defines the messages a charging station and a management platform exchange: authorization, session start and stop, meter values, status, firmware updates, and load management profiles. Released in 2015, it remains widely implemented across chargers and management platforms. It does not guarantee that a charger lets you change its backend URL, so check that setting per model.

What is the difference between OCPP 1.6-J and OCPP 1.6-S? The J variant carries OCPP 1.6 messages as JSON over WebSocket; the S variant uses SOAP. Modern backends and most current chargers use OCPP 1.6-J, and the secure form runs TLS over wss. If a datasheet only says OCPP 1.6, ask which variant it means.

What if my charger model is not on a supported models list? A field-driven list grows with deployments, so a missing model usually means nobody has connected one yet, not that it fails. On ELVO you define the model yourself and register the station the same way as any other, fully self-service, with reactive support if a model-specific issue appears.

Should I only buy chargers that support OCPP 2.0.1? No, not as a blanket rule. As of July 2026, OCPP 1.6 covers what most European deployments and tenders require, and OCPP 2.0.1, which is not backward compatible with 1.6, appears mostly in newer large public requirements. Check whether a requirement names 2.0.1 explicitly before paying for it. ELVO has OCPP 2.0.1 on its roadmap, with a stable release targeted for Q4 2026.

Can AC and DC chargers run on the same platform? Yes. AC wallboxes and DC fast chargers register on the same vendor-neutral OCPP 1.6 backend, whatever the brand mix, including models that reach the backend through a hub or master unit. Each station points its OCPP endpoint at the platform and appears in the same dashboard.

In short

Compatibility is decided by OCPP 1.6 and a configurable endpoint URL, not by the brand on the casing.
Check four things on any model: version and variant, endpoint configurability, TLS over wss, direct or hub connection.
The real traps are locked endpoints, rebadged hardware from unnamed makers, and app-only wallboxes.
ELVO runs 700+ station models in production, field-proven rather than lab-listed, as of July 2026.
Prove any new model on a trial backend with one live session before you sign the purchase order.