Where Wialon's built-in reports stop

A template configured once and run on a schedule — mileage for the month, fuel by vehicle, a trip list for a period — is exactly what the reporting engine was built for. It reads the same messages FleetTAB reads, and for that job it needs no help from anyone.

If nobody in your organisation is exporting a report to a spreadsheet on a schedule and reshaping it by hand, you can stop reading here: an add-on would be overhead bought for nothing, and we would rather say so before an invoice than after one.

Wialon has been closing part of this gap itself. The Q1 2026 platform update widened what FleetSpace dashboards can do: analysis periods from a single day to a full year, and drill-down from a widget into a detailed view and on into the related report. If your only complaint about the platform was that a dashboard could not be scoped to the period you cared about, check the current version before you add anything to it.

What the update does not change is the editing side. A dashboard that drills down still answers questions; it does not let you write a status, a driver and a note across a filtered month of trips, attach an invoice to a service record, or hand two departments their own saved board. That division — the platform asks and reports, the add-on edits and organises — is the honest summary of where the line sits today.

Wialon Hosting keeps messages for a set period — 400 days by default. Reports read those messages, so the history a report can reach is the history the platform still holds, and what ages out cannot be recovered by any tool afterwards.

FleetTAB reads the same window: it is an interface, not an archive. If the requirement is history that outlives the platform's retention, or fleet data joined against ERP and finance tables, that is a different product — FleetSQL copies a Wialon account into a PostgreSQL database you own, and fleets commonly run both.

It does not track. There is no ingestion from hardware, no device configuration and no live dispatch — those stay in Wialon, which keeps being the operational system and the source of truth.

It does not replace the reporting engine either. Wialon report templates remain useful, and their output stays where it is. FleetTAB adds the working surface around them: dashboards to ask with, a logbook to edit in, scores to discuss, intervals to plan against.