Google Maps Products for Odoo

All modules target Odoo 19.0 and work on both Community and Enterprise editions. There is no dependency on any Enterprise-only feature — the suite is built entirely on standard Odoo framework APIs.

Older Odoo versions (16, 17, 18) are not supported. The modules rely on OWL 2.x and the Odoo 19 view registration system.

No — a standard Google Cloud account with a billing method attached is sufficient. Google Maps Platform requires a billing account to be enabled, but provides a $200 USD free credit per month which covers most small-to-medium Odoo deployments without any charge.

If your usage exceeds the free credit, standard Google Maps Platform rates apply. Current pricing is available at mapsplatform.google.com/pricing.

Yes — for map tile rendering and Google API calls (Places, Geocoding, Maps JavaScript API). Both the Odoo server and users' browsers need outbound access to Google API endpoints.

The Google Maps JavaScript API is loaded from Google's CDN at runtime, so browsers need access to maps.googleapis.com and related Google domains.

No — beyond a standard Odoo 19.0 deployment. GPS coordinates are stored in standard PostgreSQL Float columns and GeoJSON data in JSONB fields. No PostGIS extension is required.

You can install any module individually. Dependencies are resolved automatically — installing an application module pulls in the foundation modules it requires. You never have to install modules you won't use.

The suite is also pre-packaged as nine focused sub-products if you need a specific capability — from the full 16-module bundle down to targeted 3-module suites for Sales, Delivery, or CRM Autocomplete only.

Foundation modules provide the shared infrastructure — the Google Maps JavaScript API integration, map view types, the Place Autocomplete widget, and the click-to-add-place mixin. They are model-agnostic and reusable across any Odoo module.

Application modules wire the foundation layer into a specific Odoo app — Contacts, CRM, Sales, Inventory, or Projects — adding map views, autocomplete fields, and business logic to those apps' models.

Installing an application module automatically installs the foundation modules it depends on.

Yes — all suites share the same foundation modules and are designed to coexist. Installing the CRM suite and the Contacts suite together simply means both application modules are active, sharing the same base_google_map, web_view_google_map, and autocomplete foundation modules underneath.

If you plan to use Google Maps across multiple Odoo apps, the Google Maps Suite (16 modules) installs everything in one go.

The base foundation module depends only on web and base_setup — both shipped with every Odoo installation. Application modules have their own standard dependencies:

• Contacts suites — requires contacts, base_geolocalize
• CRM suites — requires crm
• Sales suite — requires sale_management
• Delivery suite — requires stock
• Project suite — requires project

None of these are Enterprise-only. All are part of the standard Odoo Community distribution.

The APIs you need to enable depend on which modules you install:

• Maps JavaScript API — required by all map view modules (web_view_google_map, web_widget_google_map)
• Places API (New) — required by all autocomplete modules (web_widget_google_place_autocomplete)
• Maps Embed API — required by form-embedded map widgets (web_widget_google_map)
• Geocoding API — required if you use address-to-coordinate geocoding features

All APIs are enabled in the Google Cloud Console under APIs & Services → Library.

After installing the modules, go to Settings → Technical → System Parameters and set the value for base_google_map.google_maps_api_key to your Google Maps API key. All map and autocomplete modules read from this single parameter — you only need to set it once.

In the Google Cloud Console, open your API key and configure:

• Application restrictions — set to HTTP referrers and add your Odoo domain (e.g. https://yourodoo.com/*)
• API restrictions — limit the key to only the specific APIs you have enabled (Maps JavaScript API, Places API, etc.)

This prevents your key quota from being consumed if the key value is ever exposed in browser developer tools.

Map views will fail to render and autocomplete fields will not show suggestions. The browser console will log a Google Maps API error. The rest of your Odoo instance is unaffected — only the features that require the API key will stop working.

The Google Maps Suite (16 modules) installs the complete integration across all supported Odoo apps in one go — Contacts, CRM, Sales, Inventory, and Projects.

The individual sub-product suites install only the foundation modules and the application modules for a specific Odoo app. For example, the Sales Google Maps Suite (3 modules) installs only base_google_map, web_view_google_map, and sale_google_map — nothing else.

Choose the Full Suite if you want everything immediately. Choose individual suites if you want a minimal footprint or are rolling out app by app.

When the web_widget_google_place_autocomplete widget is active on a form, typing in the address field sends the input to the Google Places API (New) and shows a dropdown of matching places. Selecting a result populates all address fields — street, city, state, postal code, country — plus coordinates, phone, and website, all in a single selection.

Field mapping is fully configurable via the google.places.mapping configuration model, so you can control exactly which Google Places fields map to which Odoo fields.

Yes — the base_google_map_add_place foundation module provides a click-to-create mixin. Application modules that include this feature (Contacts, CRM) show a + button on the map toolbar. Clicking a location on the map opens a quick-create dialog pre-filled with the address from Google Places, letting you create a new Contact or Lead directly from the map without leaving the view.

The foundation layer provides three map view types:

• Map list view (web_view_google_map) — displays records as markers on a full-page Google Map, with a sidebar listing. Supports clustering, filtering, and record navigation.
• Embedded map widget (web_widget_google_map) — renders a Google Map inline on a form view, showing the record's location. Supports satellite view for site-based records (used in Project Google Maps).
• Drawing view (web_view_google_map_drawing) — adds a full GIS-style drawing toolbar to any model, enabling users to draw, edit, and store geographic shapes (polygons, rectangles, circles, lines, points) as GeoJSON directly on a Google Map.

Yes — all modules are licensed under LGPL-3 (GNU Lesser General Public License v3). The license grants you the right to use, modify, and distribute the code, and ensures that modifications to the module source itself remain open under the same license — while your own proprietary Odoo code that uses the modules as a library is unaffected.

The source code is hosted on a private GitHub repository. Access is granted upon purchase — you receive an invitation to the repository as part of the onboarding process. The code is not publicly browsable without purchasing a license.

The main ongoing cost is your Google Maps Platform account. Google bills based on API calls (map loads, geocoding, Places requests). The $200/month free credit covers most small-to-medium Odoo deployments at no charge.

The modules themselves carry no subscription fee after purchase — you pay once and own the code under LGPL-3.

Yes. Under LGPL-3 you can install and use the modules in your clients' Odoo instances. Each client deployment will need its own Google Maps API key registered in their Google Cloud account — Google usage is billed per account.

If you modify the module source code, those modifications must be made available under the same LGPL-3 license, but your own proprietary code that uses the modules as a library is not affected.

Yes — this is an explicit design goal. The foundation layer provides reusable, model-agnostic building blocks:

• web_view_google_map view type — declare a map list view in XML like any other Odoo view, on any model with latitude/longitude fields
• web_widget_google_map form widget — embed a Google Map on any form field
• web_widget_google_place_autocomplete widget — add Google Places autocomplete to any address field
• google.drawing.shape mixin — add GeoJSON drawing capability to any custom model
• google_map.add_place.mixin — enable click-to-create from the map on any model

Apply them to any custom Odoo model by adding field declarations and a few XML view lines — no custom JavaScript required to get a working map view.

Everything follows standard Odoo conventions:

• New view types registered via the standard Odoo view registry
• API key management via ir.config_parameter
• All frontend components in OWL — Odoo's standard JavaScript framework
• Geocoding integrated through Odoo's native geocoder provider system
• No monkey-patching of core Odoo code
• No non-standard Python packages required

The key is stored in ir.config_parameter and sent to the browser as part of map initialization — standard behavior for a browser-facing Maps API key. To restrict its use to your domain, configure HTTP referrer restrictions and API restrictions in the Google Cloud Console. This prevents unauthorized use even if the key value is visible in browser developer tools.