Quantcast StorefrontBacktalk » Blog Archive » What Do Best Buy, Rite Aid Say About Data In A Merging World?
advertisement
advertisement

What Do Best Buy, Rite Aid Say About Data In A Merging World?

Written by Evan Schuman
February 11th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

Some four months after Best Buy dropped $121 million in mid-September 2008 to take over downloadable music pioneer Napster, both companies quietly said that Napster’s privacy policy was changing to let Best Buy do a wide range of unannounced things with the newly obtained data riches. Napster’s CEO, Chris Gorog, went so far as to write a blog that spoke of “personalized music pre-loaded on new MP3 players or mobile phones because of our collaboration.”

Regardless of what Best Buy ends up doing, in today’s rock-bottom economy, with its mergers and bankruptcies, the retail concept of data ownership is getting quite a workout. For example, CompUSA closed its doors but has now reemerged in a very different form in Florida. And there’s no telling where the petabytes (exabytes?) of customer information now controlled by Circuit City will wind up.

From a privacy perspective, there are even scarier possibilities than someone’s music or computer purchases falling into the wrong hands. In a February 6 story, U.S. News & World Report listed 15 major companies that could kick the financial bucket this year and included the $25 billion pharmacy giant Rite Aid on its list. Let’s say, for argument’s sake, that something does happen to Rite Aid. If it gets merged with Walgreens or another pharmacy chain, there’s probably not a huge data impact.

But what if it gets purchased by the nation’s largest seller of pharmaceuticals, a tiny merchant called Wal-Mart? Could Wal-Mart start leveraging that data the way Best Buy is considering Napster’s data?

Let’s take this to the next stage. What if a major drug-maker itself wanted to purchase the chain and use its data to target doctors and consumers prescribing rival drugs? For that matter, what if one of the larger and financially stronger medical insurance companies bought the chain? Or, in the case of a bankruptcy, just the chain’s CRM database?

Retailers have always reserved the right to change or amend their data privacy policies at whim, with little or no notice. These declarations are hardly legally binding contracts with customers. Of course, it wouldn’t matter if they were legally binding, because acquisitions and certainly bankruptcies have almost always voided all contracts.

Therefore, this isn’t primarily a legal concern. Yes, there could be a legal argument that the U.S. Constitution includes an inherent right to privacy. But we don’t even need to go there to find a reason to be nervous about these database transfers. Enlightened self-interest may do the job all on its own. If Best Buy proceeds with an aggressive use of Napster data and, in so doing, alienates lots of Napster customers along with other downloadable music fans, that could devastate the value of its acquisition.

How Next-Gen Consumers See It

This possibility brings up the real issue: Would Napster customers in fact be alienated by even the most brazen abuse of customer purchase data? Are American consumers—especially younger consumers—so cynical today about privacy that it’s almost impossible to alienate them with CRM projects? I’ve noticed a staggering disconnect between senior retail executive perceptions—who project their own discomfort and assume major consumer backlash if the full details of what they do came out–and those of younger consumers who already assume retailers are doing far worse and seem to not care.

I do visiting lecture work at a New York University graduate program dealing with business strategy issues and saw an eye-opening discussion in class last week (February 2). This particular class consisted of students who were mostly in their early 20s, and we were arguing about retail data usage strategies. In a role-playing exercise, the students said they believed American consumers would rebel and abandon retailers if they found out their plans.

We talked about how many retail execs—in the hours after the TJX and Hannaford breaches became known—initially feared financial disaster for both chains based on their belief that customers would quickly abandon them. In the cases of TJX and Hannaford, revenues actually increased slightly for both chains. There was no consumer backlash whatsoever.

Getting back to the class, after a couple of hours of discussion, a scenario was painted where a consumer was sold an especially desired product based on the retailer using highly confidential data. The class was asked, by a show of hands, which students—upon subsequently learning how the sale was made—would have returned the item? Zero hands went up. How many would refuse to shop at that chain any more? Again, a unanimous decision: They’d still shop there.

Weren’t these the exact same students who had just said consumers would rebel? And yet, they themselves wouldn’t. One student speculated that it might have been because the outcome was positive for the consumer. OK. The scenario was changed to have a negative outcome. Specifically, it turned into a car company that jacked up the price of a vehicle upon learning that the consumer just received a huge raise. Another show of hands (would you refuse to accept the car?) and another unanimous verdict in favor of consumers near the end of the ‘00 decade opting for a refresh of an age-old slogan: “Tread On Me.”

Maybe that’s a bit harsh. But no matter the interpretation, it’s clear that many consumers are much more interested in the deals being offered by retailers and less with how they came to be offered. Although sad, accepting that fact is liberating for American retailers.

Note: I have said “American retailers,” because the aforementioned NYU grad class also had several students from other countries (including Turkey, Cuba and Hong Kong), and the non-U.S. students were unanimous in saying that their fellow countrymen wouldn’t be nearly as tolerant as their American friends. But they voted as American consumers, which explains the unanimous votes.

Key Takeaways

So what conclusions should retail IT execs draw from this exercise? Two key ones. First, as we’ve noted before, there are two very different—polar opposite, actually—groups within U.S. consumers. Older consumers who can easily be alienated with aggressive use of data, and younger ones who, as a group, are quite apathetic about how a sales pitch came to happen. If your prospects are a mix of these groups, proceed with extreme caution and insist on opt-in as much as possible. That way, your audience members who want to be excluded can be.

The second takeaway is strictly for younger consumers, and it is that you need to get back to the basics. If the ultimate offer is a good one, proceed. But it needs to make sense for the consumer and to truly be something better than what your competition offers.

These distinctions are liberating, because they will allow retailers to truly experiment with customization, to try and replicate the mythic neighborhood shopkeeper of yesteryear who knew his customers so well that he could anticipate their wants and needs.

This tactic also means delivering true value. Gimmicky promotions using newly acquired CRM data will alienate customers, but not because you used that data. Rather, it is because you used it poorly and because you delivered something that was not worthwhile to the consumer.

Here’s another test case: If a co-worker rifles through the personal things on my desk but uses that knowledge to get me the most brilliantly perfect gift in the world, I’ll likely be fine with it, even if I later learn how that person figured out that I needed this thing. But if that co-worker used that knowledge and then delivered something cheesy, well, forgiveness will be much less apparent.

With that in mind, let’s look at what Napster’s Gorog wrote in his blog: “As we explore options on this front, we expect this combination will provide future enhancements to personalize the Napster experience for our users. For example, we hope to be able to present specialized digital music offers and personalized recommendations based on your Best Buy CD purchases. Determining the number of Napster customers who are also Best Buy Reward Zone members may enable us to create a Reward Zone benefit for Napster Subscribers. Looking even further out, it is possible to envision personalized music pre-loaded on new MP3 players or mobile phones because of our collaboration.”

Music pre-loaded on an MP3 player? What if that purchase history consisted mostly of gifts for others? For that matter, maybe the CRM database is filled with songs this customer bought and decided they hated? Or songs they liked once but now can’t stand? Maybe they’ll want it just to listen to podcasts at the gym?

Wouldn’t it be a better offering to let the consumer log onto the Best Buy site and piece together their customized MP3 files from lists they can choose from? Of course, that wouldn’t involve using any CRM data, and it would also be much more useful to the customer. A classic example of how retailers should not be using such data.


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

What’s The Rush For New PCI Call Center Requirements?

And I have not heard anyone mention the impact on companies who provide quality improvement services. Many merchants hire quality improvement companies to review their audio recordings to provide guidance on how to improve their sales staff’s effectiveness in customer service and sales retention. PCI Council needs to rethink this requirement until there is a widely available commercially viable solution. Read more...
Another ridiculous decision where regulators don't think critically enough about the unintended consequences of their decision. This will be a huge problem for the credit and collections industry. We have to keep all recorded calls for other reasons not related to cc information. We can't purge all of our calls and we don't have the technology to not record part of the conversation. Even if we did, I am not sure we could afford it. Read more...
This "clarification" is causing a lot of panic with large FS clients who now appear to be non-compliant after spending 7 figure sums on their compliance programs. The only alternative to call recording would now appear to be some sort of IVR/push button type interrupt to take card data away from the contact centre. The council is a position to force that sort of process and technology change and this may backfire on them and the vendors that lobbied hard for this clarification. Read more...
PCI council has made a one-sided decision; They should have done a much more in-depth research that could have provided more insight on what regards to the implications of such decision. Read more...

Will Old OS Cause PCI Violation? No, But Marketing Still Says So

This is an interesting issue, because there's more to it than what's apparent on the surface. PA-DSS requires supported and patched operating systems and other software components (e.g., databases, libraries, Java, etc.) per PA-DSS 7.1.b and 8.1, and the option for compensating controls simply isn't there. Merchants can make use of compensating controls for most PCI DSS requirements, but only when legitimate constraints exist and only in ways that meet the intent and rigor of the requirement and go above and beyond the other PCI DSS requirements. Read more...
Why would one automatically upgrade to a "new" OS -- some of the older versions of certain OS-es are more stable and more robust than the crap being peddled today. This is yet another clear example of PCI SSC being out of touch with reality. Rather than requiring a "current" OS, the requirement should be to demonstrate the OS in use is stable and robust, and is adequately hardened against threats. Read more...
There are compensating controls that encrypt the swipe at the driver level as it enter the PC, there are hardware encrypting card swipes so the cardholder data is already encrypted before it comes to the PC -- either of these, especially the second, would remove the OS entirely from a cardholder data risk profile. Read more...
In my opinion, the only thing the vendor did wrong was they didn’t know of that FAQ entry. Even if they did, it changes nothing about the need for merchants to update software that no longer receives updates. Read more...

MasterCard Blinks, Drops Dec. 31 Level 2 PCI Deadline

Reciprocity between MasterCard and Visa was always been a factor in Acquirer merchant level assignments. The brief removal of reciprocity generated a great deal of interest in being able to be classified at a lower level in MasterCard's world. Nevertheless the return of the reciprocity language in the December changes did not effectively create any new Level 2 merchants, but it DID dash the hopes of a lot of them.... :-( Read more...
Let's given them credit??? For being idiotic in the first place? Not on your life! Everyone has just had to scramble and include the costs of the previously announced M/C requirement in their 2010 budgets, and start negotiating with the QSAs for the additional services. All for naught! Read more...
"A bunch of Level 3 and Level 4 merchants just became Level 2s". Is this an accurate statement? MasterCard & Visa have historically included the caveat "or is a Level X in another brand" in their level setting criteria. MasterCard appeared to back way from this in the June pronouncement, and have simply returned to the status quo. Have Acquirers have been tracking and reporting merchants at separate levels by brand? Read more...
I stick by my comment (quoted in the column) about a bunch of L3 and L4 merchants becoming L2s and requiring an onsite. To me, what made MasterCard's original requirement for an onsite assessment for L2s palatable was that they took away their reciprocity provision. That is, they seemed to focus on larger merchants with over a million MasterCard trans/year. With reciprocity in place, a lot of smaller merchants are pulled into the onsite requirement. Rather than causing confusion, I think reciprocity will lead to additional work for processors and acquirers. Read more...

Retailers Sue POS Vendor, Questions Raised Where PCI Duties Stop

I would add a couple more questions: "did the breach involve the use of the default passwords?" (The story doesn't say.) And "were the default passwords used by Computer World to remotely administer the store systems?" "where is the PCI auditor in all this?" Did the restaurant group think they didn't need an audit because Radiant was (mis)representing Aloha as PCI compliant? How is a retailer or even a PCI auditor to know otherwise? A PCI auditor is not necessarily a qualified computer forensic investigator capable of finding the card data on the hard drives. They can only base a decision on information given to them by others. Read more...
There are so many holes in the process it will be difficult to pin blame on just one constituent. It is ridiculous that the technology exists to better secure these transactions (PIN, EMV, etc) yet banks won't use them. Only the banks or government can force this change, and retailers will suffer until then. Read more...
A major issue in this case will be if the restaurants had any support agreements in place with Computer World and if so what those agreements say. In my experience many single unit/small operators choose to skip the support agreements in favor of a "pay as you go" arrangement. In this scenario I can't imagine how the POS VAR can be held responsible for a system they don't own nor exclusively manage. Read more...
There is a big difference in having the POS installation guide say "make sure you set this password because the security of your CHD depends on this" vs. a POS application not storing the CHD in the first place. Traditionally only the merchant was liable for breaches and PCI related fees (fines). Maybe dragging some of the vendors into the liability mud fight will open the eyes of some of these vendors. Read more...

Should Credit Card Transactions Be Free? There May Be A Way

Here in the Netherlands, where the population is notoriously penny-pinching, credit card acceptance is amazingly low. It's both a result of the consumer not wanting to pay interest on everyday purchases as well as merchants not giving up a slice of the action. It is both legal and common to pass the processing fee onto the customer as a surcharge. Now things are moving to leave the credit cards behind: mobile phone payments are becoming more and more common here, and the transaction fees are minimal. Parking and entertainment (movie/concert tickets, nightclubs) have been amongst the first, and it's rapidly gaining momentum because the market has been hungry for the convenience at a price it is willing to pay. Read more...
"Free" is an illusion. Don't charge one person but charge double to someone else. I am very skeptical on anyone who says that advertising will create valid cashflow. Just look at the advertising struggles in a TiVo world. And if you sell your customers data, just be warned that the one group that might have issue with that are you customers (which to me is very important to cashflow. Read more...
Another factor not mentioned here is the impending costs that the processors and issuers are going to incur when someone decides on an end-to-end encryption method, and it then becomes government mandated. I can guarantee that this is a when question and not an if question. The back-end networks are pretty antiquated right now, and it's going to cost billions to replace everything. The cost of tech may be going down, but the cost of replacing millions of servers and hardware, and creating new, proprietary, software is still really expensive. Read more...
Accepting credit cards are not "risk-free" for merchants, contrary to Jim's comments above. Chargebacks are an expense - both in terms of actual transaction reversals and costs associated with managing the process. Chargeback rules and expenses can be everything from a thorny issue to an onerous expense for some merchants, especially for convenience stores that allow customers to pay for gasoline at the pump, or other retailers that allow in-store self-checkout options. Read more...
I've wondered for years why the price of transactions has been so high. Phone companies long ago started offering unlimited calling for flat rates because they understood that in many cases it cost more to report on the transactions (calls) than it did to fulfill them. Read more...
If a home-owner defaults on the mortgage, who is taking the risk? The bank making the loan to the consumer or the person selling the house? It is obviously the bank that takes this risk and is rewarded for that risk through interest rate charges. In my mind, we have mixed together two distinct and unrelated transactions. Read more...
The one big factor not mentioned in this article is who will take over the risk ? Taking credit cards is risk free to merchants and the issuing Banks take the risk if a customer defaults on the payments ! If you had a "interchange free" payment system will the merchants assume the risk ? Also, if there isn't enough profit for the issuing banks they will stop issuing credit cards which will in turn kill our economy. Read more...

The Dangerous Out-Of-Scope PCI Charade

If tokens are ever deemed in-scope, then where does the line stop? I ask this because it would mean that all timestamps, sequential number, random numbers or any other piece of information that may or may not be used to generate a token is within scope -- all data a POS uses and stores, not just payment data. Read more...
Having the ability to do both Tokenization and End to End Encryption (not mere point to point) can have tremendous scope and risk reduction benefits and agility to adapt to change in this fast moving compliance landscape. Being able to have both on tap from a single platform is a solid approach to avoiding the pitfalls. Read more...
But the consumer walks into a particular retail chain, gives their payment card to someone wearing that chain's uniform and the card is swiped. If, six months later, there's a breach and that card was misused, it's the retailer who will in the spotlight. They're the deep pocket and, therefore, the target. If the consumer is angry and wants to cut off business, it will hit the retailer. Therefore, if the retailer is going to end up being blamed no matter what, they have to stay involved. Read more...
True, that someone may be storing a token-to-PAN cross reference. But that would be the bank, not the retailer. If the bank is not sure they can keep their data secure, then there are bigger problems to be addressed than bringing tokens into scope. Read more...
Good general point, Steve, but for the record, not all tokenization is done the same way. Many tokens are associated with lookup lists that allow for them to re-matched to the card data if it's needed, such as for a chargeback. A token doesn't have to be decryptable (is that a word?) for there to be a way to access the original data. Read more...
The out-of-scope argument is very valid but in reference to tokens, the premise of temporarily out-of-scope or abruptly deemed in-scope is flawed. Conway was quoted “anything that could be made unreadable can, in various ways, be made readable again,” this statement is true when talking about encryption technologies (all encryption technologies) but not so with true tokens. True tokens are in no way related to the original data other than as a reference key. Read more...