WooCommerce iOS app: what it takes to reach the App Store
By Abdalla Kamesh · Published October 29, 2026 · 7 min read

You have a WooCommerce store, and you want it on the iPhone as a real app, with an App Store listing. This post puts the whole path in one place. Each section is short and links to the post that covers it in full.
One fact up front, because it shapes everything else: the app is published under your own Apple Developer account, not ours. Apple requires that, and it is also what you want.
What the iOS app is
A StoreToNative app for iPhone and iPad is built from your WooCommerce store. The catalog, search, cart and account screens are native screens that read your store’s live data. At checkout you choose between your store’s own checkout page inside the app (the default) and a native checkout form (an add-on). Either way, payment runs on your own gateway. Physical goods stay outside Apple’s in-app purchase rules, so there is no Apple commission on your sales.
The app runs on iOS 15 and newer.
Native, WebView or PWA explains the difference between a native storefront and a website in a frame, and Why the payment step belongs on the web covers the checkout step.
Step 1: your own Apple Developer account
- The cost: the Apple Developer Program is $99 a year, paid to Apple. It is not part of your StoreToNative plan. Apple and Google developer fees, explained breaks it down.
- Why your own: Apple’s Guideline 4.2.6 rejects apps made from a template or app-generation service unless the content provider submits them. You are the content provider, so you submit under your account. Guideline 4.2.6 explains what that means for any vendor you look at.
- How long: individuals usually enroll in a day or two. A company needs a D-U-N-S number first, and the legal name must match exactly. Getting an Apple Developer account as a business walks through it. An Apple Enterprise account cannot ship to the App Store.
Start this first. It is the one delay you cannot buy your way out of.
Step 2: how you get the app on your own iPhone
This is different from Android, so read it twice.
On Android, every build leaves an APK you can install from a link, on the trial too. iOS has no such path. The free trial step for iOS is a compile check: it proves the app builds, but it cannot be installed on an iPhone. The way onto your own iPhone is a store build, which StoreToNative signs and uploads to TestFlight, Apple’s testing app. You invite testers from App Store Connect.
A store build needs a paid plan and your own Apple Developer account. So on the trial you design your app, preview it, and test the Android APK. The iPhone build comes once you are on a plan.
Step 3: connect App Store Connect
Open Publish → App Store in the console. You paste three things, and StoreToNative checks the first two with Apple before saving:
- your Apple Team ID,
- an App Store Connect API key (a Team key with the Admin role),
- a push key (APNs), so order updates and campaigns reach iPhones.
Then you create the app record by hand in App Store Connect. The console shows the values to copy: app name, bundle id, SKU and version. Your app is signed with your own keys and appears under your own name. StoreToNative never signs or submits under its own account.
The full checklist is on the Publish to the App Store help page.
Step 4: the listing and the screenshots
The listing has a name of up to 30 characters, a subtitle of 30, a keywords field of 100 characters and a description of up to 4,000. Draft from my store writes a first version from your catalog. Edit it: Apple looks for signs that the app is your store’s own, and the page warns about a generic description, the default brand color, policy pages on another domain and an app name without your store’s name.
Apple needs screenshots in two sizes: 6.9-inch iPhone and 13-inch iPad. Capture screenshots takes them from your real app with your real catalog, or you upload your own. App Store screenshots for a shopping app covers what to show.
Step 5: privacy answers and the four things to confirm yourself
Apple asks what data the app collects. Filling in app privacy and data-safety forms explains the questions.
Four settings live only in App Store Connect, and Apple gives no way to read them, so the console cannot check them for you: EU trader status, the App Privacy answers, the tax category, and the agreements, which the Account Holder must accept. Confirm each one before you submit.
Step 6: submit for review
When the blockers list is empty, you press Submit for review. The console sends your latest TestFlight build, the listing and the screenshots to Apple, with your own App Store Connect key. It fills in the price (free), the Shopping category and the age rating. Nothing is rebuilt. Then the card tracks the review: waiting in Apple’s queue, in review, approved, live, or rejected.
Step 7: the review itself
A native storefront is built outside Guideline 4.2’s category: it is not a repackaged website. That removes a common reason for rejection. It does not decide the outcome. Apple’s reviewers do, and we can’t promise any reviewer’s decision.
The guideline WooCommerce stores meet most often is 4.3, “spam or similar apps”. The defense is to look like your store: your own name, icon, colors, policy pages and a description you wrote. If Apple does reject the app, the Rejection playbook on the Publish page turns Apple’s message into steps and a reply you can paste.
Three posts go deeper:
- Why Apple rejects wrapper apps under Guideline 4.2
- Will Apple reject my WooCommerce app?
- The rejections e-commerce apps actually get
After you are live
- Product links open in the app. iOS Universal Links need a small file,
apple-app-site-association, on your store’s own domain, completed with your Apple Team ID. The optional WordPress companion plugin serves it for you, or you download it from the console’s Growth page. - Bring shoppers over. A smart app banner on your mobile site points iPhone visitors at your listing.
- Change the app without a new review. Colors, home sections and content reach installed apps over the air, within a launch or two, with no rebuild and no store re-review. A new build is needed only for the app name on the home screen, the launcher icon, the app id, the launch-screen color or a new store domain. OTA, explained covers the line between the two.
Related reading
- Publishing your store app to the App Store and Play
- Guideline 4.2.6: the rule that decides your app vendor
- Getting an Apple Developer account as a business
- Apple and Google developer fees, explained for merchants
- Will Apple reject my WooCommerce app?
Guided App Store publishing, under your own developer account, is part of every paid StoreToNative plan. See what each plan includes.