Article
Mobile Checkout: 8 Form Fixes That Lift Conversion on Phones
On a phone the keyboard covers half the screen, so every extra field and every error costs orders. Here are 8 concrete form fixes, with code, error message templates and a 20-minute test.
Published on: 10.11.2026 • Written by: Team Launify Reading Time: 6 min
Mobile Checkout: 8 Form Fixes That Lift Conversion on Phones
A shopper is standing on a crowded tram, phone in one hand, shopping bag in the other. She has a €49 gift in her cart and is typing her delivery address. At the postcode field she gets the full letter keyboard, hunts for the numbers, makes a typo, and after she taps submit the form turns red and jumps back to the top. The tram stops, she gets off – and the order is left unfinished.
According to Baymard Institute research, the touch keyboard covers roughly half the screen in portrait mode. The label, the field, the error message and the button all have to fit in what is left. That is why every unnecessary field and every error hurts more on a phone than on a desktop. Most of the eight fixes below need no redesign – just better form settings.
On mobile you don't raise conversion by adding something new. You raise it by taking typing, scrolling and correcting away from the customer.
Keyboards and typing: three fixes for one afternoon
1. Give every field the right keyboard
Back in 2015, Baymard found that 54% of major e-commerce sites failed to show an optimised keyboard for phone, postcode or card number fields (source). The fix is a single HTML attribute:
- Email:
type="email"– keyboard with @ and dot. - Phone:
type="tel"– large numeric keypad. - Numeric postcodes:
inputmode="numeric"– digits only.
Watch out for one detail if you sell across Europe: the iPhone numeric keypad has no space or hyphen. Czech and Slovak postcodes are written “110 00”, Polish ones “00-950”. Your form must accept “11000” or “00950” and add the separator itself. And never force a numeric keyboard on UK or Dutch postcodes – they contain letters.
2. Turn off autocorrect where it does harm
Autocorrect can turn an unusual surname or street name into an everyday word, and customers often don't notice. On name, email and address fields set autocorrect="off" and spellcheck="false". On email also add autocapitalize="off" so the address doesn't start with a capital letter. On name, street and city use autocapitalize="words" instead.
3. Let the browser fill in what it already knows
A customer's phone usually knows their name, email, phone number and address. To offer them, the fields need an autocomplete attribute. Google's web.dev lists the recommended values:
- First and last name:
given-name,family-name - Email and phone:
email,tel - Street and number:
address-line1 - City and postcode:
address-level2,postal-code - Country:
country
Add enterkeyhint="next" so the keyboard button moves the cursor to the next field, and enterkeyhint="done" on the last one.
A shorter form: fewer fields, less scrolling
4. Cut the form down to the essentials
Baymard's data shows the average checkout has 11.3 form fields, while most sites need only 8 (source). The same study shows where people drop off: 30% of test participants stalled at “Address line 2”, and 42% typed their full name into the first-name field at least once.
Go through your form field by field and put each one into one of three groups:
- Keep: name, email, phone (if the carrier needs it), street and number, city, postcode.
- Hide behind a checkbox: company name and VAT number (“I'm buying for a business”), a separate billing address (“Billing address is different”).
- Hide behind a link: address line 2 (“+ Add flat, floor or company”), order notes.
5. Put labels above fields, not inside them
Grey text inside a field (the placeholder) disappears as soon as you start typing. On a small screen the customer then can't tell whether they are typing into “City” or “Postcode”. Put the label above the field and use the placeholder only for a format example.
- Bad: an empty field with grey text saying “Postcode”.
- Good: the label “Postcode” above the field and “e.g. 10115” in grey inside it.
Errors: catch them before the customer taps “Place order”
6. Validate when the field loses focus – and write like a human
An error shown only after submitting means scrolling up on a phone and hunting for the red field. Validate each field when the customer leaves it, not while they are still typing. And say exactly what to do. Templates you can use straight away:
- Instead of “Invalid format”: “Postcodes in Germany have 5 digits, e.g. 10115.”
- Instead of “Invalid email”: “Your email address is missing an @. Please check it.”
- Instead of “Required field”: “Please add your house number – the courier can't deliver without it.”
- Instead of “Invalid phone number”: “Enter your mobile number – we'll add the country code for you.”
7. Let the address autocomplete instead of making people type it
The address is the longest part of the form. As an example, “Vinohradská 2029/124, 130 00 Praha 3” is over 30 characters across three fields, switching between letters and numbers. With address autocomplete, the customer types “Vinohr”, the house number, taps the right suggestion, and city and postcode are filled in correctly. Several tools do this; besides speed they also check that the address actually exists, so fewer parcels come back undelivered.
If you don't want to add autocomplete yet, at least fill in the city automatically once the postcode is entered.
The thumb zone: buttons and order summary
8. A big button at the bottom and the price always visible
Most people hold their phone in one hand and use their thumb. Put the main button at the bottom of the screen, full width. The accessibility standard WCAG 2.2 sets a minimum target of 24 × 24 CSS pixels; for your main button, go for double that.
- Say on the button what will happen: “Pay €53.90 and place order” instead of “Continue”.
- Show the total including shipping in a bar that stays visible while scrolling.
- Make checkboxes and shipping options tappable across the whole row, not just on the small circle.
How to test your mobile checkout in 20 minutes
You don't need a lab. Two phones (an iPhone and an Android) and a stopwatch are enough:
- Place an order one-handed, without zooming. Time it from cart to confirmation.
- For each field, note which keyboard appeared and whether the browser offered autofill.
- Deliberately make three mistakes (postcode without a space, email without @, address without a house number) and watch when and how the form responds.
- Record the screen and show it to a colleague who doesn't know the form. Wherever they hesitate, you have work to do.
Summary: what to do this week
- Add
type,inputmodeandautocompleteto every checkout field. - Turn off autocorrect on name, email and address.
- Hide company details, address line 2 and order notes.
- Move labels above fields and rewrite error messages using the templates above.
- Speed up address entry with autocomplete, or at least fill in the city from the postcode.
- Move the main button to the bottom, with the price and a clear label.
- Run a 20-minute test on two phones.
If you want faster address entry on mobile without touching code, tools such as Launify offer address autocomplete and validation as an add-on for common e-commerce platforms.