The updates and capabilities mentioned below are available at the end of October first week.
1. Now Track Product Sellout through Customer Network
So far it was only possible to report sellout from a store only against a consumer (like it happens in modern trade channel where a promoter marks sellout to consumers walk-ins).
Now with this release store/customer sellout can be tagged to other customers who are part of the network
(For example sales team can now report offtake at wholesalers against retailers connected to that particular wholesalers, Or in agri-input industry, sales team can now report offtake at distributors against retailers/dealers connected to that particular distributor)
This change opens us to the possibility of our clients being able to track their products down the supply chain till they reach the end consumer & offer rewards at product scan at different levels in the supply chain.
Following features have been added to this workflow available via configurations -
(i) Record log sales with an Option to Change UOM -> Now users can record offtake in alternate UOM. No. of scans will be equivalent to quantity in terms of selected UOM.
(ii) Log Sales directly by Product Scan -> Users will not need to enter or search products manually, if product serial nos are updated in beatroute & system is able to read serial no from QR code scan (There is a configuration built in system to configure this already) then system will validate the reported offtake directly from QR code scan. Default unit for the scanned item will be considered as selling UOM with an option with the user to change. This will only work as an online functionality, if the user is offline then the present way will continue to function.
(iii) Now Report Offtake Against Associated Customers -> Till now in BeatRoute, offtake could only be recorded against a consumer. There are cases where offtake needs to be marked to other customers. Now offtake can be marked to a customer entity from another customer in BeatRoute. This will enhance visibility of sales even at tertiary level & down.
Associated Impact on Inventory -> This will increase inventory of associated customers and reduce the inventory of entities at which log sales is marked. In terms of impact on “Customer stock/Inventory” report for customer on whom log sales is marked this is an outbound transaction while for the other associated customer this is an inbound purchase transaction.
Transaction type for the customer on whom log sales is recorded -> Sales_log (Same as present)
Transaction type for the customer on whom log sales is marked against -> Tertiary_purchase (New transaction type introduced to handles such cases).
Associated changes in Reports & Dashboard are as following -
2. Payment CSV Download ->
There is a column with the name “activity by user” where it updates the user once payment status changes. So the present version of the report loses visibility on who collected how much.
We have renamed the column “activity by user” which is column L in Payment report with “collected_by”. It will just be who collected the payment and it will not change even when payment status changes. We have also added one additional column which is “payment_status” in the present report. This will show what is the status of a particular payment in terms of pending for approval/approved etc.
We at BeatRoute are committed to continuous refinement of the platform for our users to drive their business goals better. Thank you for your continued support.
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