<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Newegg.com&#8217;s Usability Blunder</title>
	<atom:link href="http://www.ecommerce-blog.org/archives/neweggcoms-usability-blunder/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ecommerce-blog.org/archives/neweggcoms-usability-blunder/</link>
	<description>Ecommerce, Online Marketing, SEO, Web Design and Programming</description>
	<lastBuildDate>Wed, 04 Jan 2012 19:17:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: dsadsa</title>
		<link>http://www.ecommerce-blog.org/archives/neweggcoms-usability-blunder/comment-page-1/#comment-23203</link>
		<dc:creator>dsadsa</dc:creator>
		<pubDate>Fri, 09 Apr 2010 03:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.ecommerce-blog.org/?p=239#comment-23203</guid>
		<description>dsfdsin their site that newegg had neglected to test for. I was surprised when I followed the link in your post, though, and saw that newegg has documented this issue in their FAQ â€” which implies that itâ€™s a known issue â€” instead of just fixing it!

Iâ€™m also a newegg customer. While I canâ€™t say that theyâ€™re going to lose my business over this issue, it is pretty surprising to me that theyâ€™d opt to document this bug instead of fixing it, and thereby risk losing other usersâ€™ business (like yours, as you mentioned).</description>
		<content:encoded><![CDATA[<p>dsfdsin their site that newegg had neglected to test for. I was surprised when I followed the link in your post, though, and saw that newegg has documented this issue in their FAQ â€” which implies that itâ€™s a known issue â€” instead of just fixing it!</p>
<p>Iâ€™m also a newegg customer. While I canâ€™t say that theyâ€™re going to lose my business over this issue, it is pretty surprising to me that theyâ€™d opt to document this bug instead of fixing it, and thereby risk losing other usersâ€™ business (like yours, as you mentioned).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: louis vuitton</title>
		<link>http://www.ecommerce-blog.org/archives/neweggcoms-usability-blunder/comment-page-1/#comment-23102</link>
		<dc:creator>louis vuitton</dc:creator>
		<pubDate>Mon, 08 Mar 2010 09:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ecommerce-blog.org/?p=239#comment-23102</guid>
		<description>Upon reading your post, Jamie, I assumed that this behavior was just a bug in their site that newegg had neglected to test for. I was surprised when I followed the link in your post, though, and saw that newegg has documented this issue in their FAQ â€” which implies that itâ€™s a known issue â€” instead of just fixing it!

Iâ€™m also a newegg customer. While I canâ€™t say that theyâ€™re going to lose my business over this issue, it is pretty surprising to me that theyâ€™d opt to document this bug instead of fixing it, and thereby risk losing other usersâ€™ business (like yours, as you mentioned).</description>
		<content:encoded><![CDATA[<p>Upon reading your post, Jamie, I assumed that this behavior was just a bug in their site that newegg had neglected to test for. I was surprised when I followed the link in your post, though, and saw that newegg has documented this issue in their FAQ â€” which implies that itâ€™s a known issue â€” instead of just fixing it!</p>
<p>Iâ€™m also a newegg customer. While I canâ€™t say that theyâ€™re going to lose my business over this issue, it is pretty surprising to me that theyâ€™d opt to document this bug instead of fixing it, and thereby risk losing other usersâ€™ business (like yours, as you mentioned).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Newegg Support</title>
		<link>http://www.ecommerce-blog.org/archives/neweggcoms-usability-blunder/comment-page-1/#comment-20605</link>
		<dc:creator>Newegg Support</dc:creator>
		<pubDate>Tue, 27 Jan 2009 23:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.ecommerce-blog.org/?p=239#comment-20605</guid>
		<description>Dear Customer,

Thank you so much for you writing this blog. We truly apologize for any inconvenience this issue has caused you. Just to let you know I have went ahead and brought this issue up to our management team in which was reviewed quite quickly. The response we can give you to this matter is that we will start removing this kind of check from our web site. We truly Thank you for your information and asure you this will be taken care of. If you have any further questions or concerns please feel free to contact me personally at alex.a.villarino@newegg.com or via phone at 800-390-1119 ext. 25040.

Sincerely,

Newegg Support</description>
		<content:encoded><![CDATA[<p>Dear Customer,</p>
<p>Thank you so much for you writing this blog. We truly apologize for any inconvenience this issue has caused you. Just to let you know I have went ahead and brought this issue up to our management team in which was reviewed quite quickly. The response we can give you to this matter is that we will start removing this kind of check from our web site. We truly Thank you for your information and asure you this will be taken care of. If you have any further questions or concerns please feel free to contact me personally at <a href="mailto:alex.a.villarino@newegg.com">alex.a.villarino@newegg.com</a> or via phone at 800-390-1119 ext. 25040.</p>
<p>Sincerely,</p>
<p>Newegg Support</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Schneider</title>
		<link>http://www.ecommerce-blog.org/archives/neweggcoms-usability-blunder/comment-page-1/#comment-20601</link>
		<dc:creator>Jon Schneider</dc:creator>
		<pubDate>Tue, 27 Jan 2009 18:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.ecommerce-blog.org/?p=239#comment-20601</guid>
		<description>Upon reading your post, Jamie, I assumed that this behavior was just a bug in their site that newegg had neglected to test for.  I was surprised when I followed the link in your post, though, and saw that newegg has documented this issue in their FAQ -- which implies that it&#039;s a known issue -- instead of just fixing it!

I&#039;m also a newegg customer.  While I can&#039;t say that they&#039;re going to lose my business over this issue, it is pretty surprising to me that they&#039;d opt to document this bug instead of fixing it, and thereby risk losing other users&#039; business (like yours, as you mentioned).</description>
		<content:encoded><![CDATA[<p>Upon reading your post, Jamie, I assumed that this behavior was just a bug in their site that newegg had neglected to test for.  I was surprised when I followed the link in your post, though, and saw that newegg has documented this issue in their FAQ &#8212; which implies that it&#8217;s a known issue &#8212; instead of just fixing it!</p>
<p>I&#8217;m also a newegg customer.  While I can&#8217;t say that they&#8217;re going to lose my business over this issue, it is pretty surprising to me that they&#8217;d opt to document this bug instead of fixing it, and thereby risk losing other users&#8217; business (like yours, as you mentioned).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

