In today’s hyper-competitive grocery environment, collaboration between retailers and CPGs is more than just a “nice to have”; it’s a genuine strategic enabler, something that can help tackle a diverse set of challenges that range from profitability through to the quality of the customer experience.
As impactful as it can be though, collaboration – and specifically shopper first collaboration – doesn’t just happen. To ensure that their efforts are successful, and conducted with their customers’ best interests in mind, retailers and brands need access to the granular, individual shopper-level data that can help them hone their strategies based on real insight rather than gut feel.
The unique value of retailer-owned data is clearly recognised within the industry itself. Asked to specify which data sources they believed would prove most useful to their future collaboration efforts, more than three-quarters (77%) of respondents to a recent dunnhumby study put shopper-level data in their top three. While online browsing data and syndicated EPOS data placed second and third, they enjoyed significantly less support in comparison (53% and 48% respectively).
As heartening as this is for a business that works regularly with that kind of data and can testify to its transformative impact, we do see some cause for alarm here too. Clear though the importance of retailer-owned data may be, there’s a difference between appreciating its value and actually being able to capture or scrutinise it.
To turn insights into action, and to put their data to work in service of the customer, retailers need to work collaboratively and transparently with their suppliers – making decisions based on what’s right for shoppers rather than just margin or sales data.
As much as they might like to, though, many retailers still can’t do that, lacking the systems they need to collect shopper-level data and “democratise” it in a way that makes it usable by their CPG partners. That has significant implications from a collaboration perspective, and heightens the importance of implementing a fit-for-purpose data strategy that can support a constructive dialogue between the retailer and its partners.
Creating a collaboration-ready environment
The importance of understanding customers in terms of their individual purchasing behaviours can’t be understated when it comes to collaborative planning. By blending their own data with the expertise and brand equity of their supplier partners, retailers can drive a fundamental shift in their ability to communicate with shoppers and execute effectively against their needs.
Achieving that kind of harmonisation, however, means having the right processes and structures in place when it comes to data. Namely:
The last of these points is particularly important. So long as they have access to it, CPGs can complement shopper-level data with their own insights and learnings. That includes sources such as market-wide sales data, household panel data, and other quantitative and qualitative research, all of which can help to create more sophisticated, shopper-relevant brand and category strategies.
Moreover, with the right arrangements in place, CPGs can effectively serve as an extension of a retailer’s category teams – helping them generate contextual, relevant insights that can be delivered at the shelf. Let’s look at a few examples of how that could work in practice.
1.Combining multiple sources of online data, and working together to understand them
Online purchasing data can be an excellent way to understand how customers shop different categories and brands, particularly when complemented with offline data to create an omnichannel view. That’s not the only kind of online data that retailers can share with their CPG partners, though.
Browsing data, which includes information on how customers navigate a site, what they search for, how they add to their baskets, and more, can be an effective planning tool as well. Used well, it can help CPGs understand how to adapt their range to online only and multichannel shoppers, run media placements in the most effective areas of a site, and simplify product discovery.
2. Tackling the problem of out-of-stocks with a collaborative approach to forecasting
While the extreme disruptions in global supply that resulted from the pandemic may now be behind us, inventory continues to be a complex issue. Getting it right means providing CPGs with the data they need to make better projections about supply, including the ability to highlight any shortages or pressure points in advance.
Done right, that offers benefits for both parties. By minimising the need for substitutions, retailers have a better chance to grow basket spend amongst online shoppers, as well as maximising the efficiency of their online picking operations. In turn, CPGs can improve their profitability by reducing the risk of late shipment penalties.
3. Meeting a breadth of shopper needs with a more targeted range
The danger of adding products to a category based purely on sales performance or margin contribution is that retailers can end up with duplicate-heavy range that over-indexes on the same set of shopper needs. By providing CPGs with data about customer behaviours, retailers can spark more informed and productive discussions about their assortment.
That presents multiple advantages. Firstly, it can help to prioritise and deprioritise items based on their relative importance to, and performance with, customers. Secondly, it can help to prevent items that are important to certain shopper groups from being removed if they begin to underperform from a commercial standpoint. Finally, it can provide the insights required to help retailers arrange their displays in harmony with shopper needs – ensuring that customers can find their preferred products quickly and easily.
As compelling as these examples may be, they’re really just a small snapshot of a much bigger opportunity. And while it might require work – and in some cases, investment – a collaboration-ready approach to data can deliver value all the way from.
Amplify Customer understanding to create strategies that drive results
Customer First solutionsCookie | Description |
---|---|
cli_user_preference | The cookie is set by the GDPR Cookie Consent plugin and is used to store the yes/no selection the consent given for cookie usage. It does not store any personal data. |
cookielawinfo-checkbox-advertisement | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
cookielawinfo-checkbox-necessary | 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". |
CookieLawInfoConsent | The cookie is set by the GDPR Cookie Consent plugin and is used to store the summary of the consent given for cookie usage. It does not store any personal data. |
viewed_cookie_policy | 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. |
wsaffinity | Set by the dunnhumby website, that allows all subsequent traffic and requests from an initial client session to be passed to the same server in the pool. Session affinity is also referred to as session persistence, server affinity, server persistence, or server sticky. |
Cookie | Description |
---|---|
wordpress_test_cookie | WordPress cookie to read if cookies can be placed, and lasts for the session. |
wp_lang | This cookie is used to remember the language chosen by the user while browsing. |
Cookie | Description |
---|---|
CONSENT | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
fs_cid | This cookie is set by FullStory to store the user’s cookie consent preferences for session tracking. |
fs_lua | This cookie is set by FullStory to record the time of the user’s last activity, helping manage session timeouts. |
fs_uid | This cookie is set by FullStory to assign a unique ID to each user and record session replays and interactions. |
osano_consentmanager | This cookie is set by FullStory’s consent management system (Osano) to store the user’s cookie consent preferences and ensure compliance with privacy regulations. |
osano_consentmanager_uuid | This cookie is set by FullStory’s consent management system (Osano) to uniquely identify a user’s consent session for consistent consent tracking. |
vuid | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
yt-remote-device-id | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
_fs_tab_id | This temporary session value is used by FullStory to track user activity across multiple tabs. |
_ga | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_gat_gtag_UA_* | This cookie is set by Google Analytics to throttle request rates and limit data collection on high-traffic sites. |
_ga_* | Set by Google Analytics to persist session state. |
_gid | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_lfa | This cookie is set by the provider Leadfeeder to identify the IP address of devices visiting the website, in order to retarget multiple users routing from the same IP address. |
__q_state_* | This cookie is set by FullStory to track session state and user interactions across page views. It helps rebuild session context for accurate session replay and analytics. |
Cookie | Description |
---|---|
aam_uuid | Set by LinkedIn, for ID sync for Adobe Audience Manager. |
AEC | Set by Google, ‘AEC’ cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user’s knowledge. |
AMCVS_14215E3D5995C57C0A495C55%40AdobeOrg | Set by LinkedIn, indicates the start of a session for Adobe Experience Cloud. |
AMCV_14215E3D5995C57C0A495C55%40AdobeOrg | Set by LinkedIn, Unique Identifier for Adobe Experience Cloud. |
AnalyticsSyncHistory | Set by LinkedIn, used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
bcookie | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognise browser ID. |
bscookie | LinkedIn sets this cookie to store performed actions on the website. |
DV | Set by Google, used for the purpose of targeted advertising, to collect information about how visitors use our site. |
ELOQUA | This cookie is set by Eloqua Marketing Automation Tool. It contains a unique identifier to recognise returning visitors and track their visit data across multiple visits and multiple OpenText Websites. This data is logged in pseudonymised form, unless a visitor provides us with their personal data through creating a profile, such as when signing up for events or for downloading information that is not available to the public. |
gpv_pn | Set by LinkedIn, used to retain and fetch previous page visited in Adobe Analytics. |
lang | Session-based cookie, set by LinkedIn, used to set default locale/language. |
lidc | LinkedIn sets the lidc cookie to facilitate data center selection. |
lidc | Set by LinkedIn, used for routing from Share buttons and ad tags. |
li_gc | Set by LinkedIn to store consent of guests regarding the use of cookies for non-essential purposes. |
li_sugr | Set by LinkedIn, used to make a probabilistic match of a user's identity outside the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
lms_analytics | Set by LinkedIn to identify LinkedIn Members in the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland) for analytics. |
NID | Set by Google, registers a unique ID that identifies a returning user’s device. The ID is used for targeted ads. |
OGP / OGPC | Set by Google, cookie enables the functionality of Google Maps. |
OTZ | Set by Google, used to support Google’s advertising services. This cookie is used by Google Analytics to provide an analysis of website visitors in aggregate. |
s_cc | Set by LinkedIn, used to determine if cookies are enabled for Adobe Analytics. |
s_ips | Set by LinkedIn, tracks percent of page viewed. |
s_plt | Set by LinkedIn, this cookie tracks the time that the previous page took to load. |
s_pltp | Set by LinkedIn, this cookie provides page name value (URL) for use by Adobe Analytics. |
s_ppv | Set by LinkedIn, used by Adobe Analytics to retain and fetch what percentage of a page was viewed. |
s_sq | Set by LinkedIn, used to store information about the previous link that was clicked on by the user by Adobe Analytics. |
s_tp | Set by LinkedIn, this cookie measures a visitor’s scroll activity to see how much of a page they view before moving on to another page. |
s_tslv | Set by LinkedIn, used to retain and fetch time since last visit in Adobe Analytics. |
test_cookie | Set by doubleclick.net (part of Google), the purpose of the cookie is to determine if the users' browser supports cookies. |
U | Set by LinkedIn, Browser Identifier for users outside the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
UserMatchHistory | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
UserMatchHistory | This cookie is used by LinkedIn Ads to help dunnhumby measure advertising performance. More information can be found in their cookie policy. |
VISITOR_INFO1_LIVE | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | YSC cookie is set by YouTube and is used to track the views of embedded videos on YouTube pages. |
yt-remote-connected-devices | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
_gcl_au | Set by Google Tag Manager to store and track conversion events. It is typically associated with Google Ads, but may be set even if no active ad campaigns are running, especially when GTM is configured with default settings. The cookie helps measure the effectiveness of ad clicks in relation to site actions. |