Odoo Apps: The 10-15 an SME Actually Uses

Odoo Apps: The 10-15 an SME Actually Uses (Not All 40,000)

Search "odoo apps" and you land in one of two places: Odoo's own All Apps page listing its official applications inside eight categories, or an App Store that ballooned past 40,000 listings — surrounded by "Top 10 Odoo apps" listicles from Odoo-only partners that all recommend the same ten. Neither is genuinely curated for a small or medium business. Flectic implements both Odoo and Microsoft Dynamics 365 for SMEs across Canada, the UK, and the US, so we have no incentive to oversell Odoo apps. Here is the opinionated tour — which 10 to 15 Odoo apps your SME should run, what each silently pulls in through the dependency chain, what to leave switched off, and where the Enterprise-versus-Community line actually falls.

If you want the full technical reference on module mechanics and the dependency map, see /learn/odoo-modules. This post is the SME buyer's tour that sits on top of it.

How many Odoo apps are there, really? (~50 vs Enterprise vs 40,000)

Three numbers travel together in Odoo marketing, and conflating them is the first mistake buyers make.

• The official main applications — the apps Odoo itself develops and lists on its All Apps page, organised into eight categories: Website, Sales, Finance, Inventory & Manufacturing, Human Resources, Marketing, Services, and Productivity.
• Enterprise-exclusive apps — the main set plus apps only available on Enterprise (Studio, Helpdesk, Sign, VoIP, IoT, Quality, PLM, Subscriptions, and others), all bundled at one per-user price.
• 40,000+ in the App Store — community- and partner-built modules. Odoo first claimed the "world's largest business apps store" title at 10,000 listings, then larger than Salesforce AppExchange at roughly 2,800; the store has roughly quadrupled since.

The 40,000 figure is the misleading one. Only a fraction are maintained for the current Odoo version, many duplicate each other, and the ones a typical SME actually wants overlap almost completely with the official main apps. A useful mental model: all apps are modules, but only modules declaring application: True in their __manifest__.py show up as installable apps in the Odoo Apps dashboard. Most of the 40,000 are modules (extensions, bridges, connectors), not standalone apps.

The practical takeaway for an SME: ignore the 40,000. Your shortlist lives inside the official main apps, and the large majority of SMEs run a subset of roughly 10 to 15 of them.

The 10 Odoo apps almost every SME needs (the foundation set)

This is the foundation. Regardless of whether you sell services, physical goods, or manufactured products, these ten cover finance, sales, and the operational backbone almost every SME shares.

• **CRM** — What it does: Pipeline, leads, opportunities · Who needs it: Every business that sells · Auto-installs with it: sales_team, mail
• **Sales** — What it does: Quotes, orders, customer contracts · Who needs it: Any business that invoices · Auto-installs with it: sales_team, product
• **Invoicing / Accounting** — What it does: Customer invoices, bills, ledger, reporting · Who needs it: Every business (Accounting is Enterprise; Invoicing is the Community entry point) · Auto-installs with it: account depends on product, analytic
• **Inventory** — What it does: Warehouses, stock moves, routing · Who needs it: Any business handling physical goods · Auto-installs with it: stock depends on product
• **Purchase — What it does: Purchase orders, vendor bills, reordering · Who needs it: Any business buying physical inputs · Auto-installs with it: **Both stock and account
• **Manufacturing (MRP)** — What it does: Bills of materials, production orders · Who needs it: Any business that transforms inputs · Auto-installs with it: mrp depends on stock, product
• **Project** — What it does: Tasks, milestones, project accounting · Who needs it: Services firms, internal ops · Auto-installs with it: project
• **Timesheets** — What it does: Time tracking on tasks/projects · Who needs it: Services firms billing time · Auto-installs with it: hr_timesheet
• **Expenses** — What it does: Employee expense reports, reimbursement · Who needs it: Any business with employees · Auto-installs with it: hr_expense
• **Website** — What it does: CMS, landing pages, SEO foundations · Who needs it: Any business with a web presence · Auto-installs with it: website

Two notes worth flagging. First, Purchase is heavier than it looks: it requires both Inventory and Accounting, so installing it drags the full procure-to-pay chain in with it. Second, Sales alone does not pull in Inventory — a pure services business can run CRM + Sales + Invoicing and never touch stock. That distinction is the single most useful thing to know before you start clicking Install.

The SME consensus on this set is remarkably consistent across the Odoo forum and r/Odoo: start with CRM, Sales, and Accounting; add Inventory if you sell physical goods, Project if you sell services; layer Website and eCommerce only once you are established.

Apps 11-15 — pick by business model (the persona set)

On top of the foundation ten, add three to five apps based on how your business actually makes money.

Services / professional services

• Project + Timesheets + Expenses + Subscriptions (Enterprise, for retainer and recurring billing).
• These feed Accounting for project costing and P&L. Odoo Timesheets automates time capture so billable hours do not leak between billing cycles. See /services/erp for how we scope a services-industry rollout.

Trader / distributor / retail

• Point of Sale + eCommerce + Subscriptions.
• POS and eCommerce share the same product and stock backbone, so an order taken in-store, online, or by a sales rep lands in one inventory and one ledger. See /solutions/odoo.

Maker / manufacturer

• Manufacturing (MRP) + Quality + Maintenance + PLM (all Enterprise except base MRP).
• Per Odoo's manufacturing documentation, MRP is fully integrated with Inventory and Purchase — manufacturing orders trigger stock moves, reorder rules generate purchase requisitions, and costs flow into Accounting automatically. See /industries/manufacturing.

The dependency chain — why "one click" installs five apps

This is the most under-explained fact on the "odoo apps" SERP, and it is the one that catches buyers by surprise.

Every Odoo module declares its dependencies in the depends key of __manifest__.py. When you install a module, Odoo recursively installs every dependency first — you do not get a choice. On top of explicit dependencies, Odoo ships bridge modules with an auto_install flag: install two apps that a bridge connects (for example sale and stock) and the bridge module sale_stock installs itself automatically. The same happens with sale_purchase.

The four-line version an SME buyer can act on:

1. Sales is light. It depends on sales_team and product — no Inventory. A services firm can sell without ever opening a warehouse.
2. Purchase is heavy. It needs both Inventory and Invoicing, so it activates the full procurement chain.
3. Bridges auto-install. Once two related apps are present, Odoo wires them together without asking.
4. Plan the install order. Install foundation apps first (CRM, Sales, Invoicing), then persona apps, so you can see exactly what each new app drags in.

For the full dependency map, the __manifest__.py mechanics, and every bridge module, see /learn/odoo-modules.

Odoo Studio — the Enterprise wildcard that can replace a custom module

Odoo Studio is the no-code / low-code customization tool bundled only with Odoo Enterprise. It lets authorised users create custom fields, redesign views (kanban, list, form, pivot, graph), tailor PDF reports, automate simple workflows, and build small in-house apps — without writing Python.

Studio is one of the most common reasons SMEs move from Community to Enterprise. It genuinely covers a lot of configuration-level ground: custom fields, tailored views, bespoke reports, and light workflow automation that would otherwise need a developer.

It has an honest limit, though. Studio handles configuration-level customization well — but the moment you need logic that genuinely belongs in a computed field or a server action, you need a Python developer. Studio customizations also may not appear on the Odoo mobile app, which uses separate web and mobile views. Treat Studio as a way to defer (not replace) custom development: it buys you months or years of no-code agility until you hit a real logic wall.

Community vs Enterprise — which apps you lose by staying free

Odoo Community is free, open-source under LGPLv3, and self-hosted. Odoo Enterprise is a subscription built on top of Community that adds official support, managed hosting, automated upgrades, and a set of Enterprise-exclusive apps. Every Community app is also in Enterprise; the gap is one-directional.

• **Studio** — No-code fields, views, reports, mini-apps
• **Accounting / Invoicing (full)** — Full ledger, reporting, multi-company, fiscal localisation
• **Helpdesk** — Ticketing, SLAs, customer service
• **Sign** — E-signature on quotes, contracts, HR docs
• **VoIP** — Softphone inside the CRM
• **IoT** — Connect scales, printers, cameras, payment terminals
• **Barcode (advanced)** — Mobile barcode workflows for picking/receiving
• **Quality** — Quality control points on production and receipts
• **Maintenance (advanced)** — Equipment maintenance and preventive scheduling
• **PLM** — Engineering change management for manufacturers
• **Subscriptions** — Recurring billing and subscription management
• **Approvals** — Configurable approval flows
• **Dashboards** — Cross-app KPI dashboards
• **Timesheets (full)** — Enterprise Timesheets with reporting

The Community fallback is the Odoo Community Association (OCA), which maintains thousands of free LGPL-3 / AGPL-3 modules that fill many of these gaps. The trade-off: OCA modules are community-supported (no vendor SLA) and require self-hosting on Community or Odoo.sh. For the pricing comparison between the two editions and the Odoo.sh hosting cost, see /learn/odoo-pricing.

The Odoo Online constraint — why some apps force you onto Odoo.sh

Almost no "odoo apps" SERP page states this rule plainly, and it determines which apps you can even run.

Importable modules on Odoo Online (the SaaS offering) cannot include Python files — only data files, views, and JavaScript. Any third-party App Store app or custom module that contains Python code requires self-hosted Community, self-hosted Enterprise, or Odoo.sh. The Odoo Apps Store FAQ confirms the same constraint for third-party apps: they cannot be installed on Odoo Online unless they are data-only.

The practical impact is real and easy to underestimate. If your "must-have" list includes any code-bearing third-party app — a payment-gateway localisation, a carrier integration, a custom workflow module — budget for Odoo.sh hosting from day one, not after launch. Discovering the constraint post-contract forces an expensive mid-project migration. We flag this during discovery specifically because it changes both the hosting line item and the implementation timeline.

The over-installation trap — what partner blogs will not tell you

The deepest insight the SERP almost never states: on Enterprise's all-apps-included per-user pricing, every app you switch on is "free" in licence terms but "expensive" in three other currencies.

1. Performance. Every installed module loads its code, hooks, and computed fields into each request. More modules means more RAM and CPU consumed across the whole database, not just on the screens that use them.
2. Upgrade breakage. Each custom or third-party module must be re-validated against every new Odoo version. Odoo 19 was released on 18 September 2025 at Odoo Experience 2025 — and every version bump is a re-test event for non-official modules. The more you have installed, the more breaks.
3. Data lock-in. Uninstalling a module that has accumulated data is risky and often incomplete, so "just try it" modules tend to stay installed for years even after everyone has stopped using them.

The remedy is the opposite of what most partner blogs imply: install the 10 to 15 essentials, run them for two to three months, and add more only on a documented need. The right number is the smallest set that runs your business — not "as many as possible." Over-installation is a documented implementation pitfall, and it is the one we explicitly design against during scoping.

For a neutral point of comparison: Dynamics 365 Business Central is priced per module tier (Essentials, Premium, Team Members) rather than all-apps-included. The two platforms make the cost of over-installation visible in very different ways: Odoo hides it in performance load, Business Central hides it in licence tiering. See /learn/odoo-vs-dynamics-365 for the full side-by-side.

How Flectic helps you pick the right Odoo apps (and leave the rest)

Because we implement both Odoo and Dynamics 365 for SMEs across Canada, the UK, and the US, we have no incentive to oversell Odoo apps — fewer apps well-configured beats many apps half-configured every time.

• Platform-neutral scoping. We start from your workflows and recommend the platform (Odoo or Business Central) and the app set that fits, not the one that bills more hours. See /services/erp and /solutions/odoo.
• AI-Accelerated Delivery Framework. Our delivery methodology is designed to deliver up to 3x faster than traditional ERP implementation — never as an unconditional guarantee. AI assists discovery, documentation, QA, and training; expert consultants stay accountable for the outcome.
• Phased scope. Foundation ten first, persona apps second, everything else only on documented need — so you avoid the configuration debt that buries most SME rollouts.
• Lifecycle support after go-live. Go-live is the beginning of value, not the end of the project. We support adoption, optimisation, and the version upgrades that will inevitably come.

If you are weighing Odoo against Business Central specifically, start with /learn/odoo-vs-dynamics-365. If you are further along and ready to scope, /learn/erp-implementation covers our delivery lifecycle end to end.

Book an ERP Readiness Call

Get a platform-neutral app shortlist from a partner that implements both Odoo and Dynamics 365. We map the 10 to 15 apps your SME actually needs, trace what each pulls in through the dependency chain, flag whether you need Odoo.sh or can stay on Odoo Online, and tell you what to leave off — even if the honest answer is fewer apps than you planned for.

Book an ERP Readiness Call →