<?xml version="1.0" encoding="UTF-8"?>
<blog-post>
  <author-id type="integer">42244</author-id>
  <blog-comments-count type="integer">1</blog-comments-count>
  <blog-post-status-id type="integer">3</blog-post-status-id>
  <body-format>econsultancy_xml</body-format>
  <body-formatted>
  &lt;p&gt;If&#160;they have to do too much work to figure out why an error was made, and what they have to do to fix it, they are likely to give up on the whole process, and you will have lost a sale.&lt;/p&gt;
  &lt;p&gt;The key here is to make the process as simple as possible to avoid common errors, and to make them easy to fix if they do happen.&lt;/p&gt;
  &lt;p&gt;
    &lt;em&gt;Here are&#160;a few suggestions...&lt;/em&gt;
  &lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Make the process easy to understand&lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;However&#160;well designed&#160;your checkout process is, human nature means that customers will make mistakes. Making it easy to use will minimise the number of errors though.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Adhere to web standards and&#160;conventions&lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;Customers will expect your checkout forms to be broadly similar to those they have used on other e-commerce sites, so any departures from convention are risky.&lt;/p&gt;
  &lt;p&gt;For instance, users will expect an asterisk or shading to denote a form field which must be completed, so any deviation from this is likely to cause confusion in the customer's mind.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Flexible form input&lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;Don't be too insistent on entries being in upper or lower case, as this just makes customers have to work harder to figure it all out. You should allow customers to enter postcodes in lower or&#160;upper&#160;case without a space, for example.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Make error messages clear&lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;When people have made an error, let them know exactly what they need to do to correct it and get back onto the purchase.&lt;/p&gt;
  &lt;p&gt;I got this message after entering credit card details at Oasis, which was far too vague to help me correct the problem. It didn't specify where the problem was in the form, meaning I had to check every single part of the form.&lt;/p&gt;
  &lt;p&gt;
    &lt;img alt="Checkout error message" src="http://farm4.static.flickr.com/3277/2986684384_797828185b_o.jpg" /&gt;
  &lt;/p&gt;
  &lt;p&gt;After double checking and still getting the message, I ended up giving up on the purchase, something many other customers would have done in the same circumstances.&lt;/p&gt;
  &lt;p&gt;Comet does a better job here, after I forgot to enter an evening phone number, and made a mistake confirming my email address:&#160;&lt;/p&gt;
  &lt;p&gt;
    &lt;img alt="Comet address form error message" src="http://farm4.static.flickr.com/3198/2985828681_2fdae7b437_o.jpg" /&gt;
  &lt;/p&gt;
  &lt;p&gt;This time I am told exactly the mistakes I have made when completing the form and can easily figure out how to fix the problem.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Highlight the field(s) containing the error&lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;This is another way to help the customer recognise where a mistake had been made and correct it. Highlighting the form field by shading or placing red error text next to it will help avoid frustration.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Don't delete information already entered &lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;I have encountered a few websites that will, in the case of an error made in one form field, will automatically delete the information in the whole form. This is guaranteed to annoy customers.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Make error messages polite&lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;Even if the user has made an obvious mistake, the tone of your error message should be friendly and polite. Pejorative terms like &lt;em&gt;illegal&lt;/em&gt; or &lt;em&gt;invalid&lt;/em&gt; should be avoided when referring to errors, while capitals are also not advisable.&lt;/p&gt;
  &lt;p&gt;Basically, the message should not blame the user, but seek to help the correct their mistake.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;Related articles:&lt;br /&gt;&lt;/strong&gt;
    &lt;a href="/blog/1646-tips-on-improving-the-checkout-process"&gt;Tips on improving the checkout process&lt;/a&gt;
    &lt;br /&gt;
    &lt;a href="/blog/1459-why-do-customers-abandon-the-checkout-process"&gt;Why do customers abandon the checkout process?&lt;/a&gt;
  &lt;/p&gt;
</body-formatted>
  <body-unformatted>&lt;FormattedContent xmlns="http://www.e-consultancy.com/schema/formattedContent/"&gt;
  &lt;Paragraph&gt;If&#160;they have to do too much work to figure out why an error was made, and what they have to do to fix it, they are likely to give up on the whole process, and you will have lost a sale.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;The key here is to make the process as simple as possible to avoid common errors, and to make them easy to fix if they do happen.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Quote&gt;Here are&#160;a few suggestions...&lt;/Quote&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Make the process easy to understand&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;However&#160;well designed&#160;your checkout process is, human nature means that customers will make mistakes. Making it easy to use will minimise the number of errors though.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Adhere to web standards and&#160;conventions&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;Customers will expect your checkout forms to be broadly similar to those they have used on other e-commerce sites, so any departures from convention are risky.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;For instance, users will expect an asterisk or shading to denote a form field which must be completed, so any deviation from this is likely to cause confusion in the customer's mind.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Flexible form input&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;Don't be too insistent on entries being in upper or lower case, as this just makes customers have to work harder to figure it all out. You should allow customers to enter postcodes in lower or&#160;upper&#160;case without a space, for example.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Make error messages clear&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;When people have made an error, let them know exactly what they need to do to correct it and get back onto the purchase.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;I got this message after entering credit card details at Oasis, which was far too vague to help me correct the problem. It didn't specify where the problem was in the form, meaning I had to check every single part of the form.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Image AlternateText="Checkout error message" Source="http://farm4.static.flickr.com/3277/2986684384_797828185b_o.jpg"&gt;
    &lt;/Image&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;After double checking and still getting the message, I ended up giving up on the purchase, something many other customers would have done in the same circumstances.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;Comet does a better job here, after I forgot to enter an evening phone number, and made a mistake confirming my email address:&#160;&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Image AlternateText="Comet address form error message" Source="http://farm4.static.flickr.com/3198/2985828681_2fdae7b437_o.jpg"&gt;
    &lt;/Image&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;This time I am told exactly the mistakes I have made when completing the form and can easily figure out how to fix the problem.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Highlight the field(s) containing the error&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;This is another way to help the customer recognise where a mistake had been made and correct it. Highlighting the form field by shading or placing red error text next to it will help avoid frustration.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Don't delete information already entered &lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;I have encountered a few websites that will, in the case of an error made in one form field, will automatically delete the information in the whole form. This is guaranteed to annoy customers.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Make error messages polite&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;Even if the user has made an obvious mistake, the tone of your error message should be friendly and polite. Pejorative terms like &lt;Quote&gt;illegal&lt;/Quote&gt; or &lt;Quote&gt;invalid&lt;/Quote&gt; should be avoided when referring to errors, while capitals are also not advisable.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;Basically, the message should not blame the user, but seek to help the correct their mistake.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;Related articles:&lt;LineBreak /&gt;&lt;/Emphasis&gt;
    &lt;Link URL="/blog/1646-tips-on-improving-the-checkout-process" Window="Self"&gt;Tips on improving the checkout process&lt;/Link&gt;
    &lt;LineBreak /&gt;
    &lt;Link URL="/blog/1459-why-do-customers-abandon-the-checkout-process" Window="Self"&gt;Why do customers abandon the checkout process?&lt;/Link&gt;
  &lt;/Paragraph&gt;
&lt;/FormattedContent&gt;</body-unformatted>
  <created-at type="datetime">2008-10-29T15:59:00+00:00</created-at>
  <enabled-blog-comments-count type="integer">1</enabled-blog-comments-count>
  <expertise-level-id type="integer">1</expertise-level-id>
  <extract-format>econsultancy_xml</extract-format>
  <extract-formatted>
  &lt;p&gt;
    &lt;strong&gt;When going through the checkout process, customers in the process of&#160;paying for&#160;items are bound to make a few mistakes here and there. &lt;/strong&gt;
  &lt;/p&gt;
  &lt;p&gt;The key here is to handle these problems&#160;smoothly, enabling customers to correct any errors they make without causing unnecessary frustration.&lt;/p&gt;
</extract-formatted>
  <extract-unformatted>&lt;FormattedContent xmlns="http://www.e-consultancy.com/schema/formattedContent/"&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;When going through the checkout process, customers in the process of&#160;paying for&#160;items are bound to make a few mistakes here and there. &lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
  &lt;Paragraph&gt;The key here is to handle these problems&#160;smoothly, enabling customers to correct any errors they make without causing unnecessary frustration.&lt;/Paragraph&gt;
&lt;/FormattedContent&gt;</extract-unformatted>
  <featured type="boolean">false</featured>
  <id type="integer">2914</id>
  <learn-more-formatted>&lt;p&gt;Econsultancy have published an &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/online-retail-2007-checkout-special"&gt;Online Retail Checkout Special&lt;/a&gt;&lt;/strong&gt;, which covers online checkout best practice in detail.&lt;/p&gt;</learn-more-formatted>
  <learn-more-unformatted>&lt;p&gt;Econsultancy have published an &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/online-retail-2007-checkout-special"&gt;Online Retail Checkout Special&lt;/a&gt;&lt;/strong&gt;, which covers online checkout best practice in detail.&lt;/p&gt;</learn-more-unformatted>
  <legacy-article-id type="integer">366618</legacy-article-id>
  <name>How to handle checkout errors</name>
  <private type="boolean">false</private>
  <published-at type="datetime">2008-10-31T09:00:00+00:00</published-at>
  <slug>how-to-handle-checkout-errors</slug>
  <tweetbacks-updated-at type="datetime">2009-04-29T21:51:09+01:00</tweetbacks-updated-at>
  <unpublished-at type="datetime" nil="true"></unpublished-at>
  <updated-at type="datetime">2009-10-13T09:51:20+01:00</updated-at>
  <views-count type="integer">523</views-count>
</blog-post>
