Odoo App Store: What to Install, Avoid, and Pay For

Navigating the Odoo App Store: What SMEs Should Install, Avoid, and Pay For

The Odoo App Store lists 40,000+ community apps, and Odoo markets it as the world's largest business apps store. That scale is the appeal and the problem. There is no mandatory code review before a module is listed, support falls to each module's author rather than Odoo S.A., and the wrong $50 module can quietly block your next major-version upgrade. This guide treats the Odoo App Store as a procurement decision, not an app drawer.

How the Odoo App Store actually works

The store is an open marketplace. Anyone with a publisher account can upload a module, and the only hard technical gate is a valid __manifest__.py containing a name, version, license, and dependency list. Odoo's own Vendor Guidelines do not require pre-publication inspection of the publisher's identity or the published code.

A few economics and rules worth knowing before you install anything:

Commission and price floor. Odoo S.A. takes a 30% commission on every app sale (25% on themes). The minimum price for a paid app is 9 EUR, and listings must be priced in EUR or USD (Vendor Guidelines).
Hosting restriction. Third-party modules that include Python files cannot be installed on Odoo Online (the SaaS tier). They run only on Odoo.sh (PaaS) or self-hosted/on-premise, and most buyers discover this after purchasing (Tatvamasilabs).
Per-version products. From Odoo v14 onward, each major version is sold as a separate product. Buying a module for v18 gives you no rights to the v19 version, and the seller is under no obligation to provide one (Tatvamasilabs).
Enterprise clones are prohibited. Odoo reserves the right to unpublish any module that duplicates Enterprise functionality (Vendor Guidelines).

For context on where the store sits in the platform: Odoo Community is the free open-source core, and Odoo Enterprise is the paid layer that adds proprietary modules, official bug fixes, upgrades, and support on top of that same core (Odoo Editions). App Store modules sit alongside both. For the full license and TCO picture, see our /learn/odoo-pricing hub; for what each core module actually does, see /learn/odoo-modules.

Quality signals — how to read an Odoo App Store listing

This is the part most buyers get wrong. Odoo's own ranking algorithm scores only five listing-quality criteria: has an icon, has a cover image, license is set in the manifest, rating ≥ 3, and an HTML description. Higher scores rank higher; ties break on best-seller status (Vendor Guidelines). None of those criteria measure code quality, business-logic safety, or upgrade compatibility. A polished page is not a safe module.

Use this table to translate what a listing actually tells you:

Ranking position — What it looks like: Top of search results · What it really tells you: Listing cosmetics scored well (icon, cover, HTML desc) · Type: Cosmetic
Star rating — What it looks like: 4.5+ stars · What it really tells you: Buyer sentiment, not code review · Type: Cosmetic
Downloads count — What it looks like: 500+ across versions · What it really tells you: Real adoption — a decent maintainability proxy · Type: Quality
Version coverage — What it looks like: Listed for v16, v17, v18 · What it really tells you: Author maintains across upgrades · Type: Quality
Last updated — What it looks like: Within 12 months · What it really tells you: Author is still active · Type: Quality
Author profile — What it looks like: 20+ modules, multi-version track record · What it really tells you: A real maintenance operation, not a side project · Type: Quality
Core models touched — What it looks like: sale.order, stock.picking, account.move in depends · What it really tells you: High upgrade-risk surface · Type: Risk
Forum mentions — What it looks like: Active threads, real issues answered · What it really tells you: Community is actually using and debugging it · Type: Quality

A practical evaluation baseline one certified Odoo partner surfaced from 80+ projects between 2019 and 2026: 500+ downloads across multiple versions, an author with 20+ maintained modules across versions, and a last-updated date within 12 months are reasonable signals of a maintainable module (Tatvamasilabs).

The safer first stop for standard needs is the OCA. The Odoo Community Association enforces peer review and strict contribution guidelines before modules are published, and its 250+ GitHub repositories are widely regarded as higher-quality than the average App Store listing (OCA on GitHub). For common needs — accounting localizations, common integrations, reporting — check OCA first, then the App Store.

Free vs paid Odoo apps — and the support reality

The historical split, using a 2018 baseline: roughly 76% of Odoo App Store apps were free and 24% paid (up from 15% paid at the start of 2017), with prices ranging from under 1 EUR to almost 8,000 EUR and about 12 new apps published per day (Unkkuri). The paid share has grown since, but the free tier is still enormous.

What no listing puts on the page is the support reality:

App Store apps are not covered by Odoo's official support or maintenance — free or paid. Under the Vendor Guidelines, support services are not required for free apps at all. For paid apps, the author — not Odoo S.A. — must resolve bugs, malfunctions, and config issues "in a timely fashion," enforced by Odoo only loosely through ratings (Vendor Guidelines).
The refund window closes two months after purchase. After that, even a module that breaks on your next upgrade has no recourse through Odoo (Vendor Guidelines).
Community discussion confirms the practical gap between the listed support commitment and what buyers actually receive (r/Odoo).

When free is the right call versus when paid earns its price:

Standard, cross-industry need — Niche or vertical integration (carriers, e-commerce, local payment gateways)
An OCA equivalent exists and is peer-reviewed — The author maintains 20+ modules across multiple Odoo versions
The module touches no core models — A support email and version roadmap are visible in the manifest/listing
You are prototyping and can afford to rip it out — The module replaces fragile custom code you would otherwise own
You run Odoo.sh or on-premise (Python files allowed) — You have confirmed it runs on your hosting tier before buying

For budgeting the broader rollout, see /learn/erp-implementation-cost; for SME platform context, see /learn/best-erp-for-small-business.

What to avoid on the Odoo App Store

One partner blog is blunt: after reviewing many apps, the majority do not follow proper coding standards, and many re-publish functionality that is now built into core Odoo each new release without checking (OdooExperts). The red flags below cover the failure patterns that actually bite in production.

It overrides core models — The signal: sale.order, stock.picking, account.move in depends/inherit · The downstream cost: Leading cause of upgrade failures — you block the next major version (Tatvamasilabs)
No version for your exact Odoo version — The signal: Listing only shows v16, you are on v18 · The downstream cost: You buy a dead product; repurchase required per major version
Last updated > 12 months ago — The signal: Stale manifest, no recent changelog · The downstream cost: Author has moved on; bugs will not be fixed
Single-module author — The signal: No track record across versions · The downstream cost: No reason to expect maintenance past your current version
Duplicates core functionality — The signal: Feature now exists in vanilla Odoo · The downstream cost: You pay for and maintain something you already own
Silent conflict risk — The signal: Two modules inherit the same model · The downstream cost: Last loaded wins, the other breaks with no error — Odoo does not mediate (Tatvamasilabs)
Bought for Odoo Online — The signal: Module ships Python files · The downstream cost: Will not install at all on SaaS — discovered post-purchase

Two deserve calling out because they are silent failures, not loud ones. Modules that override core models (sale.order, stock.picking, account.move) are the single leading cause of upgrade failures observed across 80+ projects (Tatvamasilabs). And when two third-party modules inherit the same model and write to the same field or method, the last one loaded wins and the other breaks silently — no exception is thrown, and Odoo does not mediate between vendors (Tatvamasilabs). You will find that one during month-end close, not during install.

When to buy, when to build, when to walk away

App Store apps are best suited for third-party integrations (carriers, e-commerce, payments), very specific edge cases, and fast prototyping — and should be avoided when an app overrides core logic with no clear benefit or is poorly documented (Much Consulting).

Buy when the need is standard and cross-industry, the module touches no core models, you are prototyping, and the author has a proven multi-version track record.
Build custom when the process is unique to your business, the logic touches sales, inventory, or accounting core models, you plan to upgrade within two years, or you need long-term maintained support that the App Store's two-month refund window and author-dependent support cannot guarantee.
Walk away when the module is poorly documented, hard to isolate or remove, or changes core logic with no clear benefit.

The partner red flag cuts both ways. A partner who never checks the App Store and builds everything from scratch is overcharging you. A partner who installs store modules blindly is putting your upgrade path at risk. A competent partner checks the store first, reviews the code-level footprint (which core models a module touches), and recommends custom development only when the store cannot reliably deliver (Much Consulting). Flectic's AI-Accelerated Delivery is designed to deliver that triage up to 3x faster on discovery and specification — never to skip it. We review, test, and validate App Store modules across Canada, the UK, and the US, and we build custom where the store cannot deliver.

For delivery methodology, see /learn/odoo-implementation; for a platform-neutral comparison, see /learn/odoo-vs-dynamics-365. For engagement models, see our /services/erp and /solutions/odoo pages, and the industries we serve at /industries.

Frequently asked questions

Is the Odoo App Store safe for production? Conditionally. There is no mandatory technical code review before listing (Vendor Guidelines), so safety depends entirely on your own due diligence — version coverage, author track record, and which core models the module touches. Treat every install as a procurement decision.

Are free Odoo App Store apps supported? No, not by Odoo. Under the Vendor Guidelines, support is not required for free apps at all. For paid apps, the author — not Odoo — is responsible for resolving bugs "in a timely fashion." Either way, App Store apps sit outside Odoo's official support and maintenance scope (Vendor Guidelines; r/Odoo).

Can I install Odoo App Store apps on Odoo Online? Only shell and theme modules. Anything that ships Python files requires Odoo.sh (PaaS) or self-hosted/on-premise — Odoo Online SaaS will not install it. Confirm this before buying, not after (Tatvamasilabs).

What happens to my App Store modules when I upgrade Odoo? From v14 onward, each major version is a separate product. You may need to repurchase the module for the new version, and data migration is a separate exercise. Modules that override core models (sale.order, stock.picking, account.move) are the most likely to break an upgrade (Tatvamasilabs).

How do I know if an Odoo app will conflict with my other modules? Check which core models each module inherits. If two modules inherit the same model and write to the same field or method, the last one loaded wins and the other breaks silently — no error is thrown, and Odoo does not mediate (Tatvamasilabs).

Should I use the Odoo App Store or the OCA? OCA first for standard needs. OCA modules are peer-reviewed on GitHub before publication and are widely regarded as higher-quality than the average App Store listing (OCA). Use the App Store for niche integrations and paid modules from authors with a proven multi-version track record.

Book an ERP Readiness Call. Flectic reviews, tests, and validates Odoo App Store modules — and builds custom where the store cannot deliver — across Canada, the UK, and the US. Our AI-Accelerated Delivery is designed to deliver up to 3x faster, never unconditionally.