Skip to main content

My black friday nightmare with Walmart.com

This past black Friday, I decided to do the smart and yet fiscally-responsible thing: shop online for electronics. Our current TV has been making weird noises that I interpret to be death rattles. So what better way to snag a big screen TV than by shopping super early on black Friday. Like a smart consumer, I did my research before hand and found Walmart.com had 2 TVs at really good prices: 47 inch LG for $699 and a 55 inch LG for $898. As soon as it was 12:05am, I logged on to Walmart.com and bummer, the 55 inch was "sold out". I settled on the 47 inch and made the purchase with an AMEX card. Why AMEX? Because they offer free extended warranty on electronics. Done with my shopping, I went to sleep. Woke up around 7am and decided to try the 55 inch again. Luckily it was in stock and I bought it too figuring I'll just return the 47 inch when it arrives. Free shipping on both TVs meant I wouldn't have wasted money on shipping the unwanted 47 inch. I was feeling very proud of myself. I had managed to snag the item I wanted for an incredibly low price. Little did I know that my nightmare with Walmart.com (I keep saying Walmart.com because this story involves the online part of Walmart) had just begun.

A few hours later, my phone chirped to signal a new email. The email said my order for the 55 inch TV had been canceled. No reason given. They just canceled my TV. My first thought was "this is probably AMEX trying to protect me because they think making 2 large purchases so close together is suspicious". So I called them and they were like "Nope, everything is good on our end. In fact, I just put through a $1000 authorization as walmart and it went through. Everything is good here." Hmmm, that's weird. Why would Walmart cancel the 55 inch and ship the 47 inch when both orders were purchased on the same Walmart.com account using the same credit card? Makes no sense. I waited till they were open and called their customer service number. Spoke to a nice lady that essentially said "Don't worry about it. I'll fix the 55 inch order and even cancel the 47 inch to save you the trouble of schlepping it over to a physical store". Nice!

Because I am anal like that, I checked hours later and it was still canceled. So the "nice lady" hadn't done much. Suffice to say, I am still stuck in Walmart.com customer service hell. I have now ordered this same TV 4 times and they still can't tell me why my orders keep getting canceled. I have called AMEX 3 times to make sure everything is ok. All to no avail. I have heard several conflicting and non-helpful statements from Walmart.com service reps. For example:

Agent: Please correct your information and try the order again
Me: What information should I correct? Everything is correct as evidenced by the 47 inch order going through
Agent: Please correct your information and try the order again
Me: What information?
Agent: Your information
Me: What information specifically, my name, address, what?
Agent: Your information

Meanwhile the price of the TV has gone up by $106 and after over 7 calls and tweets to Walmart.com and  hours wasted, I still don't have the TV and there are all these pending authorizations on my AMEX from Walmart.




So why not just buy the damn tv from Amazon or BestBuy? Because even with price hike, Walmart is still cheaper and I like the convenience of being able to return to a physical store (imagine having to ship a 55 inch TV back to Amazon).

PS: Here are my notes from my interaction with Walmart.com service representatives. Warning: Contains some strong language
Here's a screenshot of the form letter email I got from Walmart.com when I contacted them via email. They couldn't even be bothered to replaced the placeholder text.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design. For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial so