Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: Customers - To Register or Not To Register

  1. #1
    jazzloft99 is offline Senior Member
    Join Date
    Feb 2008
    Posts
    202

    Default Customers - To Register or Not To Register

    I've read that 30% of customers might turn away if they had to register so I turned this off. Now I get tons of emails from customers who can't log into their accounts because they now have 3-5 different accounts and/or they didn't register the first time and try to register later using the same email.

    What do most people do? Is it best to force them to register? Some advise here would be appreciated!

  2. #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    That's a common problem with anonymous checkout, specially if you're allowing duplicate email addresses (appconfig: AllowCustomerDuplicateEMailAddresses). It is actually necessary to make changes directly in the database if a customer ever decides to register with an address that has been used multiple times. You can follow these directions in the KB.

  3. #3
    jazzloft99 is offline Senior Member
    Join Date
    Feb 2008
    Posts
    202

    Default

    Yep, I do this. So which is better and more standard practice? I also have a lot of customers who say they can't log in because the email is already used because I don't allow duplicate emails.

    So what's standard practice? Force the user to register or not? Is there a good solution to make it the least difficult and easiest for the customer?