[RELEASED] Uber Checkout 1.5.x - Improved Checkout System

1. The language files repeat certain variables within even the same file! This may be eliminated.
2. Perhaps you could try to use some of the variables already declared in cart and checkout language files. It doesn't matter for English shops, but does matter for other languages as then folks have to re-translate large parts (or at least search and paste)..which is wasteful.
3. Please consider moving the "Account creation" box (i.e. provide password) to the end of the 2nd step/page, instead of the 1st step/page

• Section headers, e.g. text_shipping_method
• Section descriptions. e.g. text_shipping_methods
• Help text, e.g. text_coupon

• On page 1, email box is tiny and password box is huge. Should be other way round.
• Uses its own Button images. Terrible idea! Should really use the theme's button images.
• For most part, shouldn't even have a separate css...should just merge into existing theme by using active css

OC2PS wrote:Installed it.

Seems lots of language fields are not being used at all. e.g.

• Section headers, e.g. text_shipping_method
• Section descriptions. e.g. text_shipping_methods
• Help text, e.g. text_coupon

Then there is one or two hard to decipher language variables, e.g. entry_account

Also, some cosmetic things:

• On page 1, email box is tiny and password box is huge. Should be other way round.
• Uses its own Button images. Terrible idea! Should really use the theme's button images.
• For most part, shouldn't even have a separate css...should just merge into existing theme by using active css

Overall very happy with the extension, and hope you can make these small usability tweaks.
(or I could make them and send to you, if you are happy to merge)

Qphoria wrote:You have apparently never tried to code for OpenCart 1.5.0 through 1.5.4 before..

Qphoria wrote:A lot more thought went into this than you think young padawan

OC2PS wrote:3. Please consider moving the "Account creation" box (i.e. provide password) to the end of the 2nd step/page, instead of the 1st step/page

Qphoria wrote:As far as moving the password to the end.. my initial idea was to put it on the success page, but that can be overlooked sometimes, and required an additional change to the success page which complicates things again with custom themes and some payments have custom success pages. So I decided to keep the related stuff on the same page. I think as a customer, whether its step 1 or step 2 you know if you want an account.

Qphoria wrote:There are hundreds of combinations of possible opinions.. I can only go with what makes sense for most.

Jared M. Spool, Founder of User Interface Engineering wrote:How Changing a Button Increased a Site's Annual Revenues by $300 Million

It's hard to imagine a form that could be simpler: two fields, two buttons, and one link. Yet, it turns out this form was preventing customers from purchasing products from a major e-commerce site, to the tune of $300,000,000 a year. What was even worse: the designers of the site had no clue there was even a problem.

The form was simple. The fields were Email Address and Password. The buttons were Login and Register. The link was Forgot Password. It was the login form for the site. It's a form users encounter all the time. How could they have problems with it?

The problem wasn't as much about the form's layout as it was where the form lived. Users would encounter it after they filled their shopping cart with products they wanted to purchase and pressed the Checkout button. It came before they could actually enter the information to pay for the product.

The team saw the form as enabling repeat customers to purchase faster. First-time purchasers wouldn't mind the extra effort of registering because, after all, they will come back for more and they'll appreciate the expediency in subsequent purchases. Everybody wins, right?

"I'm Not Here To Be In a Relationship"

We conducted usability tests with people who needed to buy products from the site. We asked them to bring their shopping lists and we gave them the money to make the purchases. All they needed to do was complete the purchase.

We were wrong about the first-time shoppers. They did mind registering. They resented having to register when they encountered the page. As one shopper told us, "I'm not here to enter into a relationship. I just want to buy something."

Some first-time shoppers couldn't remember if it was their first time, becoming frustrated as each common email and password combination failed. We were surprised how much they resisted registering.

Without even knowing what was involved in registration, all the users that clicked on the button did so with a sense of despair. Many vocalized how the retailer only wanted their information to pester them with marketing messages they didn't want. Some imagined other nefarious purposes of the obvious attempt to invade privacy. (In reality, the site asked nothing during registration that it didn't need to complete the purchase: name, shipping address, billing address, and payment information.)

Not So Good For Repeat Customers Either

Repeat customers weren't any happier. Except for a very few who remembered their login information, most stumbled on the form. They couldn't remember the email address or password they used. Remembering which email address they registered with was problematic - many had multiple email addresses or had changed them over the years.

When a shopper couldn't remember the email address and password, they'd attempt at guessing what it could be multiple times. These guesses rarely succeeded. Some would eventually ask the site to send the password to their email address, which is a problem if you can't remember which email address you initially registered with.

(Later, we did an analysis of the retailer's database, only to discover 45% of all customers had multiple registrations in the system, some as many as 10. We also analyzed how many people requested passwords, to find out it reached about 160,000 per day. 75% of these people never tried to complete the purchase once requested.)

The form, intended to make shopping easier, turned out to only help a small percentage of the customers who encountered it. (Even many of those customers weren't helped, since it took just as much effort to update any incorrect information, such as changed addresses or new credit cards.) Instead, the form just prevented sales - a lot of sales.

The $300,000,000 Fix

The designers fixed the problem simply. They took away the Register button. In its place, they put a Continue button with a simple message: "You do not need to create an account to make purchases on our site. Simply click Continue to proceed to checkout. To make your future purchases even faster, you can create an account during checkout."

The results: The number of customers purchasing went up by 45%. The extra purchases resulted in an extra $15 million the first month. For the first year, the site saw an additional $300,000,000.

On my answering machine is the message I received from the CEO of the $25 billion retailer, the first week they saw the new sales numbers from the redesigned form. It's a simple message: "Spool! You're the man!" It didn't need to be a complex message. All we did was change a button.

rph wrote:I've thought about this a bit and for the life of me I can't come up with a way to deal with customers who are already registered but checkout as a guest/new account. It's not an issue if the passwords match but if they don't you now have a customer who's entered all their checkout information for it to fail out on the very last step.

The only solution I can come up with is adding email entry as a step all on its own at the very beginning.

rph wrote:You have a customer who forgot they previously registered. if they enter a password and it doesn't match the existing account then you've got an issue.

OC2PS wrote:When going from 1st page to 2nd page, the system already has the email of the customer and can match against database to check if account exists.

rph wrote:Q, if they checkout as a guest they no longer have any order history and automated account functions like re-order and returns.

rph wrote: You're also creating issues for stores that deal with digital products.