The most frequent question we have been asked since early April is not “how much does the G2V2 cost”, but “if I have the G2V2, do I still need fleet management?”. It’s the same logic that, twenty years ago, made some people wonder whether satellite navigation would make trip planning obsolete. The answer is no, and understanding why saves you two expensive decisions: buying an “all-in-one” platform that doesn’t scale, or thinking you can put the telematics conversation on hold because “the tachograph now records everything”.
The second-generation smart tachograph (G2V2) that becomes mandatory on 2.5-3.5 t vans from 1 July 2026 for international transport or cabotage is a compliance device with a remarkably high-quality operational data source attached to it. It is not a fleet management platform, but for the first time it is a talking node: it talks to the fleet management system through a standardised interface. Understanding where one ends and the other begins is the strategic step that separates an informed choice from a forced purchase.
The dual nature of G2V2
The G2V2 is two things at once:
- A compliance device. It records driver activities (driving, other work, availability, rest) on the driver card, stores 56 days of data in the vehicle’s mass memory, cryptographically signs every record to make it legally admissible, and communicates with enforcement authorities via DSRC.
- A structured operational data source. GNSS positions, loading/unloading timestamps, border crossings and event anomalies form a data stream that, until a few years ago, van fleets simply did not have.
Both natures matter, but they are different by design. The first is regulated, sealed, immutable. The second is available but raw, in tachograph format (.ddd/.v1b/.v2b), not directly analysable in Excel. This is where fleet telematics comes into play.
What the G2V2 records: the precise matrix
For clarity, here is the exact list of what the G2V2 records by default (Reg. EU 165/2014 as amended by Reg. EU 2020/1054):
| Data type | Frequency | Retention |
|---|---|---|
| Driver activity (driving/work/availability/rest) | Continuous | 56 days VU + 28 days card |
| GNSS position start/end of day | Per event | 56 days |
| GNSS position every 3 h cumulative driving | Cumulative | 56 days |
| Border crossing | Automatic | 56 days |
| Loading/unloading start/end (manual) | Per event | 56 days |
| Instant speed last 24 hours | 1 Hz | 24 h |
| Distance travelled | Cumulative | Vehicle history |
| Driver IDs | On card insertion | Permanent |
| Anomalies and events (tamper, GNSS lost, sensor errors) | Per event | 56 days |
| Calibration and technical parameters | On intervention | Vehicle history |
It is a rich stream, but it is enforcement-oriented: it is built for an inspector to reconstruct a driver’s activity, not for a fleet manager to plan tomorrow’s route.
What the G2V2 does NOT do
Almost everything a fleet manager actually needs for day-to-day operations is not in the G2V2:
- Route planning. The G2V2 doesn’t compute or optimise routes. It doesn’t know that customer X has a 9-12 window and customer Y only after 2 pm.
- Dynamic ETAs for customers. The G2V2 doesn’t text the recipient “the courier arrives in 30 minutes”.
- Digital Proof of Delivery. Electronic signature, photo of delivered parcel, OTP for controlled deliveries: that lives in the driver app, not in the tachograph. See our deep dive on the benefits of digital proof of delivery.
- Real-time alerting. The G2V2 surfaces anomalies on the dashboard display but doesn’t push to the dispatcher when a vehicle has been parked off-site for 40 minutes.
- Fleet KPIs. Cost per kilometre, deliveries per hour, first-attempt success ratio, average consumption per round: the G2V2 doesn’t calculate them. For the 7 KPIs every fleet manager should track you need data cross-referenced with orders, revenue and fuel costs.
- Driver communication. The G2V2 has a menu, not a messaging interface.
- Reporting for customers, banks, audits. The
.dddis a legal file, not a human-readable report.
In short: the G2V2 sees, but it doesn’t decide or act.
What you need from fleet telematics
For the five functions the G2V2 doesn’t cover, you need a dedicated system. The five families of features that today distinguish a modern fleet telematics platform from a plain GPS tracker:
1. Route planning and optimisation (VRP)
Computing optimised routes for mixed fleets under real constraints (customer windows, vehicle capacity, regulated driving times, cold chain, urban access). The leap from Excel to automated planning is not something the G2V2 makes by itself.
2. Continuous operational tracking
Real-time vehicle position (not every 3 h), dwell times at customers, deviations from planned route, anomaly alerts. On electric vehicles, next-generation telematics also captures SoC, regenerative braking, consumption by driving style.
3. Driver app with digital POD
Ordered delivery list, integrated navigation, customer signature capture, photos, OTP for controlled deliveries, return management, two-way communication with dispatch.
4. Reporting and KPIs
Fleet manager dashboards with cost per kilometre, TCO calculation, ROI of optimisation work, KPIs by driver and customer, exports for ESG audit and CSRD reporting.
5. Integrations and workflow
Connectors to TMS, ERP, e-commerce; webhooks for delivery status; APIs for customer portals; automated handling of returns and reverse logistics.
The ITS interface: where the two worlds meet
The pivotal point introduced by the G2V2 is the ITS (Intelligent Transport Systems) interface, mandatory under Regulation EU 165/2014 article 10a. It is a standardised data port (Bluetooth, USB or Ethernet depending on the manufacturer) through which a third-party telematics system — the fleet’s chosen fleet management — can read a subset of tachograph data in real time:
- Current driver activity
- Cumulative driving time status
- Imminent-violation warnings (e.g. 15 minutes to limit)
- Snapshot of data for automatic download
Access is gated by the driver’s explicit consent, in line with the EU Data Act and the GDPR. The driver knows that data leaves the tachograph and goes to the company system, and the company has the signed consent on file.
This is the integration point: the G2V2 produces the compliance datum, fleet management turns it into operational information. Without an ITS connection there is no automation possible: you fall back into the world of USB stick + physical visit to the vehicle every 90 days (see the data download playbook for SME fleets).
Worked example: SME with 12 vans, two scenarios
Take a refrigerated logistics SME, 12 vans of 3.3 t running Italy–Slovenia–Austria routes, 4 drivers, 1 part-time fleet manager.
Scenario A — G2V2 only
- Compliance: ✅ covered
- Planning: manual spreadsheet, 6 h/week of fleet manager
- Data download: manual every 90 days vehicle, every 28 days driver. Time: ~3 h/month
- Customer ETAs: phone calls
- POD: paper, 4-6 disputes per year
- Hidden annual cost (estimate): 480 h fleet manager + 20 h dispute = ~€17,000 + dispute costs
Scenario B — G2V2 + fleet management integrated via ITS
- Compliance: ✅ covered
- Planning: automatic, 1.5 h/week for validation
- Data download: automatic via ITS, 0 hours
- Customer ETAs: automatic SMS
- POD: digital, <1 dispute/year
- Software cost: €8-15/vehicle/month × 12 = €1,150-2,150/year
- Efficiency recovery: ~€13,000/year
Scenario B costs less than scenario A. This is not an exception: it is the structural dynamic for any fleet above 6-8 vehicles.
Common purchasing mistakes
Three offerings currently in the market generate the most confusion:
1. G2V2 with embedded “fleet management modules”
Some tachograph vendors propose a proprietary app that reads G2V2 data and shows a dashboard. It is a decent “first tier” for someone managing 3-5 homogeneous vehicles, but it doesn’t scale: no planning, no VRP, no external integrations, vendor lock-in on the tachograph.
2. GPS trackers sold as “digital tachographs”
A category of non-certified hardware that reads speed from the CAN bus and simulates tachograph recordings. They are not compliant with Reg. EU 165/2014. Buying them is throwing money away: they need to be replaced with a real G2V2 by July.
3. Fleet management systems that don’t “talk to” the G2V2
Telematics platforms that haven’t implemented the ITS interface keep using OBD-II or CAN bus to infer data. It technically works, but it’s a parallel source: two truths instead of one. To avoid. The question to ask the vendor: “Do you read G2V2 data via the ITS interface with driver consent, or do you infer it from CAN bus?”.
In short
- The G2V2 is a compliance device + raw data source. It records in a certified way; it doesn’t plan.
- Telematics/fleet management is the operating system of the fleet: it plans, communicates, reports, integrates.
- The two talk through the standardised ITS interface (Reg. EU 165/2014 art. 10a) with driver consent.
- Without an ITS connection, data download stays manual and doesn’t scale above 6-8 vehicles.
- Three purchasing traps: G2V2 with non-scalable embedded apps, GPS trackers passed off as tachographs, fleet management that doesn’t read the G2V2 via ITS.
A platform like Optivo is designed to read G2V2 data via the ITS interface, turn it into planning, KPIs and reporting, and keep compliance (the archived .ddd) separate from operations (tomorrow’s route). If you manage a fleet exposed to the Mobility Package and are figuring out how to structure the transition, download the Mobility Package 2026 checklist or book a free demo to see how G2V2 ↔ fleet management integration works on a fleet like yours.