← All guidesStart here

Connect your store

The five-step wizard that checks your WooCommerce store, takes API access, and creates your app.

Updated September 25, 2026

Press Add new app on the Dashboard to open the wizard. It has five steps: Store, Access, Branding, Publishing, Confirm. You can skip the Access step and connect later from the App Builder.

Step 1: Store

Enter your store address and press Check store. StoreToNative checks that WordPress and WooCommerce are active and counts your products. Nothing is installed on your site at this step. A bare address is treated as https://.

If the check fails, the message names what it saw, with a link to the fix:

  • Blocked. Your site wouldn’t let us read its public data at /wp-json. A security plugin, Cloudflare or a host firewall is the usual cause.
  • Not found. WordPress’s REST API isn’t at /wp-json. Plain permalinks are the usual cause: switch to Post name under Settings → Permalinks.
  • Answered, but not with WordPress data. Either the address isn’t your WordPress site, or something on it served a page instead. Open /wp-json/ on your site in a private window to see which.
  • Secure connection failed. The site’s SSL certificate didn’t pass the check.
  • Address not found. The domain name doesn’t resolve. Check the spelling.
  • Redirects to another site. When we can read where it points, the wizard offers a button with that address.
  • WooCommerce or one of its APIs not listed. The app needs the public Store API, and sync needs the REST API (wc/v3).
  • Unreachable. The address didn’t answer, or answered with an error. Check for typos and that the site is online.
  • Points to a private network. The address resolves to an internal or local address. Use your public domain.

Each one is explained on Troubleshooting. If someone else looks after your site, press Copy steps for my developer, where it’s shown, to copy the cause and the fix as plain text.

To try the console without a real store, use the built-in demo store: the address is shown as the field’s placeholder. It has 312 products and carries a Demo badge everywhere it appears.

Step 2: Access

The app reads your public catalog without any keys. Access keys are needed for the rest: syncing categories and prices, registering order webhooks, creating discount codes, and native checkout. There are three ways to grant them.

Companion plugin (recommended). Download the plugin, install and activate it, open the new StoreToNative menu in wp-admin, and press Generate pairing code in the wizard. Type the eight-character code into the plugin. Codes expire after 15 minutes; press Regenerate code if one runs out. The plugin creates its own read/write key and sends it to StoreToNative once. See The WordPress plugin.

Approve in wp-admin. Press Open approval page. WooCommerce asks you to approve read/write access to products, orders and webhooks, and sends the keys back. You can revoke them any time under WooCommerce → Settings → Advanced → REST API. If the page sits too long the approval expires; reopen it from the wizard.

Manual keys. Create a key yourself under WooCommerce → Settings → Advanced → REST API → Add key, with Read/Write permissions, and paste the consumer key (ck_…) and consumer secret (cs_…). Keys are encrypted at rest and never sent back to the browser.

All three end on the same card: Store connected — access keys received. Press Skip for now to continue without keys; the WooCommerce tab in the App Builder lets you connect later.

Step 3: Branding

  • App name, prefilled from your store name. This is the name shoppers see.
  • App icon. If your site has a square site icon of 512 × 512 or larger, the wizard offers to use it. Otherwise you can upload one in the App Builder after the app is created.
  • App id, suggested as com.yourstore.appname. This is a permanent id baked into the app’s binary. It must be lowercase, dot-separated, with at least two segments, and it is locked for good after your first store build. Choose it carefully; you cannot change it later without publishing a new app.

Step 4: Publishing

Apple requires every store to publish under its own developer account, so the wizard asks about your accounts now:

  • Apple Developer account: $99 per year, and companies need a D-U-N-S number.
  • Google Play Console: $25, one time.

Choose I already have one or Guide me — create new for each. Nothing here blocks creating the app; the Publish page picks it up later.

Step 5: Confirm

The summary shows the name and address, how many products will sync, the app id, whether keys were provided, and the publishing answers. Press Create my app.

The first catalog sync starts immediately. Where the Preview app is available, the last screen shows a preview code so you can see the app on your phone straight away.

If creation fails

  • Your plan includes N apps. You are at the app limit. Owners see Upgrade to add another app.
  • This id is already used by another app. Pick a different app id.
  • This store is already connected to another app in your workspace. The message links to it.
  • Already connected to another StoreToNative account. A store can power one app. Contact support if you own both accounts.

Still stuck? Open a ticket from Support in the console, or contact us.