BeatRoute New Features (Release 9.5.0 - Narmada)

We are excited to announce Release 9.5.0 (codenamed Narmada) of our Sales Team Android App and Brand Panel, launching this week. This release introduces batch-level sales execution and inventory tracking, additional conditions in the Cumulative Scheme Engine, new Attendance Module, and improvements to Joint Visit Module.

1.  Introducing Batch Management for Inventory and Sales

BeatRoute now supports batch-level inventory tracking, designed for industries like Pharma, FMCG, where stock is managed by batch to support expiry management at batch level and compliance requirements.

If inventory is managed at batch level, then users can place primary orders for specific batches, take secondary orders, take returns & mark dispatches at batch level. Ready stock users can be issued stock at batch level & users will be able to see which batch stock they are carrying in their Van, and take orders by batch.

2. Additional Conditions in Cumulative Schemes

We have introduced an Additional Conditions bucket for Cumulative Schemes in our Trade Promotions Module. This will help add additional special conditions. In this release, we have started with two important additions that give you more precision in how trade schemes are structured and evaluated.

• Focus Product Mix Condition: A new condition type that allows you to enforce a minimum threshold % or value of focus products in overall billing. This is a commonly required condition in trade schemes to ensure certain products remain a meaningful part of a customer’s purchase.

• Additional Conditions for End-of-Period Schemes: Additional conditions were previously only available when schemes were evaluated on every new transaction (orders). They can now also be applied when schemes are evaluated at the end of the scheme period (dispatches), removing a key gap in scheme configuration.

3. New Attendance Module with Activity Based Attendance

We are transforming the Attendance module from simple time-span detection into an activity based attendance module that puts more emphasis on the quality of work. Secondly, we are introducing holiday calendar and the concept of fractional attendance to make it payroll-ready.

• Minimum Norms for Attendance: Admins can now optionally define Full Day, Three Quarter Day, Half Day, and Quarter Day criteria for each designation — based on metrics like total calls, productive calls, first visit time, schedule adherence, joint visits, and more. Only selected metrics are evaluated per norm.

• Fractional Attendance: Attendance is now calculated as 0, 0.25 (Quarter Day), 0.5 (Half Day), 0.75 (Three Quarter Day), or 1 (Full Day) rather than a simple present/absent flag.

• Holiday Calendar: Public Holidays (configured at org level) and Weekly Holidays are now part of the attendance engine. Activity on these days does not override the holiday status.

• Leave Supremacy & Leave Cap: Approved leaves are supreme. If a user is on full leave, attendance is 0 regardless of activity. Half and quarter leaves cap attendance at 0.5 and 0.75 respectively, with norms evaluated only for the remaining working portion.

• Reporting Changes: Attendance Summary Report now uses standardized abbreviations (FD, HD, QD, AB, SL, CL, OL, PH, WH). The Report Builder’s User Availability Analysis data source is also updated.

• Backward Compatible: All existing customers will be auto-migrated with a minimum leave unit set to Full Day and norms disabled, so there is no change in existing attendance behavior unless you choose to configure norms.

• API changes?

4. Joint Visit Now Goes from Reporting to Active Facilitation

As of now, Joint Visits report was available, derived automatically from visits done together by frontline and their managers. This release takes Joint Visits from post-facto reporting to active facilitation to execute Joint Visits more intuitively.

• Start a Joint Visit Session: Managers can initiate a joint visit session from the Sales Team App Homepage and add one or more members they are going with. Selected members receive a confirmation pop-up to accept or reject the joint visit. Once accepted, an active session banner is visible to all participants.

• Automatic Joint Visit Tagging: Visits are automatically tagged as joint visits when session participants have overlapping check-in and check-out times at the same customer. Geo-fencing provides the location validation — no additional GPS verification is needed.

• Real-Time Nudging: When one participant checks in at a customer, others in the session receive a real-time notification prompting them to check in as well, reducing missed joint visit tags.

• Reporting & Analytics: Joint visit data is now reflected across Daily Rigor, Team Productivity & Adherence Report (new Joint Calls column), Pocket MIS, and Report Builder (Customer Activity Analysis data source). Use cases enabled include coaching intensity by manager, region-wise engagement, and joint visits vs productivity analysis.

• Session Rules: Only one active joint session per initiator at a time. Multiple sessions can be run in a day with the same or different users. Sessions auto-end when any participant ends their day.