Every Odoo module declares a license in its manifest. Two values cover almost everything you will meet on the Odoo Apps Store: LGPL-3 and OPL-1. They lead to genuinely different rights, and the difference is worth understanding before you standardise on a module.
Where the licence is declared
It sits in __manifest__.py, next to the version and the author:
{
'name': 'My Module',
'version': '19.0.1.0.0',
'license': 'OPL-1',
}Odoo itself is dual-licensed: the Community edition is LGPL-3, and the Enterprise edition is covered by the Odoo Enterprise Edition Licence. Modules published on the Apps Store choose their own.
LGPL-3 in practice
LGPL-3 is a free software licence. In broad terms it allows you to use, modify and redistribute the module, including in a commercial context, provided you keep the licence attached and make modifications to the LGPL code available under the same terms.
For an Odoo user this usually means: install it on as many databases as you want, fork it, adapt it, and keep your adaptations as long as you respect the licence obligations on the LGPL parts themselves.
OPL-1 in practice
OPL-1 is the Odoo Proprietary Licence. It is the standard licence for paid modules on the Apps Store. It grants the purchaser the right to use and modify the module for their own purposes, but it does not grant the right to redistribute or resell it.
The practical consequences buyers care about are the number of databases covered, whether a partner may deploy it for a client, and what happens when you fork it. These are answered by the licence text and by the purchase terms, not by convention — read them rather than assuming.
Why paid modules are usually OPL-1
Because LGPL-3 permits redistribution, a paid LGPL module can lawfully be passed on by any purchaser. Authors who need to sustain paid development therefore tend to choose OPL-1, which is why most commercial Apps Store listings carry it.
This is not a judgement about quality. Plenty of excellent modules are LGPL-3, and some authors deliberately release paid work under it.
What this means for our modules
Most of our modules are published under OPL-1. Two are LGPL-3: Theme OpenC and Payment Paie Privacy. Each article in the catalogue states the licence in its compatibility table.
A note on what this article is not
This is a practical orientation for Odoo users, not legal advice. Licence terms are the authoritative source, and if a deployment scenario involves real money or real risk — a partner deploying across many client databases, for instance — the licence text and a lawyer beat a blog post.
Next steps
The licence of every module we publish is listed on its product page and in its documentation article. Ask us if your deployment scenario is unusual.
Frequently asked questions
What is the difference between LGPL-3 and OPL-1 in one sentence?
LGPL-3 lets you redistribute the module; OPL-1 lets you use and modify it for your own purposes but not redistribute or resell it.
Can I modify a module I bought under OPL-1?
OPL-1 permits modification for your own use. What it restricts is redistribution. Check the licence text for the exact scope, particularly around the number of databases covered.
Is Odoo Community LGPL?
Yes, the Odoo Community edition is released under LGPL-3. The Enterprise edition is covered by a separate proprietary licence.
Where do I find a module's licence?
In the license key of its __manifest__.py, and on its Apps Store or shop listing.
Is this legal advice?
No. It is a practical orientation for Odoo users. The licence text is authoritative, and unusual deployment scenarios deserve proper legal review.