Teams that run multiple Odoo website themes — or one theme that keeps growing — hit the same wall: every design duplicates the same building blocks. The same hero snippets, the same pricing tables, the same color and typography rules, the same JS carousel and mega-menu code get copy-pasted from one theme module into the next. When a brand color changes or a snippet has a bug, you edit it in five places and inevitably miss one. Odoo's native website builder gives you snippets and a theme structure, but it has no concept of a shared library that several themes can depend on; core website assets are global and hard to version, and a stock off-the-shelf apps.odoo.com theme ships its utilities locked inside its own package where your other themes can't reuse them. That is exactly the gap this build-to-order module closes.

We build theme_common as a dedicated foundation module that your other theme modules declare as a dependency in their __manifest__.py. It centralizes the parts that should only exist once: a versioned SCSS layer of design tokens (color palette, spacing scale, typography, breakpoints) exposed as CSS custom properties and Bootstrap/Odoo SCSS variable overrides; a curated set of reusable QWeb <template> snippets registered against website.snippets so they appear in the drag-and-drop builder of every child theme; and a library of OWL components and vanilla JS website widgets (publicWidget) for interactive elements like sliders, tabbed content, animated counters, and sticky headers. Assets are wired through the assets_frontend and web.assets_frontend bundles so each dependent theme loads the shared code once, in the right order, without duplication.

Technically, the module is structured so child themes override rather than fork. Design tokens live in SCSS partials that a child theme can re-declare to re-skin the entire component set without touching markup. Snippet options are defined in the standard snippet_options XML so your editors get the same inline controls (color pickers, layout toggles, spacing) across every design. Where content needs to be data-driven we add small models.Model helpers with computed fields (@api.depends) and expose them safely to the frontend, with access governed by ir.model.access.csv and record rules so public-website rendering never leaks backend data. Everything is built and tested against Odoo 17.0, 18.0, and 19.0, and we note the Community vs Enterprise differences that matter for website features so your deployment target is handled correctly from day one.

Because this is made-to-order, delivery works as a short, structured engagement rather than an instant download. We start with a scoping call to inventory your existing themes, the snippets and widgets you want consolidated, your token/design system, and your target Odoo version and edition. We then build on a staging branch, run UAT against your real content, and hand over installable source, documentation, and a git repository. Typical delivery is 2–4 weeks from confirmed scope, depending on how many themes and components are folded into the shared layer. Pricing starts from $249 (indicative, single-company base scope); the number of child themes consolidated, the depth of the design-token system, custom interactive widgets, and any migration of existing snippet content increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.