I
Impetora

AI route optimization in logistics: regulatory map

By Impetora -

Route optimization is the most economically valuable AI deployment in logistics and the most regulatorily benign. Annex III of the EU AI Act lists Annex III 2 (critical infrastructure) and 4 (employment) as high-risk triggers, but pure route optimization sits outside both for typical fleet operators. UNECE WP.29 vehicle-cybersecurity rules and NIS2 supply-chain measures apply at the edges [1].

Annex III 2
AI Act critical infrastructure trigger
EUR-Lex
Annex III 4
AI Act employment trigger
EUR-Lex
UNECE R155
Cyber Security Management System
UNECE
NIS2
Directive 2022/2555
EUR-Lex

What does AI route optimization actually do?

The system computes vehicle routes that minimise distance, time, fuel or carbon while respecting constraints: delivery windows, vehicle capacity, driver hours, road restrictions, customer priority. Inputs are orders, fleet status, real-time traffic, weather and historical patterns. Outputs are sequences of stops with estimated arrival times, fed to driver applications and dispatch consoles.

The system is computational, not safety-critical. It does not control the vehicle; the driver does. That distinction is what keeps the deployment outside the AI Act high-risk regime in normal fleet operations.

Why is route optimization not high-risk by default?

Annex III 2 covers AI systems intended to be used as safety components in the management and operation of critical infrastructure including road traffic and the supply of water, gas, heating and electricity. Pure routing for a private fleet does not manage road traffic at the network level. It plans the operator's own vehicles. Supervisors have not extended Annex III 2 to fleet routing in any published guidance to date [1].

Annex III 4 covers AI in employment, worker management and access to self-employment. A routing tool that assigns drivers to routes touches employment if it materially determines work allocation, performance evaluation or termination. The boundary is whether the tool drives HR decisions or merely informs operational planning. Most fleet routing falls on the operational-planning side.

Annex III 2/4
trigger conditions, neither typically engaged
EUR-Lex

When does routing AI become high-risk?

Three patterns push it across the line. First, integration with autonomous-driving features that make the AI a safety component of the vehicle (Annex III 2 plus UNECE WP.29). Second, integration with worker-management systems where the routing score determines pay, performance review or contract continuation (Annex III 4). Third, deployment in critical-infrastructure logistics (energy, water, hospital supply) where operational disruption has societal consequences (potential Annex III 2 reach).

For each, the conformity-assessment, data-governance and oversight obligations of Chapter III engage.

What about UNECE WP.29 vehicle-cybersecurity rules?

UNECE Regulation No. 155 (Cyber Security Management System) and No. 156 (Software Update Management System) apply to type approval of new vehicle classes from 2024 onwards. Routing AI that runs on the vehicle (in-cab system) becomes part of the vehicle's software stack and falls inside the scope of UNECE R156 update management [2].

For routing AI that runs in the cloud and is consumed by drivers via a phone or dispatch terminal, the vehicle-cybersecurity regulations do not engage directly. The supply-chain cybersecurity reach comes from NIS2 instead.

How does NIS2 apply?

Directive (EU) 2022/2555 (NIS2) covers transport (including road) as an essential sector and postal and courier services as important. Article 21 requires risk-management measures including supply-chain security, business-continuity, incident handling and basic cyber hygiene. AI vendors providing routing services to in-scope operators inherit those expectations through contractual flow-down and direct supply-chain assessment [3].

The Cyber Resilience Act (Regulation (EU) 2024/2847) adds product-level cybersecurity requirements for connected products. Cloud-routing-as-a-service is not a product under the CRA, but on-premise routing software with digital elements is.

What does a defensible routing-AI design look like?

Five elements. Narrow intended-purpose statement (operational route planning, not driver evaluation, not autonomous control). Segregation of routing data from worker-performance systems where employment risk would otherwise engage. NIS2-aligned supplier security including breach-notification cooperation and supply-chain risk management. UNECE R156 alignment if the AI runs on the vehicle. Driver-facing transparency on automated assignment under Article 50 if the AI directly communicates with workers.

Frequently asked questions

Is fleet routing subject to AI Act conformity assessment?
No, by default. Annex III 2 (critical infrastructure) and Annex III 4 (employment) do not engage for typical operational route planning. Conformity-assessment obligations apply only if the deployment crosses into safety-component or worker-management territory.
What if the routing AI also assigns gig workers to deliveries?
Then Annex III 4 (employment, worker management, access to self-employment) likely engages. The full Chapter III obligations apply: risk management, data governance, technical documentation, logging, transparency, human oversight, accuracy and post-market monitoring.
Does NIS2 apply to a SaaS routing vendor?
Indirectly. The vendor is part of the supply chain of a road-transport operator that is itself in scope of NIS2 as an essential or important entity. Article 21(2)(d) requires the operator to assess and manage supply-chain risks. The vendor inherits security expectations through the contract and through direct supplier assessments.
What about telematics data and GDPR?
Telematics data identifying drivers is personal data under GDPR. Article 28 processor agreement, Article 32 security measures and a clear lawful basis (typically legitimate interests with a balancing assessment) are required. Some Member States have additional rules on monitoring of workers under Article 88; works-council consultation is mandatory in several jurisdictions.
Is there a UNECE rule for cloud-only routing software?
Not directly. UNECE R155 and R156 apply to vehicle type approval. Cloud-only routing consumed via driver apps does not fall inside the type-approval perimeter. NIS2 supply-chain security and the Cyber Resilience Act (for products with digital elements) are the relevant cyber regimes for cloud routing.
Impetora

Ready to scope your project? Submit a short brief and we reply within one business day.

Sources cited

Sources cited (5) - show
  1. Regulation (EU) 2024/1689 (Artificial Intelligence Act). European Union, Official Journal, 2024-07-12. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R1689
  2. UNECE Regulation No. 155 - Cyber Security Management System. United Nations Economic Commission for Europe, 2021-01-22. https://unece.org/transport/vehicle-regulations
  3. Directive (EU) 2022/2555 (NIS2). European Union, Official Journal, 2022-12-14. https://eur-lex.europa.eu/eli/dir/2022/2555/oj
  4. Regulation (EU) 2024/2847 (Cyber Resilience Act). European Union, Official Journal, 2024-10-23. https://eur-lex.europa.eu/eli/reg/2024/2847/oj
  5. Regulation (EU) 2016/679 (GDPR). European Union, Official Journal, 2016-04-27. https://eur-lex.europa.eu/eli/reg/2016/679/oj
About Impetora
Impetora designs, builds, and deploys custom AI systems for enterprises in regulated industries. We operate from Vilnius and Amsterdam and work in five languages.
Discovery call

Book a discovery call

Tell us what you would like to build. We reply within one business day.

30-minute call. Free of charge. No obligation.