odoobarcelona
← Back to the blog
GUIDE

Odoo reviews: an honest take from the people who implement it

An unfiltered assessment of Odoo: where it shines, where it genuinely hurts (learning curve, third-party modules, yearly versions, partner dependency, per-user cost), who it suits and who it doesn't, and what to ask before you sign.

Search for Odoo reviews and you'll find two kinds of text: the vendor and its partners saying it does everything, and the company that had a bad implementation saying it's useless. Both are unfair. We make our living implementing Odoo for companies in Catalonia, so we have an obvious interest: that's exactly why this article skips the generic praise and focuses on where Odoo works really well and where it can hurt you if nobody warns you.

You won't find scores from review sites or client testimonials here. Not because there aren't any, but because an average rating tells you nothing about your case. What can help is knowing where problems usually appear, and we see that every week.

Odoo almost never fails because of the software: it fails when it's implemented without first deciding what must not be customised.

Where Odoo is genuinely good

One database for the whole company

It's its strongest argument and it holds up. CRM, sales, purchasing, inventory, invoicing, accounting, projects and HR share the same data. An accepted quote becomes a sales order, the order moves stock and generates the invoice, and the invoice reaches accounting without exporting anything to a spreadsheet. For a small business that currently runs four programs that don't talk to each other, the change is huge.

Modular: start small and grow

You don't need to switch everything on from day one. You can start with invoicing and CRM and add inventory or manufacturing when it makes sense. That lets you spread effort and cost across phases, which is hard with more rigid ERPs.

Open source, without total lock-in

The Community edition is open source. Your data and the software don't depend on a single company: if one day you want to change partner or server, you can. With Enterprise the licence belongs to the publisher, but the core is still the same public code. We cover the differences in depth in our Community vs Enterprise comparison.

A living product

Odoo ships a major version every year (16 in October 2022, 17 in November 2023, 18 in October 2024, 19 in September 2025 and 20 in September 2026, according to the official documentation). Each version brings real usability improvements and new features. Few ERPs evolve at this pace.

Where Odoo hurts (and nobody mentions it in the demo)

The learning curve

The interface is clean, but Odoo is an ERP, not a note-taking app. Setting up accounting journals, fiscal positions, warehouse routes or price lists properly requires understanding how it was designed. End users adapt within a few weeks; whoever administers it needs a lot longer. If nobody inside the company understands the underlying logic, every small change ends up as a call to the partner.

Third-party modules of very uneven quality

There are thousands of third-party modules, on the Odoo app store and in the OCA community. Some are excellent and maintained for years; others were written by someone for one specific project and never touched again. A poorly built module can block an upgrade or break with the next version. Our rule: every external module needs a reason, an owner and a plan for the next migration.

The yearly version cycle has a cost

The flip side of a living product. According to the official documentation, each major version gets three years of standard support, and security updates are only provided during that standard support; after that there is paid extended support. In practice, you need to migrate every two or three years. If your installation is close to standard, the migration is manageable. If it's full of custom development, each migration is a project in its own right.

Dependency on the partner

Odoo is sold mostly through partners, and the quality of an implementation depends far more on the partner than on the software. A bad partner can leave you with customisations only they understand, no documentation and no access to the code. It's the risk we see most often in companies that come to us from another implementation.

Enterprise: the cost grows with every user

The Enterprise edition is paid per user per month (on our pricing, from €19.90 per user per month). With ten users it's reasonable; with fifty, the licence becomes a significant line item every year, and it doesn't go down. Before choosing it, run the five-year numbers and compare them with Community plus the modules you actually need.

Pros and cons at a glance

StrengthWeakness
Every area in a single databaseYou need to understand its logic to administer it well
Modular: roll it out in phasesThird-party modules of uneven quality
Open-source Community, no licencesSome features only exist in Enterprise
A new major version every yearMigrate every few years to stay supported
Large partner ecosystemQuality depends heavily on the partner
Low entry priceEnterprise grows with every user

Who Odoo is for, and who it isn't for

Odoo fits very well in small and mid-sized companies that want to unify sales, operations and finance, that are willing to adapt some processes to the standard, and that have at least one person ready to own it internally. It also suits growing companies that want to start small and add modules over time.

It's not the best option if you need a very specific vertical program your industry has already solved (and that Odoo would only cover with heavy development), if you want the software to fit one hundred per cent of how you work today without changing anything, or if nobody in the company can spend time on the implementation. In those cases, better to know before rather than six months into the project.

What to ask an implementer before you sign

  • Which part of the project will be standard and which will be custom? Get it in writing.
  • Which third-party modules will you install, who maintains them, and what happens to them in the next version?
  • Is the custom code mine? Will I have access to the repository?
  • Roughly how much will it cost to migrate to the next version with this configuration?
  • Community or Enterprise: why, and what is the five-year total cost with the users I expect?
  • Who will train the person who will administer it internally?
  • How are Verifactu and SII handled in my edition?

A good implementer answers these questions without discomfort. If any answer is vague, take note.

Frequently asked questions

Is Odoo good for a small business?

Yes, it's one of its natural audiences, as long as the company is willing to stay close to the standard and invest time in the implementation. The risk isn't size, it's customising everything.

How often does Odoo need upgrading?

A major version comes out every year and each one gets three years of standard support, which is when security updates are provided. In practice, it's wise to migrate every two or three years.

Is Odoo Community enough, or do I need Enterprise?

It depends on the features you need and how many users you have. We analyse it in our Community vs Enterprise comparison; the key is running the five-year cost numbers.

Can I switch partner if I'm not happy?

Yes, as long as you have access to your data and your custom code. That's why it must be spelled out in the contract from day one.

Keep reading