An owner of four vans knows exactly what he pays for fuel, but not how much of it burned at idle outside a warehouse gate. A dispatcher remembers the complaint about a late delivery, but has nothing to prove the vehicle waited two hours at the dock. Telematics solves those problems. The question is whether, in your fleet, it solves them for less than it costs.
This guide is a calculation, not a brochure: price ranges per vehicle, worked examples for fleets of 3, 5 and 10 vehicles, a month-by-month payback curve, four implementation levels compared and an honest list of cases where telematics does not pay off. The perspective is an owner who dispatches the work and signs the invoices, not a corporate fleet manager with an IT department behind him.
What is telematics and how does it work in a small transport company?
Telematics is telecommunications combined with vehicle IT: a device in the vehicle collects data on position, engine work and driver behaviour, sends it over the cellular network to a server, and a platform turns those records into maps, reports and alerts. In a small fleet it logs every kilometre and every stop without human input.
Is telematics the same as GPS?
No. GPS answers one question only, where the vehicle is at a given moment, while telematics adds context from the vehicle electronics: fuel consumption, engine revolutions, engine hours, harsh braking, diagnostic codes and, in the extended version, tachograph and sensor data. A tracker shows a trace on a map. Telematics shows what that trace cost you.
What telematics means in a car and what it means in transport
In a passenger car, telematics means driver services: eCall, remote unlocking, service reminders, usage-based insurance. In transport, the weight shifts to the fleet and to settlement: who drove, on which route, how much fuel was burned, how long the vehicle stood at loading and whether vehicle data matches the fuel invoice. Same technology, a different business use.
What a telematics system consists of: device, SIM card, platform
There are three parts: an onboard device (in a van plugged into the OBD-II socket, in a truck connected to the FMS/CAN bus), a data SIM card included in the subscription, and a browser platform with maps, reports and alerts. The architecture is covered in depth in the guide to van telematics under 3.5 tonnes. Here the focus stays on what you pay and what you get back.
What data does telematics collect and what does an owner actually see?
Basic data: location, mileage, engine hours
The basic package gives position refreshed every few dozen seconds, route history accurate down to individual stops, daily and monthly mileage, and engine hours split between driving and idling. Idling alone is often the fastest source of savings, because in small fleets it can eat 8 to 15 percent of total engine hours.
Advanced data: driving style, fuel use, diagnostics, temperature
A full package adds driver scoring (harsh acceleration, braking, speeding), fuel consumption calculated from vehicle data, diagnostic fault codes, geofencing around your base and customer warehouses, and with extra sensors the temperature inside a refrigerated body and cargo door opening. This is the layer that turns monitoring into a cost management tool.
What telematics will not do for you
Telematics will not plan a route, negotiate a rate or force a driver to change habits. It shows facts, and the decisions stay with the owner. It also does not replace a tachograph or a working time settlement system, although it supplies the data both rely on.
What benefits does telematics deliver in a fleet of 1-15 vehicles?
Six benefits that show up fastest in a small fleet:
- Lower fuel consumption, typically 5 to 12 percent once driving style improves and idling drops.
- Fewer empty and private kilometres, usually 3 to 8 percent of monthly fleet mileage.
- Less administration, roughly 4 to 8 hours a month saved on mileage logs and route reconstruction.
- Evidence in customer disputes, route history accurate to the minute of waiting at a dock.
- Faster vehicle recovery, an unauthorised movement alert within seconds of the event.
- Fewer unplanned repairs, thanks to servicing scheduled on actual mileage instead of memory.
Lower fuel use and fewer empty kilometres
The largest share of savings comes from unglamorous things: the engine running while parked, driving above the economical rev range and harsh braking. Emailing a driving report to the crew once a week usually cuts fuel use by a few percent with no training involved. The second layer is kilometres nobody ordered.
Less admin: the end of manual mileage logs and retyped routes
In a company with five vehicles, keeping mileage records by hand and reconstructing routes from drivers’ recollections takes several hours a month. Telematics generates those summaries automatically, and with order system integration the data flows straight into job settlement. That is real owner time, usually spent in the evening.
Fewer disputes with customers: route history as proof of waiting and arrival
An argument about whether the vehicle waited two hours at loading ends the moment you produce entry and exit times for the warehouse geofence. The same mechanism helps defend a waiting charge and verify whether time windows are realistic at all, a subject we cover in the article on precise route planning.
Vehicle, cargo and driver safety
An alert on movement outside working hours, geofencing around the yard and a live position for the police all shorten reaction time to theft. On refrigerated bodies, a temperature sensor documents an unbroken cold chain, sometimes a condition of acceptance. Some insurers price monitoring into a policy, so ask your broker before installation.
Where the savings come from in a small fleet
| Source of savings | Share in the first year |
|---|---|
| Fuel and driving style | 38 percent |
| Empty and private kilometres | 22 percent |
| Administration and settlement | 18 percent |
| Damage, fines, penalties | 12 percent |
| Servicing and inspections | 10 percent |
Structure of typical first-year savings, ONYX analysis based on rollouts in fleets of up to 15 vehicles.
The practical conclusion: more than half of the effect sits in fuel and kilometres, so a fleet with no problem in either area should calculate its payback more conservatively.
How much does telematics cost in 2026? Indicative ranges per vehicle
Telematics in 2026 typically falls in the ranges of about PLN 25–40 per vehicle per month for a basic package with GPS and reports, and about PLN 50–90 per vehicle per month for a full package with driving style, fuel use and alerts, with a one-off device and installation cost between zero and about PLN 300 per vehicle. These are market ranges, not any provider’s price list.
| Implementation level | Indicative subscription (PLN/vehicle/month) | Indicative saving (PLN/vehicle/month) |
|---|---|---|
| GPS tracker only | approx. 25–40 | approx. 40–80 |
| OBD-II telematics, full package | approx. 50–90 | approx. 150–250 |
| Telematics + remote tachograph download | approx. 90–130 | approx. 220–350 |
| Telematics + tachograph + TMS | approx. 200 | approx. 300–450 |
Midpoints of indicative market ranges for Poland in 2026. Not an offer or a price list for any provider.
The chart shows the thing that surprises buyers most often: the cheapest option has the worst cost-to-effect ratio. A bare tracker usually pays back more weakly than a full package, because only fuel and driving style data unlock the biggest savings line.
One-off cost: device and installation
An OBD-II device is often bundled into the subscription on a 24-month contract, or costs PLN 150 to PLN 300 bought outright. Installation in a van takes a few minutes in the yard, so it rarely becomes a separate line. Costs rise with hardwired installation, extra sensors and a remote tachograph download module, where the realistic range is PLN 200 to PLN 400 per vehicle.
Monthly subscription: what actually moves the price
The price depends on the number of vehicles (volume discounts usually start around 10 units), position reporting frequency, the range of reports, the presence of a tachograph module, the number of panel users, and whether data travels through an API to an external system. The map itself is cheap. You pay for analytics and integrations.
Hidden costs: contract length, roaming, tachograph download fee, service call-out
Four items that most often fall out of the first calculation:
- Contract length. The advertised price normally applies to 24 or 36 months. On a shorter term it rises by 20 to 40 percent.
- Transmission abroad. On international work, check whether roaming is included in the subscription or billed separately.
- Tachograph download. This is sometimes a separate line in the price list, charged per vehicle or per downloaded file.
- Service call-out. If a device fails away from base, the fleet carries the technician travel cost and the standstill unless the contract says otherwise.
What a fleet of 3, 5 and 10 vehicles pays: three indicative ranges
| Fleet | Scope | Indicative monthly subscription | Indicative start-up cost | Indicative first-year cost |
|---|---|---|---|---|
| 3 vehicles | basic package | approx. PLN 75–120 | approx. PLN 0–900 | approx. PLN 0.9–2.3k |
| 5 vehicles | full package | approx. PLN 250–450 | approx. PLN 0–1,500 | approx. PLN 3–7k |
| 10 vehicles | full package with tachograph download | approx. PLN 900–1,300 | approx. PLN 0–4,000 | approx. PLN 11–20k |
Smaller fleets that want to start with one tool rather than a full stack of systems usually pick a light option such as ONYX Direct, then extend the scope after the first quarter of working with real data. The figures above are market ranges only.
How long does it take for telematics to pay for itself?
With a fleet of five vans and typical full-package ranges (subscription about PLN 50–90 per vehicle, installation about PLN 0–300 per vehicle, savings ramping up to about PLN 150–250 per vehicle), the cumulative net balance often turns positive around months 2–4 after installation. The simulation below uses the midpoint of those ranges for illustration only — it is not a quote from any provider.
| Month | Indicative saving (PLN/vehicle) | Indicative cumulative net balance (PLN) |
|---|---|---|
| 1 | 60 | -750 |
| 2 | 120 | -450 |
| 3 | 180 | 150 |
| 4 | 200 | 850 |
| 5 | 200 | 1,550 |
| 6 | 200 | 2,250 |
| 7 | 200 | 2,950 |
| 8 | 200 | 3,650 |
| 9 | 200 | 4,350 |
| 10 | 200 | 5,050 |
| 11 | 200 | 5,750 |
| 12 | 200 | 6,450 |
Illustration at the midpoint of indicative market ranges (subscription approx. PLN 50–90/veh./month, installation approx. PLN 0–300/veh.). Not an offer.
The first three months of that curve are the part that matters. Month one usually closes near zero, because drivers are only learning that the data is being read. The effect often stabilises at a fuller level from month four onwards.
How to calculate the break-even point for your own fleet (formula)
Work it out on paper in five steps:
- Take monthly fleet fuel spend and multiply it by 0.07 (a conservative 7 percent saving on consumption).
- Take monthly fleet mileage, multiply by 0.05 and by your cost per kilometre, to price the empty kilometres you will cut.
- Take monthly hours of administration and multiply by your own hourly rate.
- Add those three figures together and subtract the subscription multiplied by the number of vehicles.
- Divide the start-up cost (devices and installation) by the result of step 4. That number is your months to payback.
If the result exceeds 8 months, limit the rollout to the basic package or postpone it until the fleet grows.
Example: a fleet of five vans, payback around month three
The fleet spends about PLN 18,000 a month on fuel and covers about 22,000 km. Seven percent on fuel is about PLN 1,260. Cutting 5 percent of mileage at a cost of about PLN 1.90 per kilometre is about PLN 2,090. Six hours of admin at about PLN 80 is about PLN 480. That totals about PLN 3,830 of potential monthly savings against a subscription in the range of about PLN 250–450 for five vehicles. Even after halving those figures out of caution, the start-up cost in typical ranges is usually recovered around months 2–4.
When telematics does not pay off
Four situations where we honestly advise against a rollout:
- A one-person company with one vehicle, where the owner drives and settles the jobs personally.
- A fleet with very low mileage, below roughly 1,500 km per vehicle per month, where fuel savings will not cover the subscription.
- Vehicles heading for sale or lease end, if they have fewer than three or four months left in the company.
- A company that has no intention of reading the reports. Without a conversation with the driver and a correction to routes, the system generates no saving at all, only cost.
Comparing the options: GPS tracker, telematics, telematics with TMS
Four implementation levels and who each one is for
| Level | Scope | Indicative cost (PLN/vehicle/month) | Who it is for |
|---|---|---|---|
| 1. GPS tracker | position, route history, movement alarm | approx. 25–40 | 1-2 vehicles, anti-theft purpose |
| 2. OBD-II telematics | position, fuel use, driving style, geofencing, reports | approx. 50–90 | 3-15 vehicles, focus on fuel and kilometre costs |
| 3. Telematics + remote tachograph download | level 2 plus DDD files and driver working time | approx. 90–130 | fleets with tachographs, including vans on international work |
| 4. Telematics + tachograph + TMS | level 3 plus orders, settlement and customer status updates | approx. 200 | fleets from a few vehicles up that want one system instead of three |
Level four makes sense when vehicle data is meant to close an order and an invoice, not just draw a map. That part is handled by ONYX TMS, which telematics feeds without anyone retyping trips.
OBD-II in a van versus FMS/CAN in a truck (in brief)
In a van under 3.5 tonnes the device plugs into the OBD-II socket and reads a limited parameter set. In a truck it uses the FMS standard on the CAN bus and reaches full engine, fuel and tachograph data. So one provider can deliver two different reporting scopes inside a single mixed fleet. The detailed comparison sits in the guide to van telematics under 3.5 tonnes.
Factory telematics from the manufacturer versus an independent provider
Factory telematics (manufacturer services) is often available immediately, with no installation, and reports diagnostics for that one brand well. The problem starts in a mixed fleet, where the owner ends up with two or three separate panels and no common report. An independent provider gives one platform for all brands, better data export and integration with an order system. In a single-brand fleet, check first what the manufacturer package already includes.
Comparing telematics providers: ONYX, Webfleet and GBox
If you are considering a first rollout, you will naturally compare three common paths on the Polish market: a local provider with a full transport ecosystem, an international fleet platform and a system strongly focused on tachographs. The table below is not a quote, but it shows what to look for in a 3–15 vehicle fleet where the owner reads reports personally and there is no IT department.
Comparison table for a small transport fleet (2026)
| Criterion | ONYX Telematics | Webfleet | GBox (Inelo) |
|---|---|---|---|
| One panel: van + truck, mixed brands | Yes | Yes | Yes |
| Polish support and onboarding | Yes, direct from the provider | Yes, via partner | Yes |
| Remote DDD file download | Yes, in extended package | Available, often higher tier | Yes, strong focus |
| TMS and order status integration | Yes, native with ONYX TMS | API, integrator project | Limited |
| Fuel card and tolls in the same ecosystem | Yes (Direct, SmartPass) | No | No |
| Trial on one vehicle before fleet decision | Yes | Depends on partner | Yes |
| Data export (CSV, API) | Yes | Yes | Yes |
| Verdict for a small PL fleet | Best balance: tachograph, TMS and one transport supplier | Strong for international fleets, often a longer start | Strong for DDD, weaker path to order planning |
Why ONYX wins for a small company just starting out: you are not buying a map alone, but a platform that later connects to order billing, fuel cards and road tolls without stacking more systems. TMS integration removes hours of manual status updates for customers. Webfleet and GBox make sense when the priority is international monitoring alone or tachographs alone, but a small transport company rarely has only one such problem. Check indicative market subscription ranges (about PLN 50–90/veh./month for a full package) always in a quote — we do not compare specific provider price lists here.
Implementation details and report scope are on the ONYX telematics page. To see how this works on your fleet, book a free consultation.
How to choose a telematics provider: 10 questions before signing
- What is the total first-year cost, including device, installation and activation?
- How many months does the contract run and what is the notice period?
- Who owns the device after the contract ends and who pays for removal?
- Is data transmission outside the country included in the subscription?
- Does the system allow data export (CSV, JSON) and does it expose an API?
- Does the provider support remote DDD file download, and at what price?
- How long is route history retained and can it be downloaded after the contract ends?
- What is the service response time if a device fails on the road?
- Is support available in your language, and during which hours?
- Can the system be tested on a single vehicle before committing the whole fleet?
The answers for a small fleet, together with the reports available as standard, are collected on the ONYX telematics page.
Contract length, notice period and what happens to the hardware afterwards
The market standard is 24 months with the device included in the subscription. Three clauses deserve attention: automatic renewal, the early termination fee and the status of the hardware afterwards. If the device stays the provider’s property, ask who pays for removal and whether failing to return it triggers a penalty.
Is the data yours? Export, API and TMS integration
The contract should state plainly that your company is the controller of the vehicle data and the provider is a processor. The practical test is whether you can download the full route and report history in a machine-readable format at any time. Without that, changing provider means losing your history and integration with an order system is impossible.
Installation, support and service response time
Establish whether installation happens at your base, how many vehicles a technician handles in a day, and what happens when a device fails 800 km from home. Support in your own language, with a real phone number and a declared response time, matters more in a small fleet than an extra tab in the panel.
Telematics and the formal obligations of a small fleet
Tachographs in 2.5-3.5 t vans: where things stand after July 1, 2026
The obligation to fit a tachograph in vehicles with a gross weight between 2.5 and 3.5 tonnes performing international carriage of goods applies from 1 July 2026 under Regulation (EU) 2020/1054. Practical preparation is covered in the article on the tachograph obligation in vans and the service scope on the tachograph for vans page. Moving from domestic to international work also changes your cost base, as set out in the comparison of domestic and international transport.
Does telematics replace a tachograph?
No. A tachograph is a type-approved recording device required by regulation, while telematics is an IT system without that legal status, so no telematics system releases you from the duty to install a tachograph. What telematics can do is automate the obligations around it: download DDD files remotely within the required deadlines and make sure no download is missed.
GDPR and vehicle monitoring: what must be on paper before installation
Before the first installation, prepare three documents: the legal basis and purpose of processing (Article 6 GDPR), driver information compliant with Article 13 GDPR, and a clause in the work rules or a formal notice describing the scope of monitoring. Add rules for using the vehicle outside working hours and a private mode where the vehicle is used privately.
Telematics, fuel cards and road tolls: what is worth combining
What you see when you match telematics data against the fuel invoice
Telematics tells you how much the vehicle burned and where it was. The fuel card tells you how much fuel was bought and where. Matching both catches refuelling at a location the vehicle never visited, litres exceeding tank capacity and a systematic gap between reported and invoiced consumption. In a small fleet, this single check can return the subscription cost in the first month.
Fuel cards (OMV, DKV, E100, Eurowag, AS 24): which parameter matters for fleet reporting
From a reporting perspective, the number of stations in the network is not the deciding factor. Transaction data quality is:
| Card parameter | Why it matters for fleet reporting |
|---|---|
| Registration number on the transaction | Without it you cannot match a refuelling to a specific vehicle |
| Date and time accurate to the minute | A precondition for comparing against the GPS position at that moment |
| Station location (address or coordinates) | Lets you spot refuelling away from the planned route |
| CSV export or API | Decides whether data reaches your system automatically or by hand |
| Fuel separated from additional services | Without it your cost per kilometre is inflated by tolls and fees |
The full comparison of offers and acceptance networks sits in the comparison of OMV, E100, Eurowag, AS 24 and DKV fuel cards, practical refuelling tactics in the guide on how to fuel a fleet cheaply, and terms for smaller fleets on the fuel cards page.
Do vans under 3.5 t pay tolls in Europe?
Usually not in electronic toll systems, because those most often cover vehicles above 3.5 tonnes. In many countries a time-based vignette obligation remains on motorways, and the rules differ by country, vehicle category and road type. Current rates and the scope of obligations per country are collected in the road tolls section.
Step-by-step rollout in a small company (without an IT department)
Week 1: pilot on one or two vehicles
Start with one vehicle on typical mileage and one with the highest fuel consumption. For the first week, change nothing in how work is organised, just collect baseline data: fuel use, idling, daily mileage, number of stops. Without that reference point you cannot prove a saving later.
How to talk to drivers about telematics so there is no revolt
Say plainly what the system collects and why, before the driver hears it from a colleague. Three arguments work best: route history defends the driver in a dispute over waiting time or a speed camera fine, fuel data allows a fair bonus, and alerts protect the vehicle from theft. If you run an economical driving bonus, announce it together with the rollout.
The first three reports worth setting up
- Idling report, weekly, broken down by vehicle and driver.
- Fuel consumption report, monthly, reconciled against fuel invoices.
- Mileage outside assigned jobs report, monthly, to catch private kilometres.
Three reports are enough for the first quarter. Add more only once you are drawing conclusions and making decisions from these three.
The most common mistakes small companies make with telematics
- Buying the cheapest tracker and expecting fuel results the hardware cannot possibly deliver.
- No baseline measurement before installation, so six months later no saving can be demonstrated.
- Rolling out across the whole fleet at once, with no pilot and no check on transmission quality along typical routes.
- Installing without GDPR documentation, arranged verbally in the yard.
- Signing a 36-month contract before testing, with no trial period and no data export clause.
- Nobody reads the reports. The most common and most expensive mistake, because the cost runs while the effect never arrives.
- Treating the system as a tool for policing drivers instead of managing cost, which drives resistance and turnover in the crew.
Summary
In a small fleet, telematics is a calculable investment rather than a matter of faith. A full package typically sits in the indicative range of about PLN 50–90 per vehicle per month against an estimated saving of about PLN 150–250 per vehicle, so with five vans the balance often turns positive around months 2–4. More than half of that effect comes from fuel and kilometres, which is why a fleet with low mileage, or a single vehicle driven by the owner, should run the numbers especially carefully.
The three decisions with the biggest impact on the outcome are the implementation level (tracker, telematics, telematics with tachograph download, telematics with an order system), the contract clauses on data and termination, and whether someone in the company will read the reports regularly. Every figure in this article is an indicative market range for Poland in 2026 and is not an offer or a price list for any provider.
To have the break-even point calculated for your own fleet on real numbers, book free consultations or write to us through contact, and we will match the telematics scope to your transport profile.
References / Legal sources
- Regulation (EU) 2020/1054 of the European Parliament and of the Council, scope of the tachograph obligation for 2.5-3.5 t vehicles in international carriage of goods from 1 July 2026.
- Regulation (EU) No 165/2014 of the European Parliament and of the Council, tachographs in road transport, deadlines for downloading data from the driver card and tachograph memory.
- Regulation (EU) 2016/679 (GDPR), Articles 6 and 13, legal basis for processing and the information duty towards the driver.
- Polish Road Transport Inspectorate (GITD), enforcement requirements for recording equipment and driver working time.
- FMS-Standard, the truck data interface specification used in fleet telematics.
- ONYX product materials: telematics scope for fleets of up to 15 vehicles, remote DDD file download, integration with ONYX TMS.
