Documentation / FluxNative Commerce
Create a Commerce app
In the Commerce dialog: bring a FluxBuilder app from its env.dart and config files, start from the template as one app type on your own store, or copy one of your Commerce apps.
Open the dialog
Choose Create app on the Commerce page. Migrate from FluxBuilder on the Dashboard, and the buttons on the template's page, open it too. Without a site it starts by buying one. Then pick a way:
| Way | Pick it when |
|---|---|
| From a FluxBuilder app | You made a FluxStore or FluxNews app with FluxBuilder |
| Start from the template | You start fresh, as one app type on your store |
| Copy an app | You want the same design and type for another store |
From a FluxBuilder app
- Choose From a FluxBuilder app.
- Drop your app's
lib/env.dart, itslib/config/config_<language>.jsonfiles (one per language) andconfigs/env.propsif it has one, then Read the files. - Read the report: what moved, what got the closest match, what the assistant builds next and what is left out. Choose Continue.
- Name the app and pick its Main language. Keep Use 1 site for … on to connect your website now.
- Start the first AI turn is on: the assistant checks the app with your store's data and builds the first missing feature, for the credits shown. Untick it to skip.
- Choose Migrate.
- The report is free: Check my app reads it before you buy. Migrate needs a site: Buy a site opens checkout in a new tab and unlocks it once you've paid.
- Up to 12 files, 2 MB each and 8 MB in all. Store keys in
env.dartare never shown back, and are dropped if you close before the app is made. - Your FluxBuilder app and your site don't change.
- In the new app's chat, What the migration left to do lists what didn't move as it was, each with a request it puts in the message box. Nothing is sent until you press Send.
Start from the template
- Choose Start from the template, pick the App type and choose Continue.
- Enter the App name and the fields below. A WooCommerce store may Use the demo store for now and connect yours later.
- Keep Use 1 site for … on to connect your website now.
- Optional: under What should change?, say what to change. The assistant starts on it once the app is made, for credits.
- Choose Create app. FluxNative checks your store first, and Home then shows your own categories.
| App type | You enter |
|---|---|
| WooCommerce store | Store address, then Connect with WooCommerce and approve on your store. Or a Read key's Consumer key and Consumer secret from WooCommerce › Settings › Advanced › REST API |
| Shopify store | Store address and the Storefront access token from Shopify's Headless channel, or Install in Shopify where it shows |
| Marketplace, Seller app | The Marketplace plugin (Dokan or WCFM), then as a WooCommerce store |
| Driver app | The Delivery plugin (WooCommerce, Dokan or WCFM), then as a WooCommerce store |
| WordPress news | Site address |
| Directory | The Directory theme (Listeo or MyListing) and With a shop: with it, as a WooCommerce store; without, the Site address |
- Install the FluxNative plugin on a WordPress store: the app signs in, checks out and runs its areas on it, and the check says when it is missing. A WordPress news site needs it for sign in and comments.
- WooCommerce keys are optional. The coupon list needs them. Connect with WooCommerce makes them on your store: approve there, then come back. They ship in the app, so a seller or driver app asks for Read/Write and every other app for Read. It needs the store's
https://address. - Approved but nothing happens? Set Settings › Permalinks to anything but Plain, or a security plugin or firewall may stop your store sending the keys. Enter them by hand.
- Shopify Admin API tokens are refused: use the Storefront token.
- For Dokan or WCFM, the store must list its sellers with that plugin.
- Each person can check stores ten times an hour.
Copy an app
- Choose Copy an app, pick one of your Commerce apps and choose Copy app.
- The copy opens on Server › Backend › Your store. Connect its store there.
The copy keeps the design and your changes. For the same website it builds with the same site; another website needs another site.
Good to know
- Make as many Commerce apps as you like: they don't count toward your plan's app limit.
- Creating an app needs permission to create apps. Use 1 site also needs permission to edit code and manage billing.
- No Use 1 site box, or no free site? Connect the website later from Build › Connect website.