| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Field Service (industry_fsm)
• Project (project) • Discuss (mail) • Timesheets (timesheet_grid) • Employees (hr) • Sales (sale_management) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 793 |
| Technical Name |
fsm_reports |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Field Service (industry_fsm)
• Project (project) • Discuss (mail) • Timesheets (timesheet_grid) • Employees (hr) • Sales (sale_management) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 793 |
| Technical Name |
fsm_reports |
| License | OPL-1 |
| Website | https://www.ganemo.co |
FSM Reports
Field Service Analytics & Intelligence
Know exactly how many visits were executed, how many became sales, and how much revenue your field team generated — broken down by salesperson, customer, and month.
What We're Solving
----------------
No Visit Tracking
Without this module, there is no native way to aggregate executed vs. not-executed visits per salesperson in a pivot or graph. Supervisors have to manually count through task lists.
Visit-to-Sale Gap
Managers couldn't quickly see which executed visits generated a confirmed sale and which didn't — or understand why using the captured lost reasons.
No Privacy by Default
FSM users could potentially see data from other salespeople. This module enforces row-level visibility: users see only their own assigned tasks; managers see everything.
Revenue from Field
Directors had no dedicated report to see total sales revenue generated by field visits, broken down by customer, salesperson, and month in a single pivot table.
Setup & User Manual
Step-by-Step implementation
1. Installation
Install this module alongside its dependencies:
- industry_fsm — Native Field Service
- industry_fsm_sale — FSM + Sales integration
- auto_cancel_fsm_task — Adds the not_executed flag
- fsm_sale_lost_reason — Adds the lost_reason_id field
2. Accessing the Reports
Navigate to Field Service → Reporting and find three new sub-menus:
Efectividad de Visitas
Pivot by salesperson × month. Measures: Executed, Not Executed. Bar chart stacked view.
Conversión → Venta
Of executed visits, how many generated a confirmed SO. Includes lost reason analysis.
Análisis de Ventas
Revenue amounts by customer × salesperson × month. Manager access only.
3. Row-Level Security
FSM User (group_fsm_user):
- Sees only rows where they are the assigned salesperson
- Access to: Efectividad and Conversión reports
FSM Manager (group_fsm_manager):
- Sees all rows across all salespersons
- Access to: all 3 reports including Análisis de Ventas
Global Ready | Multi-Language Support
This module is fully translated into English and Spanish (en_US, es_ES, es_PE, es_MX).
Why Choose Ganemo?
----------------
Ganemo is the world's leading Odoo App developer and a multi-award-winning Gold Partner. For over 5 years, we have been recognized as the #1 seller of high-quality apps on the Odoo App Store. Trusted as the "Best Partner" in USA, Mexico, Chile, Spain, Colombia, Ecuador, and Peru, we deliver robust, secure, and localization-compliant solutions.
QA / User Testing Scenarios
Enterprise Validation Plan
Scenario 1: Row-Level Security (User)
- Log in as an FSM User (group_fsm_user) assigned to Task A.
- Go to Field Service → Reporting → Efectividad de Visitas.
- Expected: Only rows where the user is the salesperson are visible.
- Log in as a second FSM User assigned to different tasks.
- Expected: Each user sees only their own data — no cross-contamination.
Scenario 2: Manager Full Access
- Log in as an FSM Manager (group_fsm_manager).
- Go to Field Service → Reporting → Análisis de Ventas.
- Expected: All rows from all salespersons are visible.
- Apply group-by: Salesperson. Expected: All agents appear in the pivot.
Scenario 3: Visit Conversion Accuracy
- Create an FSM Task assigned to User A. Mark it as executed (not not_executed).
- Create and confirm a Sale Order linked to that task.
- Go to Conversión → Venta. Filter by User A.
- Expected: Row shows has_sale = True and correct sale_amount_total.
- Create another executed task without a SO — Expected: Row shows has_sale = False.
Scenario 4: Lost Reason Grouping
- Create executed FSM Tasks without SO, fill the lost_reason_id field.
- Go to Conversión → Venta.
- Apply filter "Sin Venta" and group-by "Motivo No Venta".
- Expected: Rows correctly grouped by lost reason with correct counts.
FAQ & Troubleshooting
Common Resolutions
Report shows no data?
Reason: The report filters FSM tasks only (is_fsm = True, active = True, no subtasks).
Fix: Ensure the project has FSM mode enabled and tasks are assigned to users.
I can't see the "Análisis de Ventas" menu?
Reason: This report is restricted to FSM Managers only.
Fix: Ask an administrator to assign you to the group_fsm_manager group.
Task shows duplicate rows in pivot?
Reason: A task with multiple assigned users generates one row per user — by design.
This is intentional for the record rule to work. Group by Task to de-duplicate.
Sale amounts look too large?
Reason: If a task has multiple users and multiple SOs, amounts multiply per user row.
Fix: Always group by Task + Salesperson when analyzing amounts per visit.
Get a Quote & Resolve Commercial Doubts
Join thousands of satisfied clients on Odoo. Contact our sales team directly.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Schedule Meeting
Need More? We Do It All
Professional Odoo Services
ERP Implementation
Full Odoo implementation including FSM, Sales, Inventory, and Accounting. We analyze, configure, and train your team.
Module Dev & Migration
Custom modules, report tailoring, and migration to Odoo 19 with zero data loss. Expert Odoo developers at your service.
Commercial & Sales
For inquiries about licenses, demos, or partnerships.
Official WhatsApp
+1 (828) 672-6150
Sales Email
leads@ganemo.com
Book a Demo
ganemo.co/appointment/5
Technical Support
Existing customers regarding module functionality.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module