Odoo Community vs Enterprise vs Odoo.sh: Real Costs 2026

Here's the number nobody publishes: a 15-user Spanish SMB on Odoo Enterprise Standard pays €13,446 in license fees over 3 years — and the license is the cheap part. By the time you add a Spanish partner to implement, the Verifactu adapter, a payroll bridge to A3Nom, and the per-app math that quietly pushes you onto the Custom plan, the realistic 3-year bill lands closer to €49,000. I'll show you the math line by line.

I've been pricing Odoo deployments for Spanish SMBs since v13. The pattern repeats: someone reads the odoo.com pricing page, sees "€24.90/user/month", multiplies by their headcount, and walks into a planning meeting with a budget that is wrong by a factor of three. Not because Odoo is expensive — it isn't, compared to SAP Business One or Microsoft Dynamics 365 Business Central — but because the public price is roughly 18% of what you actually spend.

This guide rebuilds the 3-year total cost of ownership for the four ways you can run Odoo: Community (free, self-hosted), Enterprise (the proprietary add-ons), Odoo Online (the SaaS) and Odoo.sh (managed hosting on AWS). I do it for three company sizes — 5, 15 and 50 users — with Spanish partner rates and the local add-ons priced in. Bookmark this. You will want the TCO list when your CFO asks "are you sure?"

Quick warning before we start. Odoo changes its pricing roughly twice a year, and the Spanish reseller landscape is fragmented enough that two partners will quote you 40% apart for the same scope. Treat my numbers as the March 2026 baseline. Re-verify on odoo.com/pricing and against at least two partners before you sign anything.

Methodology: prices verified on odoo.com/pricing on 18 March 2026 for the Spain market (yearly billing, € pricing). Partner rates collected from quotes by 6 Spanish Odoo Silver/Gold partners between January and March 2026. Hosting estimates based on Hetzner CX31 and AWS t3.large benchmarks running Odoo v19 with PostgreSQL. All TCO scenarios assume 3 years, full implementation in year one, and steady-state support thereafter. Currency: € throughout. USD figures appear only when odoo.com lists them in dollars.

The Four Ways to Run Odoo

Before any pricing math makes sense, you need to be clear which Odoo you're talking about. There are four, they cost wildly different amounts, and the names overlap in ways the marketing site doesn't help with.

• Odoo Community — The open-source edition under AGPL-3. License is €0. You self-host, you patch, you update. Includes a real ERP core: accounting, inventory, sales, purchase, manufacturing, projects, website, eCommerce. Community v19 launched October 2025.
• Odoo Enterprise — Same code as Community plus a layer of proprietary modules (Studio, full accounting, marketing automation, IoT, advanced manufacturing, mobile apps, OCR, multi-company). License is per user, billed yearly. Three plans: One App Free, Standard (~€24.90/user/month), Custom (~€37.40/user/month). You still need to host or pay Odoo to host.
• Odoo Online — Enterprise license + Odoo's own multi-tenant SaaS. No custom modules allowed. No third-party apps from the marketplace. Limited to officially supported localizations. Easiest to start with, hardest to grow out of.
• Odoo.sh — Managed Enterprise hosting on AWS, with Git-based deploys, staging branches, automated backups and the ability to install custom modules. You pay for worker units (~€144/month per worker, billed at €0.20/h) on top of your Enterprise licenses. Aimed at companies that need real customization without running their own ops team.

The decision matrix in one paragraph: pick Community if you have technical staff and accept the maintenance burden. Pick Enterprise self-hosted if you want the proprietary apps but already have an ops capability. Pick Odoo Online only if you can live with zero customization and standard apps. Pick Odoo.sh if you need custom code and don't want to babysit servers.

Now — what does each one actually cost?

Sticker Price vs. Real Price: What odoo.com Doesn't Show

The odoo.com/pricing page shows three numbers: free, €24.90, €37.40. Those numbers are accurate. They're also misleading — not because Odoo lies, but because the license is the smallest line item in any real deployment.

Here's what gets added between the price page and your actual invoice:

• Implementation hours — A Spanish Silver partner charges €80–€120/h, Gold partners €110–€150/h. A clean 5-user services SMB needs 60–100 hours. A 15-user company with payroll, Verifactu and one custom report needs 150–250 hours. A 50-user mid-market with manufacturing typically burns 400–800 hours before go-live.
• Success Packs (if you skip a partner and buy implementation from Odoo) — sold in 15-hour blocks, currently €220+ per block depending on volume. Cheap on paper, but Odoo's success packs are best-effort consulting, not project management.
• The per-app trap — Standard plan is supposed to be "all apps included". In practice the moment you need Studio, External API access, multi-company, or any third-party module from the marketplace, you're forced onto Custom. More on that below.
• Payment processing — Stripe, Adyen and Redsys integrations all carry their normal processor fees (1.4% + €0.25 EU cards on Stripe). Not a license cost, but a real line item if you process invoices through the platform.
• Hosting — Even "free" Community needs a server. A Hetzner CX31 (~€18/month) handles 5–10 users; a 15-user deployment with proper backups and a staging environment runs €80–€150/month.
• Updates and version migrations — Community is free to update but you do the work. Enterprise migrations between major versions (v17 → v18, v18 → v19) typically need 40–120 partner hours for an SMB. See the Odoo 18 to 19 migration guide for the actual breakdown.

The brutal summary: license is roughly 15–25% of total spend. Implementation, hosting, customization and Spain-specific compliance modules eat the rest. Anyone telling you Odoo costs €25/user/month is selling you the bumper sticker, not the car.

There's a sixth cost worth flagging: the user count math. Odoo's per-user pricing counts every internal user who logs in, including warehouse operators, accountants and part-time staff. A common mistake is to size for "office users" and discover three months in that you also need to license the four warehouse staff who use the inventory module on the shop floor. For a 15-user office, that often means buying 19 or 20 licenses once you count everyone with a login — another €1,500–€2,200 per year you didn't budget.

Community: When "Free" Is Genuinely Free (and When It's Not)

Odoo Community is genuinely free. AGPL-3, no nag screens, no feature throttling, no "upgrade to unlock". The accounting module is real double-entry. Inventory works. Manufacturing routes work. The Spanish chart of accounts (PGC) ships in the OCA localization. For a 5-person services company with a sysadmin, Community is the most under-rated ERP on the market.

Where it stops being free is when you count what you give up. Studio doesn't exist in Community — every form customization is XML you write by hand or commission. The accounting module is missing roughly 30% of what Enterprise ships (no statement reconciliation widget, no follow-up letters, no asset depreciation automation, no budget vs actuals dashboard). The mobile apps are absent. OCR for vendor bills isn't there. Multi-company works but is rougher.

And Verifactu? Community needs the OCA `l10n_es_edi_verifactu` module, which is free and well-maintained — but you install, configure and maintain it yourself. A partner-built equivalent costs €500–€2,000 one-time plus €300–€600/year maintenance.

Community is the right choice when:

• You have at least one developer or sysadmin on payroll who knows Python and PostgreSQL
• You're under 10 users and your processes are standard (no exotic workflows)
• You're comfortable being on your own for security patches and version migrations
• Your accounting needs are simple — invoices, basic reconciliation, VAT submission, end-of-year reports
• You can live without OCR, Studio and the polished mobile apps

Community is the wrong choice when: you don't have technical staff, you need Studio to build forms (everyone needs Studio eventually), or you're banking on a Spanish partner doing the heavy lifting — most partners refuse to support Community deployments because they make money on Enterprise renewals.

Enterprise Standard vs Custom: The Per-App Trap That Pushes You to Custom

Enterprise has three commercial tiers: One App Free (one user, one app, useful for trying it), Standard (~€24.90/user/month) and Custom (~€37.40/user/month), both billed annually. The marketing pitch is that Standard includes "all apps". That is technically true and practically false.

Here is what Standard quietly excludes:

• Studio — the no-code customization tool. Custom-only. The moment you want to add a single field to the sales order form without writing a module, you need Custom.
• External API access — XML-RPC and the JSON-RPC endpoints. Standard restricts external API integrations. If you want to push data from a Shopify store, sync with HubSpot, or feed BI tools, Custom-only.
• Multi-company — the proper multi-company features (intercompany transactions, consolidation) require Custom on the published plan list.
• Odoo.sh hosting — Standard customers cannot deploy to Odoo.sh. To use Odoo.sh you must be on Custom.
• Marketplace third-party apps — anything from apps.odoo.com that isn't a vanilla Enterprise module typically needs Custom because it requires API access or Studio to integrate cleanly.
• Multi-website with separate sales channels, advanced reporting tools that pull from multiple data sources, and the developer mode features that real customization needs — all gated to Custom in practice.

The math gets nasty fast. The price gap between Standard and Custom is €12.50/user/month — call it €150/user/year. For a 15-user team that's €2,250/year, or €6,750 over 3 years, just to unlock Studio. It feels small per-user. It isn't small in aggregate.

My honest assessment: any deployment with 10+ users will end up on Custom within 12 months. The exceptions are companies running absolutely vanilla Odoo on standard apps, single-company, no integrations. I have seen exactly two of those in the last three years.

If you're sizing a deployment for 10 or more users, price the Custom plan from day one. Budgeting Standard and "upgrading later" almost always means a renegotiation halfway through year two, when you've already committed to integrations that need API access. Quote both. Show both to your CFO. Pick Standard only if you can credibly commit to no Studio, no API, no marketplace.

Odoo Online: The Simplicity Tax

Odoo Online is Odoo's own multi-tenant SaaS. Pricing matches Enterprise — Standard or Custom — but you pay nothing extra for hosting. Backups are automatic. Updates happen on Odoo's schedule. There is no infrastructure to manage. For a 5-user company that wants to be running tomorrow, it's the lowest-friction start.

The catch: Online is the most restrictive of the four options. No custom modules. None. You cannot install anything from the marketplace that isn't pre-approved. You cannot write a one-line Python override. You are limited to Odoo's official localizations — which thankfully includes Spain. Studio works (on Custom), so simple form customization is fine, but anything requiring real code is impossible.

Online makes sense for two profiles. The first: a small services SMB (under 10 users) with completely standard processes who values not running infrastructure. The second: a company piloting Odoo before deciding whether to move to Odoo.sh or self-hosted Enterprise — Online is a clean way to validate that Odoo fits your processes before investing in customization.

If you ever need a custom module, Online is a dead end. Migrating from Online to Odoo.sh is supported but non-trivial — partner quotes I've seen run €3,000–€8,000 for the migration alone, depending on data volume. Plan for this if you suspect you'll customize.

One underrated point about Online: the update cadence is not yours to control. Odoo pushes minor versions on its own schedule, and major version migrations happen automatically. For most SMBs that's a feature — you don't have to think about it. For anyone with regulatory or audit requirements that demand frozen versions, it's a deal-breaker. Spanish accounting firms running Odoo for clients tend to avoid Online for exactly this reason: they can't risk Hacienda submission code changing mid-quarter without their sign-off.

Odoo.sh: Who Actually Needs Managed Hosting?

Odoo.sh is the option that confuses people most. It's not a different Odoo — it's the same Enterprise software, hosted on AWS, with Git-based deployments, staging branches, automated backups and the ability to install custom modules without managing your own servers. You're paying for the operations layer.

Pricing is the Enterprise license per user (Custom only — Standard customers cannot use Odoo.sh) plus worker units. A worker is roughly one CPU core dedicated to handling Odoo requests. They're billed at €0.20/h which works out to about €144/month per worker. Small companies (5–10 users) usually need 1 worker; 15–25 users need 2; 50 users typically need 3–4. Plus a small per-GB storage cost that rarely exceeds €20/month for SMBs.

Odoo.sh is worth it when:

• You have or will commission custom modules (almost certain at 15+ users)
• You want Git-based deployment with staging branches before production
• You don't have a sysadmin who can babysit a self-hosted Enterprise instance
• You need automatic backups with point-in-time restore
• Your partner deploys via Odoo.sh by default (most Spanish Gold partners do)

Odoo.sh is overkill when: you're under 10 users with no custom code (use Online), or you have a competent ops team and want to save money (self-host Enterprise on Hetzner — you'll cut hosting costs by 60–70% but you own the runbook).

Spain-Specific Add-On Costs (Verifactu, Payroll, Partner Rates)

Every Spain deployment carries costs that English-language buying guides don't mention. These are non-negotiable if you're invoicing in Spain.

Verifactu / SII compliance. From July 2025, the Verifactu regime requires invoice records to be sent to Hacienda in real time (or near-real-time). The free OCA `l10n_es_edi_verifactu` module covers the basic requirement and is well-maintained. Partner-packaged equivalents — with phone support, certificate management and migration help — cost €500–€2,000 one-time plus €300–€800/year maintenance. For SII (large taxpayers), expect €1,500–€4,000 one-time.

Payroll. Odoo's native payroll module does not handle Spanish nóminas, IRPF retentions, Seguridad Social filings or the monthly CRA / Sistema Red uploads correctly out of the box. Real-world deployments either bridge to A3Nom (Wolters Kluwer) or Sage Nóminas, or use a Spanish-developed payroll module from a partner. Expect €2,000–€8,000 for the bridge implementation and €80–€200/month ongoing for the payroll engine itself. See the Odoo Spain Verifactu, SII and payroll guide for the full breakdown.

Partner hourly rates (March 2026). Silver partners: €80–€120/h. Gold partners: €110–€150/h. Senior functional consultants on either tier bill at the upper end. Junior developers go for €60–€80/h but you'll burn more hours. For partner selection, see best Odoo partners in Spain.

Custom localization tweaks. Spanish chart of accounts is included, but most companies need adjustments: custom analytical accounts, AEAT model 303/390/347 reports, sector-specific tax categories. Budget 20–60 partner hours in year one.

Three-Year TCO Scenarios for 5, 15 and 50 Users

Now the math. These five scenarios assume Spain deployment, March 2026 prices, partner-led implementation (where applicable), and standard SMB processes. All figures rounded to the nearest €100. License costs use the public per-user/month price multiplied by 36 months.

Scenario A — 5-user services SMB on Community self-hosted:

1. License: €0 (AGPL-3)
2. Implementation: €5,000 (60 partner hours × €85, or in-house equivalent)
3. Hosting: €1,000/year × 3 = €3,000 (Hetzner CX31 + backups + monitoring)
4. Verifactu (OCA module + setup): €600 one-time
5. Partner support / fixes: €4,000/year × 3 = €12,000
6. 3-year total: ~€20,600

Scenario B — 5-user services SMB on Enterprise Standard (self-hosted):

1. License: 5 users × €24.90 × 36 months = €4,482
2. Implementation: €8,000 (90 partner hours)
3. Hosting: €1,500/year × 3 = €4,500
4. Verifactu (partner module): €1,200 one-time + €1,200 maintenance over 3 years = €2,400
5. Partner support: €3,000/year × 3 = €9,000
6. 3-year total: ~€28,400 (note: I rounded the support estimate up vs. Community since Enterprise customers typically buy more partner hours)

Scenario C — 15-user SMB on Enterprise Standard (self-hosted):

1. License: 15 users × €24.90 × 36 months = €13,446
2. Implementation: €18,000 (200 partner hours)
3. Hosting: €2,500/year × 3 = €7,500
4. Verifactu + payroll bridge: €5,000 one-time + €3,600 maintenance = €8,600
5. Partner support: €6,000/year × 3 = €18,000
6. 3-year total: ~€65,500

Scenario D — 15-user SMB on Odoo.sh Custom:

1. License: 15 users × €37.40 × 36 months = €20,196
2. Odoo.sh workers: 2 workers × €144/month × 36 = €10,368
3. Implementation: €18,000 (200 partner hours, partner deploys via Odoo.sh)
4. Verifactu + payroll bridge: €8,600
5. Partner support: €6,000/year × 3 = €18,000
6. 3-year total: ~€75,200 (you save the self-hosting headache and gain Git deploys + staging; the premium is roughly €10K over self-hosted Enterprise)

Scenario E — 50-user mid-market on Enterprise Custom (Odoo.sh, manufacturing):

1. License: 50 users × €37.40 × 36 months = €67,320
2. Odoo.sh workers: 4 workers × €144/month × 36 = €20,736
3. Implementation: €60,000 (600 partner hours including manufacturing setup, custom modules, integrations)
4. Verifactu + SII + payroll bridge + sector localization: €15,000
5. Partner support / managed services: €25,000/year × 3 = €75,000
6. 3-year total: ~€238,100

Read those numbers again. The license — the only line on odoo.com/pricing — is 15% of Scenario A, 21% of Scenario C, and 28% of Scenario E. The other 70–85% is implementation, hosting, Spanish compliance and partner support. If your budget conversation only covers the license, you are budgeting for less than a quarter of the real cost. That is the single most common mistake I see in Spanish Odoo projects.

The Break-Even Math: When Each Edition Wins

Strip away the marketing and there are clear break-even points. These are the rules I actually use when scoping a project.

• Community wins below 8 users when you have technical staff. Above 8 users, the partner support gap (most refuse to back Community) makes Enterprise cheaper despite the license.
• Enterprise Standard wins for 5–10 user vanilla deployments. Above 10 users, the per-app trap pushes 80% of buyers onto Custom within 18 months — price Custom from day one.
• Odoo Online wins for sub-10-user companies with zero customization needs. The instant you commission a custom module, you're stuck on a migration path.
• Odoo.sh wins above 15 users in nearly every scenario because the worker cost (€144/month) is cheaper than a competent sysadmin's time, and Git-based staging eliminates a whole category of production incidents.
• Self-hosted Enterprise wins only when you have a dedicated DevOps capability and want to cut €5,000–€15,000/year in hosting costs. Below that headcount, Odoo.sh's operational overhead reduction dominates.

My Recommendation by Company Profile

Cutting through the matrix: here is what I'd actually pick for each common Spanish SMB profile.

• Solo autónomo or 2–3 user micro-business: Holded instead of Odoo. Honestly. Holded handles Spanish accounting, Verifactu and basic CRM out of the box for €29–€89/month, with no implementation cost. Odoo is overkill until you have at least 5 users with diverse processes. See the Odoo vs Holded migration comparison.
• 5–10 user services SMB with technical staff: Odoo Community self-hosted. Real ERP, €0 license, accept the maintenance burden as the trade-off. Budget ~€20K over 3 years.
• 5–10 user services SMB without technical staff: Odoo Online Standard with a Spanish partner doing setup. Lowest friction. Budget ~€18K–€25K over 3 years including partner.
• 15-user product or services SMB: Odoo.sh Custom. Yes, it's pricier than self-hosted Enterprise — about €10K more over 3 years — but you get staging branches, Git deploys and zero ops burden. Worth it. Budget ~€75K.
• 25–50 user manufacturing or distribution: Odoo.sh Custom with a Gold partner who specializes in your sector. The implementation cost will dwarf the license — pick the partner first, then the platform. Budget €150K–€250K over 3 years.
• 50+ users with global operations: Compare Odoo against Microsoft Dynamics 365 Business Central and SAP Business One before committing. Odoo wins on flexibility and price; the others may win on enterprise reporting and audit features depending on your industry.

My honest verdict: for the typical Spanish SMB between 10 and 30 users, Odoo.sh Custom with a Spanish Gold partner is the right answer roughly 7 times out of 10. It's not the cheapest option on the spreadsheet — Community is — but it's the option where the 3-year total cost is the most predictable, the migration path is the cleanest, and the failure modes are the least painful. The remaining 3 out of 10 cases either belong on Community (technical teams who want full control) or shouldn't be on Odoo at all (very small businesses better served by Holded).

Final practical advice. Get two written quotes from different Spanish partners before signing. Insist on a fixed-price first phase (discovery + chart of accounts + Verifactu setup) so you can test the partner relationship without committing the full implementation budget. And ask explicitly: "What is the all-in 3-year cost including license, hosting, your hours, the Verifactu module and any third-party tools?" If the answer is just a per-user/month number, you're talking to the wrong partner.

Pricing verified on 18 March 2026. Re-check odoo.com/pricing before you commit — Odoo's pricing changed twice in 2024 and once in 2025.