If you operate a fleet in Italy or the wider EU, there’s a very high probability that at least half of your vehicles carry a Stellantis brand: Fiat, Peugeot, Citroën, Opel, Jeep, Alfa Romeo, Lancia. The group born from the 2021 FCA-PSA merger covers a dominant share of the European commercial fleet — and for fleet managers, that means one very concrete question: how do you access Stellantis telematics data without aftermarket devices, in 2026?
The answer runs through Mobilisights, the autonomous data company within the Stellantis group, launched in 2022. It’s the channel through which — in compliance with the EU Data Act — telematics data from connected vehicles is made available to fleets and qualified third-party providers like Optivo. No aftermarket OBD, no workshop visits, no cabling. Just the vehicle VIN and the owner’s consent.
This article explains how the process actually works: the operational steps, the real timelines, what’s included, what it costs, and the most common pitfalls in early activations.
What Mobilisights is, in practice
Mobilisights is the Stellantis division with exclusive control over the group’s embedded telematics data — the data the vehicle produces natively and transmits to the manufacturer through on-board connectivity. To give a sense of scale: it covers 14 automotive brands across the Stellantis group, from mass-market brands like Fiat and Peugeot through premium ones like Maserati and DS Automobiles, including the Pro One commercial vehicle division.
Technically, Mobilisights exposes a high-performance REST API that allows third-party fleet management systems to receive near-real-time operational data: mileage, geolocation, fuel consumption, battery state (for EVs), driving parameters, diagnostic codes, maintenance alerts. The model is data-as-a-service: the customer installs nothing, the manufacturer transmits, the third-party provider receives and surfaces the data.
The differentiator is scale. In a mid-2024 release, Mobilisights’ Head of North America Sales noted they activated 50,000 vehicles in two days, adding that “doing the same thing with aftermarket hardware would have taken months”. That number — 50,000 in 48 hours — is the practical difference between an API-based system and one based on boxes you have to ship and install one vehicle at a time.
Which vehicles are supported
The first filter is model year. Mobilisights covers vehicles produced from 2019 onwards (MY 2019+), with a handful of exceptions on specific pre-2019 models that already shipped with connectivity hardware. The general rule: if your vehicle is from 2019 or later and carries a Stellantis brand, it’s almost certainly in coverage.
Included brands:
- Mass-market: Fiat, Peugeot, Citroën, Opel, Vauxhall (UK market)
- Premium: Alfa Romeo, DS Automobiles, Lancia
- Off-road: Jeep
- Luxury: Maserati
- Commercial: Fiat Professional (Ducato, Fiorino, Scudo, Doblò), Peugeot Boxer/Partner, Citroën Jumper/Berlingo, Opel Movano/Combo, Vauxhall Vivaro
For a typical European mixed fleet, this means most post-2019 commercial vans — Fiat Ducato, Peugeot Boxer, Citroën Jumper, Opel Movano (all variants of the same vehicle produced under a joint platform) — are covered. If you have 25 Ducatos from 2021 on operational lease, the case is almost automatic.
The second filter is active connectivity. Stellantis vehicles from 2019 onwards ship with hardware connectivity installed, but two conditions matter: connectivity must have been activated (which typically happens at the dealership on first ignition), and the owner must have consented to data transmission. For corporate fleets, consent is centralised — you don’t need to collect it vehicle by vehicle if a single legal entity owns the fleet.
How activation actually works: the four steps
The end-to-end process for activating a Stellantis fleet through Mobilisights is simpler than it sounds. Four steps.
Step one: census and VIN collection. For each vehicle you need the VIN (17-character chassis number), the model and the year — all the information already on the vehicle registration. For mid-sized fleets (20-50 vehicles) the census typically takes 1-2 hours of admin work.
Step two: consent chain verification. This is where care matters. If you own the vehicles, you’re the owner and consent is direct. If they’re on operational lease or long-term rental, the contract must recognise you as the “user” of the vehicle for Data Act purposes — which is the norm, but worth verifying by reading the data-access clause. If you’re on financial lease, you’re the formal owner (though substantive ownership sits with the lessor until buyout) — same rule applies.
Step three: formal request to Stellantis via the third-party provider. This is where Optivo (or another qualified provider) steps in. The request flows through the Mobilisights portal, where the third party is registered as an “authorised recipient” and identifies the VINs for which to request data flow activation. The fleet owner confirms consent through e-signature. Processing time depends on Mobilisights’ workload but is typically in the order of hours or a few business days.
Step four: data in dashboard. Once Mobilisights authorises the flow, data starts arriving via API to the fleet management platform. In Optivo’s case, data feeds into the same dashboard that handles any aftermarket OBD or CAN bus vehicles — the fleet manager doesn’t see three separate systems, just one, with a source tag per vehicle.
How long it really takes
Mobilisights’ commercial timeline claims activations within minutes once the paperwork is complete. In actual European operational reality, end-to-end from census to data live in dashboard, typical timing is:
- Single-brand fleet (e.g., all Fiat Ducato): 3-5 business days end-to-end
- Multi-brand Stellantis fleet (Fiat + Peugeot + Citroën): 5-10 days, because some checks run by brand
- Fleet with edge-of-coverage vehicles (2019 models needing verification): add 2-3 days for cross-checking
The bottleneck is rarely technical. Almost always it’s administrative: consent chain to verify with the leasing company, contracts to re-read, formal designation of the authorised company representative. Once the paperwork is unblocked, technical activation is near-instant.
A practical comparison: a fleet of 25 Ducatos on operational lease that needs aftermarket OBD across the board typically requires 2-3 weeks (installation scheduling, box logistics, 30-60 min vehicle downtime per unit, initial configuration). The same fleet through Cloud OEM Stellantis is operational in about 5 days.
What it actually costs
Mobilisights doesn’t publish a price list. The model is subscription per VIN, with pricing that scales with:
- Number of vehicles (lower per-vehicle rates above 50-100 active VINs)
- Data package type requested (the Fleet Plus Data Pack is the standard operational package for fleet management)
- Data refresh frequency (some use cases need 15-minute granularity, others 24-hour)
- Contract duration
Order-of-magnitude indications based on 2025-2026 market benchmarks: per-vehicle cost for Cloud OEM Mobilisights is generally comparable to an aftermarket OBD telematics package, with a growing margin advantage as fleet size increases. If you pay around €100-150 per vehicle per year all-in for aftermarket OBD (amortised hardware, data subscription, maintenance), you pay similar figures for Cloud OEM Mobilisights — but you zero out upfront hardware, installation and ongoing device management.
A notable detail: Mobilisights offers a free 3-month Fleet Plus Data Pack Trial for VINs not previously activated. For a fleet exploring the option without economic commitment, it’s a concrete mechanism to test data quality before signing multi-year contracts.
The three most common pitfalls in early activations
Working with customers transitioning from aftermarket OBD to Cloud OEM Stellantis, three mistakes recur often enough to warrant calling out.
Pitfall one: not verifying coverage before census. It happens to discover mid-project that 3 vans in the fleet are from 2017 or 2018 and therefore outside the supported model year. The first step should always be a VIN-by-VIN check against Mobilisights — Optivo does this in the scoping phase, before even proposing activation, precisely to avoid surprises.
Pitfall two: ambiguous consent chain on tripartite leases. When operational lease goes through a third-party rental company (not Stellantis Financial Services), the consent chain can require additional steps: the formal owner of the vehicle is the rental company, the user is you. The contract must clarify who has authority to nominate the third-party data recipient. If ambiguous, it’s worth amending the contract before starting — saves months of limbo. For the specific contractual points to verify on a leased fleet, see the guide to the 5 things to know about Cloud OEM on leased fleets.
Pitfall three: wrong comparison between Cloud OEM and aftermarket. Cloud OEM Stellantis gives access to data the vehicle produces natively — which is plentiful and high-quality, but does not include, for example, remote engine immobilisation or advanced CAN bus diagnostics. If your fleet needs these specific features (e.g., anti-theft on high-value vehicles, predictive maintenance on heavy trucks) Cloud OEM doesn’t replace a CAN bus system — it sits alongside it on a subset of the fleet. Optivo handles mixing modes in the same platform; see the three tracking modes for the full picture.
What changes for those choosing Cloud OEM Stellantis
For European fleet managers in 2026, activating Cloud OEM Stellantis via Mobilisights means three concrete things: zero hardware to manage on natively connected vehicles, faster onboarding of new units down to a handful of days, and freedom from lock-in to the imposed manufacturer telematics package.
The most recurring case among our customers is a 15-30 unit fleet of Fiat Professional vans on operational lease. Before activation, the company managed minimal GPS tracking from the manufacturer’s telematics package (sufficient for position, nothing more), spent annually on aftermarket OBD installed at its own cost to get accurate fuel consumption and driver scoring, and ended up with two data sources that didn’t talk to each other. After activation: one dashboard, first-quality data, zero hardware, and annual per-vehicle cost reduced by 20-30% relative to the previous double-source scenario.
It’s not always the right choice for 100% of the fleet — older vehicles fall outside coverage, some use cases (engine lock, multi-zone temperature for cold chain) still require CAN bus. But for the part of the fleet that is “modern and connected”, in 2026 it’s the natural choice.
If you want to find out whether your Stellantis fleet is a candidate, see what we support on Cloud OEM or request a VIN census in demo. Response within 24 business hours with how many vehicles can be activated and on what timeline.
Read next:
- EU Data Act for fleets: what changed on 12 September 2025 — Regulation (EU) 2023/2854 is what makes Cloud OEM possible on Stellantis and other manufacturers
- Fleet tracking without hardware: the complete 2026 guide — the general picture of who Cloud OEM is right for beyond the Stellantis case
- EU Data Act one year later: balance for fleets — what manufacturers did in the first 12 months, early-mover lessons learned