Where WooCommerce stores lose repeat mobile sales
By Abdalla Kamesh · Published October 26, 2026 · 6 min read

Your store passes every mobile test. It loads fast, the buttons are big enough, checkout works with a thumb. So when a customer buys once on their phone and never comes back, the site is not the problem. The problem is that the site itself cannot start the next visit.
This post has no statistics in it, on purpose. Benchmarks about “app users buy X times more” mix up cause and effect, and the structural argument is stronger anyway. If you want numbers, measure your own: app vs mobile web conversion shows how.
A visit and a return are different events
A first visit comes from outside: a search result, an ad, a post, a link in an email. Your mobile site is built for that moment, and it is the right tool for it. Nobody installs an app to look at a store once.
A return has to come from somewhere too. On the web, it comes from the same places: the customer searches again, sees another ad, or opens an email you sent. Search and ads are channels you pay for or compete in, and your competitors are there too. Email is yours, but it shares an inbox with everyone else’s. The mobile-friendly site itself does nothing to bring the customer back. It waits.
An installed app sits on the home screen, stays signed in, and can be opened from a notification. That gives the next visit one more way to start with you instead of with a search box.
The three moments a web store goes quiet
Here are three moments in every store’s life where a customer would welcome a message, and where a website has little to send it with.
1. The order changed status. The customer wants to know. On the web, that is a transactional email in a busy inbox. In the app, when the order was placed in the app, the status change in WooCommerce becomes a notification on the phone, “Order #123 — Your order is now completed”, once per change. Order-status updates are on every plan while the Push notifications add-on is on. Shoppers can still turn notifications off on the app’s Account screen, so send nothing they would not want. Order-status notifications pay for the app explains why support tickets fall when this is on.
2. The cart was left. On the web, an abandoned cart belongs to a browser session that may already be gone. In the app, a shopper who leaves items for 30 minutes gets one nudge, “Still thinking it over? Your cart is waiting.”, once per cart and never repeated. Abandoned-cart recovery is on the Pro and Agency plans, with its own switch. Abandoned-cart push vs web push covers the difference in trigger, timing and opt-in.
3. The product came back in stock. A customer who wanted something you did not have is a warm lead, and on the web you have no way to reach them unless they filled in a form. In the app, a shopper taps a watch button on the product page and gets a push when it returns. Price-drop alerts work the same way. Both are on the Pro and Agency plans.
At each of these moments the website itself can only wait, or hope an email gets opened. Not because you forgot, but because a browser tab is not a channel. That is the whole case for an app, and it is a retention case, not an acquisition one.
What an app does not fix
Be honest about this before you spend a subscription on it.
- Slow hosting. An app renders its own screens and then waits for your store’s API. If your store is slow, the app is slow, with nicer loading states. Your store’s speed is your app’s speed splits the delay into the half that is yours.
- Bad product photos. The app shows the photos you have, bigger. A dark, cropped, 400-pixel photo gets worse, not better.
- A checkout that asks for too much. The app uses your store’s own checkout fields, and payment runs on your own gateway, so every extra field you ask for on the web, you ask for in the app. Fix the form once and both benefit.
- A product nobody reorders. Furniture, a bicycle, a wedding dress. If a customer buys once a decade, there is no repeat sale to lose, and no app will make one.
If one of these is your real problem, fix it first. The app question will still be there, with a better answer.
A test that costs nothing
You do not have to reason about this. Run your own store through the StoreToNative demo: it reads your store’s public product catalog, the same pages any shopper can see, and lays it out as a native iPhone and Android app. It does not sign in, installs nothing and changes nothing on your store.
Look at it the way a returning customer would. Would you keep it on your home screen? Is there a product you would want to be told about? Then check one number in WooCommerce, your repeat-purchase rate. The demo tells you what the app would feel like; the repeat rate tells you how many people there are to retain. My site is mobile-friendly. Do I need an app? turns that number into a decision.
Measure your own numbers
Whatever you decide, do not take a benchmark’s word for it. Three numbers are yours to measure:
- Repeat-purchase rate in WooCommerce, before the app and after.
- Push opens. The console’s Push page lists every send and how many devices it reached, and opens are tracked per campaign on the Analytics page.
- Orders via the app, on the console’s Analytics page. An order counts as “via app” only when the shopper placed it from the app; website orders are never credited to it.
If the app adds returns, those three numbers say so in a month. If it does not, they say that too, and you learned something a benchmark could not have told you. How to get your store’s first 1,000 app installs is the next step once the answer is yes.
Related reading
- Push notifications for a WooCommerce store, end to end
- My site is mobile-friendly. Do I need an app?
- Order-status notifications pay for the app
- Abandoned-cart push vs web push for WooCommerce
- How to get your store’s first 1,000 app installs
Order-status updates are on every StoreToNative plan; abandoned-cart recovery and back-in-stock and price-drop alerts are on Pro and Agency. See what each plan includes.