A generic error banner is insufficient when the shopper cannot find the field to fix.
Checkout errors and recovery
After an error, shoppers should retain their input and find what needs correction. Explain the problem at the field and make the next action clear.
Research context: Baymard · Checkout error recovery ↗
Field messages describe what needs correction. An error summary lets keyboard users move directly to the field; other input is retained.
Try the pattern
Task and expected result
- 01
Leave email empty in the lab: the summary and field message should guide you to the field.
- 02
Try an invalid postal code, then fix it. Name and address should remain.
- 03
Simulate payment failure and retry: preserve fulfillment and quantity.
- 04
Submit the lab with an invalid email: the error link focuses email without erasing the name.
- 05
Simulate payment failure, edit quantity and retry: review and total use the new quantity.
How to investigate value
Measure confirmed, deduplicated outcomes per eligible checkout start. Define paid orders and accepted credit orders separately.
Watch for side effects
Payment errors, duplicate orders, incorrect totals, unclear arrival dates and discount cost. A pay click is only an attempt.
This is a proposed investigation, not a measured result. Choose one hypothesis and define the audience before testing.
Build a measurement plan for this concept ↗