Tracking and telematics integrators
You sell the hardware, fit it, keep it online and bill for it every month.
Every device you fitted.
Every SIM you pay for.
01 — Sound familiar
The money leaks where the records aren't
Fitting hardware to vehicles is a real operation — stock, jobs, subscriptions, customers. Most of it ends up in spreadsheets, because neither the tracking platform nor a general ERP was built to hold it.
See what replaces them- 01 You find out On the carrier invoice
You pay for SIM cards nobody is using
Activated for a job, never cancelled when the unit came off the vehicle. They keep billing, quietly, for months.
- 02 You find out While the customer waits
Nobody can say what is fitted to that vehicle
The serial is on a job sheet, the IMEI is in someone's messages, and the customer is on the phone right now.
- 03 You find out When they leave
The install history leaves with the technician
Who fitted it, on what date, under whose warranty. If it is not written down in one place, it walks out of the door.
- 04 You find out Never
Monthly fees nobody remembered to bill
The unit went live, the fee was agreed on the phone, and the invoice waits for someone to remember it. The tracking platform cannot remind you — it has never known who pays.
02 — What you get
One place the whole business can be asked about.
Everything on this page is in the product today. The screens below are the running application, not drawings of it.
Ask what is on that vehicle, answer in one search
One record per installed unit: the serial, the IMEI, the SIM inside it, the vehicle it is fitted to, where it is and who owns it. Complete the job form and the record moves with it — nobody retypes an install. Your team stops opening three tabs and a spreadsheet to answer a question the customer asks in five seconds.
- Serial, IMEI and SIM on the same record
- Vehicle, customer and install date written by the completed job form
- The customer and the division it belongs to
Swipe the screen to look around
Stop paying for SIM cards nobody is using
Every SIM, its number, its provider and the asset it sits in. Receive, activate and deactivate them in batches that post in one go, and the request reaches the carrier by e-mail with the cards attached — so your register is something you can hold the carrier's invoice against instead of a folder of e-mails.
- Receive, activation and deactivation registers
- Batches posted in one action, not card by card
- Carrier requests e-mailed with the SIM list attached
- Every card tied to the asset it is fitted to
Swipe the screen to look around
Bill every unit, every month, without remembering to
A contract sets the customer's prices, a subscription says what they pay for and how often, and a nightly run raises the invoices that fall due. A completed job form becomes an invoice in one step. Invoices go out as a PDF by e-mail, payments and credit notes settle them, and aging shows who owes what.
- Subscriptions invoiced overnight, on the day they fall due
- A completed job form invoiced in one step
- Quotations, invoices and credit notes as PDF, sent by e-mail
- Receivables aging, overdue invoices, sales by month
Swipe the screen to look around
Hand a customer their equipment list in one click
Filter to the customer, the site or the status, and export exactly what is on the screen — every matching row, not just the page you scrolled to. It is the same table your team works in every day, so there is no reporting tool to keep in step with reality.
- Asset audit and SIM-on-asset reports
- Scoped to one customer or the whole book
- Excel or CSV, with the columns you are looking at
Swipe the screen to look around
And it also holds
Job forms
The work that fitted the unit and the readings the technician took, printed on your letterhead.
Quotes that become invoices
An approved quotation turns into an invoice without retyping a line, at the prices the customer agreed.
Customers and contacts
Divisions, sites and the people to call, with the assets that belong to each.
Told when there is work
A job ready to invoice, the night's billing run, an e-mail that bounced — in the feed of whoever can act on it.
A history on every record
Who changed what, and when. Nothing quietly becomes true overnight.
Your team, scoped
Roles decide, object by object, who can see, change, post and export. Nobody registers themselves.
Your spreadsheets, in and out
Import by CSV with the columns mapped by hand; export any list or report to Excel or CSV.
On a phone, too
Lists turn into cards and forms fit the screen, for whoever is at the vehicle — as long as there is signal.
It holds at size
Twenty thousand units in a list that scrolls like twenty. Searching is instant.
03 — Who it's for
Built for the business that fits the hardware.
Vehicle fitting workshops
Trackers, cameras, sensors, immobilisers — installed on someone else's fleet.
Fleets with their own install team
You run the vehicles and the hardware in them, and answer to finance for both.
Not for you if all you need is live positions and alerts. That is your tracking platform, it does that well, and FleetERP is not trying to replace it.
04 — Getting started
Three steps, and the first one is a conversation.
Not a trial you are left alone with. Your data is in the workspace before you decide anything.
- 01
Tell us what you run today
A call, and a look at the spreadsheets you keep. We say plainly whether this replaces them or not.
An honest answer
- 02
We load your data
Customers, assets and SIM cards come straight out of the system you use now, the rest by CSV, mapped to your fields. A rehearsal first; the final load on the day you switch.
Your records, in
- 03
Your team starts working in it
Roles for your people, a short walk-through, and the day's work moves across. No project plan, no quarter-long programme.
A live workspace
05 — Questions
The things people ask before signing.
Does it replace Wialon or our tracking platform?
No, and it is not trying to. The platform keeps doing live positions, alerts and dispatch. FleetERP holds the business around it: who the customer is, what is fitted to which vehicle, which SIM is in it, what was done on what date, and what the customer is billed for.
We already have an ERP. Why another system?
Because a general ERP has nowhere to put a serial number, an IMEI or an ICCID, so they end up in a notes field and stop being searchable. FleetERP starts from the installed unit and the SIM in it, which is what your business actually sells and services.
Does it invoice?
Yes. A contract sets each customer's prices, subscriptions invoice themselves overnight when they fall due, and a completed job form becomes an invoice in one step. Invoices take payments and credit notes, go to the customer as a PDF by e-mail, and the aging and overdue reports show who owes what. It does not replace your accounting system: there is no QuickBooks or Xero connection yet, so invoices reach your accountant as an Excel or CSV export.
Do invoices go out from our own address?
Yes. You give the workspace your own mail account, and invoices, quotations and carrier requests leave from your address with your letterhead on the PDF. If a message is refused, whoever sent it is told in the application instead of finding out from the customer.
Our asset fields are not the same as anyone else's.
That is the normal case. Your fields, your statuses and the columns a list opens with are configuration in your own workspace, set up with you during the rollout — not a custom build and not a branch of the product.
How does our data get out of the old system?
Where the old system can be read, we pull it straight out: customers with their contacts and divisions, installed units, SIM cards and their batches. Anything else comes in by CSV. The first load is a rehearsal you check; the last runs on the day you switch and updates what the rehearsal loaded instead of duplicating it. Numbers your customers already know, like TP-C000042, stay the same.
Can we get our data back out?
Any list and any report exports to Excel or CSV — every row it matches, with the columns on screen. Your data sits in a standard PostgreSQL database and it stays yours; if you want to query it directly, that is what FleetSQL is for. It is backed up as standard PostgreSQL dumps, and a dump is trusted only once it has been restored and checked table by table.
Who in our team can see what?
Roles decide it, object by object: who can open invoices, who can post them, who can export. Each person sees and changes only what their role allows, every workspace is separated from every other, and nobody can register themselves into yours.
What does it cost?
It is priced per workspace, by the number of assets and SIM cards you keep in it. While it is in private rollout the number is agreed on the call, once we both know what you are moving across.
How do we get started?
Ask for a demo. The first step is a conversation about the data you keep today, not a sign-up form — then we load it into a workspace so you are looking at your own records rather than a sandbox.
Request a demo
See it with your own data in it.
Tell us what you run today — the spreadsheets, the platform, how many units and SIM cards you keep alive, and how you bill for them. We will show you the same screens with your records in them, and say plainly whether this replaces what you have.
Or write to fleeterp@theassettrack.com