BESTAR
SELECTION GUIDE · PROTOCOL

OCPP 1.6J vs OCPP 2.0.1

OCPP is the language your chargers and your back office speak. Version 1.6J is what most installed networks run today; 2.0.1 is what new public build-outs are increasingly specifying. This guide sets out what actually changes, and what it means for the hardware you buy.

1.6J
Widest installed base
2.0.1
Default for new build
No
Backward compatibility
Updated 2026-10-23 · Written for buyers specifying charging and storage equipment.

Key takeaways

What OCPP actually does

OCPP (Open Charge Point Protocol) standardises the messages between a charge point and the central system that manages it — authorisation, transactions, meter values, firmware and status.

If you operate more than one or two charge points, this is the layer that decides whether you can swap your back office later, or whether the hardware locks you in.

The protocol version is a property of the charge point controller and the CSMS (charge point management system). Both ends must speak the same major version.

What 1.6J gives you

1.6 is the 2015 release; "1.6J" is the JSON encoding together with the security extension published alongside it, and it is what most hardware and software in the field implements.

In practice 1.6J covers everything a private or semi-public network needs: RFID authorisation, start/stop transactions, meter values, smart charging with simple limits, and basic diagnostics.

Its strength is compatibility: nearly every CSMS, roaming hub and payment terminal supports it.

What 2.0.1 adds

2.0 was a rewrite rather than an update, and 2.0.1 is its maintained release. The additions matter most at scale.

Device management is built in, so configuration, monitoring and component-level diagnostics are standardised instead of vendor-specific.

Security profiles are defined in the specification, and ISO 15118 Plug & Charge is supported natively — the vehicle authenticates itself and the driver simply plugs in.

Smart charging is more expressive, which is what grid-aware and fleet-depot schedules tend to need.

Compatibility and migration

This is the point that catches buyers out: 2.0.1 is not a superset of 1.6J.

A 1.6J charge point will not talk to a 2.0.1-only back office, and the reverse also holds. Networks in transition therefore run a CSMS that accepts both, or keep the two populations separate.

Ask two questions before ordering: can the controller firmware be updated in the field, and does your CSMS vendor commit to a 2.0.1 date?

How to choose

Match the version to the network you are building, not to the newest number on the spec.

SituationRecommendedWhy
Home, workplace or small fleet, one back office1.6JEverything needed is covered and compatibility is widest
Public network with roaming and payment terminals2.0.1Device management and security profiles reduce bespoke integration
Plug & Charge planned within the project life2.0.1ISO 15118 support is native rather than bolted on
Existing 1.6J estate being extended1.6J, with 2.0.1-capable hardwareAvoids a fork in the network while keeping the upgrade path open

Frequently asked questions

Is OCPP 2.0.1 backward compatible with 1.6J?

No. The two are separate major versions and a charge point speaking one cannot exchange messages with a central system that only speaks the other. In transition, operators use a CSMS that supports both.

Do I need 2.0.1 for Plug & Charge?

Not strictly — ISO 15120/15118 flows can run over 1.6J with vendor extensions — but 2.0.1 supports Plug & Charge natively, which is far less work to deploy and to keep working.

Can a 1.6J charger be upgraded to 2.0.1 later?

Only if the controller has sufficient resources and the vendor ships 2.0.1 firmware for it. Treat "field upgradable firmware" as a purchasing requirement rather than an assumption.

What is a CSMS?

The charge point management system — the back office that authorises users, records transactions, sets charging limits and monitors the estate. OCPP is the message set between it and the chargers.

Does the protocol affect the hardware I buy?

Yes. The protocol runs on the charge point controller, so the controller and its firmware roadmap determine which versions you can run over the life of the installation.

Which version does BESTAR supply?

OCPP 1.6J as standard on AC wallboxes and DC chargers, with 2.0.1 available on request. Tell us which back office you use and we confirm the combination before you order.

Related products

Level 2 AC Wallbox 7-22 kW

Level 2 AC Wallbox 7-22 kW

CategoryAC Charging
Output7.4 / 11 / 22 kW
MOQ1 unit / 1 set
Certification('IEC 61851-1:2017 (CB, TÜV Rheinland), CE (RED 2014/53/EU), UKCA, TÜV tested', True)
View specifications →
DC Fast Charging Station 60-160 kW

DC Fast Charging Station 60-160 kW

CategoryDC Charging
Output60 / 80 / 120 / 160 kW
MOQ1 unit / 1 set
Certification('supplied to match your target market', False)
View specifications →
Compact DC Charger 20-40 kW

Compact DC Charger 20-40 kW

CategoryDC Charging
Output20 / 30 / 40 kW
MOQ1 unit / 1 set
Certification('supplied to match your target market', False)
View specifications →
Need the numbers for your site?
Request a quote