July 3, 2020 | 02 min read
Share:
Have you ever thought about why retailers buy your products?
I was working with a medium-sized FMCG company that had legacy issues regarding the service. Distributors and sales teams had very high attrition rates, and sales were miserable. The challenge was to increase sales by 300% in one year. How did I do it?
I followed simple six steps and surpassed the target by achieving more than 450% growth in one year. You can follow the same six steps while onboarding retailers on the Bizom Retailer App.
1. Identify: To begin this, we need to identify which area is most suitable for us to digitise the retailers. How is our distribution network in that area? If the answer is satisfactory, pin it down to two areas with a handful of distributors. These two areas should be under different regional managers. E.g. A packaged food company decided to go live with the Retailer App in two states – Karnataka and Chattisgarh. The reason was that the brand had good relationships with channel partners in the two states. Also, sub-stockists had less than 100 outlets under them, while a majority of retailers had Android smartphones.
2. Communicate: All strategies are path-breaking. What makes them great is execution. 95% of strategies fail because of a lack of understanding of the objective. The management team needs to make a clear communication plan on why they are enabling the retailer app. The communication should go to all stakeholders, including distributors, and they need to be taken on board. Brands can take cues from the Atmanirbhar campaign. E.g. The packaged food company hosted two live webinars, one with all the concerned sales team and another with sub-stockists and super stockists. Made them understand their vision and road map. Also addressed all concerns of the channel partners regarding claims, schemes, incentives, etc.
3. Incentivise: Like Flipkart and Amazon lured their initial customers by giving massive discounts to encourage online ordering, and providing schemes to retailers. It can be a 2-3% discount on app-only orders. It should be backed by incentives to distributors as well for fulfilling the app-only orders in a stipulated time, generally within 36 hours. Incentives can be points that can be redeemed by giving gifts like television, mobile handset, mixers, bikes, etc. Give incentives to salespeople as well for encouraging their retailers to self-order (Atmanirbhar).
4. Engage and address grievances: When the status quo is changed, there is bound to be resistance. Brands should proactively talk with all the stakeholders (sales team, distributors, and retailers). Understand their pain points or grievances and address them. E.g. After one week, the management held a web conference again and took stock of first-hand information from the ground. They also sought suggestions from all the stakeholders.
5. Follow up: Most critical part is following up with steps 2 to step 4 persistently. We tend to give up one or two attempts. Success comes from consistently doing the same thing and not from early successes. E.g. The packaged food company addressed all the concerns of the channel partners and sales team within 48 hours. It took measures to communicate with all stakeholders and held a web conference to follow up on the progress. It helped communicate to the channel partners that management was serious about the new way of working.
6. Expand: After trying out one geography and overcoming all unseen challenges, it is time to expand to new geographies. While doing that, it is vital to document all experiments and learnings and share them with the team. By not repeating the same learning curve, going to market becomes quick and effective. E.g. After a successful launch in two districts, the company expanded into all districts under the same two ASMs along with a few ASMs under the same RSMs. It shared the learning with other RSMs to help them implement the retailer app in their regions.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
collect_chat_launcher_load | 1 month | This cookie is set by the provider Collect.chat. This cookie is used for enabling the chat function on the website. |
collect_chat_page_load | 1 month | This cookie is set by the provider Collect.chat. This cookie is used for optimizing the chat-box functionality by recognising the user. |
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 16 years 4 months 14 hours 16 minutes | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gat_gtag_UA_34263932_3 | 1 minute | This cookie is set by Google and is used to distinguish users. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
Cookie | Duration | Description |
---|---|---|
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
yt-remote-connected-devices | never | These cookies are set via embedded youtube-videos. |
yt-remote-device-id | never | These cookies are set via embedded youtube-videos. |
yt.innertube::nextId | never | These cookies are set via embedded youtube-videos. |
yt.innertube::requests | never | These cookies are set via embedded youtube-videos. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |