Odoo Industry Packages Explained: Install, Customize and Roll Back

Odoo industry packages look like a shortcut to a finished ERP, and for a small business they can be a good start. The risk sits in the details: extra apps, changed settings and demo data in production. Our Odoo implementation services start every industry setup on a test copy for that reason.

This guide is for owners, admins and project leads who have seen the Industries filter in the Apps menu and want to know what really happens when they click Install. If you have not chosen your hosting yet, read our Odoo Online vs Odoo.sh vs on-premise guide first.

What are Odoo industry packages?

Odoo industry packages are importable data modules that configure standard Odoo apps for a specific sector. They contain no Python business logic, only data files, so they can run on Odoo Online where custom code is not allowed.

Odoo's own tutorial calls these "importable modules" or "data modules". The Odoo guide to writing importable modules explains that they define models, fields and logic in XML because hosted platforms like Odoo Online do not allow custom Python code.

In the Apps menu, these packages appear under a separate Industries filter. Odoo's code lists them as a module type called Industries, next to Official Apps, and fetches the list live from apps.odoo.com. Each package has its own version number and is built for one Odoo major version.

What does an Odoo industry package install?

An industry package installs its dependent apps first, then loads configuration data, and only loads sample records if you tick the demo option. The table shows what the official packages contain, using the 20.0 Bakery and General Contractor manifests as examples.

Layer	What it adds	Example from official packages	Stays after uninstall?
Dependent apps	Standard apps the package needs	Construction pulls in CRM, Documents, Helpdesk, Purchase, Planning and Timesheets	Usually yes
Settings	Feature switches turned on	Pricelists, analytic accounting, units of measure, warnings	Settings stay as set
Configuration data	Products, stages, menus, job positions	Project stages, product categories, quotation templates	No, deleted with the package
Knowledge articles	A guided setup article and a tour	Welcome article with step-by-step tips	No, deleted with the package
Demo data (optional)	Sample company details, customers, orders	Bakery demo renames the main company to "MyBakery"	Hard to remove cleanly

Two details surprise most admins. First, the Construction package alone depends on nine modules, so one click can add several paid apps. Second, the Bakery demo file overwrites your main company name, logo, email and address with sample values.

Which Odoo plan and edition do industry packages need?

Industry packages need Odoo Enterprise, and some also need the Custom plan because they depend on Studio. They do not install on Community.

Every official package we checked carries the OEEL-1 Enterprise license and depends on Enterprise apps such as Knowledge, Documents or Planning. If a dependency is missing, Odoo's installer warns that "You may need the Enterprise version to install the data module."

Studio is the hidden cost. The 20.0 Beverage Distributor package lists Studio as a dependency. Odoo's Studio documentation says installing Studio on a Standard plan database "automatically triggers an upsell to the Custom pricing plan."

On the Odoo pricing page, the US price billed yearly is US$31.10 per user a month for Standard and US$61.00 for Custom. Because a package installs several apps at once, it also takes you out of the One App Free plan. Check each package's dependency list before you install.

Odoo Online vs Odoo.sh vs on-premise: how do industry installs differ?

The install button is the same everywhere, but testing, backups and rollback depend on your hosting. This is the gap most install guides skip.

Factor	Odoo Online	Odoo.sh	On-premise
Where to install	Apps menu, Industries filter	Apps menu on a staging branch first	Apps menu, Enterprise addons in path
Test copy	Duplicate, test mode, 15-day expiry	Staging branch with neutralized production copy	Duplicate with the neutralize option
Backups	Daily, downloadable from database manager	7 daily, 4 weekly, 3 monthly on production	Your own backup routine
Custom code on top	Data modules and Studio only	Python modules in your Git branch	Python modules in your addons path
Internet needed	Handled by Odoo servers	Handled by Odoo.sh servers	Server must reach apps.odoo.com
Rollback path	Keep the pre-install backup; ask Odoo Support about a restore	Restore a backup from the Backups tab	Restore your own database dump

The core rule is identical on all three: never try a package for the first time on production. What changes is how easily you can make a safe copy and how fast you can go back.

How do you install an Odoo industry package?

You install an Odoo industry package from the Apps menu as an administrator, after testing it on a copy of your database. Only administrators can install data modules; Odoo blocks everyone else.

1. Make a copy: duplicate the database, or use an Odoo.sh staging branch.
2. Check the version: pick a package built for your Odoo major version.
3. Open Apps: remove the default Apps filter and choose the Industries filter.
4. Read the dependencies: open the package card and note every app it will add.
5. Click Install: Odoo downloads the package and opens an "Install an Industry" window.
6. Decide on demo data: leave it off unless the database is a throwaway test.
7. Review the result: walk through the Knowledge welcome article, settings and menus.
8. Repeat on production: only after your team signs off on the test copy.

The Odoo apps and modules guide warns that adding apps "can significantly affect other apps in the database and modify subscription costs." It recommends testing on a duplicate first, which is the step people skip.

Should you load the demo data when you install an Odoo industry?

Load demo data only on a test or training database, never on the one you will run your business on. Odoo's own installer says so in plain words.

When you install an industry, the window reads: "Load demo data to test the industry's features with sample records. Do not load them if this is your production database." Demo data adds sample customers, vendors, employees, sales orders, purchase orders and, in some packages, stock and timesheets.

Removing it later is painful. On the Odoo forum, the accepted answer to a user asking how to delete demo data and start from scratch was that it cannot be deleted once inserted, and that a new database is the clean fix.

A good pattern is two databases: a demo copy for training and exploring, and a clean copy with only the configuration data. Your team learns on the first and keys real data into the second.

How do you install an Odoo industry package on Odoo.sh?

On Odoo.sh, install and test the industry package on a staging branch first, then repeat it on production once it passes. Staging gives you a neutralized copy of real production data.

The Odoo.sh branches documentation explains that staging databases disable scheduled actions and intercept outgoing email. That makes them a safe place to see how a package collides with your live settings and records.

One Odoo.sh detail matters here. Merging staging into production only merges source code, not database changes. An industry package installed through the Apps menu is a database change, so you must install it again on production, or script it.

Before you do, take a manual backup of production from the Backups tab. Odoo.sh keeps manual backups for three days and allows five a day, on top of its seven daily, four weekly and three monthly automatic backups.

How do you install an Odoo industry package on-premise?

On-premise, the Apps menu install works the same way, provided your server can reach apps.odoo.com and has the Enterprise addons in its path. Without both, the download or the dependency check fails.

Odoo's installer fetches the industry list and the package ZIP from apps.odoo.com. A firewalled server shows a connection error instead. Some packages also need website themes; Odoo's installer points to the design themes repository when they are missing.

For a test copy, use the database manager at https://erp.iventureteam.com/web/database/manager and tick the neutralize box when you duplicate. Odoo's on-premise guide says this runs the neutralize scripts of every installed module, so mail and scheduled jobs do not fire from the copy.

Developers can also deploy data modules from the command line with `odoo-bin deploy`. The user doing it needs Administration/Settings rights, the same as in the interface.

How do you customize an Odoo industry package?

Customize an industry package with settings and Studio first, then with a separate data module or Python module, and never by editing the package itself. That keeps the original intact and your changes upgradeable.

• Settings and configuration: change stages, products, templates and menus directly; these are your data, not code.
• Studio: add fields, views, reports and automation rules; on Online this is the main tool.
• Studio export: Odoo's Studio export and import guide shows how to export customizations as a ZIP module and import it into another database.
• Your own data module: on Odoo Online, use Apps, then Import Module in developer mode; model and field names must start with x_.
• Python modules: on Odoo.sh and on-premise, add real business logic in your Git branch or addons path.

Data modules have limits. Odoo's tutorial notes you cannot change a field's type after creating it, and removed fields are not deleted on re-upload. Code inside data modules runs in a sandbox that cannot import libraries. Our Odoo Studio vs custom development guide explains when each path fits.

When the package needs more than settings and Studio can give, our Odoo customization services build the extra logic as a separate module. For the developer view, see our Odoo module development guide.

Can you uninstall or roll back an Odoo industry package?

You can uninstall an Odoo industry package, but uninstalling is not a true rollback; restoring a backup is. Uninstall removes the package's own records and leaves most other changes in place.

Odoo's apps guide warns that uninstalling apps "also deletes their database records" and can remove dependent apps too. For imported modules, Odoo's code also deletes the module record itself, because an imported module cannot be reinstalled without its files.

The apps a package pulled in stay. Uninstalling a module in Odoo removes the modules that depend on it, never the apps it depends on. Settings switched on and demo data loaded also stay.

What you want to undo	Uninstall the package	Restore a backup
Package products, stages and articles	Removed	Removed
Extra apps it installed	Usually stay, uninstall each one	Removed
Settings it turned on	Stay as set	Reverted
Demo records	Hard to remove cleanly	Removed
Work your team did since install	Kept	Lost after the backup point

So the safe order is simple: back up, install on a copy, test, then install on production. If production goes wrong within days, restoring the pre-install backup is often cleaner than uninstalling.

Which Odoo industry package fits your business?

Use the closest package as a starting point, then fill the gaps with configuration and light custom work. The table shows how we usually approach common sectors.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Construction	Quotes, site tasks and costs in separate tools	General Contractor package with Projects, Planning and Documents	Map BOQ and progress billing on top
Bakery and food retail	Shop, online orders and buying in one place	Bakery package with Point of Sale, eCommerce and Purchase	Set up recipes, lots and expiry rules
Beverage distribution	Deposits, excise and route sales	Beverage Distributor package with deposits and excise	Check Studio impact on your plan
Real estate	Listings, viewings and commissions	Real Estate package with Appointments, Sign and commissions	Adapt listing flows and contracts
Florist and gift retail	Seasonal peaks, loyalty and online sales	Florist package with POS, loyalty and website	Connect channels to one stock ledger

If no package matches, start from standard apps instead. Our Odoo app selector tool and our guide on how to choose Odoo modules by sector help you build the list. For contractors, see our Odoo ERP for construction page.

Common Odoo industry install problems and fixes

Most failed industry installs come from a version mismatch, a missing Enterprise app or a blocked connection. These are the errors we see most.

• "Unknown module dependencies": the package needs an app your database does not have; check edition and version.
• "Studio customizations require the Odoo Studio app": install Studio, and plan for the Custom plan upsell.
• Industry list will not load: the server cannot reach apps.odoo.com; open outbound access.
• "Only administrators can install data modules": sign in as an admin.
• ZIP refused on import: the module folder must sit at the root of the ZIP with its manifest; Odoo caps each file at 100 MB.
• Company name changed: demo data was loaded; restore or correct the company record by hand.

Check what changed in the current release on our Odoo 20 release notes before you pick a package version.

How iVentureTeam helps install and customize Odoo industry packages

We treat an industry package as a starting point for an implementation, not a finished system. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Fit test: we install the package on a duplicate or staging branch and walk your team through it.
• Gap list: we compare the package with your real processes and list what to configure, add or skip.
• Plan check: we flag Studio dependencies and extra apps before they change your subscription.
• Upgrade-safe customization: Studio exports, data modules or Python modules kept apart from the package.
• Clean go-live: a backup, a production install without demo data, and data migration from your old system.

For a first budget, try our Odoo project estimate tool. Our published implementation ranges start at $3k to $9k over 4 to 8 weeks for a small company, depending on scope.

The bottom line on Odoo industry packages

Odoo industry packages are a fast, low-risk start only if you install them on a copy first, skip demo data in production and keep a backup ready. Treat them as a template, not a promise of a finished ERP.

Check the dependency list for extra apps and Studio, test on your hosting's safe copy, customize outside the package, and restore a backup if you need a real rollback. Done that way, a package can cut weeks of setup.

Ready to test an Odoo industry package safely?

Let us run the package on a copy of your database and show you what it changes before you commit. Plan your Odoo industry setup with our team, call +91-90235-15208, or email business@iventureteam.com.