Your shop on the home screen
Customers open your shop from their own icon, with your launch screen, on iPhone and Android.
For PrestaShop stores
Your app loads your live front office, so the payment modules, pickup-point carriers and group prices you set up come with it. Nothing to install in your back office.
Before you paste: Shop in maintenance mode? Turn it off first, or use a public staging URL.
See how it worksComes with you
Customers open your shop from their own icon, with your launch screen, on iPhone and Android.
Point native tabs at pages your shop already has, such as Prices drop, New products, the cart and order history.
Send a title, text, image and link from your own Firebase project. Sent to everyone who opted in.
Edit products, prices and modules as usual and the app shows them on the next visit. No connector module or webservice key.
We fill in your name and icon. AI sorts your links into a header, side menu and tabs, and writes the script that hides your site’s own header and pop-ups. You adjust the rest.
Scan a code and use your real site as an app, before you pay.
You may be asked to install our preview app first.
We build in the cloud, so you need no Mac or Xcode. iOS lands in TestFlight in your Apple account; Android downloads as an AAB or APK. You submit for review from your own accounts.
Many PrestaShop app modules redraw your catalog as native screens, so checkout support depends on which payment and carrier modules the vendor has integrated.
You want natively drawn product screens, abandoned-cart push or offline browsing, and every payment and carrier module you use is on the vendor’s list.
The app shows your shop in a WebView, which behaves like a mobile browser with a few differences worth checking.
Your theme renders them, and group prices follow the customer account as on the web.
Try it: Open a product with combinations and compare trade prices.
Category filters, product combinations, vouchers, hidden prices for visitors and tax-excluded display are all drawn by your theme, so they load as they do in a phone browser. Group prices depend on the customer account, so compare a product price and a cart total with the same trade account on your website. For app review, be ready to give Apple and Google a working test account.
iDEAL, Bancontact, BLIK or Bizum approvals leave the app and must return to your order.
Try it: Pay with each method through to confirmation.
Test each method that leaves your shop (3-D Secure, PayPal, a banking-app approval) and confirm you land on the order confirmation inside the app. If the cart comes back empty, check Cookie SameSite under Advanced Parameters > Administration and ask your payment module’s support which value it needs.
Map widgets load in the delivery step; search by postcode and check the point sticks.
Try it: Choose a pickup point and find it on the confirmation.
Carrier modules for pickup points and lockers usually draw a map widget in the delivery step, often loaded from the carrier’s own servers. Open it in the preview, search by postcode, choose a point and check the choice is still attached to the order on the confirmation page. Do not rely on "use my location" alone; make sure typing a postcode works.
The 20-day cookie normally keeps logins, but the IP check can sign out moving phones.
Try it: Close the app, reopen it, then reorder.
The front-office cookie lasts 480 hours (20 days) by default, so a returning app customer normally still has their login and cart. The same Administration page has a "Check the cookie’s IP address" option. With it on, a phone moving between Wi-Fi and mobile data can be signed out, so review it if app users report losing their session.
Apple Pay, Google Pay and "Continue with Google" may not appear or work in a WebView.
Try it: Try each button, with card and email login available.
Wallet buttons depend on your payment module’s own check of the environment, so a button that shows in Safari or Chrome may be missing in the app. Google can block its sign-in screen in embedded WebViews, so test it rather than assume. Keep card payment and email-and-password login available as the fallback, and try every button you offer in the preview on both iPhone and Android.
The app starts on one language URL, so keep language and currency selectors reachable.
Do this: Switch language and currency, then answer the cookie banner.
The app starts on one URL. PrestaShop puts the language in the address (for example /fr/ or /es/), so start on the language most app customers read and keep the language and currency selectors reachable in your theme. With multistore, each shop has its own URL: build the app around one shop, or one app per shop if they are separate brands.
These are a starting point for your free preview, not a claim that every site setup or integration has been tested. Not for apps that need Bluetooth, AR, heavy offline use or background processing.
Planning the build?Setup walkthroughReadiness checklist
Website changes show up in the app without a rebuild. No subscription, and the price doesn’t change as your app gains users.
Paid to Apple and Google
Later rebuilds, such as a new icon, are included.
Yes, you can turn a PrestaShop store into an iOS and Android app with SiteTo.App without rebuilding it. The app loads your live PrestaShop store, adds your branding and menus, and costs $29 for Android, $79 for iOS or $99 for both, paid once per platform. Apple and Google developer accounts are separate.
No. SiteTo.App works from your public shop URL. You do not install a module, create a webservice key or open API access, and there is no catalog sync to maintain. It is not tied to your PrestaShop version either, as long as the shop is responsive on a phone.
Yes. Those modules connect to your shop’s data and redraw the catalog as native screens, with support for the payment and carrier modules their vendor has integrated. SiteTo.App loads your live shop, so the modules on your mobile site load with it. Choose a module if you want natively drawn product screens or abandoned-cart push.
Customers see the latest version of your website when they open or refresh the app, so ordinary content, product and page updates do not need a new app build. A new app icon, app name or launch screen needs a new build.
Apple decides, so nobody can guarantee it. Apple can reject apps that add nothing beyond a website (Guideline 4.2), so plan for real app features such as native navigation and push, and test your key journeys in the preview first.
Yes. Paste your URL and open the preview on your own phone. You don’t need an account or a card to preview, though you may be asked to install our preview app first. You only pay when you choose a build.
Paste your shop URL and preview on your phone. Nothing to install in PrestaShop. Pay when you build.
No account or card to preview.