Odoo Per-User Licensing: Reducing Cost Without Losing Function

Many Odoo bills carry people who left and staff who only log their leave. Our Odoo consulting services often start with an Odoo licensing audit, because the fix is usually a role change, not a new system.

This guide is for owners, CFOs and IT leads on Odoo Enterprise who want a lower bill without breaking daily work. If you need the Light User rules in full, read our Odoo 20 Light User guide first.

What counts as a paid user in Odoo licensing?

In Odoo licensing, a paid user is anyone who works in the Odoo backend, plus, from Odoo 20, any active employee record without a full login. Portal users and archived accounts cost nothing.

The Odoo pricing page defines a paying user as "someone who has access to the Odoo backend to create, view, or edit documents or an employee (record in hr application) who has no linked user."

Person in your database	How Odoo counts them
Login with any right outside the Light list	Full User
Login set to the Light role (Odoo 20)	Light User
Active employee record with no full login	Light User
Employee linked only to a portal login	Light User
Customer or supplier on the portal	Not counted
Archived user or archived employee	Not counted

The Odoo Enterprise Subscription Agreement (version 13) adds that Odoo's software reports your number of Users and Light Users to Odoo. So the count on your bill is the count in your database.

Full User, Light User, portal user or employee record: which does each person need?

Each person needs the lowest license that still covers their daily job, and the job decides it, not the title. Use this table as your first sort.

Role	Full User	Light User	Portal user
US price per month	US$31.10 Standard, US$61.00 Custom	US$8.90	Free
Sales, purchase, accounting	Yes	No	No
Approves leave or expenses	Yes	No, own requests only	No
Own time off, expenses, attendance	Yes	Yes	No
POS, barcode, shop floor	Yes	Yes	No
Edits records in Odoo	Yes	Own and front-line tasks only	No, read only

Odoo's pricing page lists Light User tasks: own time off, expenses, appraisals, attendance, referrals and planning, Field Service, barcode work and read-only Knowledge, plus payslips, Point of Sale and shop floor.

Three rules catch most teams:

• One extra right makes a full User: in Odoo 20 the role is recomputed when rights change, so Sales on "own documents" makes a full User.
• Approvers are full Users: a team lead who approves leave or expenses needs a full license.
• Light needs a quote: Odoo sells Light Users through an Odoo Advisor, and launch coverage says Light needs at least one full user.

How do you archive inactive users and employees without losing history?

Archive both the user and the employee record of everyone who has left, because archiving keeps their history and removes them from the count. Deleting is rarely needed and can break links to old documents.

Odoo's user docs explain how to deactivate (archive) users from Settings, Users, Manage Users, then Actions, Archive. The HR docs show how to archive an employee with a departure reason and end date.

Do both. If you archive only the login, the active employee record left behind is billed as a Light User under the Odoo 20 definition. If you archive only the employee, the login stays a full User.

Archiving does not shrink your contract by itself. On the Odoo forum, an answer to a customer who archived a departed staff member's account was clear: "There is no automatic adjustment" and users are reduced at renewal. Tell your Odoo account manager before the renewal date.

Why does sharing one Odoo login break the Enterprise agreement?

Sharing one login hides paying users, and on Odoo's cloud the agreement directly tells you not to share passwords. It also leaves you with no record of who did what.

Section 6.1 of the agreement asks cloud customers to keep accounts secure, "including by choosing a strong password and not sharing it with anyone else." On any hosting, each person with backend access is a paying user, so a shared login understates your count.

You must also "immediately notify Odoo SA" when Users or Light Users exceed your contract. Tampering with Odoo's usage check carries a fee of 300% of list price for the actual users.

In Odoo 20, sharing saves even less: each person still has an employee record, and those count as Light Users. You lose the audit trail and approval history for almost no saving.

Odoo Standard vs Custom plan: which one do you actually need?

Stay on Standard unless you need Studio, several companies, the external API, or Odoo.sh or on-premise hosting. Custom costs about twice as much per user, so the plan choice is often the biggest single lever.

Need	Standard	Custom
US price, billed yearly	US$31.10 per user	US$61.00 per user
All apps	Yes	Yes
Odoo Studio and agentic AI	No	Yes
Several companies in one database	No	Yes
External API	No	Yes
Hosting	Odoo Online	Online, Odoo.sh or on-premise

Odoo raised the Custom rate by about 20% with Odoo 20 and kept Standard unchanged, as reported by The Brussels Times. In India, Standard is Rs 725 and Custom Rs 1,350 per user a month billed yearly.

Watch the automatic switch: Odoo says installing Studio or adding companies will "automatically switch to the Custom plan." Calls Odoo makes to payment providers, carriers or bank feeds stay on Standard.

Our Odoo Studio vs custom development guide helps decide if Studio earns its place.

One App Free is the other option. It gives one app, with its dependent apps, to unlimited users at no cost, and it allows several companies or Studio as the chosen app. Install a second standalone app and you move to a paid plan.

Yearly vs monthly billing: how much does the billing choice cost?

Yearly billing costs about 20% less than monthly at list price, and new users get a first-year discount on top. Monthly billing only pays off if your headcount swings a lot.

Plan (US, per user a month)	First year, yearly	Yearly list	First year, monthly	Monthly list
Standard	US$24.90	US$31.10	US$31.10	US$38.90
Custom	US$49.00	US$61.00	US$61.10	US$76.20

Odoo says the discount is "valid for 12 months, for initial users ordered." Users added later pay list price, and your bill steps up in month 13.

Billing also changes how extra users land. Monthly plans update automatically, while yearly plans show a banner and an upsell quote, with 30 days to pay or archive users before the database expires.

What happens at renewal: the 7% rule and extra users at list price

At renewal, discounted prices can rise by up to 7% a year, and any users you added mid-term are charged at list price for the rest of the term. Both rules come from sections 5.1 and 5.2 of the agreement.

• Renewal increase: if your previous charges were below the current list price, they "will increase by up to 7% per year of the previous Term."
• Extra users: Users or Light Users above your contract are billed at the list price on the day you go over, until the term ends.
• Reductions: cutting users happens at renewal, so do the audit two to three months before the date.

How do you avoid the Odoo legacy surcharge?

Stay on one of the three most recent major versions, today Odoo 18, 19 and 20, and you pay no legacy surcharge. On an older version, Odoo adds 25% of your annualized price once a year.

The agreement charges the fee no earlier than six months after a new major version is released. It is calculated on your per-user price and your number of Users and Light Users, so a bloated user list makes it bigger. Our Odoo legacy surcharge guide covers dates and break-even math.

Clean the user list first, then plan the move with our Odoo upgrade services.

Worked example: a 40-person company before and after a license audit

In this illustrative example, a 40-person company on Custom cuts its yearly license cost by about half by archiving leavers and moving front-line staff to Light Users. All figures use US list prices billed yearly.

Before the audit, the company has 44 active full Users on Custom: its 40 staff plus 4 people who left. It needs Custom for an API link to its online store, so the plan stays.

Line (illustrative)	Before audit	After audit
Full Users on Custom at US$61.00	44	18
Light Users at US$8.90	0	22
Leavers (user and employee archived)	4 active	0
Monthly cost	US$2,684.00	US$1,293.80
Yearly cost	US$32,208.00	US$15,525.60
Yearly saving		US$16,682.40

The 18 full Users sell, buy, keep the books, approve leave or log project timesheets. The 22 Light Users are 10 shop-floor operators, 4 barcode pickers and 8 staff who only use time off, expenses and attendance.

Two warnings from the same example. Billed monthly, the 18 Custom users alone would cost US$3,283.20 more a year. Left on a non-covered version, the 25% legacy surcharge would add US$3,881.40 a year. For a full project number, try our Odoo project estimate tool.

What do you lose if you cut Odoo licenses too far?

Cutting too far moves cost into lost approvals, broken audit trails and surprise list-price bills. The aim is the right license per role, not the smallest count.

1. Approvals stop: a manager moved to Light can no longer approve leave or expenses for the team.
2. Rights get stripped: setting a role back to Light removes rights outside the Light list, so the person may lose access they relied on.
3. Portal is read only: Odoo's docs say portal users only have read access and cannot edit documents.
4. Studio work is at risk: dropping from Custom to Standard means no Studio, no multi-company and no external API.
5. True-ups cost more: if usage creeps back, extra users are billed at list price for the rest of the term.

Odoo license audit checklist

Run this Odoo licensing checklist two to three months before every renewal and after every restructure. Work from exports, not memory.

1. Export all active users with their access rights and last login date.
2. Export all active employee records and match each one to a login.
3. Archive the user and the employee record of everyone who has left.
4. Mark each remaining person as full User, Light User, portal user or employee record only.
5. Check every manager and approver keeps a full User.
6. Confirm the Custom plan is still needed: Studio, multi-company, external API or Odoo.sh.
7. Compare yearly and monthly billing for your real headcount pattern.
8. Check your version is one of the three most recent.
9. Ask your Odoo Advisor for a written Light User quote, then tell your account manager the new numbers.

Odoo licensing by industry

The best license mix depends on how many of your staff work on the front line versus in the back office. The table shows where we usually find savings.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Manufacturing	Shop-floor staff on full logins	Light Users on the shop floor	Map work centers to roles
Retail and eCommerce	Cashiers and pickers on full licenses	Light for POS and barcode, free shoppers	Split back office from store roles
Wholesale and distribution	Many warehouse logins	Light barcode operators	Review warehouse access rights
Professional services	Timesheets need full Users	Full Users for billable staff only	Check who logs billable time
Multi-company groups	Every full User at the Custom rate	Light Users for front-line staff	Confirm one database is really needed

Retailers gain most, since shoppers are free and cashiers can be Light. See Odoo ERP for retail, and our Odoo pricing guide for costs beyond licenses.

How iVentureTeam helps reduce Odoo licensing cost

iVentureTeam audits your users, roles, plan and contract, then makes the changes without breaking daily work. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• User and employee audit: every login and employee record mapped to full, Light, portal or archive.
• Role redesign: access rights rebuilt so Light Users stay Light and approvers keep full access.
• Plan review: a clear yes or no on Custom, with options from our Odoo Online vs Odoo.sh vs on-premise comparison.
• Renewal check: your quote checked against the agreement before you sign.
• Version plan: an upgrade path that avoids the legacy surcharge.

Odoo licensing case study: Indian grocery eCommerce retailer

An Indian grocery retailer runs its website, in-store POS, Android app and a commission-based agent network on one Odoo backend.

We delivered the project in 14 weeks. It covers Odoo eCommerce and Website, Point of Sale, Sales, CRM, and Accounting and Invoicing, with RazorPay serving both web and Android checkout.

Every order from web, store or app flows into the same inventory, invoicing and CRM records. A custom commission engine computes agent payouts and promotes agents automatically from live sales data, and the retailer changes levels and targets without code.

The license lesson for a model like this: online shoppers do not need users, so plan backend logins for the people who run the business, and check how external partners such as agents will access Odoo. Read the grocery eCommerce and channel commissions case study.

The bottom line on Odoo licensing

Pay for full Users only where people create, approve or manage, use Light Users for self-service and front-line work, and archive everyone who has left. Then check plan, billing term and version.

Audit before your renewal date, because reductions land at renewal and extras are billed at list price. Sharing logins or stripping rights costs more in lost control than it saves.

Ready to audit your Odoo licenses?

Find out which users, plan and terms you really need before your next renewal. Request an Odoo license and renewal review, call +91-90235-15208, or email business@iventureteam.com.