Catalog templates
A catalog template is a ready-made set of values for a new environment, so you do not have to choose them one by one.
What a template is, and is not
Section titled “What a template is, and is not”A template sets:
- the environment’s type (dev, staging or production);
- its resources (CPU cores and memory);
- its options, such as PGTune, PgBouncer or Mailtest;
- some odoo.conf values, such as the number of workers.
A template does not bring code. Odoo’s version and your addons come from the project you deploy it into: its main repository, addon repositories and uploaded modules. The modules a template names are a suggestion; the platform does not install them.
The templates
Section titled “The templates”| Category | Templates |
|---|---|
| General | Dev Sandbox, Staging Standard, Production Starter, Production Standard, High Performance |
| eCommerce | eCommerce Store, eCommerce High Traffic |
| Point of sale | POS Retail |
| Manufacturing | Manufacturing ERP |
| Accounting | Accounting Firm |
| HR | HR |
Deploy a template
Section titled “Deploy a template”You need a prepared server and a project. Deploying a template needs an owner or admin.
- Open Catalog in the sidebar. Filter by Category if you like.
- On a template’s card, press Deploy this template.
- Choose the Project and the Server, and enter a Name (small letters, digits and
-). - Start it.
The environment is created with the template’s values and its first deploy starts at once.
Afterwards
Section titled “Afterwards”It is an ordinary environment. Change anything the template set under Settings and options.

