This module extends the contact management functionality. It allows recording of a partner's gender among three options: "Male", "Female", "Other".
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds a Gender field to contacts, letting users record whether a contact is Male, Female or Other. The field appears on the Personal Information tab of the contact form.
This module adds one extra piece of information to every contact in Odoo: gender. On the contact form, inside the Personal Information tab, a new Gender field is shown next to the other personal details. Users can pick one of three values: Male, Female or Other, or leave it empty.
The field is stored on the contact record itself (res.partner), so it is available anywhere contacts are used, such as customers, vendors and other partners. It is a simple selection field: there are no automatic checks, no computed values, no restrictions and no emails or scheduled actions attached to it.
Because the module depends on the personal information page module, the field only appears where that page already exists on the contact form. No new menu or separate screen is created; the change is limited to the existing contact form view. Nothing else in Odoo is modified by this module.
Required by other modules
Models and fields (1)
- res.partner · extends an existing modelgender
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/partner-contact.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0A value for 'Gender' can be selected on the 'Personal Information' tab of the partner contact form.
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.