Fleet operators have a charging problem that single-vehicle owners don’t: their vehicles range widely, often charging at public networks far from the home depot. They need an account-and-billing model that works across many networks without becoming an administrative nightmare.
OCPI is what enables this. By participating in OCPI roaming (typically through a fleet-focused eMSP), a fleet can have a single charging account that works at thousands of stations across many networks.
This article covers how OCPI works for fleets, the integration patterns, and the operational considerations.
The fleet roaming model
A typical fleet roaming setup:
- Fleet operator has many vehicles operating across a region.
- Fleet partners with a fleet-focused eMSP (or operates one internally for larger fleets).
- eMSP has OCPI roaming agreements with many CPOs (or connects through hubs that aggregate).
- Fleet vehicles charge anywhere that’s reachable through the eMSP’s OCPI network.
- eMSP receives sessions and CDRs from all the CPOs and consolidates billing for the fleet.
- Fleet receives one consolidated bill instead of accounts at dozens of networks.
The fleet experiences single-account simplicity; the eMSP handles the OCPI complexity.
flowchart LR
F[Fleet<br/>vehicles] --> M[Fleet eMSP]
M -->|OCPI| C1[CPO A]
M -->|OCPI| C2[CPO B]
M -->|OCPI| H[Roaming hub]
H --> C3[Many CPOs]
C1 -->|CDRs| M
C2 -->|CDRs| M
C3 -->|CDRs| H
M -->|One bill| F
style M fill:#e0f2fe,stroke:#0284c7If the mechanics of who-sends-what feel unfamiliar, the What is OCPI primer covers the CPO/eMSP roles and the roaming handshake in more depth.
Fleet-focused eMSPs
A few characteristics that distinguish fleet eMSPs from consumer eMSPs.
B2B contract structure. Bilateral contracts with the fleet operator, not consumer signups. Payment terms are net-30 or similar, not credit cards.
Volume-based pricing. Fees scale with energy or session volume; sometimes flat per-vehicle.
Reporting depth. Fleets need per-vehicle, per-driver, per-route, per-cost-center reporting. Consumer eMSPs typically don’t provide this.
Account hierarchies. Multiple drivers per vehicle, multiple vehicles per cost center, multiple cost centers per fleet. The eMSP’s data model handles this.
Integration APIs. Fleet management systems integrate with the eMSP via APIs. Not just an app — programmatic access.
Custom tariff handling. Fleets may negotiate special rates with the eMSP, which the eMSP may pass through (or absorb).
Compliance support. Tax handling, mileage tracking, emissions reporting — fleet operations need these for regulatory and tax purposes.
Examples in 2026 span both sides of the Atlantic: in North America, ChargePoint fleet, EV Connect fleet, EVgo, and Electrify America commercial offerings; in Europe, Shell Fleet Solutions and BP fleet products; plus regional players in various markets.
OCPI tokens for fleet vehicles
How does a fleet vehicle authenticate at a public charger?
RFID cards or fobs distributed to drivers. Each driver has a card or built-in vehicle RFID. The card’s UID is the Token that the eMSP validates via OCPI.
App-based authentication. Driver opens the eMSP’s fleet app to start a session.
ISO 15118 Plug & Charge. Vehicle has a contract certificate from the fleet’s eMSP. PnC works at any network in the fleet’s roaming reach.
For fleets, PnC is particularly valuable — drivers don’t have to fumble with cards or apps; the vehicle’s identity is enough.
CDR consolidation
When fleet vehicle X charges at CPO Y’s station:
- CPO Y’s CSMS records the session.
- CPO Y sends a CDR via OCPI to the eMSP that owns the user (the fleet eMSP).
- The eMSP receives CDRs from many CPOs and aggregates.
- Periodically (typically monthly), the eMSP invoices the fleet for all consolidated CDRs.
- The eMSP settles with each CPO based on the agreed roaming terms.
The fleet operator sees one invoice with detail per-session-per-CPO if they want it. The CDRs module is what carries that billing record between operators, and understanding OCPI tariffs helps explain why the same station can produce different per-kWh costs.
Cost allocation within the fleet
A fleet often needs to allocate charging costs to internal cost centers:
- Per vehicle (which department owns the vehicle).
- Per driver (sometimes).
- Per route or job (especially in service fleets).
- Per project (for capital projects).
- Per geography (regional cost analysis).
The eMSP provides the CDR data; the fleet’s internal systems (typically the fleet management software or accounting system) handle the allocation.
OCPI provides the granular data; the allocation logic is the fleet’s business problem.
Mixed depot + roaming
Most fleets have a mix of depot charging (home, controlled, cheap) and roaming (public, occasional, premium).
A typical pattern:
- 80-90% of energy at depot. Cheap, scheduled, controlled.
- 10-20% of energy at public networks for vehicles on long routes or away from depot.
The depot uses OCPP (charger-to-CSMS) for fleet depot operations (coming soon). The public charging uses OCPI (CSMS-to-eMSP-to-CPO).
Reporting consolidates both:
- Depot charging data from the fleet’s CSMS.
- Roaming charging data from the eMSP’s CDRs.
- Combined view: total energy, total cost, per-vehicle metrics.
A good fleet management platform integrates both data sources.
Larger fleets as CPO+eMSP
Some larger fleets operate at a scale where being just a customer of an eMSP isn’t optimal. They may:
Operate their own eMSP function — they have their own OCPI integration into their CSMS, with direct relationships with key CPO partners.
Operate their depot as a CPO — their depot chargers are publicly accessible (for employees, partners, occasional guests).
Negotiate directly with CPOs for special rates at high-volume corridors they use.
This is operationally more complex but gives more control and may save money at scale. Whether that trade-off pays off depends on the same economics covered in EV charging business models (coming soon).
Cost considerations
Public charging is typically 2-4x more expensive per kWh than depot charging:
- Depot: maybe $0.10-$0.15/kWh (including infrastructure amortization).
- Public AC: $0.20-$0.40/kWh.
- Public DC fast: $0.30-$0.60/kWh.
For fleets, minimizing public charging — and maximizing depot charging when public is needed — is a key cost lever.
Strategies:
- Route planning that returns vehicles to depot when possible.
- Preferred-partner pricing with specific CPOs along common routes.
- Time-of-use awareness for public charging (off-peak rates when possible).
- Avoid emergency-grade pricing — plan ahead rather than topping up at the most expensive last-mile location.
The eMSP can help with some of these (especially preferred-partner pricing); the fleet handles route planning.
Compliance and reporting
Fleet operators often have compliance and reporting needs that touch OCPI data.
Emissions reporting. Many jurisdictions require fleet operators to report carbon footprint. Energy consumed (with grid carbon intensity) is a key input.
Mileage tax / reporting. Some jurisdictions tax based on miles driven. Cross-referencing OCPI session data (when and where vehicle charged) with miles data is useful.
Fuel-card-equivalent reporting. Many fleets had fuel cards historically; the EV equivalent is OCPI-backed charging. Reporting needs to maintain audit-grade quality.
Driver expense management. If drivers occasionally charge using personal accounts (reimbursed by fleet), reconciliation needs careful handling.
The eMSP’s reporting capabilities matter — fleet-grade reporting is more demanding than consumer-grade.
Common operational issues
A few things that come up.
Charger unavailable. Public networks aren’t 100% reliable. Driver pulls into a charger and it doesn’t work. Need backup plans.
Pricing surprises. A charger that was supposed to be $0.30/kWh turns out to be $0.50. Either tariff change or a confused tariff display. Reconciliation needed.
Failed authorization. RFID doesn’t work; app crashes; PnC fails. Driver stranded. Customer service from the eMSP matters.
Roaming gaps. The eMSP doesn’t have coverage in a specific region. Driver finds a charger but can’t use it. Plan routes around coverage.
Currency / cross-border. Driving across countries means crossing OCPI roaming boundaries. Some hubs handle this seamlessly; some don’t.
Disputes. Bill doesn’t match what driver experienced. Resolution process matters.
What fleet operators should ask their eMSP
A checklist of questions when choosing a fleet eMSP.
Coverage. Which networks in which regions? Important corridors covered?
Pricing. Negotiable based on volume?
Reporting. Does the reporting depth match fleet needs?
Integration. APIs to fleet management software?
SLA. What happens when a driver is stranded by a failed charger?
Account hierarchy. Cost-center, vehicle, driver structure supported?
ISO 15118 PnC support. Important for friction-free driver experience.
Compliance reporting. Emissions, tax, audit-ready outputs?
Customer service. B2B-grade support hours and channels?
Contract terms. Lock-in, termination clauses, price-change policies?
The honest summary
OCPI is the protocol that makes fleet roaming work — single account, broad coverage, consolidated billing. Most fleets work through a fleet-focused eMSP that handles the OCPI integration on their behalf. Larger fleets sometimes integrate more deeply (operating their own eMSP function, direct CPO relationships). Either way, depot OCPP and public OCPI together cover the fleet’s charging needs, with cost optimization, compliance, and operational integration being the recurring themes.