HomeHome Product Discus... Product Discus...SmithCartSmithCartUser RegistrationUser Registration
Previous
 
Next
New Post
2/16/2010 3:19 PM
 

On the product roadmap is this note: "Adding option to prompt user to login at the beginning of checkout."

Can this also force user registration to the beginning, as well as clean up the new customer registration?

If you require registration the current user path is more than confusing.

At the the first prompt "I am a new customer" the button offered is "Sign in using our secure server." You click that and you get to a screen where you enter your name, address, etc. Then to a credit card page, and the finally to the order confirmation page. At the bottom of which is "Log Information: (Required) and a login autofilled with their email address and a blank password prompt.

The user hasn't registered yet, they've apparently almost completed their desired transaction but are told to log in. They're not told they're registering.

Additionally, what is really their registration and also their purchase is accomplished by the "Process payment" button, but they also told to only click that button once. If they error on the password (which has no user tip or instruction) then of course they have to click again. That's IF they understand they're also registering as a user.

I ran a two different test customers through this of varrying computer skill. One a frequent online shopper, the other a newbie. Frustration for both. The regular online shopper was more irritated than the newbie who just assumes all computer stuff is incomprehensible.

Regards,

 
New Post
2/16/2010 5:46 PM
 

Regarding your comment about "Adding option to prompt user to login at the beginning of checkout." I couldnt tell from your post if you are running the latest version of the cart with the new sign in screen but the new sign on screen has been released in the new version of the cart v2.58. In the cart admin settings if you check the box to show the login screen at the beginning of the checkout then you should check the box "Hide Login" to hide the login on the coinfirmation page.


At your service,
Dave Smith
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
2/17/2010 12:07 AM
 

Running 2.53.

Is there some notification that I'm missing on version updates with d/l instructions? For my other modules I get those via snowcovered.

 
New Post
2/17/2010 12:04 PM
 

We have posted several updates to snowcovered for the 2.5x release. Here is our upgrade policy:



http://www.smith-consulting.com/forums/upgradepolicy.aspx



Please email sales@smithcart.com with your purchase receipt to get a copy of the latest version of the cart


At your service,
Dave Smith
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
3/5/2010 12:15 PM
 

Okay let's try this again. I wanted to force users to register. Running v2.60 I have checked the show login screen under general configuration and require login under confirmation configuration (if hide login is selected the require login is apparently overridden). New user starts the check out process. They are shown this screen.

What button does the new user press? The only option is the sign in button. They click that and are shown the "Enter shipping information" page. So the user thinks what? They fill that info in and go to the billing information page. Now they reach the order confirmation page and at the bottom they find this.

Log in is required. But the new user never registered. So they wonder if this is where they register? The only buttons to select are "Back" and "Process Payment" which has a note under it saying only press once. Say they get brave and enter a password. The password is not going to be accepted because they don't know the password rule. So that errors out and now they have a problem, i.e., what about that whole only press payment button once warning?

As a new user I'd just give up and go find somewhere else to make my purchase.

Why not consolidate this registration point with the returning customer log in?

 
New Post
3/5/2010 8:00 PM
 

The purpose of this Sign in screen is to allow the user to login prior to the checkout screens so they do not have to re enter their shipping and billing information. If the user selects the “I am a returning customer” radio button and enters a valid login id and password then their shipping and billing information will be automatically populated on step 1 and step 2 of the checkout so they dont have to re key all their information if they already have an account.

Prior to adding this new signin screen to the cart, if the customer was a returning user and already had an account on your portal they had to use the standard dnn login to signin prior to checking out if they wanted the cart to retrieve their profile and prepopulate their info in the checkout screens.

If the user chooses the “I am a new customer” radio button on the signin screen and enters their login id the cart will populate the login id on the confirm page where they enter their password.

The signin screen was modeled after the way amazon.com prompts for a user to login before entering the checkout and I'm sure they conducted hundreds of hours of usability testing before implementing their sign in screen.

Regarding the button on the new sign in page, its an image button and can be changed to any button and text you like.

Regarding password rules, every portal has different password rules that are set in the web.config. If the user enters a password that does not meet the minimum password requirement for your portal the confirm page displays a message indicating such. If you want to alert the user to the minimum password requirement for your portal before they key in their password then you can add some help text next to the password textbox.

If you want to change the message the confirm page displays when the user enters a password that doesnt meet the minimum password requirement for your portal then you can modify the following line of code in the confirm.ascx page:

Password must be minimum of 7 characters." ValidationExpression=".{8}.*" Display="dynamic"/>

If think your comment about the user giving up is a bit of a stretch, if the customer is a new user their loginid is pre populated for them and all they have to do is enter a password and then click process payment, pretty standard stuff not sure how much easier it could be.

Why not consolidate this registration point with the returning customer log in?

For a new user, I think the last page in the checkout before the creidt card is authorized is the correct place for the user to enter and confirm their password. If we moved the password and confirm password textboxes from the confirm screen to the new sign in screen I think you would see more abandoned carts. I think the user is more willing to enter and confirm their password after they have entered their billing information. That being said I am always open to change and hearing everyones opinion so please leave your feedback.


At your service,
Dave Smith
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
3/5/2010 8:32 PM
 

The Amazon model would be a good one to follow.

The user is prompted that they'll enter their password later if they're a new customer. An easy enough modification to the existing cart login.

Then they're presented with this:

User registration is completed before the checkout process.

In cases where the registration is prompted before final checkout, the user is taken to a new registration point and then brought back to checkout. I've never seen it integrated within the checkout page. The final checkout is where you ask the customer to trust the transaction - it's not the place to add confusion.

But I'm curious what others think as well.

 
Previous
 
Next
HomeHome Product Discus... Product Discus...SmithCartSmithCartUser RegistrationUser Registration