Mobile online store: how to test a purchase on your phone

A person shopping on a phone while riding public transport

The keyboard pops up and covers the “Next” button. The customer types a house number with a typo, gets an error message and sees an empty form, so the whole address has to be typed again, with a thumb, on a tram. You will not see things like this on a computer, even in a narrowed browser window. That is why a mobile online store has to be walked through the way a customer walks through it, with a phone in hand and all the way to the return from payment.

A mobile online store in your analytics

In Gemius’s report “E-commerce in Poland 2025”, the smartphone collected 82% of mentions as a device used for online shopping. Those are respondents’ declarations. How many of your customers buy on a phone, only your analytics can tell you.

Compare the phone with the computer over the same period and look at the traffic source as well, because someone who reached the store from an ad buys in different conditions than a regular customer typing the address from memory. A difference in conversion between devices does not by itself point to an error in the form.

Look for where the purchase breaks off. If phone customers reach the choice of delivery and vanish there, you start the test with that step. If they drop out earlier, you start with the product page and adding a variant to the cart.

The product page on a small screen

Pick up a real phone and start with the product page. The photo should zoom with the fingers, and a description hidden in collapsible sections must open and be readable without scrolling sideways. Pay attention also to everything stuck to the screen edge, from the promotion bar to the buy button, because on a phone such elements can eat a large part of the view.

While you are there, check when the customer first sees the delivery cost. If only in the last step, they have to get through the whole form on a phone before they learn what they will really pay.

The form on the on-screen keyboard

In the form, start with no saved data, because that is how it looks to someone buying from you for the first time with no account yet. Count the fields and ask which of them you truly cannot ship without. Then repeat the attempt with autofill and see whether the address landed in the right fields.

Now make a mistake on purpose. Enter a wrong value in a required field and try to go on. A good form shows what to correct and leaves the rest of the data in place, since one slip in a house number should not mean retyping the whole address from the beginning.

Baymard’s research on mobile forms describes problems with the keyboard and the small space on the screen. So at each field check that the right keyboard appears, for example a numeric one for a phone number and a postcode, and that the field label does not vanish when you start typing. With the phone number, see also whether the store accepts it in the form your customers type it, for example with spaces or with +48.

Payment and the return to the store

The least obvious stretch is the hop to the payment provider and back. Go through your chosen method to the end, and then once more, this time cancelling the payment halfway and retrying. Write down what you see after each attempt. Payment gateways differ from one another, and the test concerns your integration and your theme, so other people’s experience tells you little here.

Does the chat cover the buy button on a phone?

Before checkout the customer should be able to check the chosen variant and quantity, so open the product photo and the size chart, and then go back to the cart. Going back must not wipe the choice or throw you to the top of a long product list.

What remains is the chat window. Open it on a product page and check whether it can be closed in one move and whether the closed bubble covers the “Add to cart” button, also when a cookie banner is still hanging at the bottom of the screen. Repeat this with enlarged text in the phone settings, because not everyone reads at the default font size.

CartBot shows product cards in the conversation and on supported platforms adds a product straight to the cart, which shortens the path to purchase on a small screen. Check it on your own theme, together with variant selection. The chat is still an additional route, so after it is closed the product information and the buy button must stay in their place.

How to describe a fault so someone can fix it

Given the phrase “the mobile version sells poorly”, whoever repairs the store can only guess. The sentence “after returning from payment the cart is empty but there is no confirmation” gives them a concrete starting point, especially if you add the page address and the phone model and browser on which the error appeared.

First you fix what blocks the purchase. After each fix you go through the same steps again, and only then look at results from similar traffic, because otherwise you do not know whether the fix helped or the campaign changed. Keep a recording or a note from the test. At the next theme change you can use it to check whether the old error has come back.

Try CartBot in your store

Quote within 24 h. No commitment, no card.