The limits of the Odoo builder.

Odoo's Website module is an excellent tool: it lets anyone build a working website without coding. But after using it on demanding projects, we know its blind spots well. This article is not an indictment of Odoo. It is an honest map of its limits, and of how we get past them without ever leaving the ecosystem.

What the builder does really well.

Let's start with the positives, because they are real. The Odoo builder lets you create and edit pages without a developer, connects forms natively to the CRM, handles multilingual content and stays consistent with the rest of the ERP. For a simple website built in house, it is a very good tool.

So our reservations are not about “is Odoo a good CMS?”. It is. They are about what happens when you want a website that stands out.

The “catalogue” look.

The first limit is visual. The ready-made blocks are designed to suit everyone, so they surprise no one. Built from the same bricks, most sites end up speaking the same visual language: the same heroes, the same cards, the same spacing. Hence the well-known “that looks like Odoo” effect.

You can adjust colours and fonts, but the underlying structure is still that of the blocks. For a design with a real signature, you have to step outside the catalogue, which we explore in an Odoo website can be beautiful.

HTML that keeps getting heavier.

Every block you add stacks up containers, classes and options. On a rich page, the generated HTML becomes heavy: lots of nested div elements, unnecessary CSS, scripts loaded “just in case”. The result: pages that are slower than they need to be.

Yet speed has a direct impact on SEO and conversion. A site weighed down by the builder can fall short on Core Web Vitals, an issue we break down in is your Odoo website slow?.

Official benchmark: Google considers a page good with an LCP under 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1, measured at the 75^th percentile of page loads. Source: Google, Core Web Vitals, accessed in August 2026.

Restricted animations and interactions.

Drag and drop offers a fixed set of animations and effects. As soon as you want a precise interaction, such as a custom transition, a scroll animation designed to tell a story or a specific interactive component, you run into the limits of the editor.

These details are not cosmetic: they are what give a website a feeling of quality and care. Reproducing them faithfully means writing code, not ticking options.

The missing components.

Sooner or later, a project needs a component the catalogue does not offer: a particular editorial layout, a specific comparison table, a section designed for one unique use case. The builder can only offer what was planned in advance.

• Editorial layouts that break out of the standard grid.
• Business components specific to your activity.
• Micro-interactions and custom animations.
• Fine-grained SEO structures (precise schema, accurate markup).

How we get past these limits.

The good news: getting past these limits does not mean leaving Odoo. We code the key pages directly in QWeb, Odoo's templating engine, with custom CSS. You keep the whole ecosystem (CRM, multilingual, back office) and we only replace drag and drop with clean code where it matters.

That is exactly what we do, and the reason we hand-code in Odoo. To understand the language behind it: QWeb explained simply.

Need to go further than the website builder? Talk to our Odoo agency.