What the interface standardizes
The VDA publishes the interface specification and versions. Use the agreed specification when evaluating order and status exchange between control software and vehicles. [Source]
The VDA announced version 3.0 in April 2026. A new publication does not mean every installed vehicle or platform already supports that version. [Source]
What remains outside a compatibility label
- The exact vehicle model and software combination.
- Supported actions for load handling, charging and special equipment.
- Process ownership, station readiness and business-system feedback.
- Navigation and safety responsibilities at the vehicle and site.
A shared protocol name alone does not prove that a complete process can be executed. A vendor-specific function may also require an additional interface or adapter.
Different platform approaches
The practical selection question is which approach supports the actual vehicles and workflows. A protocol list does not replace a demonstration of the required actions.
Questions for acceptance
- Which version is supported by both controller and vehicle?
- Which optional actions and state fields are used?
- How are unsupported actions rejected or handled?
- What happens after communication loss and recovery?
- How do load dimensions, routes and stations enter the configuration?
- Who maintains compatibility after an update?
Sources and context
Base review: 18 September 2026. Manufacturer information is not an independent comparative test.