Skip to content

WebBox Fleet Tracking

GPS tracking for Odoo fleet: one ingest seam, geofences, offline computed not flagged.

The short answer

WebBox Fleet Tracking is a free, LGPL-3 Odoo application that extends Odoo's own fleet module with live GPS. Positions arrive from nine device protocols over raw TCP and from phones over HTTP, and both routes pass through one ingest method, so geofence, motion, overspeed and alarm events fire whichever way a position came in. For operators running their own trackers.

Request this module

Last updated

What it is for

A vehicle that disappears from a tracking system does not announce itself. Its last position stays on the map, at a plausible place, and it goes on looking like a van parked up until somebody wonders why it has not moved since Tuesday. The other quiet failure is the geofence. Plenty of integrations evaluate crossings only on the path a hardware tracker uses, so a driver's phone posting positions produces a lovely trail and not one alert.

Platform
Odoo
Category
Assets & rentals
Works with
Odoo 18 · Odoo 19
Technical name
fleet_tracking
Status
Direct from webbox
Pricing
Free

What is inside it

  1. 01

    One ingest seam

    Every position, whether it came over raw TCP from a tracker or over HTTP from a phone, goes through the same ingest method, so every rule runs once and none is quietly skipped.

  2. 02

    Live map

    A device list sits beside the map, filtered by whether a device is talking to you. Each row carries how long ago it reported and how fast it was going.

  3. 03

    The board

    Devices, positions, geofences, events, drivers, groups, commands and an audit trail. The tiles count what the layer models: 9 protocols, 2 ingest paths, 2 geofence shapes, 20 event types.

What it looks like in practice

  1. A tracker is pulled out of a van and nobody notices

    The device stops reporting. Its last position is still sitting on the map, and it reads as a vehicle standing still.

    Offline is computed from how long ago the device last reported, not from a flag somebody sets, so the device drops offline by itself. The sidebar states how long it has been silent before you have found it among the markers.

    Silent for
    31 hours

    Figures from the module's own demo data, on a fresh install. Install with demo data and open Fleet Tracking, then Devices.

    One ingest seamLive map

  2. A driver's phone posts positions and the geofence still fires

    There is no hardware tracker in that vehicle, only a phone posting over HTTP to the same server.

    The HTTP route calls the same ingest method as the raw TCP protocols, so enter and exit on a geofence, motion and overspeed all originate in one place. Writing position records straight to the table would draw the trail perfectly and fire nothing.

    Behaviour of the shipped code.

    One ingest seamLive map

  3. The depot boundary is the first geofence worth drawing

    Arrivals and departures at the yard are what a shift log gets reconciled against, and nobody has drawn a boundary yet.

    A geofence is a circle or a polygon on the map, and crossings become events carrying a type and a severity. Because both ingest paths share the seam, a phone-fed vehicle raises the same enter and exit rows as a tracker-fed one.

    Behaviour of the shipped code.

    One ingest seamThe board

What it deliberately does not do

No hardware and no SIM
You supply the trackers and their data plans. This is the server side, and it speaks the protocols those devices already send.
No route optimisation
It records where vehicles went. Deciding where they should go next is a different product.
No driver behaviour scoring
Hard braking and cornering are recorded as event types. Turning them into a driver score is not attempted.
Map tiles come from OpenStreetMap
No key is needed and nothing is billed, but tiles come from a public service, so a heavy install should point at its own.

Questions

Can I install this on Odoo Online?
No. Odoo Online cannot install modules that contain Python, so this runs on Odoo.sh or a self-hosted instance. Check the versions listed above for the series and edition it is verified against.
Do the trackers come with it?
No. You supply the devices and their data plans; this is the server side, and it speaks the protocols those devices already send. It also does not decide where a vehicle should go next, and it does not turn harsh-braking events into a driver score.
It is free, so what is the catch?
There is no catch and no key to enter. The licence is LGPL-3 and nothing needs activating. It depends only on fleet, mail, bus and sms, all of which ship with Odoo, and devices link to fleet.vehicle records so a tracker belongs to the vehicle your maintenance and cost records already use.
Where do the map tiles come from?
OpenStreetMap. No key is required and nothing is billed, but the tiles are fetched from a public service, so a large install should point the map at its own tile server. Commands sent to devices and configuration changes are kept in an audit trail rather than assumed.

Have something to build?

Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.

Start a project Browse services
  • Free scoping call
  • Reply within 1 business day
  • No lock-in