An Odoo site can be beautiful.

Odoo carries a stubborn reputation: that of a powerful management tool but one that produces bland websites, recognisable at first glance. This reputation comes from a misunderstanding of what customisation really is in Odoo. It’s not about choosing a colour from a menu, but about understanding the three levels to which we can act on the design.

Most Odoo sites are built in the same way: you activate the Website module, choose a theme from those offered, drag and drop a few pre-made blocks, and publish. The result works, but it carries the same visual signature everywhere: same spacing, same typography, same block structures.

It's not Odoo's fault. It's the price of convenience. A standard theme and ready-to-use blocks are quick and accessible — but by design, that's what everyone uses. Differentiation, on the other hand, requires going a step further.

To understand what can be done with an Odoo theme, we need to distinguish three levels of intervention, from the simplest to the most powerful.

• Level 1 — The theme and its options. Colours, fonts, headers, footers: settings accessible without code. Quick, but everyone has access to the same settings.
• Level 2 — The blocks and snippets. We assemble and adjust the provided blocks. More freedom, but we remain within Odoo's visual vocabulary.
• Level 3 — Custom code (QWeb + CSS). You write your own components directly in Odoo's template engine. Total design freedom, no builder limits.

Almost all Odoo sites stop at level 1 or 2. It's at level 3 that true differentiation happens — and that's precisely where a specialised agency works. To understand this language, our article QWeb explained simply details the engine behind all this.

At level 3, the question is no longer “what does Odoo allow?” but “what does the web allow?”. Specifically, on our projects, we redefine:

• Typography. Variable fonts, fluid sizes, custom vertical rhythm — not the 3 fonts offered by default.
• Components. Cards, hero sections, editorial layouts, scroll animations: designed for the brand, not picked from a catalogue.
• Interactions. Micro-animations, transitions, hover effects that give a sense of quality, impossible in pure drag-and-drop.
• The grid and space. The breathing of a page — often what distinguishes a “pro” site from a “template” site — is coded to the pixel.

Everything remains managed in Odoo: the client edits their texts normally, the forms feed the CRM, nothing is outsourced. We add customisation without breaking the ecosystem.

The classic trap: wanting a spectacular site at the expense of performance. On many platforms, each effect adds a plugin, each plugin adds weight, and the site ends up slow. A slow site loses in SEO and conversions — we explain it in is your Odoo site slow?.

The right approach is to code the design cleanly, without layers: native CSS, light animations, no unnecessary library. Result: a site that is both unique and fast, which passes the Core Web Vitals in the green.

We don't always need to redo everything. If your Odoo site is already running, we can gradually recode the key pages (home, services) while keeping the instance in place. It's a redesign, not a rebuild.

If the site is from another tool, we start from a blank design page, but still within your Odoo. In both cases, the goal is the same: a site that looks only like you.

At WebNest, we never start from a theme. We build a small design system — a coherent set of components, colours and typographies — that we code directly in QWeb in our Odoo. This is what allows for signed, fast, and easy-to-evolve sites.

That's also why we code by hand rather than drag-and-drop: the native builder quickly reaches its limits as soon as we want to stand out. We detail these limits — and how to overcome them — in our dedicated article.

• Can we really customise an Odoo theme?

  Yes, at three levels: the theme options (colours, fonts), the blocks and snippets, and especially the custom code in QWeb and CSS. It is this last level that allows for a truly unique design, indistinguishable from a classic bespoke site.
• Does a customised Odoo site remain easy to manage?

  Yes. Customisation affects the design and structure, not content editing. You continue to modify your texts, images, and pages in the usual Odoo interface, and your forms remain connected to your CRM.
• Does bespoke design slow down the site?

  Not if done properly. By coding cleanly, without stacking effect plugins, you get a site that is both customised and fast, passing the Core Web Vitals. The weight comes from overlays, not from bespoke.
• Do we need to redo the entire site to customise it?

  No. We can progressively recode the key pages in your existing Odoo instance, without starting from scratch. This is the principle of a targeted redesign.