Teams that run Odoo lose real time to the single-view backend. When an accountant is deep in a customer invoice and needs to check a sales order, or a support agent jumps from a helpdesk ticket to the linked contact and back, Odoo's default web client discards where they were — one action pushes the previous record out of view, and the routes back are the breadcrumb, the browser back button (which frequently drops unsaved form state), or re-searching from scratch. People compensate by duplicating the whole session across native browser tabs, which spins up a fresh JS bundle and session per tab and quietly multiplies memory and login friction. Odoo core was simply never designed for parallel, keep-it-open workflows.

Multi Tabs adds a browser-like tab strip to the top of the Odoo backend so multiple records, list views, kanban boards, and even different apps stay open at once, each in its own tab, and switching between them is instant with no server round-trip or full re-render. We build it as a proper Odoo module: a small __manifest__.py declaring an assets bundle that extends web.assets_backend, with OWL components and a service layer that hook into the existing action manager and router so opening an action can spawn or reuse a tab instead of replacing the current view. Because it cooperates with the action manager rather than working around it, breadcrumbs, form dirty-state (unsaved-changes) warnings, and access rules all keep behaving normally inside every tab.

Technically, each tab holds its own action stack and controller state, so a half-filled form in one tab is untouched while you work in another, and a tab carries its own breadcrumb trail. We persist the open-tab set per user — typically in the browser via a client-side store keyed to the session, with an optional res.users / ir.config_parameter-backed server model when you want tab sets to survive across devices or be governed by policy. Optional touches we commonly scope in: a configurable max-tab count, middle-click / keyboard shortcuts (Ctrl+click to open in a new background tab, Ctrl+number to jump), pinned and renameable tabs, duplicate-tab, "close others / close to the right," and a dirty-tab indicator so a user never closes a tab with unsaved edits by accident. Everything is guarded by standard ir.model.access.csv and record rules where a server model is involved, and the whole feature is togglable per user group so you can pilot it before a full rollout.

Because this is build-to-order, nothing is downloaded and switched on the same day — we build, install, and support it around your exact Odoo version and edition. After a short scoping call we confirm your Odoo release (17.0 / 18.0 / 19.0), Community vs Enterprise, whether you run on Odoo.sh, on-premise, or another host, and which behaviors you want (persistence model, shortcuts, group restrictions, any theme integration). We then develop against a staging copy, run UAT with your team, and deploy with a rollback plan. Pricing starts from $249 (indicative, single-company base scope); multi-company tab-scoping, custom persistence/policy models, deep theme or third-party-app integration, and support across additional Odoo versions increase the quoted scope. You receive a fixed quote after the scoping call — the from-price is a starting indication, not a firm fixed price.