How to Launch V2H: An Operator's Checklist
Read Time: 10 minutes
Author: eMabler Team
Quick Answer
Launching V2H as a charging operator requires aligning three layers: compatible hardware, a charging management platform that supports bidirectional sessions, and a clear regulatory path in your target market. The hardware must support ISO 15118-20 and be certified for bidirectional operation. The platform must handle discharge commands, dual-direction metering, and OCPP V2H integration. Before scaling, a small pilot of 10 to 20 installations will surface compatibility and operational issues that are far easier to fix at small scale.
This article covers each of these points in detail.
Most operators who are serious about V2H already understand the technology and the business case. The harder question is how to actually get it running on your platform without discovering critical gaps halfway through a deployment.
V2H implementation has more moving parts than standard charging. The vehicle, the hardware, the software, and the regulatory environment all need to align before a single session can run correctly. Getting that alignment right from the start saves significant time and cost later.
If you are still working through whether V2H makes sense for your business at all, our complete guide to V2H charging for operators covers the technology, the business case, and the regulatory landscape in full. This article assumes you have made the decision to move forward and focuses on the practical steps to get there.
Step 1: define your V2H product scope before you build
Before touching hardware or software, define what you are actually building.
V2H means different things depending on the operator. For a residential CPO, it might mean a managed home energy product with automated charge and discharge scheduling. For an energy utility, it might mean a demand response programme that uses EV batteries as a distributed flexibility resource. For a property developer, it might mean V2H-ready infrastructure in new builds, ready to activate when vehicle compatibility catches up.
Each of these has different hardware requirements, different platform needs, and different regulatory implications. Starting without a clear scope leads to decisions that work for one version of the product but block another.
Define the following before moving to step two:
Who is the customer and what problem does V2H solve for them specifically?
What is the primary value you are selling: bill savings, backup power, demand response participation, or a combination?
What is the target market and what are the applicable regulatory requirements?
What vehicles do your target customers drive, and do those vehicles support bidirectional charging?
The answers to these questions will shape every subsequent decision.
Step 2: choose the right bidirectional EVSE hardware for V2H
V2H platform integration starts with the right hardware. A standard AC wallbox cannot run a bidirectional session. You need a DC bidirectional EVSE that is specifically designed and certified for V2H operation.
What to look for in a bidirectional EVSE
ISO 15118-20 support. This is the communication standard that enables bidirectional power transfer between the vehicle and the charger. Hardware that does not support ISO 15118-20 will either be incompatible with a growing range of vehicles or will rely on proprietary protocols that limit your options over time. Ask for third-party certification, not just the supplier's own claim.
CE marking for bidirectional operation. Standard CE marking for EV charging equipment does not automatically cover bidirectional operation. Verify that the specific certification covers the hardware in its bidirectional configuration.
CCS and CHAdeMO compatibility. CHAdeMO has supported bidirectional charging the longest and most of the current compatible vehicle population uses it. CCS with ISO 15118-20 is now arriving. If your target market is European, CCS compatibility is increasingly important. If you are working with an older vehicle fleet, CHAdeMO may still be the primary requirement.
Power output range. Most residential V2H deployments use hardware in the 6 kW to 10 kW range. That is enough to cover most household loads without requiring significant electrical upgrades at the property. Higher power outputs are available but add cost and installation complexity.
Remote management capability. The charger must be manageable remotely via your platform. Check that the hardware supports the same OCPP version your platform uses and that remote configuration, firmware updates, and session control all work reliably over that connection.
Hardware suppliers to evaluate
The market for certified bidirectional EVSE is still relatively limited but growing. When evaluating suppliers, ask specifically for third-party certification documentation, confirmation of ISO 15118-20 support, and reference deployments you can speak to. A supplier who cannot provide any of those three things is not ready for a production deployment.
Step 3: choose the right V2H platform integration
This is where many operators discover the gaps. A charging management platform that works well for standard charging may not be equipped for bidirectional sessions without significant development or integration work.
Bidirectional charging software: what the platform needs to handle
Discharge command management. The platform needs to be able to send discharge commands to the charger, not just charge commands. This sounds simple but requires protocol support, session state logic that handles both directions, and safety checks that prevent discharge below a defined battery reserve.
Dual-direction metering. A standard charging session records energy delivered to the vehicle. A V2H session also records energy delivered from the vehicle to the building. The platform needs to track both directions separately, with accurate timestamps, for billing, reporting, and any demand response obligations.
Scheduling and optimisation logic. The value of V2H comes from automated decision-making: charge when electricity is cheap, discharge when it is expensive, hold when the driver needs range. The platform needs to support scheduling rules based on time-of-use tariffs, spot prices, solar generation data, or grid signals, depending on the product you are building.
Home energy system integration. For a full home energy management product, the platform needs to read real-time household consumption data, either from a smart meter or a home energy management system. Without this, the discharge logic is blind to what the house is actually using, which limits both the efficiency and the safety of the system.
Driver app transparency. The customer needs to be able to see what the system is doing and why. A charge session that runs unexpectedly or a discharge that leaves the car below the expected battery level will generate support calls. The app needs to show current session status, upcoming schedule, and the ability to override or adjust settings easily.
V2H OCPP integration
OCPP is the protocol most platforms use to communicate with chargers. Standard OCPP was designed for one-directional charging. V2H requires extensions.
OCPP 2.0.1 introduced support for some bidirectional use cases, but implementation varies across hardware and software vendors. Before committing to a hardware and platform combination, test the following specifically:
Can the platform send a discharge command and receive confirmation from the charger?
Does the charger report both charge and discharge metering data in a format the platform can record?
Can the platform set a minimum state-of-charge limit that the charger will respect during discharge?
Does the session handling cover error states specific to discharge, such as vehicle refusal to discharge or battery temperature limits?
If any of these fail in testing, you have a platform gap that needs to be resolved before deployment.
Step 4: confirm the right V2H regulatory requirements before deployment
Each market has its own requirements. Our article on V2H regulatory requirements covers the landscape in detail. For the purposes of this checklist, the key actions before deployment are:
Confirm whether discharging from a vehicle to a building is classified as generation in your target market, and what obligations that classification triggers
Contact the local DSO to confirm whether notification or approval is required before installing a bidirectional charger
Verify metering requirements: does the installation need a separate export meter, and if so, who supplies and installs it?
Confirm that your chosen EVSE meets the safety standards required for bidirectional operation in the target market
Document your regulatory analysis for each market in writing, so you have a clear record if questions arise later
Do not assume the requirements in one market apply to another. Even within a single country, DSO requirements can vary by region.
Step 5: install and commission your V2H charger
A V2H installation is more involved than a standard wallbox installation. Budget for that difference in time, cost, and technical expertise.
Site assessment
Before installation, assess:
Main fuse capacity: bidirectional chargers typically require a 32A or 63A supply. Older properties may need an upgrade
Consumer unit: confirm there is capacity for the additional circuit and that the earthing arrangement is compatible with the EVSE requirements
Metering: if a separate meter is required by the DSO or for your own billing purposes, plan that into the installation scope
Network connectivity: the charger needs a reliable internet connection for remote management. Assess whether existing Wi-Fi or an Ethernet connection is available, or whether a cellular modem is needed
Commissioning checklist
Once installed, run through the following before handing over to the customer:
Confirm the charger is communicating with the platform via OCPP
Run a test charge session and verify metering data appears correctly in the platform
Run a test discharge session and verify the charger responds to the discharge command, respects the minimum state-of-charge limit, and records discharge metering data correctly
Confirm the driver app shows accurate session status in real time
Set the customer's preferred battery reserve and verify the system respects it
Walk the customer through the app and explain how to adjust their schedule and override the system if needed
Step 6: run a pilot before you start scaling
Running a full rollout without a pilot is a risk that is easy to avoid.
A pilot of 10 to 20 installations in a controlled environment will surface issues that no amount of planning fully anticipates. Vehicle compatibility edge cases, metering discrepancies, DSO notification delays, customer behaviour patterns that differ from assumptions, integration bugs that only appear in production. All of these are manageable at pilot scale. At full rollout scale, they are expensive.
What to measure during the pilot
Technical reliability. What percentage of sessions complete without errors? What are the most common failure modes?
Energy performance. Are the savings the system delivers matching the projections? If not, is the scheduling logic the issue, the metering, or the customer's usage patterns?
Customer experience. Are customers using the app actively? Are they overriding the system frequently? If they are, find out why before rolling out to hundreds of installations.
Support volume. How many support contacts per installation per month? What are the most common questions? Use this to improve the onboarding materials and the app before scaling.
Set a minimum performance threshold before you proceed to full rollout. If the pilot does not meet it, fix the issues first.
The launch: V2H CPO checklist
Scope
Customer defined, problem defined, target market defined
Vehicle compatibility confirmed for target customer base
Hardware
Bidirectional EVSE selected with ISO 15118-20 support and third-party certification
CE marking confirmed for bidirectional operation
Connector type confirmed for target vehicle population
Remote management via OCPP confirmed
Platform
Discharge command management tested and working
Dual-direction metering confirmed
Scheduling and optimisation logic in place
Home energy system integration scoped or live
Driver app covers session status, schedule, and manual override
V2H OCPP integration
Discharge commands tested end to end
Minimum state-of-charge limits confirmed working
Error state handling confirmed
Regulatory
Generation classification confirmed for each target market
DSO notification or approval completed where required
Metering requirements confirmed and met
Safety standard compliance confirmed
Installation
Site assessment completed for each property
Commissioning checklist completed for each installation
Customer onboarding completed
Pilot
Pilot completed with minimum 10 installations
Technical reliability, energy performance, customer experience, and support volume all measured
Performance thresholds met before full rollout
Conclusion
Launching V2H is a more involved process than standard charging, but it is a manageable one if you work through each layer in sequence. The operators who run into trouble are usually the ones who skipped the platform assessment, assumed regulatory requirements were the same as another market, or went straight to full rollout without a pilot.
The checklist above covers the critical steps. Not every item will apply to every deployment, but working through it systematically will surface the gaps before they become problems.
