This module allows to propagate the brand of the sale order on the tasks created with the products of type service
auto_awesome What this module does
AI-generated from the code · Odoo 13.0When a service product on a sale order creates a project task, the task automatically inherits the brand set on the sale order.
This module links the brand of a sale order to the project tasks that Odoo creates from it. It works together with the sale timesheet, sale brand and project task brand features.
When a sale order line for a service product causes a task to be created in a project, the module copies the brand recorded on the sale order onto that new task. This means the task is created already carrying the same brand as the sale order, without the user having to set it manually.
- The brand is taken from the sale order linked to the line.
- The value is applied while the task is being prepared, so the task is created with the brand from the start.
- No new menus, screens, buttons or reports are added by this module.
- No extra checks, restrictions, emails or scheduled jobs are introduced.
The module only extends the behaviour of sale.order.line when it prepares the values used to create a task. It does not add its own models or data files. The brand field itself comes from the related brand modules that this module depends on.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 13.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/brand.
terminal Installation and usage
OCA documentation · Odoo 13.0Usage
Source · Odoo 13.0When validating a sale order that contains service type products that are configured to create tasks, the brand indicated on the sale order is propagated to the task.
No verified information in OCA: Installation, Configuration.
Installation 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.