Odoo's licensing math just changed for anyone running custom Odoo development in the US. If your team relies on Odoo Studio, third-party integrations, or Odoo.sh hosting, the plan that supports all of that just got significantly more expensive — and understanding why is the first step to protecting your budget.

What Actually Changed in 2026

In the USA, the Odoo Custom plan rose from $46.70 to $61.00 per user/month billed yearly, a 31% increase, while the Standard plan remained unchanged at $31.10. This wasn't a small adjustment — it's the largest jump seen in Odoo's published US pricing in recent memory, and it lands unevenly across the world. In Germany, the Custom plan rose from €37.40 to €44.90 (+20%), while Standard stayed unchanged at €24.90. The US increase, at 31%, is notably steeper than the euro-market adjustment.

The timing is not a coincidence. The increase coincided with Odoo 20 being unveiled at Odoo Experience 2026, and the Custom plan card on odoo.com now lists "Odoo Studio / Agentic AI" alongside a new Light User licence. Odoo appears to be repositioning the Custom tier around its expanding AI and automation capabilities — but for operations leaders, the practical effect is simpler: the tier you likely need for any real customization work now costs meaningfully more.

One detail matters for budgeting: "First-year price" is Odoo's introductory rate, valid for 12 months on initial users ordered, and first-year discounts still apply to new users — budget for the list price from year two. If you signed up recently at a promotional rate, the real cost impact hits at renewal, not immediately — which means many US teams haven't felt this yet but will within the next billing cycle.

Why This Hits Custom Development and Integration Teams Hardest

The Custom plan isn't optional padding for most technically mature Odoo deployments — it's structurally required. Odoo moves a database to Custom automatically when Studio is installed or a second company is added, and Custom is also required for the external API, custom modules, Odoo.sh, and on-premise hosting. In practice, that means:

  • Any external integration — connecting Odoo to a warehouse management system, a payment gateway, a CRM, or a custom API-driven workflow — requires Custom, since access to data via the external API is only available on Custom Odoo pricing plans and is not available on One App Free or Standard plans.
  • Multi-company or multi-entity operations trigger the same requirement, since the custom plan is for companies that want to manage multiple companies on a single database and that need to customize Odoo through Odoo Studio, agentic AI, custom developments or through the API.
  • Odoo.sh hosting, commonly used by US teams that want staging environments and CI/CD for custom module deployment, is Custom-only. Standard plan customers get Odoo Online cloud hosting only, while Custom plan customers can choose between Odoo Online, Odoo.sh (managed PaaS), or on-premise deployment.

This creates a compounding cost problem. It's not just the per-seat increase — it's that every user on a Custom database pays the higher rate, even employees who never touch Studio, the API, or a second company. A 25-person operations team that upgraded to Custom two years ago for one integration project is now paying the full 31% increase across all 25 seats, not just the users tied to that integration.

Odoo.sh, Studio, and the Real Cost of "Custom"

It's worth being precise about what the Custom plan price actually buys — and what it doesn't. Custom-plan subscription pricing does not include Odoo.sh infrastructure — Odoo.sh worker capacity, staging environments, and storage are billed separately on top of the per-user license. Similarly, custom code creates design, testing, documentation, deployment, maintenance, security, and upgrade work that lives outside the subscription entirely.

That means the real cost of a customized US Odoo deployment stacks in layers: the Custom license itself, Odoo.sh hosting fees, and the implementation/development cost of building and maintaining modules or integrations. Teams that only budgeted for the license line are the ones most exposed to this increase, because they haven't accounted for how much of their spend was already tied to the higher tier.

Deciding Between Custom and Standard: A Practical Framework

Not every team that's currently on Custom actually needs to be there. Before renewing, US operations leaders should audit their database against three questions:

1. Do you actually use Studio, multi-company, or the API — or did a one-time project leave the flag on? It's common for a database to get flipped to Custom for a single Studio tweak or a temporary second company that's since been decommissioned. If that's you, reverting to Standard can cut your license cost substantially, since the annual cost difference between Standard and Custom for a 10-user team is approximately $1,032 — and that gap only grows at the new pricing.

2. Is your integration truly external, or could it run inside Odoo? The API requirement specifically applies to external systems reaching into Odoo. The external API exists so external software can reach in, but a module running inside Odoo isn't external — it calls the ORM directly, in-process, and no external-API entitlement applies. Some integrations currently built as external API calls could be re-architected as in-database modules, avoiding the Custom-tier requirement altogether — though this trades license savings for development complexity.

3. Does the value of customization exceed the license delta? If the features you need save more than the cost difference in developer time or operational workaround costs, the upgrade pays for itself within the first year. For most mid-market US companies running real integrations, multi-entity operations, or custom workflows, that math still favors Custom — but it's worth running the numbers explicitly now that the gap has widened.

Where Grey Space Computing Fits In

Reassessing your Odoo licensing tier isn't a decision to make in isolation — it depends entirely on how your custom modules, integrations, and hosting are actually architected today. Grey Space Computing, an Odoo Ready Partner serving clients across the US, GCC, and India, works with operations leaders to audit exactly which Custom-tier features are genuinely in use, identify where API integrations or module logic can be optimized, and right-size Odoo.sh and licensing spend without disrupting live operations.

If the 2026 price increase has you rethinking your Odoo setup, talk to our team about a licensing and integration audit — we'll help you decide, with real numbers, whether Custom, Standard, or a re-architected approach is the smartest path forward for your business.