Partner Identification Numbers Unique By Category
This module extends the module partner_identification to enforce having unique id numbers by categories. This option can be set by category.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you mark an identification number category as unique, so Odoo refuses to save a partner ID number that already exists in that category.
This module adds a single option to the identification number categories used on contacts, and uses it to block duplicates.
- On each identification category (for example passport, VAT, national ID) you get a new checkbox called "Enforce unicity". It appears on the category form and in the category list.
- When the checkbox is ticked, Odoo checks every partner ID number saved in that category. If the same number already exists, saving is blocked with an error message naming the number and the category.
- The check runs when the number or its category changes, so duplicates cannot be created or moved into a protected category.
- You cannot switch a category to unique if it already contains duplicates: Odoo shows an error telling you the category still has duplicate numbers, so you must clean them up first.
- Categories left unticked keep behaving as before, allowing repeated numbers.
It works together with the partner identification module and affects the identification category and partner ID number records, plus the contact identification numbers screen where those numbers are entered.
Depends on
Models and fields (2)
- res.partner.id_number · extends an existing model
- res.partner.id_category · extends an existing modelhas_unique_numbers (Enforce unicity)
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: 3 confirmed, 6 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.