The report contains the No sales Reasons of the outlets where there were no sales done by the Employees (Non-Productive Outlets). This helps the team to find out the exact reason of No sales in a particular area or overall in the company.
Report Logic:
1. This report fetches the live data. That means, Hierarchy of the Field Users will reflect as per the current mapping.
2. Summary of active Field Users will reflect.
Date Range Filter: Yes. Up to 31 Days.
The report contains 2 Tabs:
- Summary
- Details
Summary: The Tab contains summarized data of No sales Reason. It reflects the count of each NO Sales Reason for the selected date range. This helps in doing analytics on reasons why order were not taken on retailer visit made by the field users.
Understanding the Headers in the sheet (from left to right):
Reason Category: The category selected by the Employee while filling No Sales Reason Issue. The Category can be also customized as per the requirement by the Company. For this, One needs to get in touch with the Account Manager.
Reason: Actual Reason as why the Sales was not done.
Visit Count: Number of times the particular reason was filled for a No Sales Outlet in the selected date range.
Percentage: % Ratio of that particular No Sales Reason among all the No Sales Reason filled in the selected date range.
Detailed: The tab contains detailed explanation of No Sales Reasons Outlet wise for the selected date range.
Understanding the Headers in the sheet (from left to right):
- Date: Date for which the retailing/non-retailing activity is checked for a user.
- Header (2-6) Employee Hierarchy: Hierarchy of a Field User. For Ex: ZonalSalesManager (Level-4) > RegionalSalesManager(Level-3) > AreaSalesManager(Level-2) > Reporting Manager (Whom the user is reporting) > User.
- User Rank: Rank of the user at which he is present in Company Hierarchy.
- Employee Contact No.: Contact no. of the user by which he is registered in the system.
- Visit Time: The time when No Sales Reason was punched.
- Beats ERP Id: A unique ID to represent that beat. Beat name can be same but the ERP id is unique and carries the identity of that beat.
- Beats: Name of the beat on which the Order has been done.
- Outlet ERP Id: A unique ID to represent that Outlet. Outlet name can be same but the ERP id is unique and carries the identity of that outlet.
- Outlets Name: Name of the outlet on which the Order has been done.
- Outlets Address: Address where the outlet is present.
- 4. Outlet Segmentation: Segmentation of the outlet based on the Potential of the outlet. Segmentation can be based on the Revenue generated by the outlet/Product space in the outlet/Competitors Product Sales from the outlet.
- Owner No.: Owner contact number.
- City: City where Outlet is present.
- No Sales Reason Category: : The category selected by the Employee while filling No Sales Reason Issue.
- No Sales Reason: Actual Reason as why the Sales was not done.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article