HomeModulesCRM & MarketingGeo Map View: CRM
Geo Map View: CRM
CRM & MarketingAuraOdoo Verified

Geo Map View: CRM

Puts the CRM pipeline on the map: leads as markers coloured by stage or probability.

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
LGPL-3
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
2462 lines (Python / XML / JS)

Overview & Description

Odoo 19 Odoo 20 Community and Enterprise LGPL-3 Version 19.0.1.0.0 Geo Map View: CRM Puts the pipeline on the map. Opportunities as markers coloured by stage, or as a heat ramp of where the winnable business is. The bridge between Geo Map View and CRM. It installs itself as soon as both are present, gives leads their own coordinates, and adds a Pipeline Map with two ready-made styles. Requires Geo Map View Requires CRM Installs automatically Module Overview A small bridge that answers a question a list cannot. What it adds A pipeline sorted by expected revenue tells you what is worth most. It does not tell you that eleven of your open opportunities are within an hour of each other, or that a territory you thought was covered has nothing in it at all. This module gives a lead its own position, puts the pipeline on a map, and colours the markers by stage or by probability. It is a deliberately small bridge: everything that draws, styles and layers the map lives in Geo Map View, and this only teaches CRM to speak to it. At a glance Coordinates on the lead itself Leads join the geocoding queue A Pipeline Map view and menu Markers coloured by stage A 0 to 100 probability heat ramp Position fields on the lead form Installs itself with CRM present Key Features Four things, done properly. The lead's own coordinates A lead gets a latitude and a longitude of its own, and joins the geocoding queue that fills them in from an address. They live on the lead rather than being read through the customer, because a lead very often has an address long before it has a customer at all. The Pipeline Map A map view and its own menu entry, showing open opportunities as clustered markers with the fields you care about in the popup. It is a view, so the ordinary CRM filters and group-bys apply to it, and it sits next to list and kanban in the switcher. Coloured by stage A Pipeline stages style ships ready to use, with a rule per stage. Set your own colours once and every map that uses it agrees. New stages fall to the Others catch-all rather than disappearing. Coloured by probability A Lead probability gradient from 0 to 100, so the map reads as a heat map of where the winnable business is. The legend is generated from the ramp, so nobody has to explain what the colours mean. Business Benefits What a sales manager gets out of it. Plan a week of visits Opportunities that are near each other are obvious on a map and invisible in a list sorted by revenue. See the gaps A territory with nothing in it is a hole you can point at, which is harder to argue with than a number. Assign by geography Put your sales regions on as a layer underneath and the right owner for a lead stops being a guess. Spot the concentration The probability ramp shows where the pipeline is genuinely warm, not merely where it is numerous. Screenshots What the module looks like in use. The Pipeline Map Screenshot placeholder Opportunities as clustered markers, coloured by stage, with the popup open on one of them. The probability ramp Screenshot placeholder The same pipeline read as a heat map, with the generated legend. A lead's position Screenshot placeholder The coordinate fields on the lead form, shown to a Geo Map Administrator. Territories underneath Screenshot placeholder A GeoJSON sales-region layer from the engine, with the pipeline drawn on top of it. Workflow From a pipeline to a map of it. Step 1 It installs itself With CRM and Geo Map View both present, this module is picked up automatically. There is nothing to tick. Step 2 Leads get located A new lead against a located customer starts on that customer's position. The geocoding queue fills in the rest from their addresses. Step 3 Open the map Maps, then Pipeline Map. The usual CRM filters apply, so a single team or a single month is one click away. Step 4 Colour and layer it Pick the stage style or the probability ramp, and put your own territories underneath as a layer from the engine. Configuration Two styles to adjust, and nothing else required. What ships, and what you change Item Where What to do with it Pipeline stages Maps, Configuration, Styles A rule per stage. Set the colours you want; new stages fall to the Others catch-all. Lead probability Maps, Configuration, Styles A gradient from 0 to 100. Change the two ends and the ramp between them follows. Pipeline Map Maps The view itself. Add fields to the popup or change the style it opens with. Geocoding Scheduled Actions Shared with the engine. Off by default; enable it once and leads are queued with everything else. The coordinate fields are for administrators. A lead's position sits on the form behind the Geo Map Administrator group, so a salesperson sees the map without being handed two numbers they have no reason to edit. Technical Details A bridge, and deliberately nothing more. Module Technical name aura_geo_map_crm Version 19.0.1.0.0 Category Sales / CRM Depends on aura_geo_map, crm Auto install Yes, once both dependencies are present Licence LGPL-3 Python packages None Models added None. It extends crm.lead and adds data. What it touches Where What is added crm.lead The geocodable mixin: coordinates, queue state and the address parts to geocode Lead form The position fields, behind the Geo Map Administrator group Views A geomap view over the pipeline Menus Pipeline Map, under Maps Data Two styles: Pipeline stages, and Lead probability Two decisions worth knowing The lead's address, not the customer's. A lead often has an address long before it has a customer, and once it has one the two can legitimately differ: the site being sold to is not always the billing contact. So the geocoder reads the lead's own street, city, state and country. The customer's pin only seeds a blank. A new lead against a located customer starts on that customer's coordinates, which is a useful head start. But once a lead has a pin of its own, set by the queue or by hand, reassigning the contact never moves it. Compatibility Where this module runs. Item Supported Note Odoo 19.0 Yes Built and tested on 19.0 Odoo 18.0 and earlier No Follows the engine, which is 19.0 only Odoo Online Yes No external package and no system access Odoo.sh Yes Install as a normal custom module On premise Yes Drop into the addons path and update the apps list Enterprise Map app Yes Different view name, so both can be installed Multi company Yes The map follows the record rules on crm.lead Supported Editions Community is enough. Supported Odoo Community 19.0 CRM is a Community app and so is the map engine, so the whole of this works on Community, which has no map view of its own. Supported Odoo Enterprise 19.0 Installs and runs unchanged, alongside the Enterprise Map app rather than in place of it. Geo Map View is required. This module is the CRM bridge to it and does nothing on its own. Install the map engine and CRM, and this is picked up automatically. Installation Usually nothing to do at all. Copy the module folder into your addons path, next to Geo Map View. Turn on developer mode, then choose Apps and Update Apps List. Install Geo Map View if it is not there yet. With CRM already present, this bridge installs itself at the same time. Open Maps, then Pipeline Map. Leads whose customer already has coordinates are on it straight away. Enable Geo Map: Geocode Addresses under Scheduled Actions to fill in the rest from the leads' own addresses. Open Maps, Configuration, Styles and set the colour on each of your pipeline stages. Nothing here needs a mapping key or an external service beyond the geocoder the engine already uses. Frequently Asked Questions The questions asked most often. No. It is an auto-installing bridge: as soon as both CRM and Geo Map View are on the database, Odoo picks this up on its own. It is listed separately so you can see what it does and uninstall it if you would rather not have it. The lead's own. A lead usually has an address long before it has a customer record, and once it has one the two can legitimately differ: the site being sold to is not always the billing contact. Only if the lead had no pin of its own. A new lead against a located customer starts on that customer's coordinates as a head start, but once the lead has been positioned by the queue or by hand, reassigning the contact leaves it exactly where it is. Yes. Two styles ship, stage and probability, and a style is an ordinary record in the engine. Build one over expected revenue, salesperson, team or anything else on the lead, and point the view at it. Yes, and that is where this gets useful. Add your boundaries as a GeoJSON layer in Geo Map View and they sit underneath the markers on any map, this one included. They have no coordinates yet. Enable the geocoding scheduled action and the queue works through them at a rate the geocoding service allows. A lead with no address at all cannot be placed and stays off the map until one is entered. No. It adds coordinates, a view, a menu and two styles. Stages, scoring, assignment and every other part of CRM behave exactly as they did. Changelog What has shipped. 19.0.1.0.0 First release Coordinates on crm.lead, and leads in the geocoding queue A Pipeline Map view and menu A Pipeline stages style, with a rule per stage A Lead probability gradient from 0 to 100 Position fields on the lead form, for administrators Auto install once CRM and the map engine are both present Support Documentation lives with the engine. Shared guides Installation, user guide, technical guide, testing and troubleshooting all ship inside Geo Map View. Free support 90 days of support on installation, configuration and any defect found in the module. Customisation Territory assignment, routing or a map on another sales model, quoted before any work starts. Aura Odoo Tech www.auraodoo.tech Geo Map View: CRM Odoo 19 aura_geo_map_crm LGPL-3 Copyright Aura Odoo Tech. All rights reserved.

Key Capabilities & Features

  • Coordinates on the lead itself
  • Leads join the geocoding queue
  • A Pipeline Map view and menu
  • Markers coloured by stage
  • A 0 to 100 probability heat ramp
  • Position fields on the lead form
  • Installs itself with CRM present
  • Copy the module folder into your addons path, next to Geo Map View.
  • Turn on developer mode, then choose Apps and Update Apps List.
  • Install Geo Map View if it is not there yet. With CRM already present, this bridge installs itself at the same time.
  • Open Maps, then Pipeline Map. Leads whose customer already has coordinates are on it straight away.
  • Enable Geo Map: Geocode Addresses under Scheduled Actions to fill in the rest from the leads' own addresses.
  • Open Maps, Configuration, Styles and set the colour on each of your pipeline stages.
  • Coordinates on crm.lead, and leads in the geocoding queue
  • A Pipeline stages style, with a rule per stage
  • A Lead probability gradient from 0 to 100
  • Position fields on the lead form, for administrators
  • Auto install once CRM and the map engine are both present
  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

1 image available
Geo Map View: CRM screenshot 1
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.