AFIR in 2026: What CPOs Must Plan Beyond 3,600 kW
Power targets are only one part of AFIR. Payment, price transparency, and DATEX II data must be part of a new charging hub’s system design from the start.

AFIR discussions often start with distance and megawatts. For CPOs, however, the regulation is also an operational and data requirement. A new truck-charging hub must therefore provide enough power while also supporting ad-hoc payment, transparent pricing, and standardised operating data from day one.
The next heavy-duty power milestones
| Deadline | TEN-T core network | TEN-T comprehensive network |
|---|---|---|
| 31 December 2027 | Across 50% of network length: at least 2,800 kW per pool and at least 2 × 350 kW | Across 50% of network length: at least 1,400 kW per pool and at least 1 × 350 kW |
| 31 December 2030 | Maximum 60 km spacing in each direction, at least 3,600 kW per pool and at least 2 × 350 kW | Maximum 100 km spacing in each direction, at least 1,500 kW per pool and at least 1 × 350 kW |
These figures are European minimum targets for network coverage. They are not a sizing formula for a specific site. Traffic, dwell time, service targets, spatial constraints, and grid availability may require a different or higher configuration.
Three obligations that belong in the design now
Payment: New publicly accessible points rated at 50 kW or more must enable ad-hoc payment by card reader or contactless device. From 1 January 2027, the retrofit requirement also covers older public points rated at 50 kW or more.
Price transparency: At public points rated at 50 kW or more, the ad-hoc price per kWh must be displayed at the station before charging starts. A time-based occupancy fee may be added, but must also be visible in advance.
Data: CPOs must provide static and dynamic data free of charge and without discrimination. Since 14 April 2026, the standardised DATEX II format has been mandatory.
Operations: Payment, backend, charging hardware, monitoring, and data delivery are not independent add-ons. Their interfaces must align in procurement, testing, and acceptance.
Keep the AFIR floor separate from the business case
For investment decisions, regulatory minima should be fixed constraints in the model. Demand and revenue assumptions belong in a separate scenario layer. This keeps three different questions visible: whether a configuration complies, whether it serves the expected operation, and whether it is commercially viable.
- Legal framework: Which AFIR requirements apply to the site, commissioning date, and charging-point class?
- Service: What waiting time, availability, and departure energy should the site deliver?
- Technology: Which charger, backend, payment, and data architecture achieves these targets?
- Economics: Which utilisation, prices, energy costs, and buildout phases create a viable case?
- Evidence: Which data is needed to document design, operation, and later changes?
How conduix connects the layers
conduix keeps regulatory minima, demand scenarios, and technical alternatives separate before evaluating them together. This makes it clear which decision follows from regulation and which follows from the site-specific commercial and operating concept.