Fleet tracking inside your ERP, not beside it
GPS units on your vans, on a live map, in the same system that holds the job and the customer. No second login, no separate tracking invoice, and a site visit that is verified against where the vehicle actually was.
Qaflo is ERP software for UAE contractors: quotations, purchasing, stock, job costing, invoicing, the VAT return and payroll, in one system.
One system, so the van and the job know about each other
Most contractors buy tracking from a tracking company and an ERP from an ERP company, and the two never meet. That is why "was the team actually on site on Tuesday" is a question nobody can answer from either screen. Here the vehicle, the driver, the customer address and the job are the same database, so the answer is a report rather than an argument.
- Live positions, trip history and idle time from Teltonika devices
- Geofences, an engine-on / moving / idle split, and a device command channel
- Driver assignment, whether or not that driver has an ERP login
- No second subscription and no second login
Replay any day, trip by trip
Pick a vehicle and a date and the whole day draws on the map: every trip, every stop, and how long the engine ran without the van moving. Press replay and the van drives it again, with the clock and its speed running along the bottom of the screen, so the question of where it was at ten past three is answered by watching rather than by asking the driver.
- Distance, engine-on, moving and idling time, and peak speed for the day or for one trip
- A timeline of trips and stops across the day, with a speed profile under it
- Replay fast, normal, slow or in real time, and jump to any trip or stop from the journal
Site visits located by evidence, in a fixed order of precedence
The rule is written down and the system does not bend it. If the assigned van tracker has a fix inside the window, that fix is the visit location. If it does not, the rep phone GPS is the fallback. If there is neither, the visit is recorded as unlocated and nothing is invented to fill the gap.
- The tracker wins when its fix is fresh, ahead of the phone and ahead of memory
- Stops are matched to a customer address and offered as suggested visits for a manager to verify
- Unmatched stops stay unmatched rather than being attached to the nearest customer
- The daily visits sheet per rep is a report, generated rather than retyped
Addresses built for this country
A pin is only useful if the driver can find the door. Every customer carries a UAE address record: unit, floor, building, area, emirate, PO Box and Makani number, with a coordinate whose source is recorded rather than assumed. Addresses migrated from a legacy system come across with that provenance intact.
Where this lives in the platform
One database underneath all of it, so what you enter here is what everyone else reads.
Field & fleet
Where the van went, where the rep checked in, and which customer that visit belongs to. On a live map inside the same system that holds the job, with no second login and no separate tracking bill.
Sales & CRM
Enquiries, quotations and their revisions, orders and deliveries on one pipeline. The quotation that was accepted is the one the job gets built from, and both are still there when the client asks.
What people ask about this
Do we need a separate tracking subscription?
Which trackers does it work with?
Can it prove a rep visited a customer?
The other things it does end to end
See fleet tracking on your own data
Book a working session and we will walk it through one of your own jobs rather than a demo dataset.