Tabs for Shop, Cart and Orders
Point native tabs at a category, the cart or the My Account orders page so past orders are always one tap away.
For WooCommerce stores
Your app loads your live store, so Subscriptions, add-ons and checkout come from the same WordPress install. Nothing to install in wp-admin. You add the icon, native tabs and push.
Before you paste: Use your public store URL, not wp-admin, and turn off maintenance or coming-soon mode first.
See how it worksComes with you
Point native tabs at a category, the cart or the My Account orders page so past orders are always one tap away.
Send a title, text, image and link from your own Firebase project. Sent to everyone who opted in.
It works from your store URL, with no companion plugin or API key. Edits in wp-admin appear without a new build.
AI writes scripts that hide your theme’s sticky header and newsletter pop-up inside the app only. Your website stays as it is.
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 WooCommerce app plugins redraw your products from the REST API and support a fixed list of extensions.
You want product screens redrawn natively, or automated abandoned-cart push.
Also weighed: a home-screen shortcut or PWA plugin (free, no store listing) and a custom build (a quoted project, for app-only features).
The app shows your site in a WebView, which behaves like a mobile browser with a few differences worth checking.
Variations, add-on fields, bundles and booking calendars render in your theme, as they do on mobile.
Try it: Add a variable product with an add-on to the cart.
The app shows the pages your theme and plugins already produce, so there is no supported-extensions list to check. What you see in a phone browser is the starting point for what the app shows. Coupons, shipping rates and tax are calculated by the same server, so totals should match your website. Apply a coupon with a real address in the preview and compare.
Card fields load as on mobile; redirects, 3-D Secure and wallet buttons need a test order.
Try it: Pay with a 3-D Secure card through to order received.
Card fields from WooPayments, Stripe and similar gateways load in the page and normally behave as on the mobile web. Gateways that send the customer away, such as a bank redirect, 3-D Secure challenge or PayPal window, need a full test: the payment must finish and the customer must land on your order-received page inside the app. Apple Pay and Google Pay buttons often don’t appear in in-app browsers, so test on your own phones and keep card payment available.
Check the login and cart survive a restart; Google sign-in can be blocked, so test it.
Try it: Sign in, close the app fully and reopen it.
WooCommerce keeps the cart and login in cookies, and the app normally keeps saved cookies between launches like a browser does. Check that a customer is still signed in after closing and reopening the app. Google can block its sign-in screen inside in-app browsers, so a "Continue with Google" button from a social login plugin may fail there. Email and password login is the dependable path.
Keep Cart, Checkout and My Account out of page caching, as WooCommerce advises.
Do this: Add to cart, then check the count on every page.
A cache that serves a stored Cart, Checkout or My Account page can show a customer an empty cart or someone else’s details. WooCommerce’s own guidance is to exclude those three pages and its session cookies from caching. If your host or caching plugin already follows it on the web, the app inherits the correct behavior.
Apple’s in-app purchase rule can apply to courses and downloads, and apps with accounts need a deletion option.
Check: Delete a test account from My Account.
Apple lets apps sell physical goods and real-world services through their own checkout, so a coffee subscription is fine. Digital content used inside the app, such as courses, downloads or paid memberships, can fall under Apple’s in-app purchase rules (Guideline 3.1.1), and SiteTo.App uses your website checkout, so read that rule first. Apple also requires apps with account sign-up to offer account deletion in the app, so add a self-service delete page to My Account.
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 WooCommerce store into an iOS and Android app with SiteTo.App without rebuilding it. The app loads your live WooCommerce 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. The WooCommerce app from Automattic is for you, the merchant: it handles orders, products and in-person payments. Your customers cannot shop in it. SiteTo.App produces a separate app under your own store name and icon that customers install to browse and buy.
No. SiteTo.App works from your public store URL. You do not add a plugin to WordPress or create a WooCommerce REST API key, and there is no product sync to maintain. Push notifications use your own Firebase project, which you connect in the SiteTo.App dashboard.
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 store URL and run a test order on your own phone. Pay only when you build.
No account or card to preview.