Odoo has revised its subscription terms so that certain employee records can fall within the Light User category. Version 13 of the Odoo Enterprise Subscription Agreement is dated 24 September 2026 and accompanies Odoo 20. Its definition covers designated user accounts and active employee records that meet specified conditions. (Odoo 20.0 Docs: Terms Enterprise)
This affects organisations that maintain employee records in Odoo without giving every employee an internal user account. A licence review must consider not only active non-portal accounts, but also the status of employee records and their links to those accounts. (Odoo 20.0 Docs: Terms Enterprise)
How Odoo defines a Light User
The agreement defines a Light User in two ways. The first is an active account designated as a Light User. The second is an active employee record that is not linked to an active non-portal user account. Meeting either condition brings the account or employee record within the definition. (Odoo 20.0 Docs: Terms Enterprise)
The wording makes both record status and account linkage relevant. The employee-record condition applies specifically to an active employee record and depends on whether it is linked to an active non-portal account. Employee and user data should therefore be reviewed together. (Odoo 20.0 Docs: Terms Enterprise)
Not every employee record is automatically a Light User under the supplied definition. The condition applies to active employee records that are not linked to active non-portal user accounts. Organisations should assess records against that wording rather than use the total number of employees stored in Odoo. (Odoo 20.0 Docs: Terms Enterprise)
What Light Users can access
Odoo’s pricing page lists Light User access for selected employee-facing and operational functions. These include selected HR self-service functions, Field Service, Inventory Barcode operations, read-only Knowledge access, Point of Sale and Manufacturing Shop Floor. (Pricing)
The category can therefore cover different types of work. An employee may use HR self-service, while an operational worker may need Barcode, Point of Sale or Manufacturing Shop Floor. Field Service is also listed, while Knowledge access is expressly limited to read-only use. (Pricing)
Light User status should not be treated as general access to every Odoo application. The pricing page identifies named capabilities, including an explicit restriction for Knowledge. Each role’s required tasks should be compared with this published scope before an account is designated as a Light User. (Pricing)
Published pricing varies by context
Odoo’s US pricing page lists Light User licensing at $8.90 per month. It also directs customers to contact an Odoo Advisor for a customised quote. The displayed amount is a published reference, but customer-specific pricing requires confirmation. (Pricing)
Odoo’s September announcement used European pricing and stated that Light User access would cost €7.90 per employee. The announcement also said Standard plan pricing would remain unchanged and Custom plan pricing would increase by 20%. These figures apply to their stated pricing contexts and do not establish a single worldwide rate. (Odoo Takes Stock Of 2026 And Unveils Its Ambitions For 2027 During Odoo Experience)
The supplied material does not provide an Australian Light User price. Australian organisations should confirm the regional terms, currency and quote that apply to their subscriptions. Converting the published US or European amount would not establish the price Odoo will quote to an Australian customer. (Odoo Takes Stock Of 2026 And Unveils Its Ambitions For 2027 During Odoo Experience; Pricing)
Standard and Custom plan implications
The announced treatment differs between the two core plans. Odoo said Standard plan pricing would remain unchanged, while Custom plan pricing would rise by 20%. European Light User pricing was announced separately at €7.90 per employee. (Odoo Takes Stock Of 2026 And Unveils Its Ambitions For 2027 During Odoo Experience)
Budget reviews should separate three questions: whether the subscription uses the Standard or Custom plan, how many records or accounts meet the Light User definition, and which regional Light User rate applies. Reviewing only the underlying plan price would not account for the employee-record element of the definition. (Odoo Takes Stock Of 2026 And Unveils Its Ambitions For 2027 During Odoo Experience; Odoo 20.0 Docs: Terms Enterprise)
For Custom plan customers, the announced 20% increase and Light User licensing are separate considerations. For Standard plan customers, unchanged plan pricing does not remove the need to assess active employee records. The supplied materials address plan pricing and Light User treatment as distinct parts of the revised terms. (Odoo Takes Stock Of 2026 And Unveils Its Ambitions For 2027 During Odoo Experience; Odoo 20.0 Docs: Terms Enterprise)
Review employee records and user accounts
A review can begin with all active employee records. For each record, administrators should check whether it is linked to an active non-portal user account. Active employee records without that link fall within the employee-record branch of the Light User definition. (Odoo 20.0 Docs: Terms Enterprise)
The review should separately identify active accounts already designated as Light Users. Those accounts meet the other branch of the definition independently of the employee-record condition. Keeping the two groups distinct helps preserve the two-part test used in the agreement. (Odoo 20.0 Docs: Terms Enterprise)
Organisations should then compare each role’s actual duties with the listed Light User functions. HR self-service, Field Service, Barcode, read-only Knowledge, Point of Sale and Manufacturing Shop Floor may cover particular roles, but each task performed in Odoo should be checked against the published scope. (Pricing)
Questions to confirm before renewal
Pricing requires direct confirmation. The available information does not specify an Australian Light User amount, and Odoo’s US pricing page directs customers to seek a customised quote. Organisations should confirm the applicable currency, regional rate and renewal treatment rather than budget solely from the US or European figures. (Odoo Takes Stock Of 2026 And Unveils Its Ambitions For 2027 During Odoo Experience; Pricing)
Account and record classifications also need to be checked in the organisation’s database. The agreement distinguishes active accounts, active employee records and active non-portal user accounts. The relevant statuses, links and Light User designations should be verified before the licence count is finalised. (Odoo 20.0 Docs: Terms Enterprise)
Each proposed Light User role should also be tested against the access described on Odoo’s pricing page. Knowledge is limited to read-only access, while the other capabilities are tied to named functions. If a role requires work outside that scope, the organisation should clarify the appropriate licensing as part of its quote. (Pricing)
Preparing for renewal
Before renewal, organisations should reconcile active employee records with active non-portal accounts, identify accounts designated as Light Users and map intended access to the listed functions. They can then request pricing based on their region, plan and resulting Light User count. (Odoo 20.0 Docs: Terms Enterprise; Pricing)
The change extends beyond a restricted account type because the agreement also includes qualifying active employee records. The remaining organisation-specific questions are the applicable regional quote, the count produced by the definition and whether each employee’s required work fits within the published Light User capabilities. (Odoo 20.0 Docs: Terms Enterprise; Pricing)