Partner Phone number auto format
This module formats the Partner mobile number automatically on creation.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Automatically formats a contact's mobile and phone numbers when the contact is first created, using Odoo's built-in phone validation.
This module changes how contact records are saved in Odoo. When a new contact is created, the system immediately runs the standard phone and mobile number formatting/validation on the record, so the stored number is cleaned up and formatted according to the country rules already handled by Odoo's phone validation feature.
Where it appears:
- It works in the background on the Contacts application (the res.partner model).
- There is no new menu, screen, button or report; users simply notice that phone numbers look properly formatted right after saving a new contact.
Business behaviour it adds: - On creation of a contact, the mobile number is formatted automatically. - On creation of a contact, the phone number is formatted automatically. - The formatting uses the same validation logic Odoo already applies when a user edits these fields manually, so results are consistent.
What it touches:
- It extends the res.partner model and its create method only.
- It relies on the phone_validation module for the actual formatting rules.
Note: the module only acts at creation time; it does not add checks, restrictions, emails or scheduled jobs, and it does not change existing contacts.
Depends on
Models and fields (1)
- res.partner · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.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.