PlugMapper logo
EV Charging Stations

PlugMapper Insights

OCPP vs OCPI: What Each Standard Does (and When You Need Them)

A plain‑English comparison of OCPP (charger ↔ backend) and OCPI (roaming between networks), with examples for RFPs and integrations.

EV Charging Stations Editorial Team10 min read
OCPPOCPIinteroperabilityroamingRFPs
Rows of networked servers in a data center

OCPP is a communication protocol between charge points and central systems—helping any compliant backend connect with any compliant charger. Read more

OCPI is a roaming protocol used to exchange data and enable services between charge point operators (CPOs) and e‑mobility service providers (eMSPs). Read more

The OCPP 2.0.1 specification adds a device model, improved security, and clearer use‑case structure compared to prior versions—useful features for complex sites. Read more

Quick comparison

  • OCPP: charger ↔ network for control, telemetry, and firmware
  • OCPI: network ↔ network for roaming, tariffs, and authentication
  • They complement each other—many deployments use both
Computer screen displaying API code
Your RFP can require OCPP on hardware and OCPI on the roaming layer.

What to put in an RFP

  • OCPP version support (e.g., 1.6J vs 2.0.1) and certified conformance
  • OCPI version and modules (locations, tariffs, sessions, tokens)
  • Uptime reporting, remote diagnostics, and firmware workflows
Enjoyed this story? Browse more insights on the PlugMapper blog.Talk to our team