OdooWiki OCA HUB

Partner Contact Company Propagation

partner_contact_company_propagation folder_open OCA/multi-company open_in_new
Tools License: AGPL-3

Add company_id to commercial fields, as it should be propagated to parent commercial entity and children.

auto_awesome What this module does

AI-generated from the code · Odoo 14.0

Makes the Company field on a contact a commercial field, so it is shared between a company and its child contacts instead of being set separately on each one.

This module changes how Odoo handles the Company field on contacts. In Odoo, some fields are "commercial fields": they are not stored per contact but are shared across a company and all the contacts attached to it. This module adds the Company field to that shared list.

What this means in practice:

  • When you set or change the Company on a company contact, the same value is propagated to its child contacts, and vice versa.
  • You no longer have to fill in the Company manually on every individual contact of the same company.
  • The behaviour applies wherever contacts are used in Odoo, since it is defined on the res.partner model itself.

No new menus, screens, buttons or reports are added. The module does not create any new model; it only extends the existing res.partner model by adding company_id to the list returned by _commercial_fields. There are no extra checks, emails or scheduled jobs in the code. The change is purely about how the Company information is shared between a company and its related contacts.

Depends on

base

Text generated by AI (DeepSeek) from reading the Odoo 14.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: 1 confirmed, 8 with no information of 9 versions.

Sources · Odoo 14.0

Confirmed on 2026-11-03 in branch 14.0 of OCA/multi-company.

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.