OdooWiki OCA HUB

Contract Brand

contract_brand folder_open OCA/brand open_in_new
Uncategorised License: AGPL-3

This module allows you to manage branded contracts. It adds a brand field on the contract and propagate the value on the invoices.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets you assign a brand to a contract and automatically carries that brand over to the invoices generated from it, so branded contracts and their billing stay consistent.

This module adds brand handling to recurring contracts. On the contract form, a Brand field appears right after the customer field, so you can pick which brand a contract belongs to.

When the contract generates an invoice, the same brand is automatically copied onto that invoice, so you do not have to set it again manually.

  • Contracts can be grouped by brand in the contract search view, making it easy to list all contracts of one brand.
  • The brand is also passed into the analytic distribution calculation of contract lines, so analytic accounting entries follow the contract's brand.
  • Changing the brand on a contract refreshes the analytic distribution on its lines automatically.

The module works together with the contract, account brand and analytic brand features, and it touches the contract.contract and contract.line models. No new menus are added; the changes appear inside the existing Contracts screens and search filters.

Models and fields (2)
  • contract.line · extends an existing model
  • contract.contract · new model

Text generated by AI (DeepSeek) from reading the Odoo 18.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 6 confirmed, 3 with no information of 9 versions.

terminal Installation and usage

No verified information

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.

info

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.