TUV Rheinland Starts V2G Stack Pre-Certification Pilot

On July 10, 2026, TUV Rheinland began a pre-certification pilot for the V2G protocol stack of DC fast chargers at its Frankfurt certification center. The move matters most to charger manufacturers, certification teams, software development units, and exporters seeking CE and e-Mark approval for the EU market, because it brings communication-stack review forward in the compliance process while changing what must be prepared before a product enters formal certification.

What the pilot requires from July 10

According to the provided information, the pilot applies to DC fast chargers at TUV Rheinland's Frankfurt certification center starting July 10, 2026. Products applying for combined CE and e-Mark certification must submit the source code for bidirectional communication stacks based on ISO 15118-20 and IEEE 2030.5 in advance, together with interoperability test records. The same information states that this arrangement is expected to shorten the EU end-market access cycle by about 22 days, while increasing upfront development and validation costs for Chinese manufacturers.

Where the operational impact is likely to appear

Certification preparation moves earlier for charger manufacturers

From an industry perspective, manufacturers of DC fast chargers are likely to feel the most direct effect because source-code and interoperability evidence now need to be ready before the usual certification sequence advances. The impact is likely to show up in product readiness reviews, internal compliance coordination, and handoff timing between engineering and certification functions.

Software and protocol teams face a heavier front-end workload

Analysis shows that teams responsible for ISO 15118-20 and IEEE 2030.5 implementation may need to bring validation work forward. The practical pressure is not only on coding, but also on documenting stack behavior and preserving test records in a form acceptable for pre-certification review.

Export-oriented suppliers may need to adjust delivery planning

For companies shipping into the EU market, the stated reduction in market-entry time may improve downstream launch scheduling once products reach the certification stage. At the same time, the higher upfront verification burden means planning pressure may shift earlier, especially in product release timing, technical file preparation, and coordination with customers expecting fixed delivery windows.

Service and support partners may see more pre-submission work

Observably, any party involved in compliance support, integration testing, or certification documentation could be affected because the required materials now include both source code and interoperability records. That changes the workload mix from later-stage certification support toward earlier technical preparation and review.

What companies should watch now

Track whether the pilot remains limited or becomes a firmer gate

What deserves closer attention is the practical status of the pilot over time. Companies should distinguish between the pilot as currently described and any later wording that could clarify scope, procedural detail, or broader application within certification workflows.

Check documentation readiness, not only product functionality

For affected product lines, a key issue is whether source-code packages and interoperability test records can be organized for submission without delaying certification applications. In practice, incomplete technical documentation can become a separate bottleneck even when the charger hardware and software are otherwise ready.

Reassess front-loaded cost and schedule assumptions

Analysis shows that the stated tradeoff is clear in direction: shorter EU access time, but higher upfront development and validation cost for Chinese vendors. Companies should therefore review whether existing budgeting, milestone planning, and internal approval gates still match this earlier compliance burden.

Prepare customer and partner communication around timing

Businesses serving EU-bound projects should pay attention to how this pilot may alter the sequence of engineering completion, compliance review, and shipment planning. Even where the overall certification path becomes faster, the pre-submission phase may require earlier alignment with customers, testing partners, and internal delivery teams.

Why this reads as a process signal, not just a single filing change

Observably, this development is not only about one additional document request. It indicates greater emphasis on reviewing the V2G communication layer earlier in the approval path for DC fast chargers seeking CE and e-Mark certification together. Based on the provided information alone, it is more appropriate to understand this as a concrete process change with immediate operational relevance, while also treating its longer-term implications as something that still requires continued observation rather than a settled market outcome.

How this update is best understood at this stage

At this stage, the most balanced reading is that TUV Rheinland's July 10, 2026 pilot adds a more demanding front-end compliance requirement for DC fast charger vendors, especially those targeting the EU market through combined CE and e-Mark certification. The stated benefit is a shorter end-market access cycle, but the immediate burden shifts toward earlier software-stack disclosure and interoperability validation. It is more appropriate to understand this as a near-term operational change and a longer-term signal that protocol-stack readiness is becoming more central in certification preparation.

Basis of this article and what still needs verification

This article is based on the user-provided news title, event date, and event summary. For developments of this kind, relevant source types typically include official announcements, company statements, industry association updates, authoritative media reporting, and standards-related documentation. A specific official source link was not provided in the input, so the exact wording and any later procedural updates still need to be continuously verified. Further attention should focus on whether the pilot scope, submission detail, or certification handling requirements are clarified in subsequent official communications.