How to schedule Traccar reports and email daily summaries
Traccar's reports are powerful — but you have to open the dashboard and run each one by hand. Here's how to make them arrive on a schedule instead.
Stock Traccar generates reports on demand only: you pick a vehicle and a date range in the web UI and run it right then. There is no built-in scheduler, so there's no native way to get a report for a fixed daily window or an automatic end-of-day summary emailed to you. Traccar Plus adds scheduled, time-windowed reports and emailed per-vehicle daily summaries as a drop-in companion service — one Docker container beside your own instance, with no data leaving your server.
Stock Traccar reports are on-demand only
Traccar's reporting is genuinely useful — route, summary, trips, stops, and chart reports are all there. But every one of them is pull, not push: you log into the dashboard, choose a device or group, set a from/to range, and click to generate. The moment you close the tab, nothing runs again.
That means there's no native way to say "every weekday at 18:00, email me yesterday's summary for the whole fleet." A scheduled-reports request has been open on the Traccar repo for years, but it stays unmerged while the maintainer focuses on the core tracking engine.
Why scheduled and time-windowed reports matter
For anyone actually running vehicles, recurring reports are the whole point:
- End-of-day summaries. When the day closes, you want distance travelled, idle time, and harsh-driving events per vehicle — in your inbox, not waiting for you to remember to pull it.
- Fixed time windows. A shift report for 06:00–14:00, or a depot report for after-hours movement, that runs on the same window every day without re-entering dates.
- Per user or per group. The right managers get the reports for their vehicles automatically, instead of one person manually exporting and forwarding.
The common workaround is to wire up cron jobs and scripts against Traccar's API — fragile glue that breaks on upgrades and that nobody wants to maintain.
How Traccar Plus adds scheduling as a drop-in companion
Traccar Plus is an independent companion add-on — not the official Traccar project — that runs as a single docker run container beside your existing instance. It talks to Traccar over its own API and webhooks, so there's no fork, no patched core, and no migration.
You define the schedules and windows you care about, and the add-on generates the reports on time and emails them out — including an automatic end-of-day per-vehicle summary of distance, idle time, and harsh events. It reads everything through Traccar's API, typically on the same host, so no tracking data ever leaves your own server. Upgrade Traccar whenever you like; the add-on keeps working.
Stock Traccar vs Traccar Plus reporting
| Stock Traccar | Traccar Plus | |
|---|---|---|
| On-demand reports in the UI | Yes | Yes (uses your instance) |
| Scheduled reports | No | Yes |
| Fixed time-window reports | No | Yes |
| Emailed end-of-day summary | No | Yes |
| Per user / per group routing | No | Yes |
| Setup | Cron + scripts | One Docker container |
| Data location | Your server | Your server |
Reports that arrive on time
Traccar Plus adds scheduled, time-windowed reports and emailed end-of-day vehicle summaries beside your own instance — one Docker container, data stays yours. Get started in minutes.
Enter your email for the Docker one-liner
Runs beside your own instance. Your tracking data stays on your server.
FAQ
Can Traccar schedule reports on its own?
No. Stock Traccar generates reports on demand only — you run each one manually from the dashboard. There's no built-in scheduler, so scheduled or time-windowed reports need an add-on or your own cron and scripts.
How do I get an emailed daily summary from Traccar?
Traccar Plus adds it as a drop-in companion: an automatic end-of-day per-vehicle summary — distance, idle time, and harsh events — emailed when the day closes, generated from your own instance over its API.
Does scheduling my reports send data off my server?
No. Traccar Plus runs in a Docker container beside your instance, typically on the same host, and reads through Traccar's API. Your tracking data never leaves your own server.