The account may facilitate subsequent orders, but its role should be understood. The store design must clearly explain when login is needed and what possibilities the person buying for the first time has.
Find out why the client needs an account
A history of orders, saved data and access to an individual offer can justify logging in. However, not every feature is needed on a one-time purchase. First describe the sales model and then decide when the store requires user identification.
In business sales or with certain services, the process may differ from the usual retail directory. The conditions should be explained before the final stage of the order.
Show available paths
If the store expects to purchase without an account, do not hide this possibility behind a vague signature. However, the person with the account should easily find the login and method of regaining access. All roads must keep the contents of the basket.
It is not worth presenting registration as mandatory if in fact a simpler purchase option is available.
Check back after the problem
- What happens after the wrong password?
- Does changing the purchase method keep the entered data?
- Does the client understand what information will be written down?
- Is the order confirmation available by the right way?
For example, a person who remembers the password should not re-complete the entire order on his return. Such cases are part of a process project, not only a login form.
Explain the benefit at the right time
If you can offer to create an account after purchase, the message should clearly describe the action and do not suggest that the order was not accepted without it. The final course depends on the system implemented and the rules of the store.
We write about reducing unnecessary questions in guidebook of the order formA well-designed account supports the customer, and his role remains clear at every stage of the purchase.
