This module populates the company field with user's company as the default value when creating new products.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0When you create a new product, Odoo automatically fills in the Company field with the company you are currently working in, instead of leaving it empty.
This module changes how the Company field behaves on product records. Normally, when you create a new product, the Company field is left blank. With this module installed, that field is pre-filled with the company you are currently logged into, so you do not have to select it manually every time.
The behaviour is controlled by a system setting (a configuration parameter named product_company_default.default_company_enable). It is switched on when the module is installed, so the default company is applied straight away. If an administrator sets that parameter to a different value, the automatic filling stops and the Company field goes back to being empty by default.
- Applies to the product template model (
product.template), which is the main screen where products are created and edited. - Only affects the default value shown when a new product is created; it does not change existing products.
- No new menus, buttons, reports or scheduled actions are added.
This is a small convenience module for companies that work with several companies in the same database and want new products to belong to the company they are working in without extra clicks.
Depends on
Models and fields (1)
- product.template · extends an existing modelcompany_id
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/product-attribute.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.