Tamm Fleet ↔ Odoo

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.

A fleet sync pipeline connects Tamm to Odoo's fleet module, mapping vehicle registrations, ownership transfers, and status changes onto company-scoped records. Each of the 12 companies sees only its own fleet while group-level reporting rolls up across all of them. Violation and expiry events are surfaced as actionable items in Odoo rather than as portal notices nobody reads.

Multi-company isolation was non-negotiable — one company's fleet data must never be visible to another's operators — which forced company scoping into every query and every sync job. Like the HR integrations, scheduled idempotent batches were chosen over real-time hooks for reliability at fleet scale.

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.