Partner Rank Commercial Entity
This module introduces a unified ranking system for commercial entities. Considering the customer rank and supplier rank are computed individually per contact, the ranks will be shared and aggregated globally at the level of the main commercial entity.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Makes customer and supplier ranks shared across a whole commercial entity, so all contacts of the same company show the same rank values instead of separate per-contact numbers.
This module changes how customer and supplier ranks behave on contacts in Odoo. Normally each contact keeps its own customer rank and supplier rank. With this module, those two fields are treated as commercial fields, meaning they belong to the main commercial entity (the parent company contact) rather than to each individual contact.
What changes for users:
- When a rank is increased on a contact, the increase is applied to the main commercial entity instead of only that contact.
- The updated rank values are then synchronised down to all child contacts of that entity, so every contact under the same company shows the same customer rank and supplier rank.
- Because the fields are commercial fields, Odoo's standard commercial-field synchronisation also keeps them aligned across the entity.
The module touches the res.partner model and depends on account, which is where the customer and supplier rank fields come from. It does not add new menus, screens, buttons or reports; the change is visible directly in the rank values shown on partner records. No new scheduled actions, emails or validation rules are introduced by the code shown.
Depends on
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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/partner-contact.
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.