Applies base_exception module for contacts.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Lets you define custom exception rules for contacts and automatically flags contacts that break those rules. Rules are managed from a new menu under Contacts configuration.
This module extends the generic exception rules engine to contacts. It adds a new menu entry, Contact Exception Rules, under the Contacts configuration menu, visible only to users in the exception rule manager group. From there you create rules that apply to contacts (res.partner).
Each rule can be linked to specific contacts through a Contacts field, so a rule can target only some partners instead of all of them. The rule list is filtered to show only rules whose model is Contact.
When a contact is created or updated, Odoo checks whether the change touches the exception-related fields. If it does, the contact is re-evaluated against the active rules and any broken rule is recorded on the contact. Contacts are also sorted so that those with an exception appear first.
The module touches the res.partner model and the exception.rule model, and depends on the Contacts and base exception modules. It does not add new reports or emails; it only adds rule configuration and automatic checking on contacts.
Depends on
Menus it adds
Models and fields (2)
- res.partner · new model
- exception.rule · extends an existing modelmodel, partner_ids (Contacts)
Text generated by AI (DeepSeek) from reading the Odoo 15.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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/partner-contact.
terminal Installation and usage
OCA documentation · Odoo 15.0Usage
Source · Odoo 15.0Custom exceptions on partner contact
No verified information in OCA: Installation, Configuration.
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.
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.