Telematics (GPS)
Telematics connects your provider's GPS data to Quanty: once a connection is set up, Quanty reads your vehicles' positions on a schedule and shows them live on the fleet map, and can keep a Vehicles table up to date at the same time. Telematics is part of the TMS add-on — without it the page explains that and asks you to contact Quanty.
Open Telematics from the Integrations hub. Only organization admins can connect or change a telematics account; other members can still see the fleet map once one is connected.
Providers
Eurowag is the first provider you can connect. Quanty reads vehicle positions, plates and driver names from it, on a schedule.
Quanty never writes to Eurowag
Nothing you do in Quanty changes your Eurowag account. The connection is read-only in both directions: Quanty only reads what Eurowag reports.
Webfleet, Samsara, GBox, Cartrack, Frotcom and Geotab are listed as planned: not connectable yet. Each has a Tell us you need this button, which sends a request to Quanty support naming the provider and, optionally, how many vehicles and what you need.
Eurowag: the token
Quanty does not issue the token. Eurowag does, on your request: ask your Eurowag account manager or Eurowag support for API access to your telematics data and a token for it. Paste that token into the connection wizard; Quanty encrypts it and only uses it to read your vehicles. Once stored, it cannot be shown again, not even to admins.
Tokens can expire or be revoked on Eurowag's side. When that happens the connection turns red with "The token was rejected: it has expired or was revoked." There is no advance warning, only this reaction the next time a sync runs. Fix it with Rotate token: paste the new token and Quanty tests it with the provider first, replacing the old one only when the new one works.
Connecting a provider
The wizard has four steps:
- Provider — pick the telematics service your vehicles report to.
- Access — the token or credentials the provider gave you. Quanty tests them against the provider before saving anything; a failed test saves nothing, and you go back to fix the access details or try again.
- Destination — besides the fleet map, where the positions go: write positions into a table (pick an existing Vehicles table, or let Quanty create one in your TMS project) or no table, map only.
- Schedule — how often Quanty asks the provider, from 1 minute up to 24 hours (the default is 5 minutes). The fleet map itself refreshes on its own every 30 seconds while it is open; the schedule only controls how often Quanty asks the provider for new data.
Writing positions into a Vehicles table
When a connection has a destination table, every sync writes one row per vehicle: plate, position, state, speed, address and driver. Quanty finds or creates these columns by a stable key, so renaming a column does not make the sync duplicate it, and a table already carrying matching Polish, English or German headings is reused instead of getting a second set of columns.
Two fields are filled once, on the row's first sync, and then belong to whoever edits them: plate and vehicle type. Every other synced field — state, position, speed, address, the timestamp — is overwritten on every sync, because it is the provider's live answer, not something to hand-edit.
Nothing is ever deleted by a sync. A vehicle the provider stops reporting turns Offline after a grace period; it is not removed from the table.
Position history
Quanty keeps a trail of past positions, written on meaningful movement (about every 15 metres) or a 30-minute heartbeat while a vehicle is parked. "Position history is kept for count days, then deleted" — 90 days by default. A connection can shorten that window; it cannot extend it past the platform default.
Separately, Show route on a vehicle's detail draws its actual path for a chosen window (last 6 hours, last 24 hours or last 3 days), read on demand rather than from the stored trail.
Who can see positions
There is no separate telematics permission. A vehicle's position follows access to wherever it is written:
- With a destination table — whoever can read that table sees its vehicles, exactly like any other row. "Some vehicles are not shown: positions follow the access to the table they are written to."
- With no destination table (map only) — only organization admins (and Quanty staff) see the fleet map's vehicles.
Assigning a vehicle to a person
For company cars, a vehicle's detail lets an admin Assign to person: pick the colleague who drives it, for example someone in sales or purchasing.
Location is personal data
Once a vehicle is assigned to a person, its location history is that person's location history, and everyone who can open the fleet map can see it. Your organization is responsible for telling employees about this.
What Quanty stores
| Data | Details |
|---|---|
| Vehicle | Plate, vehicle type, name and the provider's own vehicle id |
| Current position | Latitude, longitude, heading, speed, a text address and the time it was reported |
| Position history | A trail written on movement or a 30-minute heartbeat, kept 90 days by default |
| Driver | The driver name (and the provider's driver id) reported for the vehicle |
| Route on demand | Up to the last 72 hours, drawn by Show route |
| Assignment | Which person (if any) a vehicle is assigned to, and since when |
Nothing beyond this is surfaced: Quanty does not read tachograph data, remaining driving time, alerts or toll status, even where a provider's API offers them.
Related pages
- TMS add-on: the add-on telematics is part of, and the pallet ledger it ships alongside.
- Fleet map and Map view: where positions are shown, and how to add a map view to any table.
- Integrations: the hub the Telematics card sits in.
- Quanty Ghost: columns that never leave the organization.