12
%Increase in Sales Serviceability Ratio
20
%Reduction in Beat length time
11
%Reduction in total number of beats
Across 250M+ orders in 400+ cities
Key Features
Automated beat plan
Sales beat optimization for mobile workforce leading to increased profitability, resource efficiency, and time savings.
Historical data consideration
Field Force Automation by taking historical salesman data into account, such as experience, total revenue generated, the assortment of goods sold, and familiarity with the stores.
Non-overlapping clusters
The non-overlapping clusters created for each 'defined group' ensures zero mirror beats in the output.
Outlet classification
Locus' permanent journey planner takes into account business rules such as type, category and classification of outlets based on revenue, SKU stream sold and historical performance.
Salesman scores
Field Force Tracking to provide individual-level salesman scores and monitoring performances based on historical data.
Geocoding engine
Simplifies and converts ambiguous addresses into exact geographic coordinates through "EVA" (Engine for Validation of Addresses).
Beats accounting for real-life constraints
FieldPro mimics and improvises factors like fatigue, time of day, seasonality, revenue targets etc.
Automated retail fulfilment
Traffic prediction, road constraints, and factors like outlet timing for unloading are considered for optimal daily dynamic route planning for retail fulfilment.
Frequently Asked Questions
-
What is a beat plan?
-
What is a PJ plan?
-
Which industries can benefit from FieldPro?
-
Is FieldPro similar to SFA (Sales Force Automation)?
-
Is the Locus dashboard user friendly for operation/warehouse managers?
-
If my vehicle/rider needs territory mapping, can Locus take care of same?
-
Can I incorporate the static zone in route planning, as change management could be an issue for implementing Locus tool?
-
If API integration is not feasible, what are the other means through which I can use the Locus tool?
-
What are the features available on the Locus delivery app?
-
Our salesmen use an SFA, can Locus take inputs from there?
-
Can you send ETA-based SMS to our outlets?
-
Does Locus factor in the traffic parameter and route restrictions applicable on vehicle types while planning?
-
Can Locus help us in geocode verification?
-
In sales beat planning, what is the core logic behind the allocation of a beat to a salesman?
-
If we have different market operating timings and holidays, can Locus factor that in while coming up with a sales beat?
-
Can Locus help us in figuring out the frequency of outlet visits?
-
How can Locus take care of delivery beats while coming up with sales beats?
-
Is territory optimization part of sales beat planning or is it a different exercise?
-
Can Locus help in improving our serviceability ratio?
-
What is serviceability ratio?

