This module allows users to set non-official names for partners in the search_alias field, improving search usability by enabling searches using alternative names. This is particularly useful for partners known by multiple names.
The search_alias field is added to the form view after the reference field.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you store alternative names for contacts and find them by those names in Odoo search. A new 'Search Alias' field appears on the contact form and can be shown in the contact list.
This module adds one extra field, search_alias, to contacts (res.partner). You can use it to record another name a contact is known by, for example a nickname, a former company name or a common spelling.
Where it appears: - On the contact form, the new field is placed right after the Reference field. - In the contact list view, the field is available but hidden by default, so you can switch it on when needed.
What changes in search: - When you search contacts by name, Odoo also looks inside the alias field. So typing the alias returns the contact even if the official name is different. - The search matches partial text (contains), not just exact names.
Scope and limits:
- The module only touches contacts (res.partner). It does not add menus, buttons, reports, emails or scheduled actions.
- No automatic checks or restrictions are added; the alias is simply free text you fill in yourself.
- It depends only on the base module, so it works with standard Odoo contacts.
Depends on
Models and fields (1)
- res.partner · extends an existing modelsearch_alias
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.