The vehicles entering your fleet today will hit the secondary market in 2028 or 2029. The residual value they command will depend on one thing: can you prove how the batteries were treated?

Not what condition they are in. That is a point-in-time snapshot. The question remarketers and auction buyers are increasingly asking is why the battery is in that condition. Two vehicles with identical 92% State-of-Health readings have very different futures depending on whether they were smart-charged to 80% overnight or hammered with DC fast charging and left at 100% in summer heat.

The Battery Passport regulation (EU 2023/1542) makes this explicit. From February 2027, every EV battery needs a lifecycle record: state of health parameters updated throughout the battery’s life, not just at defleet.

That data has to come from somewhere. For most fleets, it comes from the Charge Point Management System.

Which means your CPMS selection is not an operational decision. It is a remarketing decision.

The Data Pipeline Problem

Fleet operations and remarketing typically sit in different parts of the organisation. Charging infrastructure gets specified for operational efficiency: fastest install, lowest cost, best driver experience. Nobody asks what data it captures or where that data goes.

Three years later, vehicles come off-lease. The remarketing team needs to demonstrate battery treatment. But the charging data is locked in a proprietary vendor portal, incomplete, or simply not there.

The gap is structural. Fleet ops optimises for today. Remarketing needs data from three years ago.

Closing that gap requires thinking about charging infrastructure as a data asset, not just an operational utility.

What OCPP 2.0.1 Actually Gives You

Open Charge Point Protocol 2.0.1 is not just a technical standard. It is a strategic choice about data ownership and interoperability.

An OCPP 2.0.1-compliant CPMS captures session timestamps, duration, and energy delivered. It records charging curves showing whether the vehicle was smart-charged to a target SoC or pushed to 100%. It tracks DC vs AC ratios across the vehicle’s charging history. It logs location and charger type for every session.

Critically, OCPP is vendor-neutral. You can swap hardware suppliers without losing your data history. You can aggregate sessions across multiple depot locations, home chargers, and third-party networks into a single vehicle record.

Proprietary systems lock you in. Open standards give you portability and a complete picture.

The Public Charging Gap

Fleet vehicles do not charge exclusively at depots. Drivers use public networks, destination chargers, home wallboxes. Each session is part of the battery’s history, but most fleets have no visibility into off-network charging.

ISO 15118 Plug & Charge changes this. It enables vehicle-based authentication at any compatible charger, linking sessions to the vehicle identity rather than a driver app or RFID card. Combined with roaming agreements and backend data aggregation, it becomes possible to build a complete “battery biography” regardless of where the vehicle charged.

The infrastructure choices you make today determine whether that data exists in 2029.

V2G: Cost Reduction and RV Protection

Vehicle-to-Grid participation is coming. Grid operators need flexible demand response. OEMs are building bidirectional capability into new models. The economics are compelling: vehicles generating revenue from grid services while parked.

The remarketing concern is predictable: does V2G participation degrade the battery and destroy residual value?

The research says no, if managed properly. Calendar aging (degradation from time and temperature) accounts for 85-90% of total battery degradation. Cyclic aging from charging and discharging is 10-15%. V2G adds cycles, but keeping the battery in a managed 20-80% SoC range actually reduces calendar aging stress compared to vehicles sitting at full charge overnight.

The real issue is documentation. A vehicle with undocumented V2G participation is a liability. A vehicle with OCPP-logged V2G sessions, showing every discharge event stayed within OEM-specified parameters, is a better-understood asset than one with no charging history at all.

V2G becomes a remarketing advantage when the data exists to prove it was done correctly.

Warranty Claims Become Engineering Conversations

Fleet managers hesitate on V2G because of warranty risk. What happens when a battery fails and the OEM asks how it was used?

With comprehensive CPMS logging, you have the answer: total energy throughput, cycle count, depth of discharge distribution, time at each SoC level, charging rates, ambient conditions. The data proves compliance with recommended usage patterns.

Warranty disputes become engineering conversations, not legal arguments. The ambiguity that drives conservative RV forecasting disappears.

This only works with open, auditable data. Proprietary systems that the OEM cannot independently verify offer no protection.

The Infrastructure Stack That Connects Fleet to Remarketing

The throughline is data continuity. Decisions made when specifying charging infrastructure determine what information exists when vehicles reach the secondary market.

The stack that delivers this: OCPP 2.0.1-compliant chargers at depots and employee homes; ISO 15118 Plug & Charge for seamless public charging data aggregation; CPMS middleware that normalises data across hardware vendors and integrates with fleet management and telematics; V2G controls that enforce SoC bounds and log every grid interaction; data export APIs that feed remarketing systems and Battery Passport compliance.

This is what Codibly builds. Our CPMS accelerators are designed for fleets that understand charging infrastructure is not just about electrons. It is about the data trail those electrons leave behind.

The February 2027 deadline is 13 months away. The vehicles you are onboarding now will be the first to require Battery Passport compliance at defleet.

The question is whether your charging infrastructure is ready to generate the data that protects their residual value.

For a technical conversation about CPMS architecture and V2G integration, contact the Codibly eMobility team.