Connect your store and website

Connect your website

A Commerce app builds for the website its .env names: your store's address. Connect it to one of your sites once, before the first native build.

1. Open Build in the app. Website for this Premium app names the website in its source.
2. Choose Connect website, then Yes, connect.

• It needs permission to edit code and manage billing.
• Another app for the same website uses the same site. Another website needs another site: Buy another site.
• Until it's connected, native builds are refused, and so is taking the source out: Download source (.zip), Push to GitHub, the desktop app and editors over MCP. The preview, editing and share links work without it.
• Local and test addresses and the demo store can't be connected.

Change the store

1. Open Server › Backend. Your store shows the store's type and address, whether keys are saved, the FluxNative plugin (its version, or Not installed with what it unlocks), MStore API where a FluxStore site still runs it, and the site.
2. Choose Change store and enter the store as when you made the app. It stays the app's own kind: a WooCommerce store app takes another WooCommerce store, never a Shopify one.
3. Choose Check and save. FluxNative checks the store, then connects it as one new version.

• For the same store, leave the keys blank to keep the saved ones, or choose Connect with WooCommerce for new ones. Revoke old FluxNative keys in WooCommerce › Settings › Advanced › REST API.
• For another store, Rebuild Home from the new store's categories is off: Home stays as you made it.
• A store on another website than the app's site needs another site to build, or a support request to move the site.
• Undo it from Version history.
• The assistant changes the app's design and features, never its store or keys.

FluxNative plugin

The app's backend on WordPress: sign in, checkout, orders, the seller, driver and listing areas, messages and the AI assistant. Your store shows its version, or Not installed with what it unlocks.

Not on wordpress.org yet? Until wordpress.org lists the plugin, Your store shows Download (zip) in place of Install for me:

1. Choose Download (zip), or download it here.
2. In WP admin, choose Plugins › Add New › Upload Plugin, pick the zip, then Install Now and Activate.
3. For a newer version, upload it the same way and choose Replace current with uploaded.

On wordpress.org:

1. Choose Install for me. Your store's Authorize Application page opens: sign in as an administrator and approve.
2. FluxNative installs and turns on the plugin from wordpress.org, then deletes the app password it used.

• Install for me needs https:// and WordPress 5.6 or later. Some security plugins and hosts block app passwords: then install it yourself.
• If FluxNative says the app password is still there, delete FluxNative in Users › Profile › Application Passwords.
• The app checks your site when it starts: it moves to the plugin at its next start, with no new build, and shoppers sign in once more. Coming from FluxStore? Keep MStore API while FluxStore's apps use it.

Move a site to another website

Only support moves a site. On the Commerce page, choose Request website change on the site's row, enter the New website and choose Send. Support moves it and replies to the request. In Build, the same button shows when the app's source names another website than its site.

Related

FluxNative Commerce · Create a Commerce app · Server