Checkout Errors That Tell Shoppers How to Fix Them

The error message is where checkouts are won and lost. A message that says what went wrong and how to fix it gets the shopper through in seconds. A message that says invalid input sends them away, and 98 percent of sites still use the vague kind.

The vague error is the expensive one

Baymard Institute's benchmark found that 98 percent of sites use generic error messages, and only 2 percent use adaptive ones. The generic kind says invalid input, or please check your details, and leaves the shopper to work out what is wrong. In Baymard's testing, participants took up to five minutes to resolve simple errors for tasks like signing in, solely because of vague wording. In the worst cases, participants could not resolve the issue at all and abandoned the purchase. The error message is not a courtesy. It is the difference between a completed checkout and an abandoned one.

The fix is to write errors that name the field, the problem, and the fix, in one line. Enter a 5-digit ZIP code. That card number is too short, it should be 16 digits. Your email address is missing the @ sign. Each of these tells the shopper what to do, and each of them can be written in advance, because the validation rules are known. A field that can fail in four ways needs four messages, not one. Baymard's research suggests four to seven messages for the most complex fields, card number, phone, email, password, goes a long way.

The discount code field post showed the same discipline on a different field: the box that makes the shopper stop and hunt is the box that costs the sale. A vague error does the same thing, one field later.

Timing is the second half of the fix

Showing the error at the wrong time is as bad as showing the wrong message. Validating while the shopper is still typing tells them they are wrong before they have finished, which is frustrating and, for a card number, always wrong on the third keystroke. Validating only on submit is worse, because the shopper has to hunt back through the whole form to find the problem. The timing Baymard's testing supports is on blur, when the shopper finishes a field and moves on. The error appears when the field is done, and it disappears when the field is fixed.

Positive inline validation is the other half: a checkmark or a short confirmed message when the input becomes valid, so the shopper does not have to review every field before submitting. It removes cognitive load, and it works best on the high-stakes fields, email and card number, where a mistake is costly. The combination is the rule: reward early, punish late. Show success as soon as the input is valid, and show the error only when the shopper has had a chance to finish.

The checkout speed post argued that a slow checkout is a conversion problem, not a technical one. A checkout that wastes five minutes on a vague error is the same kind of problem, and it is cheaper to fix than the speed.

Never clear the form

The rule that matters most is the simplest: never clear a form on error. A shopper who has typed their card number, their address, and their phone, and then sees everything wiped because one field was wrong, will not retype it. They will leave. Keep everything the shopper entered, show the error next to the field, scroll to the first error on submit, and let them fix the one thing that is wrong. That is the whole fix, and it is the one that 98 percent of sites have not done.

The measure is error recovery time: how long it takes a shopper to fix a deliberately introduced error and complete the purchase. Test it with five people, a card number with a wrong digit, and a postcode with a missing character, and time them. If the average is over a minute, the errors are too vague. Rewrite them, test again, and the time will fall. The checkout that recovers fast is the checkout that converts.

Frequently asked questions

When should a checkout show a field error?

After the shopper finishes the field and moves on, not while they are typing. Validating on the third keystroke tells someone their input is wrong before they have finished giving it. Validating on blur, when the field loses focus, is the timing Baymard's testing supports.

Where should an error message appear?

Next to the field that caused it, in words that say what to do. A message at the top of the form saying please correct the errors below makes the visitor hunt. An error summary at the top helps on submit, but the fix has to be next to the field.

What is an adaptive error message?

Adaptive error messages change with the exact subrule that failed, and give instructions for that specific failure. A postcode field might need four to seven messages: wrong length, wrong format, missing outward code, and so on. Each one tells the shopper exactly what to type.

Should a checkout keep what the shopper typed after an error?

Yes. A shopper who has typed their card number three times and had it cleared on every error will leave. Keep everything the shopper entered, show the error next to the field, and let them fix the one thing that is wrong. Clearing the form on error is the single most reliable way to lose a submission.

What is positive inline validation?

A checkmark or a short confirmed message when the input becomes valid, so the shopper does not have to review the whole form before submitting. Positive inline validation removes the need to re-check every field, and it works best on high-stakes fields like email and card number.