Checkout Address Autocomplete: The Typo That Costs the Sale

The address autocomplete on your checkout is the first thing a shopper types, and the first place the sale dies. A shopper types their street, picks the wrong suggestion, and the order goes to an address that does not exist, or the autocomplete never appears on mobile and they give up halfway through the form. Either way, the fix is not more fields. It is fewer, in the right order, with the right behaviour.

The first field is the first failure

Baymard Institute's research puts the average documented cart abandonment rate at 70.22 percent, and once you set aside shoppers who were just browsing, the top reason is extra costs too high at 40 percent, followed by slow delivery at 20 percent. A wrong address produces both of those at once: a failed delivery that has to be shipped again, and a second shipping charge that the shopper did not expect. The address autocomplete is where that failure starts, because it is the first thing the shopper types and the first place the form can mislead them.

The common failure is a suggestion list that cannot be used with a keyboard, or that covers the input on mobile, or that fills only the street and leaves the city and postcode for the shopper to type. Each of those is a small defect, and together they are the reason a shopper abandons a form they had already decided to complete.

What good autocomplete does

Good autocomplete shows suggestions after two or three characters, highlights the matched text so the shopper can see why a suggestion appeared, and lets the shopper pick with the arrow keys as well as the mouse. Selecting a suggestion fills the whole address, street, city, postcode, and country, not just the first line. The list closes with Escape, and the shopper can keep typing without the list fighting them. That is the whole behaviour, and it is the difference between a field that saves time and a field that costs a sale.

The fields also need to be named the way the browser expects. Autocomplete attributes for street, city, postcode, and country let the browser fill the whole address in one tap, and on mobile that tap is worth more than any design change. If the fields use custom names, the browser cannot help, and the shopper types everything by hand on a phone keyboard, which is the slowest way to buy anything.

Test it with a thumb, not a mouse

More than 70 percent of e-commerce traffic is mobile, and mobile checkout still converts at roughly half the desktop rate industry-wide. Test the autocomplete on a phone with a real thumb. If the suggestion list covers the keyboard, or the suggestions are too small to tap without zooming, or the list disappears when the keyboard opens, the autocomplete is hurting more than it helps. That is a design failure, not a shopper failure, and it is the one that shows up in the conversion data as a mobile gap.

Then test it with a keyboard. Tab to the address field, type two characters, and pick a suggestion with the arrow keys. If the arrow keys do nothing, or the list cannot be closed with Escape, the field fails the same keyboard test that the trust signals post passes on the same checkout. A field that only works with a mouse is a field that only works for half your shoppers.

The order that costs the least

Fix the autocomplete before you add fields, not after. The cheapest fix is to name the fields correctly so the browser can help, then to make the suggestion list keyboard-usable, then to test it on a phone. Each of those is a small change, and together they are the difference between an address field that saves time and one that costs the order.

Measure it the way Shopify's Conversion rate breakdown report lets you: sessions that reached checkout divided by sessions that completed it, split by device. If mobile completion lags desktop by more than the usual gap, the address field is the first place to look, because it is the first field the mobile shopper types.

Frequently asked questions

How should checkout address autocomplete behave?

Show suggestions after two or three characters, highlight the matched text, and let the shopper pick with the keyboard as well as the mouse. The suggestion list must be reachable by arrow keys and closable with Escape, and selecting a suggestion should fill the whole address, not just the street.

Why does a wrong autocomplete pick cost so much?

Because the autocomplete is often the only address entry, and a wrong pick sends the order to an address that does not exist. Baymard's research puts extra costs too high as the top abandonment reason at 40 percent, and delivery too slow second at 20 percent, and a wrong address produces both: a failed delivery and a second shipment.

How do I test address autocomplete on mobile?

Test it on a phone with a real thumb, because more than 70 percent of e-commerce traffic is mobile and mobile checkout still converts at roughly half the desktop rate. If the suggestion list covers the keyboard or cannot be tapped without zooming, the autocomplete is hurting more than it helps.

Does the browser's own autofill help at checkout?

Yes, but only when the fields are named the way the browser expects: autocomplete attributes for street, city, postcode, and country. The browser can then fill the whole address in one tap. If the fields use custom names, the browser cannot help, and the shopper types everything by hand.