Odoo 2027 Pricing Explained: Custom, Light Users and AI Credits

Introduction

Odoo pricing looks straightforward when viewed as a per-user subscription.

For a real business, however, the ERP budget is more complicated.

A company may have full ERP users, employees who only need limited access, external portal users, multiple companies, Studio customizations, custom modules, Odoo.sh hosting, integrations, implementation services and usage-based IAP services.

That means the more useful question is not:

How much does Odoo cost per user?

It is:

What will Odoo cost our business based on the users, plan, capabilities, usage and customization we actually need?

This question becomes particularly important for businesses planning around Odoo 20 and 2027 pricing.

Odoo's September 2026 announcement states that the Standard price remains unchanged while the Custom plan increases by 20%, alongside the introduction of the Light User access model. Odoo also highlights increasing costs associated with AI, hosting and IT as part of the reason for the pricing adjustment.

The result is a pricing model that CFOs, IT leaders and Odoo customers should evaluate through user roles, plan requirements and total cost of ownership, rather than employee headcount alone.

Odoo 2027 Pricing at a Glance

The current Odoo pricing page provides a useful reference point for understanding the commercial structure.

These are the current public figures displayed by Odoo and should not be treated as a universal final quotation for every country or contract. Odoo states that Light User access requires a customized quote, while applicable pricing depends on the commercial agreement.

For a 12-month calculation using the currently displayed annual-billing figures, the simple subscription equivalents would be approximately:

• Standard : $298.80 per full user/year

• Custom : $588 per full user/year

• Light User : $106.80 per Light User/year, if the displayed $8.90 rate applies to the specific agreement

These calculations exclude taxes, applicable discounts, Odoo.sh hosting, implementation services, IAP credits and other separately charged services.

What Is Changing for Odoo in 2027?

Odoo announced that its Standard pricing remains unchanged while the Custom plan price increases by 20%. The announcement also introduces the Light User model at €7.90 per employee in the announcement's European pricing context.

The live pricing page subsequently displays regional pricing in USD, including $49 for Custom, $24.90 for Standard and $8.90 for Light User.

This distinction matters.

Businesses should not take the euro announcement price and automatically convert it into their local renewal price.

Instead, confirm the actual commercial proposal applicable to your country, currency, contract and user requirements.

The strategic change is more important than the headline number:

Odoo customers now need to think about different types of access rather than simply counting full users.

Regular Users, Light Users and Portal Users

This is one of the most important areas of the new Odoo cost model.

Regular User

A Regular User is an internal user requiring broader backend access to Odoo applications and business processes.

Examples can include:

• Sales users

• Accountants

• Purchasing users

• Project managers

• Operations managers

Light User

Odoo's current pricing information defines a Light User in two relevant ways: an active account designated as a Light User, or an active employee record that is not linked to an active non-portal user account.

This is important because businesses should not assume:

Employee without a Regular User account = free employee record.

The Odoo 20 Enterprise Agreement explicitly includes active employee records without an active non-portal user account within its Light User definition.

Light User capabilities are restricted compared with Regular Users. Odoo lists selected employee and operational capabilities such as time off, expenses, appraisals, attendances, referrals, planning, Field Services, barcode operations, read-only Knowledge access, payslips, POS employee access and Manufacturing Shop Floor access.

Portal User

Portal users are external users accessing selected information through Odoo's portal rather than receiving broad internal backend access.

The important distinction is:

Regular User ≠ Light User ≠ Portal User

Build your pricing model around the actual Odoo user definitions and contractual terms rather than assumptions based on job titles.

What Can a Light User Do?

Light Users are designed for limited access rather than full ERP operations.

A typical decision process is:

Employee Role → Required Tasks → Required Applications → Required Permissions → User Category

For example, an employee who only needs:

• Time off

• Expenses

• Attendances

• Planning

• Payslips

may fit the Light User model.

Someone who needs:

• Sales

• Accounting

• Purchasing

• Projects

• Broad operational access

may require a Regular User.

The key point is that Light User classification should be based on Odoo's defined capabilities and the employee's actual requirements.

Standard vs Custom : Choose the Architecture Not Just the Price

The Standard and Custom plans both provide access to Odoo's applications, but they are designed for different technical requirements.

Odoo currently describes Standard as Odoo Online without custom modules, while Custom adds capabilities such as Odoo.sh, on-premise deployment, Studio, multi-company and external API access.

Therefore, the question should not be:

Which plan is cheaper?

It should be:

Which plan supports the architecture our business actually needs?

Studio, Multi-Company and API Requirements Can Change the Plan

Certain requirements can affect the subscription plan.

Studio

Odoo 20 documentation states that installing Studio on a Standard database automatically triggers an upsell to Custom. For yearly or multi-year contracts, an upsell order is created with a 30-day limit; monthly contracts switch to Custom at the next billing cycle.

Therefore:

Standard + Studio ≠ Standard pricing

Multi-Company

Odoo 20 documentation similarly states that enabling multi-company on a Standard database automatically triggers an upsell to Custom.

Businesses planning expansion should therefore consider future company structure when selecting their initial plan.

External API

If integrations require external API access, this should also be considered when determining whether the Custom plan is required. Odoo currently lists External API as a Custom capability.

Odoo.sh Is a Separate Infrastructure Cost

The Custom plan provides eligibility for Odoo.sh, but businesses should not interpret that as:

Custom subscription = Odoo.sh hosting included

Odoo's pricing page separates the Custom subscription from Odoo.sh infrastructure.

A realistic budget should therefore separate:

Custom User Subscription

from:

Odoo.sh Infrastructure

Depending on the architecture, businesses may need to budget for workers, storage, staging environments and other Odoo.sh requirements.

This distinction is particularly important for companies using custom development.

How Odoo AI Credits and IAP Affect Pricing

AI should have its own cost model.

Odoo's current pricing page lists IAP credits and custom-code maintenance among items excluded from the standard subscription scope.

Odoo's IAP model is usage-based. For example, document digitization uses prepaid credits, with one document consuming one credit in the documented service.

Odoo also currently lists an Odoo AI IAP service priced from €1 per credit, with consumption varying according to the AI feature, task complexity and request size.

Therefore:

Odoo Subscription ≠ Unlimited AI Consumption

Businesses should separately estimate:

• AI features being used

• IAP services

• Expected request volume

• Credit consumption

• Department usage

• Monthly budget

• Auto-refill requirements

• Expected growth

The important distinction is:

Access to AI functionality does not automatically mean unlimited usage at no additional cost.

Implementation and Custom Development Are Separate Costs

Subscription pricing is only one part of ERP ownership.

Implementation may involve:

• Process discovery

• Project management

• Data migration

• Configuration

• Customization

• Integration

• Training

• Testing

• Go-live support

Custom development also creates lifecycle costs:

Development → Testing → Documentation → Maintenance → Upgrade → Regression Testing

Odoo's pricing information separates implementation services and custom-code maintenance from the core subscription.

Businesses should therefore calculate:

Initial Development + Maintenance + Upgrade Work + Testing + Support

rather than treating custom development as a one-time expense.

Build Your Odoo 2027 Cost Model

A useful cost model should contain five categories.

User Costs

• Regular Users

• Light Users

• Additional users

Platform Costs

• Standard or Custom subscription

• Odoo.sh

• Required infrastructure

Usage Costs

• IAP

• AI usage

• Other usage-based services

Project Costs

• Implementation

• Migration

• Integration

• Custom development

• Training

Ongoing Costs

• Support

• Custom-code maintenance

• Upgrades

• Additional users

• Infrastructure growth

This creates a much more realistic Odoo Total Cost of Ownership model.

Illustrative Odoo Cost Example

Consider an illustrative organization with:

• 30 Regular Users

• 20 Light Users

• 50 portal users

• Custom plan

• Odoo.sh

• Some custom development

Using the currently displayed Custom annual-billing rate:

30 × $49 × 12 = $17,640/year

If the displayed Light User reference rate applies:

20 × $8.90 × 12 = $2,136/year

The illustrative subscription component becomes:

$19,776/year

Portal users with limited portal access should be treated separately from Regular Users under the applicable Odoo definitions.

Illustrative example only: This is not an Odoo quotation. Actual pricing depends on the applicable country, currency, contract, user classification, discounts, taxes and commercial terms.

Illustrative Three-Year Odoo TCO

A CFO should look beyond Year 1.

The following is an illustrative planning model, not official Odoo pricing:

The purpose of this table is to demonstrate how to structure a TCO model, not to predict what every Odoo customer will pay.

First-Year Discounts Should Not Become Your Long-Term Budget

Odoo's pricing model can include promotional discounts for initial users and contract periods.

Therefore, do not build a three-year budget using only a discounted first-year price.

Model:

Year 1 → Applicable commercial pricing

Year 2 → Expected renewal pricing

Year 3 → Renewal pricing + expected growth

Before signing, confirm:

• Discount duration

• Users covered

• Renewal pricing

• Additional-user pricing

• Plan-change rules

• Contract duration

• Currency

• Taxes

• Commercial terms

The signed commercial agreement should always take priority over an online pricing estimate.

User Governance Is Also Cost Governance

The Odoo 20 Enterprise Agreement states that charges are based on the number of Users, Light Users and the subscription plan specified in the agreement. Additional users, Light Users, or features requiring another plan can result in additional fees for the remainder of the term.

That means businesses should maintain a simple user-governance process:

Employee Join → User Classification → Access Assignment → Role Change → Deactivation → Subscription Review

This prevents inactive or incorrectly classified access from becoming an unmanaged cost.

Version Strategy Can Affect TCO

Odoo 20's Enterprise Agreement defines the three most recently released major versions as Covered Versions. It also states that customers remaining on versions older than the Covered Versions can incur an additional fee equal to 25% of the annualized price, under the agreement's stated conditions.

This makes version strategy a financial consideration as well as a technical one.

A long-term Odoo budget should therefore consider:

• Subscription

• Upgrade planning

• Custom-code migration

• Testing

• Regression validation

• Potential older-version charges

Odoo Pricing Mistakes to Avoid

Pricing Only by Employee Headcount

Not every employee requires the same level of access, but employee records can also have licensing implications under the Light User definition.

Treating Light Users as Free Employees

Odoo's current Enterprise Agreement defines active employee records without an active non-portal user account as Light Users.

Assuming Studio Remains on Standard

Installing Studio on Standard can trigger an upgrade to Custom.

Ignoring Multi-Company

Enabling multi-company on Standard can trigger an upgrade to Custom.

Treating Odoo.sh as Included Hosting

Custom supports Odoo.sh, but Odoo.sh infrastructure should be budgeted separately.

Assuming AI Is Unlimited

AI and IAP services can involve usage-based credits and should be forecast separately.

Budgeting Only for Year One

A discounted first year does not automatically represent the long-term TCO.

Ignoring Custom-Code Lifecycle Costs

Custom development can create ongoing maintenance, testing and upgrade requirements.

Odoo 2027 Pricing Checklist Before Signing

Users

• Regular Users identified

• Light Users identified

• Portal users separated

• Employee records reviewed

• User-growth forecast prepared

Plan

• Standard vs Custom evaluated

• Studio requirement checked

• Multi-company requirement checked

• External API requirement checked

• Deployment architecture defined

Infrastructure

• Odoo Online vs Odoo.sh evaluated

• Odoo.sh infrastructure estimated

• Storage requirements reviewed

• Staging requirements reviewed

AI and Usage

• AI use cases identified

• IAP services identified

• AI/IAP consumption estimated

• Usage budget established

Implementation

• Migration scope defined

• Integration scope defined

• Custom development estimated

• Training budgeted

• Support model defined

Contract

• Local pricing confirmed

• Discount confirmed

• Renewal pricing understood

• Additional-user pricing confirmed

• Plan-change rules reviewed

• Version strategy understood

• Taxes and commercial terms confirmed

Need Help Estimating Your Actual Odoo 2027 Cost?

Every business has a different combination of Regular Users, Light Users, deployment requirements, customization, integrations, AI usage and implementation effort.

A practical cost assessment should therefore begin with the business operating model, not a generic per-user calculation.

Browseinfo can help businesses evaluate user requirements, compare Standard and Custom architecture, estimate implementation and customization costs, assess Odoo.sh and integration requirements and build a realistic multi-year Odoo TCO model.

Frequently Asked Questions

1. What is changing in Odoo pricing for 2027?

Odoo has kept Standard pricing unchanged while increasing the Custom plan by 20% and introducing the Light User model in its 2027 pricing announcement. Actual customer pricing should be confirmed against the applicable country, contract and commercial proposal.

2. What is an Odoo Light User?

A Light User covers a restricted-access user and, under Odoo's current Enterprise Agreement, an active employee record that is not linked to an active non-portal user account. The applicable capabilities and commercial terms should be checked before classifying employees.

3. Are Light Users the same as portal users?

No. Light Users are associated with limited internal employee access or qualifying employee records, while portal users are external users accessing selected portal functionality. These categories should be modeled separately when planning Odoo access and cost.

4. How should businesses calculate Odoo user costs?

Businesses should classify Regular Users, Light Users and applicable portal access according to Odoo's definitions and their actual requirements. The calculation should then include regional pricing, discounts, contract terms, plan requirements and expected user growth.

5. What is the difference between Odoo Standard and Custom?

Standard is designed for Odoo Online without custom modules, while Custom supports additional capabilities such as Studio, multi-company, external API, Odoo.sh and on-premise deployment. The correct choice depends on the required architecture rather than subscription price alone.

6. Does Odoo.sh add to the total Odoo cost?

Yes, Odoo.sh should be evaluated as a separate infrastructure cost from the Custom subscription. Businesses should estimate the workers, storage, staging and other infrastructure requirements applicable to their environment.

7. What are Odoo IAP and AI credits?

IAP services are usage-based services that use prepaid credits, while Odoo currently offers AI through its IAP ecosystem with consumption depending on the AI feature and request complexity. Businesses should forecast these costs separately from user subscriptions.

8. Should AI costs be included in the Odoo 2027 budget?

Yes. Businesses should identify planned AI capabilities, determine whether they involve usage-based credits or other commercial terms and establish a separate AI budget so increasing usage does not create unexpected costs.

9. Can Studio or multi-company change the Odoo plan?

Yes. Odoo 20 documentation states that installing Studio or enabling multi-company on a Standard database can trigger an upsell to the Custom plan under the documented contract conditions.

10. How can Browseinfo help with Odoo 2027 pricing?

Browseinfo can help businesses assess user roles, plan requirements, Odoo.sh, integrations, customization, AI usage, implementation and ongoing support to build a more realistic Odoo TCO model.

Conclusion

Odoo 2027 pricing should not be reduced to a single number per user.

The actual cost depends on who needs access, what they need to do, which plan the business requires, where Odoo is hosted, how much customization is used, which IAP services are consumed and how the environment grows over time.

The introduction of Light Users creates an important opportunity for businesses to build a more precise access model. At the same time, Custom-plan requirements, Odoo.sh, Studio, multi-company, IAP, AI usage and custom-code maintenance need to be included in the broader TCO calculation.

For CFOs and IT leaders, the strongest approach is therefore to build a role-based, three-year Odoo cost model and validate every assumption against the applicable Odoo commercial proposal and contract.

The right Odoo investment is not necessarily the lowest subscription price.

It is the model that gives the organization predictable costs, appropriate access, sustainable technology architecture and measurable business value.