<?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: Why You Shouldn&#8217;t Force Customers To Log Into Your Online Store</title>
	<atom:link href="http://aldebaranwebdesign.com/blog/why-not-to-force-customers-log-into-online-store/feed/" rel="self" type="application/rss+xml" />
	<link>http://aldebaranwebdesign.com/blog/why-not-to-force-customers-log-into-online-store/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 04 Jan 2012 22:34:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jill Olkoski</title>
		<link>http://aldebaranwebdesign.com/blog/why-not-to-force-customers-log-into-online-store/comment-page-1/#comment-2884</link>
		<dc:creator>Jill Olkoski</dc:creator>
		<pubDate>Fri, 12 Dec 2008 17:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://aldebaranwebdesign.com/blog/?p=266#comment-2884</guid>
		<description>Hi Chidozie,
Thanks for your thoughtful comment. I was in no way suggesting that merchants not collect information on their customers - all online stores - including the one I work with - collect name, email,phone, address - everything necessary to ship and contact customers. I&#039;m not referring to contact information at all. I&#039;m talking about creating a login - a username and a password. This does indeed make reordering easier - easier that is if you can remember your username and password. Every single step you take to make it harder for someone to purchase, is a bad thing - that&#039;s why companies like PayPal even have &quot;PayPal express&quot; - it skips over ALL of the data entry part of online stores. 

So to repeat - I&#039;m not being critical of collecting normal contact info from customers (name, email, phone, address) but forcing - not optional but preventing purchase - by making someone create a username and password - remains, in my opinion, a bad idea. I&#039;ve also read several studies of online shopping and they usually mention forced checkout as an impediment to purchase completion and one factor in shopping cart abandonment. I suggest you read my article:
http://aldebaranwebdesign.com/blog/shopping-cart-abandonment/
as it notes several studies that actually interview folks who abandon shopping carts and frequently they cite things like the checkout process being confusing and taking too long - and call out forced registration as a bad thing. 

Until I see data that proves otherwise, forcing customer registration is something I will continue to advise my ecommerce clients to avoid. Again, thanks very much for your comment!</description>
		<content:encoded><![CDATA[<p>Hi Chidozie,<br />
Thanks for your thoughtful comment. I was in no way suggesting that merchants not collect information on their customers &#8211; all online stores &#8211; including the one I work with &#8211; collect name, email,phone, address &#8211; everything necessary to ship and contact customers. I&#8217;m not referring to contact information at all. I&#8217;m talking about creating a login &#8211; a username and a password. This does indeed make reordering easier &#8211; easier that is if you can remember your username and password. Every single step you take to make it harder for someone to purchase, is a bad thing &#8211; that&#8217;s why companies like PayPal even have &#8220;PayPal express&#8221; &#8211; it skips over ALL of the data entry part of online stores. </p>
<p>So to repeat &#8211; I&#8217;m not being critical of collecting normal contact info from customers (name, email, phone, address) but forcing &#8211; not optional but preventing purchase &#8211; by making someone create a username and password &#8211; remains, in my opinion, a bad idea. I&#8217;ve also read several studies of online shopping and they usually mention forced checkout as an impediment to purchase completion and one factor in shopping cart abandonment. I suggest you read my article:<br />
<a href="http://aldebaranwebdesign.com/blog/shopping-cart-abandonment/" rel="nofollow">http://aldebaranwebdesign.com/blog/shopping-cart-abandonment/</a><br />
as it notes several studies that actually interview folks who abandon shopping carts and frequently they cite things like the checkout process being confusing and taking too long &#8211; and call out forced registration as a bad thing. </p>
<p>Until I see data that proves otherwise, forcing customer registration is something I will continue to advise my ecommerce clients to avoid. Again, thanks very much for your comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chidozie</title>
		<link>http://aldebaranwebdesign.com/blog/why-not-to-force-customers-log-into-online-store/comment-page-1/#comment-2881</link>
		<dc:creator>Chidozie</dc:creator>
		<pubDate>Fri, 12 Dec 2008 04:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://aldebaranwebdesign.com/blog/?p=266#comment-2881</guid>
		<description>Jill,

I would disagree with you slightly on this one. I agree that if ticketmaster is going to have a time limit they should probably make it more realistic than 15 seconds. But if they don&#039;t have your contact information how would you expect them to send you a receipt or order confirmation to your email and of course they want some infromation on their customer. 

In the case of physical, shipped products the merchant wouldn&#039;t be able to send you an emailed shipping confirmation or be able to contact you if your something goes wrong with your order. Finally, if in the future you were interested in your order history or wanted to &#039;re-up&#039; on an order you wouldn&#039;t be able to do so. 

Katy mentioned she always forgets. I would recommend to use one to three (they usually lock you after 3 tries) STRONG passwords (8 characters long at least on symbol, number and capital letter - ie Pass@word1) that you can always remember for all your logins.</description>
		<content:encoded><![CDATA[<p>Jill,</p>
<p>I would disagree with you slightly on this one. I agree that if ticketmaster is going to have a time limit they should probably make it more realistic than 15 seconds. But if they don&#8217;t have your contact information how would you expect them to send you a receipt or order confirmation to your email and of course they want some infromation on their customer. </p>
<p>In the case of physical, shipped products the merchant wouldn&#8217;t be able to send you an emailed shipping confirmation or be able to contact you if your something goes wrong with your order. Finally, if in the future you were interested in your order history or wanted to &#8216;re-up&#8217; on an order you wouldn&#8217;t be able to do so. </p>
<p>Katy mentioned she always forgets. I would recommend to use one to three (they usually lock you after 3 tries) STRONG passwords (8 characters long at least on symbol, number and capital letter &#8211; ie Pass@word1) that you can always remember for all your logins.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie Kay</title>
		<link>http://aldebaranwebdesign.com/blog/why-not-to-force-customers-log-into-online-store/comment-page-1/#comment-2136</link>
		<dc:creator>Katie Kay</dc:creator>
		<pubDate>Mon, 11 Aug 2008 20:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://aldebaranwebdesign.com/blog/?p=266#comment-2136</guid>
		<description>I agree!  It is very frustrating to have to login every time you want to make a purchase, and I so often forget what username and password I used, UGH!  Ticketmaster is especially frustrating with their limited time.</description>
		<content:encoded><![CDATA[<p>I agree!  It is very frustrating to have to login every time you want to make a purchase, and I so often forget what username and password I used, UGH!  Ticketmaster is especially frustrating with their limited time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

