Tamm | Fleet Management Odoo

Overview

Fleet operations for 12 companies and 1,000+ vehicles synchronized between the Tamm platform and Odoo — registrations, transfers, and violations visible where the business manages its fleet.

Twelve companies, over a thousand vehicles, and fleet data scattered between the Tamm government platform and internal records. Registrations, transfers, and violation notices were tracked in a patchwork of portals and spreadsheets. Nobody could answer a simple question — which of our vehicles has an outstanding issue? — without a day of manual work.

How the integration works

• Fleet sync pipeline — connects Tamm to Odoo's fleet module, mapping vehicle registrations, ownership transfers, and status changes onto company-scoped records.
• Company scoping everywhere — each of the 12 companies sees only its own fleet, while group-level reporting rolls up across all of them. Isolation is enforced in every query and every sync job, not just the UI.
• Actionable events — violation and expiry events surface as actionable items inside Odoo rather than as portal notices nobody reads.

Data flow

1. Vehicle registrations, transfers, and status changes are collected from Tamm on schedule.
2. Records are mapped onto Odoo fleet models, scoped to the owning company.
3. Violation and expiry events generate actionable items assigned within Odoo.
4. Group reporting aggregates across companies without leaking one company's data to another's operators.

Key decisions

• Multi-company isolation was non-negotiable. It shaped every query and every sync job from day one — retrofitting isolation later would have been far more expensive.
• Scheduled idempotent batches over real-time hooks, for reliability at fleet scale.

Impact

12 companies and 1,000+ vehicles managed from one view in Odoo. Fleet compliance — registrations, transfers, violations — went from manual portal-hopping to a monitored, exception-driven workflow with full visibility across the group.