Your Odoo database already knows where every partner, lead, and order lives — the address fields sit right there on res.partner — but that geography is trapped in list and form views. A sales manager who wants to see which prospects cluster in a region, a field team planning the most efficient visit route, or an operations lead spotting order density by city all end up exporting to a spreadsheet and pasting coordinates into an external mapping tool. Odoo core ships no general-purpose map view in Community, and even where map-adjacent widgets exist they are narrow, hard-coded to a single model, and cannot mix contacts, crm.lead, and sale.order on one canvas. This is where teams that run Odoo hit the wall.

GeoMaps is a productized module ECOSIRE builds to order that adds a true geographic map view to the records you choose. Technically, we add a reusable OWL map component registered as a new view type and wired into the action definitions of the models you nominate — res.partner, crm.lead, sale.order, or your own custom models. We reuse Odoo's existing partner_latitude / partner_longitude geolocation fields where present and add stored coordinate fields where they are missing, populated by a configurable geocoding provider with results cached so the same address is never re-geocoded on every render. Markers are colored and clustered by fields you care about — pipeline stage, salesperson, order state, tag — via standard @api.depends compute methods, and clicking a marker opens the underlying record or a QWeb-rendered popup card.

Under the hood the module is a clean, upgrade-safe addon: a proper __manifest__.py declaring dependencies (base, plus crm / sale only when those models are in scope), models extending the standard ones via inheritance rather than overwrites, ir.model.access.csv plus record rules so map data respects your existing multi-company and salesperson visibility, and server-side batching so plotting thousands of records does not block the web worker. Geocoding can run on demand from the map, in bulk via a server action, or on a scheduled ir.cron job; the same data is reachable over Odoo's XML-RPC / JSON-RPC API for any external system that needs coordinates. It targets Odoo 17.0, 18.0, and 19.0, Community or Enterprise, and adapts to whichever tiles/geocoding provider your policy allows.

Because this is build-to-order, nothing ships until we agree on scope. After a short scoping call we confirm which models and fields you want mapped, your geocoding and tile provider, and your version and edition, then hand you a fixed quotation. Typical delivery is 2–4 weeks from confirmed scope: we build on a branch, deliver to a staging database for UAT, then install on production with a rollback plan and hand over the git repository. Pricing starts from $249 (indicative, single-company base scope); mapping additional models, custom clustering/routing logic, premium geocoding integrations, and large historical geocoding-migration volumes increase the quoted scope.