4 Contract Clauses UK Buyers Demand for EV Charger Interoperability
Interoperability is not a feature you can take on trust. It requires certified OCPP implementations, verified offline behaviour and contractual portability, written into the specification before you sign anything. Standards alone will not protect you from vendor lock-in. Ask for certificates, test evidence and firmware transparency, and you build a system that keeps working when a supplier, network or payment provider changes.
TL;DR:
Vendors must provide independent certification, firmware transparency, and test evidence specific to the firmware version in use to truly ensure interoperability.
Regulatory standards in the UK require chargers to maintain smart functions and charging capability during network outages, with clear procurement guidelines for verification.
Certification programs verify implementation for specific firmware versions, but do not guarantee consistent behavior across firmware updates or entire product lines.
Precise contractual clauses on supported OCPP versions, three-party access, and offline behavior are essential to prevent vendor lock-in during procurement.
Regular re-testing and staged rollout approaches can mitigate common interoperability issues like loss of remote command response or faulty payment integrations.
Table of Contents
1. What OCPP, ISO 15118 and the smart layer actually cover
The Open Charge Point Protocol is the closest thing the industry has to a universal language between charge points and back-office software. Its Core profile handles the basics: starting and stopping a session, sending meter readings, reporting faults. Optional profiles cover smart charging, security and integration with ISO 15118, which governs vehicle-to-charger communication and underpins Plug and Charge. You can read more about how Plug and Charge works and what it means for driver authentication.
Two chargers can both claim OCPP support and still behave differently. A vendor might implement only the mandatory Core profile, leave out smart charging entirely, or apply firmware updates that quietly change how a device responds to remote commands. None of that breaks the OCPP label, but it can break your integration.
Decision-makers should keep an eye on the bodies that steer this space: the Open Charge Alliance, which owns OCPP and its certification programme, CharIN, which focuses on connector and communication standards including CCS, and LF Energy, whose open-source projects are shaping bidirectional charging. ISO also continues to update the 15118 family as vehicle-to-grid use cases mature.
2. UK regulatory baseline and procurement implications
Purchasers do not need to guess at minimum standards. The Electric Vehicles (Smart Charge Points) Regulations 2021 set out clear obligations for relevant charge points sold or installed for private use. A charger must retain its smart functionality if the owner switches electricity supplier, and it must still be able to charge a vehicle even when it loses its communications link. The same regulations prescribe contactless payment and third-party roaming access, so a driver is never stuck because they lack a particular app or membership.
Government guidance on complying with the regulations points procurement teams towards PAS 1878 and PAS 1879, the published specifications that describe how smart charging and its supporting communications should behave. The regulatory approach is outcome-based: it tells you what a charge point must do, not which brand or software achieves it. That distinction matters at the negotiating table. A vendor brochure that lists “smart charging ready” is not the same as evidence that supplier interoperability and offline charging have been verified.
For site hosts, this translates into concrete checks: does the charger accept contactless payment without a proprietary app, does it expose availability data in a machine-readable format, and does it keep charging when the network drops. Later statutory instruments extend these obligations further, tightening reliability and data requirements, which makes future-proofing as much a compliance question as a commercial one.
3. OCPP certification, test procedures and industry initiatives
Third-party certification is the closest thing to independent proof that an implementation does what it claims. The Open Charge Alliance’s OCPP certification programme tests specific versions and profiles of OCPP, covering both 1.6 and 2.0.1. A certificate confirms that a particular device, running a particular firmware version, correctly implements the profiles it was tested against. It does not certify an entire charging station line or guarantee that a future firmware update keeps the same behaviour.
The OCA’s published test procedures rely on EV emulators, controlled firmware environments and test tools that walk through transaction handling, meter values and remote commands. These results are tied to the exact firmware and lab setup used, so a certificate issued against an older firmware version tells you little about the version running on site today.
Beyond formal certification, the sector runs its own reality checks. CharIN’s testivals bring vendors together to test real hardware against real networks, and projects such as LF Energy’s EVerest are working alongside initiatives like IEA Task 53 to sort out interoperability for bidirectional and vehicle-to-grid charging, an area where standards are still catching up with ambition.
4. Procurement checklist: precise spec items and contract clauses to avoid lock-in
A specification that names “OCPP compliant” and stops there gives a vendor room to interpret compliance however suits them. Precision protects you.
State the exact OCPP version and which profiles (Core, Smart Charging, Security, ISO 15118) must be supported, then require acceptance tests that exercise each one.
Ask for independent certification evidence tied to the firmware version you will actually run, current firmware disclosure, and a documented process for signed updates with rollback.
Specify API access and data export rights, contactless payment support, third-party roaming, and reliability service levels with named metrics.
Write in handover terms: software or firmware escrow, defined acceptance milestones, and interoperability re-testing triggered by any major update.
Pro Tip: Ask the vendor to demonstrate offline charging behaviour on the actual unit you are buying, not on a reference model, before you sign off on acceptance.
Legal teams should treat these as contract clauses, not aspirational asks. A firmware escrow clause and an exit provision cost little to include and a great deal to add later once you are dependent on one supplier’s cloud.
5. Operational risks and mitigation: real failure modes and how to reduce them
Most interoperability failures are not dramatic. They show up as a charger that stops responding to remote commands after a firmware push, a payment terminal that only accepts one operator’s app, or a device that goes dark the moment its network connection drops instead of falling back to local charging.
Insist on independent certification matched to the firmware version in production, not a historic model.
Roll out new sites or firmware in stages, with a fallback plan if a device fails an interoperability check.
Include contractual guarantees for local control modes so a cloud outage never stops a vehicle charging.
Re-test interoperability whenever the network operator, firmware or payment provider changes.
Build acceptance testing into every maintenance window, not just the initial installation.
None of this eliminates risk entirely, but it turns invisible failure modes into things you can see coming.
6. How Swift Charging supports compliant, interoperable installations
The company works with businesses from site survey through to specification, installation and long-term management, covering workplace, fleet, and destination charging projects. Our services include charger installation, migration of outdated units onto modern management platforms, software and firmware oversight, load management, and ongoing maintenance support. Support is offered to help businesses apply for available EV charging grants, which can be useful when interoperability requirements push a project towards higher-specification hardware. This combination of site experience and platform management can help reduce procurement and operational risk.
7. When to demand the highest interoperability standards
Public, rapid and fleet sites carry the highest cost of failure, so insist on full certification, verified offline behaviour and contractual portability there. Lower-traffic workplace sites can accept a phased approach, provided contracts include exit and re-testing clauses tied to firmware or network changes.
— Swift Charging
How Swift Charging can help
Choosing between vendors, protocols and certification evidence takes time most facilities or fleet teams do not have to spare. The process can be handled end to end: site assessment, specification against the standards covered above, installation, software configuration and ongoing maintenance, to help ensure infrastructure meets its regulatory baseline without requiring you to interpret test documents yourself.
Whether you are planning a single workplace site or a multi-location rollout, our commercial EV charging solutions cover the full project from feasibility through to long-term management. Get in touch to discuss your site and see what a compliant, portable specification looks like for your business.
Sources
FAQ
What is the 80% rule for EV charging?
There is no universal “80% rule” set out in the regulations covered here; the figure is more commonly associated with battery charging curves slowing once a vehicle’s battery reaches around 80% state of charge, which is a battery management behaviour rather than a charger interoperability requirement. Definitions vary by vehicle manufacturer, so treat any specific percentage as a general guide rather than a fixed standard.
Am I allowed to install my own EV charger?
Regulated smart charge points sold for private use in the relevant market must meet the requirements set out in the Smart Charge Points Regulations, including safety and electrical installation standards, so self-installation without qualified electrical work is not advisable and may not be compliant. For commercial or workplace sites, installation is typically carried out by a qualified provider to meet both electrical safety rules and the regulatory obligations covering smart functionality and reliability.
Are Type 2 and CCS2 the same connector?
No, they are different connectors that serve different purposes. Type 2 is used for AC charging, while CCS2 combines the Type 2 pins with two additional DC pins to support rapid DC charging, so a vehicle with a CCS2 inlet can generally use both AC and DC chargers.
Is CCS or NACS better for charging?
Neither standard is universally “better”; CCS remains the dominant DC rapid charging connector across most markets, while NACS (originally Tesla’s connector) is gaining adoption in North America. For buyers outside North America, CCS remains the practical choice, and procurement decisions should follow the connector standard already established in the relevant market rather than anticipating a shift.
What does OCPP certification actually guarantee?
OCPP certification confirms that a specific device running a specific firmware version correctly implements the tested profiles, verified through the Open Charge Alliance’s certification programme. It does not guarantee that every unit in a product line, or a future firmware update, will behave identically, which is why procurement teams should request certification evidence matched to the exact firmware they intend to run.
Recommended