Skip to main content
iVentureTeam
Hosting & DevOps

How to Install Third-Party Modules on Odoo.sh, On-Premise and Online

How to install third-party and custom modules on Odoo.sh, on-premise and Odoo Online in Odoo 19 and 20: GitHub, submodules, addons path, limits and fixes.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 14, 202612 min read5 views
How to Install Third-Party Modules on Odoo.sh, On-Premise and Online cover

Installing an Odoo module from the App Store or GitHub takes minutes once you know your hosting rules, and getting it wrong can break production. Our Odoo development company team installs and tests modules for clients every week.

Related service: DevOps and hosting services — Odoo.sh, self-hosting and CI/CD run by people who do it daily.

This guide is for admins, IT leads and in-house developers on Odoo 19 or Odoo 20. If you still need to choose a hosting type, start with our Odoo Online vs Odoo.sh vs on-premise comparison.

Where can you install third-party modules in Odoo?

Third-party Odoo modules: Where can you install them?

Third-party modules install on Odoo.sh and on-premise Odoo, while Odoo Online blocks them. Odoo's docs state that Odoo Online is incompatible with custom modules or modules from the Odoo Apps Store.

Hosting typeThird-party and custom modulesHow you add codePlan needed
Odoo OnlineNot supportedData modules via Import Module onlyStandard or Custom
Odoo.shSupportedGitHub repository or Git submoduleCustom
On-premise EnterpriseSupportedFolder on the addons pathCustom
On-premise CommunitySupportedFolder on the addons pathFree license
Python librariesOdoo.sh and on-premiserequirements.txt or pipSame as above
System packagesOn-premise onlyapt or your OS package managerSame as above

The plan matters. On the Odoo pricing page, Standard runs on Odoo Online only, while Custom adds Odoo.sh and on-premise hosting. So a company on Standard must move to Custom before it can run any third-party code.

This guide covers the installation steps only. For what modules cost to buy, migrate and maintain, read our guide to third-party Odoo module costs.

What should you check before you install a module?

Check five things before any install: version, dependencies, license, code quality and a test database. Most failed installs trace back to one of these.

  • Odoo series: the Odoo App Store lists each module by version, from 20.0 back to old series. Download the build that matches your database exactly.
  • Dependencies: the manifest's `depends` list names the Odoo modules that load first. Installing one module can pull in several apps, which can change your subscription cost.
  • Python libraries: the manifest's `external_dependencies` names extra Python packages. If they are missing, the install fails.
  • License and source: paid apps, free OCA modules and code from freelancers all carry different licenses and support terms.
  • Test database: Odoo's docs advise you to duplicate the database to test apps, because uninstalling an app also deletes its records.

Also have someone read the code. A module runs with full database access, so one bad module can slow every screen or block an upgrade.

How do you install a third-party module on Odoo.sh?

On Odoo.sh you never upload a zip file to the database: you push the module to the GitHub repository linked to your project, and Odoo.sh rebuilds the branch. Follow Odoo's own flow from development to staging to production.

  1. Unzip the module and check that the folder name matches the technical name and contains `__manifest__.py`.
  2. Create a development branch in the Odoo.sh Branches view, forked from production, or with Git on your computer.
  3. Add the module folder to the root of that branch, commit and push. Odoo.sh starts a new build automatically.
  4. Test on the development build. It uses a fresh database with demo data and runs the tests.
  5. Merge into staging. Staging duplicates your production data, so you test the module on real records.
  6. Install from Apps on staging. Turn on developer mode, click Update Apps List, then install the module.
  7. Merge into production and install it from Apps the same way.

Odoo's guide to deploying a module on Odoo.sh confirms staging builds do not install new modules automatically, so staging behaves like production.

Development builds install only your branch's own modules by default, not submodules. Change this under Module Installation in the branch settings.

How do Odoo.sh builds and backups treat module updates?

Odoo.sh updates a module on deploy only when you raise its version number in the manifest. It also takes an automatic backup at that point.

The Odoo.sh branches documentation says an "Update" backup runs when a merge changes a module version or its Python dependencies. Otherwise no backup runs, so take one manually first.

Staging databases are neutralized. Scheduled actions and outgoing emails are disabled, so a new module cannot email customers while you test it.

How do you add OCA or private repositories to Odoo.sh with Git submodules?

Use a Git submodule when a module lives in its own repository, such as OCA modules or a vendor's private repo. Odoo.sh detects submodules and adds them to the addons path.

Odoo's guide to Git submodules on Odoo.sh gives two routes. In the Odoo.sh interface, open the branch, click Submodule, then Run on Odoo.sh, and enter the SSH URL, the branch and a folder path.

The interface cannot add private repositories. For those, generate a deploy key in the project settings, add it to the private repository on GitHub, then run `git submodule add -b ` and push.

OCA modules often come in collections you only partly need. Odoo suggests prefixing the submodule folder with a dot so the platform ignores it, then linking only the modules you want.

How do you install a custom module on Odoo on-premise?

On a self-hosted server, an Odoo custom module install means placing the module in a folder listed in the Odoo addons path, restarting Odoo, and installing from Apps. This works the same for Community and Enterprise.

  1. Create a separate folder for third-party and custom modules, such as `/opt/odoo/custom-addons`, outside the Odoo source code.
  2. Copy the unzipped module into that folder and give the Odoo system user read access.
  3. Add the folder to `addons_path` in your Odoo configuration file, or pass `--addons-path` on the command line.
  4. Install any Python libraries the module needs with pip, inside the same environment Odoo uses.
  5. Restart the Odoo service. Odoo reads the addons path only at startup.
  6. Update the Apps list in developer mode, remove the Apps filter, search the technical name and click Activate.

You can also install from the command line with `odoo-bin -d -i --stop-after-init`, and update a module with `-u `.

For Docker, the official image mounts custom modules at `/mnt/extra-addons`. Our Odoo installation guide covers installing Odoo itself, from Docker to source setups.

Can you install custom modules on Odoo Online?

No, Odoo Online does not run custom Python modules or Odoo Apps Store modules, but it does accept XML-only data modules. This is the main limit of Odoo Online custom modules.

Odoo's tutorial on importable data modules says hosting like Odoo.com does not allow custom Python code. A data module defines models, fields and views in XML.

You upload it as a zip file under Apps, Import Module, in developer mode, with base_import_module installed.

The Odoo import module route has real limits. Python in data modules runs in a sandbox, you cannot override Python methods cleanly, and re-importing does not delete removed fields.

If you need more than Studio and data modules, plan a move to Odoo.sh or on-premise. Our comparison of Odoo Studio vs custom development helps you judge when that step is worth it.

Why is my module not showing in the Odoo Apps list?

A module missing from Apps is nearly always a path, manifest, filter or access problem, not a bug in Odoo. Work through the table in order.

SymptomLikely causeFix
Module not in Apps after copyApps list not updatedDeveloper mode, Update Apps List
Still missing after updateApps filter hides non-app modulesRemove the Apps filter, search technical name
Odoo.sh log lacks /src/user pathBroken or missing manifestFix `__manifest__.py` and push again
Private repo modules missingDeploy key or access missingAdd deploy key, check GitHub access
Install fails with import errorPython library not installedAdd it to requirements.txt or pip install
On-premise module ignoredFolder not on addons path or no restartEdit config, restart the service

These match what users report. On the Odoo forum, one admin found Odoo.sh left /src/user out of the addons path until the manifest was fixed. Another saw OCA modules only after removing the Apps filter.

What changes for Odoo 19 and Odoo 20 modules?

Odoo 20 modules follow the same install steps as Odoo 19, but each module must be ported to the new series. Odoo 20 was released in September 2026, and the App Store already lists 20.0 builds.

  • No cross-version installs: a 19.0 module is not a 20.0 module. Use the build for your series or port the code.
  • Upgrade blocker: Odoo's upgrade documentation says a database with custom modules cannot be upgraded until those modules exist for the target version.
  • External API: XML-RPC and JSON-RPC are deprecated in Odoo 20, not removed yet; removal is planned for Odoo 22. Modules that call Odoo from outside should plan for it.
  • Release changes: check our Odoo 20 release notes for app changes that affect the module you want.

If you are moving existing modules across versions, our guide to Odoo 20 custom module upgrades explains what breaks and how to fix it.

Which industries rely most on third-party Odoo modules?

Companies with local rules, many sales channels or special hardware add the most modules. The pattern below is what we see in projects, not a market survey.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
ManufacturingShop-floor devices, labels, custom pricingCustom modules on Odoo.sh or on-premiseBuild, test on staging, deploy
eCommerce and retailMarketplace and carrier connectorsApp Store connectors plus API workVet connectors, fix sync gaps
DistributionBarcode, routes, freight rulesInventory plus targeted add-onsCheck dependencies before install
ServicesBilling and project rulesStudio first, small modules afterKeep code light for upgrades
Multi-country groupsLocal tax and report gapsLocalization plus OCA modulesAdd OCA repos as submodules

How do you test and deploy Odoo modules safely?

Treat every new module like a code release: test it on a copy of production, back up, then deploy in a quiet window. This applies to Odoo.sh and self-hosted servers alike.

  1. Record the baseline: list installed modules and take a backup.
  2. Install on a copy: use an Odoo.sh staging branch or a duplicated on-premise database.
  3. Test key flows: quote to invoice, purchase to receipt, payroll or POS, whatever the module touches.
  4. Check speed and logs: look for warnings and slow screens after install.
  5. Deploy and watch: install on production, then monitor logs and users for a day.

Not sure what is already installed and how healthy it is? Run the free Odoo health check before you add more modules.

How iVentureTeam helps you install third-party modules on Odoo.sh

Adding more modules? Check health first

We install, test and maintain third-party and custom modules so your production database stays stable. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Module review: we read the code, dependencies and license before anything touches your database.
  • Odoo.sh setup: repository structure, submodules, deploy keys, requirements.txt and branch settings.
  • On-premise setup: addons path, service config, Python environment and Docker mounts.
  • Custom builds: when no module fits, our Odoo developers for hire write one built for your version.
  • Upgrades: our Odoo upgrade services port your modules to Odoo 20.

Odoo custom module install case study: Chetan Plastics

A plastics-printing manufacturer in Ahmedabad moved five departments off spreadsheets onto a customized Odoo, with custom work in 10 workflow areas. It shows why tested module deployment matters.

Chetan Plastics ran sales, purchase, delivery and receipts from a shared Excel file. Block-based print pricing was calculated by hand, and nothing linked a CRM job to its sales order, purchase order or delivery paperwork.

We built the business logic into the modules: two-step validation on sales and purchase confirmations, the block price calculator inside order lines, a repair workflow with automated stock moves, and TSC barcode labels at 100 by 75 mm.

The rollout ran over 16 weeks in phases and connected six core modules from Sales to Repair. Read the Chetan Plastics Odoo manufacturing customization case study.

The bottom line on installing third-party modules in Odoo

Install third-party modules on Odoo.sh through GitHub and staging, on-premise through the addons path, and on Odoo Online only as data modules. Match the version, test on a copy and back up first.

The install is the easy part. The real work is choosing modules you can trust, keeping them few, and porting them at each upgrade.

Ready to get your Odoo modules deployed safely?

Get module help

Let our developers install, test and document your next module. Talk to our Odoo module deployment team, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

Can I install third-party modules on Odoo Online?

+

No. Odoo Online does not support custom modules or Odoo Apps Store modules. You can import XML-only data modules and use Studio, or move to Odoo.sh or on-premise for full modules.

How do I install a module from the Odoo App Store on Odoo.sh?

+

Download the build for your Odoo series, unzip it, push the folder to a branch of your GitHub repository, then install it from Apps on staging. Merge to production and install it there.

Where do I put custom modules on an Odoo server?

+

Put them in a separate folder, add that folder to addons_path in the Odoo config file, and restart the service. Then update the Apps list in developer mode and install.

Why is my custom module not showing in Odoo Apps?

+

Usually the Apps list was not updated, the Apps filter hides it, the manifest is broken, or the folder is not on the addons path. Check the server log for the addons paths Odoo loaded.

Can I install an Odoo 19 module on Odoo 20?

+

Not reliably. Modules are built per series, so use the 20.0 build or port the code first. Odoo also blocks database upgrades until custom modules exist for the target version.

How do I add a private GitHub repository as a submodule on Odoo.sh?

+

Generate a deploy key in the Odoo.sh project settings, add it to the private repository on GitHub, then add the submodule with Git and push. The Odoo.sh interface cannot add private repos.

Do I need the Custom plan to install third-party modules?

+

For Enterprise, yes. Odoo.sh and on-premise hosting are on the Custom plan, while Standard runs on Odoo Online only. Odoo Community on your own server is free and accepts modules.

Can I install Python libraries on Odoo.sh?

+

Yes. List them in a requirements.txt file at the root of your branch and Odoo.sh installs them on build. System packages and PostgreSQL extensions are not supported.

Is it safe to install free OCA modules?

+

Often, yes, but test them like any code. Check the module's version, maintainers and dependencies, install on staging first, and keep a backup before production.

Free Odoo upgrade plan

Worried about third-party modules in your upgrade?

Tell us your version, edition and custom modules. We check what breaks, what it costs to fix and the safest path, before any work begins.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.