CRM Google Autocomplete

Sales Representatives & Business Development Teams

Reps who create leads during or immediately after calls, visits, or events. Selecting a company from the autocomplete populates the full address, phone, and website in one action — the lead is ready to work before the conversation ends. No switching to Google Maps, no manual transcription, no missing postal codes.

Inside Sales & Lead Generation Teams

Teams qualifying high volumes of inbound or outbound leads who need fast, accurate data entry. Autocomplete eliminates the individual field-by-field typing that slows down bulk lead creation and introduces formatting inconsistencies that break later filtering and segmentation.

Sales Managers & Revenue Operations

Managers who depend on accurate CRM data for territory planning, pipeline reporting, and map-based lead distribution. Autocomplete enforces data quality at the point of entry — leads arrive with verified addresses and stored coordinates, ready for the CRM map view without a separate geocoding pass.

Odoo Administrators & CRM Integrators

Administrators who configure the CRM module and want a drop-in improvement to the Lead form with no custom development. The module installs with a pre-configured mapping for crm.lead and applies the widget to the correct fields via view inheritance — no XML overrides or Python changes required beyond installation.

Lead Address Entry Is Slow and Error-Prone

Filling in company name, street, city, state, postal code, and country one field at a time takes time a sales rep doesn't have during or after a customer interaction. Abbreviation inconsistencies, wrong postal codes, and missing country selections accumulate into CRM data that filters poorly and maps incorrectly. A single autocomplete selection replaces all of that.

Leads Have No Coordinates When Created

CRM leads are created with text addresses but no latitude/longitude — so they never appear on the CRM map view without a separate geocoding step. A geocoding cron adds latency and API cost, and it only runs periodically. Autocomplete stores coordinates at creation time, in the same save operation as the address, with no extra API call.

Company Details Require a Separate Lookup

After entering a company name manually, a rep often needs to search Google separately for the phone number and website, then copy each into the lead. In places mode, selecting a company from autocomplete populates name, full address, phone, and website simultaneously — the contact details a rep would otherwise look up are delivered as part of the selection.

Street Format Varies by Country

Addresses assembled from Google's route and street-number components come out in the wrong order for a significant portion of countries if the format is not handled explicitly. The per-country street format setting in the widget framework ensures the assembled value uses the correct convention — number-first or route-first — for the country on the lead record.

Autocomplete on Lead Form

• Company name autocomplete (places mode) — The partner_name field on the Lead form shows Google Places suggestions for businesses and locations. Applied to both the quick-entry group and the detailed tab.
• Street autocomplete (address mode) — The street field shows suggestions restricted to verified street addresses and routes, reducing irrelevant results and minimising API cost.
• Applied to both form locations — Both autocomplete fields are wired to the quick-entry group at the top of the form and to the detailed lead tab so the experience is consistent regardless of how a rep creates a lead.
• Automatic install-time configuration — A post-install hook creates the google.places.mapping records for crm.lead on first install. No manual field mapping setup is needed for standard use.

Field Population & Data Quality

• Atomic multi-field update — Selecting a suggestion writes all mapped fields in one record.update() call — address, coordinates, phone, website — with no partial saves or missing values.
• Full address auto-fill — street, street2, city, state, zip, and country are populated from address components; country and state are resolved to their Many2one records automatically.
• Geolocation at creation time — customer_latitude and customer_longitude are written atomically from the place's location data. No geocoding cron, no API backlog, no missing map pins.
• Company details from places mode — Selecting a business populates phone and website in addition to the full address — sourced from internationalPhoneNumber and websiteURI in the Google Places response.
• Per-country street format — The google_street_format field on res.country controls whether the assembled street value is Route + Number or Number + Route — applied automatically at write time based on the resolved country.

Configuration & Administration

• Admin-configurable mapping — All field mappings are google.places.mapping records, not code. Adjusting which Google Places data goes to which crm.lead field is an admin action — no deployment required.
• Built-in mapping test tool — Search a real place from the mapping configuration form and see the exact parsed output — address mapping, other fields, coordinates, and raw JSON — before any change goes live.
• No Manual Edit mode — Setting no_manual_edit makes a field read-only until a Google Places suggestion is selected, enforcing verified data on fields where free-text must be blocked.