Odoo Apps: Core Modules, Process Map & SME Shortlist

What are Odoo apps?

Odoo apps are modular business applications on one shared database — CRM, Sales, Inventory, Accounting, Manufacturing, Website, HR, and dozens more — that you install only as needed. Official main apps live on Odoo’s All Apps catalog (roughly 50–80 productized apps across Website, Sales, Finance, Inventory & Manufacturing, HR, Marketing, Services, and Productivity). Enterprise bundles those official apps at one per-user price. The separate Odoo Apps Store holds 40,000+ third-party modules; most SMEs never need more than a curated 10–15 official apps.

This guide is the functional catalog for buyers: which Odoo apps map to which business process, which 10–15 an SME should run, what third-party apps are for (and the upgrade risk), how Community vs Enterprise licensing works, and starter packs by industry. For procurement rules on marketplace modules — quality checks, OCA vs App Store, what to avoid — use our companion post on the Odoo App Store. For technical dependency mechanics, see /learn/odoo-modules.

Flectic implements both Odoo and Microsoft Dynamics 365 for SMEs across Canada, the UK, and the US, so the shortlist below is platform-honest: install the smallest set that runs the business, not every tile in the Apps dashboard.

How many Odoo apps are there, really?

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

• Official main applications — apps Odoo develops and lists on All Apps: Website, eCommerce, CRM, Sales, Point of Sale, Accounting, Inventory, Manufacturing, Purchase, Project, HR, Marketing suite, Helpdesk, Studio, AI, and more.
• Enterprise-exclusive apps — the main set plus apps only on Enterprise (Studio, full Accounting depth, Helpdesk, Sign, VoIP, IoT, Quality, PLM, Subscriptions, Approvals, advanced Barcode, and others), all included in the Enterprise user subscription rather than priced per module.
• 40,000+ App Store listings — community- and partner-built modules. Odoo once claimed the “world’s largest business apps store” at 10,000 listings; the store has roughly quadrupled since. Only a fraction stay maintained for the current major version (Odoo 19 shipped September 2025).

A useful mental model: all apps are modules, but only modules with application: True in __manifest__.py show as installable apps in the dashboard. Most of the 40,000 are extensions, bridges, and connectors — not standalone business apps. For an SME, ignore the 40,000 as a shopping list. Your shortlist lives inside the official catalog.

Odoo’s own Apps and modules documentation is blunt about side effects: installing apps can pull dependencies, change subscription cost, and uninstalling apps deletes related database records. Test on a staging duplicate before production installs or uninstalls.

Odoo apps mapped to business processes (outcomes, not module names)

Search intent for “odoo apps” and “odoo application” is process-shaped. Map apps to the work they finish.

Quote-to-cash

• CRM — capture leads, score pipeline, log activity; outcome: a forecastable pipeline instead of a spreadsheet of names.
• Sales — quotations, sales orders, pricelists; outcome: one commercial document that can become delivery and invoice without retyping.
• Subscriptions (Enterprise) — recurring revenue, renewals; outcome: retainers and SaaS-style billing without a second billing tool.
• Invoicing / Accounting — customer invoices, payments, bank reconciliation; outcome: cash collection tied to the same customer record as CRM.
• Point of Sale — in-store or restaurant checkout; outcome: retail tickets that hit the same inventory and ledger as B2B sales.
• eCommerce + Website — online catalog and checkout; outcome: web orders that reserve stock and create the same sales documents as a sales rep. Deeper Website mechanics live in our Odoo Website guide.

Procure-to-pay

• Purchase — RFQs, purchase orders, vendor agreements; outcome: approved buying that lands as receipts and vendor bills.
• Inventory — multi-warehouse stock, routes, valuation; outcome: known on-hand quantity and landed cost. See Odoo Inventory.
• Accounting — vendor bills, payment runs, AP aging; outcome: liabilities and cash out tied to receipts.

Plan-to-produce (makers)

• Manufacturing (MRP) — BOMs, manufacturing orders, work centers; outcome: production orders that consume components and produce finished goods into stock.
• PLM (Enterprise) — engineering changes, versioned BOMs; outcome: controlled product changes without “which Excel BOM is real?”
• Quality (Enterprise) — control points on receipt and production; outcome: blocked bad lots before they ship.
• Maintenance — equipment, preventive work orders; outcome: fewer surprise line stops.

Project-to-cash (services)

• Project — tasks, milestones, profitability; outcome: delivery plan tied to sold scope.
• Timesheets — time on tasks and projects; outcome: billable hours that do not leak between periods.
• Expenses — employee spend and reimbursement; outcome: project and GL cost without a separate T&E silo.
• Helpdesk (Enterprise) — tickets, SLAs; outcome: support load visible next to the same customer as Sales.

Hire-to-retire and go-to-market

• Employees, Recruitment, Time Off, Appraisals — people master data and lifecycle; outcome: one employee record for leave, expense, and timesheet.
• Email / SMS / Social Marketing, Marketing Automation, Events, Survey — campaigns and nurture; outcome: marketing activity on the same partner records as CRM.
• Discuss, Knowledge, Approvals, Sign, Documents, Spreadsheets — collaboration and control; outcome: approvals and signed contracts without a second document stack.
• AI (current official Productivity app) — assistants and agents inside Odoo apps; outcome: draft and Q&A against live company data, not a disconnected chatbot.

End-to-end example (goods)

Lead enters CRM → quote in Sales → confirmed order reserves stock in Inventory → if make-to-order, Manufacturing produces → delivery confirms → Accounting invoices and reconciles payment. No CSV handoffs. That single flow is why “all apps one database” beats bolting five SaaS tools together — when the apps you install are the right few.

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

Regardless of services, distribution, or light manufacturing, these ten cover commercial, financial, and operational backbone.

• CRM — Pipeline, leads, opportunities · Every business that sells · Pulls sales_team, mail
• Sales — Quotes, orders, contracts · Any business that invoices · Pulls sales_team, product
• Invoicing / Accounting — Invoices, bills, ledger · Every business (full Accounting depth is the Enterprise path; Community starts with Invoicing) · account depends on product, analytic
• Inventory — Warehouses, moves, routing · Any physical goods · stock depends on product
• Purchase — POs, vendor bills, reordering · Any buyer of inputs · Requires both Inventory and Accounting
• Manufacturing (MRP) — BOMs, production orders · Any transformer of inputs · mrp depends on stock, product
• Project — Tasks, milestones, project cost · Services and internal ops · project
• Timesheets — Time on tasks · Services billing time · hr_timesheet
• Expenses — Employee expense reports · Any employer · hr_expense
• Website — CMS, landing pages, SEO foundations · Any web presence · website

Two facts that prevent expensive mistakes:

1. Purchase is heavier than it looks — it activates the full procure-to-pay chain (Inventory + Accounting).
2. Sales alone does not pull Inventory — a pure services firm can run CRM + Sales + Invoicing and never open a warehouse.

Forum and practitioner consensus is stable: start with CRM, Sales, and Accounting; add Inventory if you move goods; Project if you sell services; layer Website and eCommerce once the core is stable (Odoo forum, r/Odoo).

Apps 11–15 and industry starter packs

On top of the foundation, add three to five apps by how you make money — not by how many tiles look useful.

Services / professional services

• Project + Timesheets + Expenses + Subscriptions (Enterprise for retainers).
• Optional: Helpdesk for post-sale support, Planning for resource schedules.
• Outcome: project P&L and billable utilization without a separate PSA tool. Scope patterns: /services/erp.

Trader / distributor / retail

• Point of Sale + eCommerce + (often) Subscriptions for replenishment programs.
• POS and eCommerce share product and stock, so store, web, and B2B orders hit one inventory and one ledger. Platform overview: /solutions/odoo.

Maker / manufacturer

• Manufacturing + Quality + Maintenance + PLM (base MRP is available more broadly; Quality, PLM, and advanced ops features lean Enterprise).
• Per Odoo’s manufacturing documentation, MRP integrates with Inventory and Purchase: manufacturing orders drive stock moves, reorder rules drive purchase requisitions, costs flow to Accounting. Industry lens: /industries/manufacturing.

Field and hybrid

• Field Service + Helpdesk + Inventory (parts) + Timesheets.
• Outcome: on-site work, spare parts, and billing on one customer timeline.

Rule of thumb: name the industry pack after the process you must run in week one of go-live, not after aspirational analytics. Phased scope beats a 25-app day-one wishlist.

The dependency chain — why one click installs five apps

Every module lists dependencies in __manifest__.py. Install one app and Odoo recursively installs required parents. Bridge modules with auto_install wire two apps together without asking — for example, once Sales and Inventory are both present, sale_stock appears; similar bridges exist for sale–purchase flows.

What buyers need to remember:

1. Sales is light — no Inventory required. Services firms can sell without warehouses.
2. Purchase is heavy — Inventory + Invoicing come along.
3. Bridges auto-install — related apps get wired when both exist.
4. Install order is a design decision — foundation first (CRM, Sales, Invoicing), then persona apps, so each Activate is auditable on staging.

Official docs warn that uninstalling an app can uninstall dependents and delete records (Apps and modules). Full dependency map: /learn/odoo-modules.

Third-party Odoo apps: when they help, governance, upgrade risk

Queries like “odoo third party apps” deserve a clear answer here, without duplicating the full App Store buyer’s guide.

When third-party apps are useful

• Country-specific localization Odoo does not ship for your edition or host.
• Carrier, marketplace, or bank connectors your market requires (Shopify, regional carriers, local payment rails).
• Narrow vertical packs (hotel, salon, niche compliance) when standard apps would need months of custom work.
• Peer-reviewed community modules for standard gaps — start with the Odoo Community Association (OCA) before paid marketplace one-offs.

When to refuse them

• The official app already covers 80% of the need (prefer Studio configuration or process change).
• The module overrides core models heavily — upgrade blockers are common (third-party compatibility audits flag App Store modules as higher risk than OCA branches).
• The author has no track record on the last two major Odoo versions.
• You are on Odoo Online (SaaS) and the module includes Python — per the Apps Store FAQ, third-party apps with Python cannot run on Odoo Online; they need Odoo.sh or on-premise. Data-only modules are the exception.

Governance checklist (before production)

• Staging install and full process test (sales, stock, invoice).
• Named owner for upgrade on each major Odoo release (19 → next).
• Written exit plan: can you uninstall without losing critical history?
• Prefer OCA or multi-version commercial authors over anonymous $30 listings.

Deep procurement criteria, red flags, and OCA-first policy: Odoo App Store guide. This page stays the functional “which official apps”; that page is the marketplace “whether to buy a module.”

Licensing: Community, Enterprise, and which apps need which

Odoo Community is free, open-source (LGPLv3), self-hosted. Odoo Enterprise is a paid subscription on top of Community: official support options, hosting paths (including Odoo Online / Odoo.sh), automated upgrade tooling, and Enterprise-only apps. Every Community app is in Enterprise; the gap is one-directional.

Enterprise-only (or Enterprise-strong) apps SMEs care about most:

• Studio — no-code fields, views, reports, light apps
• Accounting (full) — deeper multi-company, localization, and reporting path vs Community Invoicing
• Helpdesk, Sign, VoIP, IoT
• Quality, PLM, advanced Maintenance / Barcode
• Subscriptions, Approvals, cross-app Dashboards
• Advanced Timesheets reporting

Enterprise’s commercial story is all official apps included per user, not à la carte module SKUs. That hides licence cost of over-installation and shifts the real cost into performance, training, and upgrade work (see next section). Community + OCA can replace some Enterprise gaps at the price of self-hosting and community support SLAs. Pricing and edition math: /learn/odoo-pricing.

Hosting constraint that decides third-party strategy

• Odoo Online — official apps + Studio-level customization; no Python third-party modules.
• Odoo.sh / on-premise Enterprise or Community — full third-party and custom Python addons.

If your must-have list includes code-bearing marketplace modules, budget Odoo.sh (or self-host) from day one. Discovering that after contract is a mid-project migration, not a checkbox.

Odoo Studio — Enterprise flexibility without a custom module (until it is not)

Studio is the no-code / low-code layer on Enterprise: custom fields, redesigned views (kanban, list, form, pivot, graph), PDF report tweaks, simple automations, and small in-house apps without Python.

Use Studio for configuration-level fit. Escalate to a developer when you need real computed business logic, complex multi-model workflows, or integrations that belong in a proper module. Studio customizations can lag mobile views. Treat Studio as defer custom development, not eliminate it — months of agility until you hit a logic wall that belongs in version-controlled code.

The over-installation trap

On Enterprise’s all-apps-included pricing, every Activate is “free” on the invoice and expensive in three other currencies.

1. Performance — each module loads code, hooks, and computed fields into the database workload, not only on screens that use it.
2. Upgrade breakage — every custom or third-party module must be re-validated on each major version. Odoo 19 landed 18 September 2025; each bump is a re-test event for non-official code.
3. Data lock-in — uninstall deletes related records (per official docs). “Just try it” modules tend to stay forever.

Remedy: install the 10–15 essentials, run them two to three months, add only on documented need. Over-installation is a known implementation pitfall. Dynamics 365 Business Central prices by module tier (Essentials, Premium) so over-scope shows up on the licence line; Odoo shows it in ops load. Side-by-side: /learn/odoo-vs-dynamics-365.

How Flectic helps you pick the right Odoo apps

We implement both Odoo and Dynamics 365, so we are not paid to install every Odoo tile.

• Platform-neutral scoping — workflows first, then platform and app set. /services/erp, /solutions/odoo.
• AI-Accelerated Delivery Framework — up to 3× faster than traditional ERP implementation as a design target, never an unconditional guarantee; consultants remain accountable.
• Phased app scope — foundation ten, then persona pack, then exceptions only with owners and upgrade plans.
• Lifecycle after go-live — adoption, optimisation, and version upgrades for official and third-party modules.

If you are still choosing platform, start with /learn/odoo-vs-dynamics-365. Delivery lifecycle: /learn/erp-implementation.

Book an ERP Readiness Call

Get a platform-neutral app shortlist from a partner that implements Odoo and Dynamics 365. We map the 10–15 apps your SME needs, trace dependencies, flag Odoo Online vs Odoo.sh for third-party plans, and tell you what to leave off — even when that means fewer apps than the brochure.

Book an ERP Readiness Call →

FAQ: Odoo apps

What are Odoo apps?

Odoo apps are modular applications (CRM, Sales, Inventory, Accounting, Manufacturing, Website, HR, and more) that share one database and can be installed independently. Official apps are listed on odoo.com/page/all-apps; thousands more third-party modules live on the App Store.

How many Odoo apps does an SME need?

Most SMEs run about 10–15 official apps: CRM, Sales, Accounting/Invoicing, and then Inventory, Purchase, Project, Timesheets, Expenses, Website, and a few persona-specific modules (POS, MRP, Helpdesk, Subscriptions). The 40,000 App Store figure is not a shopping list.

What is the difference between Odoo apps and Odoo modules?

Technically every installable package is a module. An app is a module marked as an application so it appears as a top-level product in the Apps dashboard. Bridges and extensions are modules that never show as standalone apps.

Can I install third-party Odoo apps on Odoo Online?

Only if they are data-only (no Python), per the Odoo Apps FAQ. Python third-party apps require Odoo.sh or on-premise. Prefer official apps and Studio on Online when possible.

Which Odoo apps require Enterprise?

Studio, Helpdesk, Sign, VoIP, IoT, Quality, PLM, Subscriptions, Approvals, advanced barcode/warehouse features, and full Accounting depth are the usual Enterprise-only (or Enterprise-strong) set. Community still covers a large CRM–Sales–Inventory–MRP core for self-hosted teams.

Odoo App Store vs this “Odoo apps” guide — which do I read?

Read this page for the official functional catalog, process map, and SME shortlist. Read the Odoo App Store guide when you are about to buy or install a third-party module and need quality, OCA, and upgrade-risk criteria.

Quick reference: five rules before you click Activate

• App vs module: “app” means a menu-level product; pricing pages care about that distinction.
• Dependencies first: one install can pull parents and bridges — stage it.
• Edition before wishlist: Community vs Enterprise decides Helpdesk, Studio, Sign, and Accounting depth.
• Smallest set that runs the business beats the 25-app brochure tour.
• Third-party last: OCA or proven authors only, with an upgrade owner — details in Odoo App Store.