OdooWiki OCA HUB

Partner Rank Single

partner_rank_single folder_open OCA/partner-contact open_in_new
Partner Management License: AGPL-3

This module introduces a constraint to ensure that a contact cannot simultaneously be both a customer and a supplier.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Prevents a contact from being both a customer and a supplier at the same time. When a contact already has a customer or supplier rank, the opposite rank is not increased.

This module adds a rule to contacts (res.partner) so that a single contact cannot be both a customer and a supplier. If someone tries to save a contact that has both a customer rank and a supplier rank greater than zero, Odoo blocks the save and shows the error message: "A contact cannot be both a customer and a supplier."

It also changes how ranks are increased automatically. When Odoo would normally increase the customer rank for a contact that already has a supplier rank, or increase the supplier rank for a contact that already has a customer rank, the increase is skipped. This means a contact keeps only one role: either customer or supplier, not both.

The rule applies everywhere contacts are created or edited, including sales and purchase documents that update ranks in the background. There are no new menus or screens; the change is a validation and automatic behaviour on the existing contact form and related processes.

Depends on

account
Models and fields (1)
  • res.partner · extends an existing 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: 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 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.