Skip to main content
An AI agent can launch a working Fluid store in about 20 minutes. A Fluid store combines an ecommerce storefront, checkout, international commerce, payments in 100+ countries, social sales channels, rep attribution, and sync with the merchant’s commission engine in one platform. Fluid bills by usage, so the agent can build everything and show the merchant a live preview. The merchant adds a credit card only when they decide to launch. This guide is for AI agents, and for the developers who build them. It picks up right after Agent signup and puts Fluid’s guided setups in launch order. Each guided setup covers one task end to end with the Fluid CLI.

What is Fluid?

Fluid is a We-Commerce platform: an ecommerce platform built for brands that sell through people. Those people might be independent reps, distributors, affiliates, ambassadors, or influencers. Fluid connects the brand’s storefront, checkout, payments, and rep attribution, so every sale is credited to the person who drove it. Read more in What is We-Commerce?.

What’s in a Fluid store?

A Fluid store is one Fluid company. It includes all of these from the start:

Who is Fluid for?

Fluid fits brands whose sales come from a network of people, not only from ads and search. The most common use cases are:
  • Direct sales and MLM companies. Run the storefront, checkout, and rep sites on Fluid, and keep the existing commission engine through Fluid Connect.
  • Brands with affiliate, ambassador, or influencer programs. Every shared link is attributed, so commissions don’t depend on coupon codes or spreadsheets.
  • Social selling. Reps share products on social media and in messages, and the brand sells through social sales channels from the same catalog.
  • Expanding into new countries. Add a country with its own currency, tax, and shipping. Choose which products sell there, translate the storefront, and take local payment methods through one payments form.
  • Replacing a dated storefront. An agent can copy the current site into a Fluid theme, so the new store looks familiar on day one.
  • Agents and agencies pitching a new store. Build a working preview of a prospect’s store before anyone pays.

How much does Fluid cost?

Fluid bills by usage. A merchant pays for the orders they process and the resources they use. There is no up-front licence to buy before you can build. For the rates, committed-use bonuses and spend limits, see Pricing. That lets an agent build the full store first, then hand the merchant a preview link. The merchant adds a credit card at Settings → Billing (https://admin.fluid.app/settings/billing) when they’re ready to launch. Adding the card is the merchant’s decision, so don’t do it for them.

What to have ready

Collect these up front, so no step stops halfway to ask:
  • Back-office credentials, if the merchant has a back office to connect in Step 2. Each Connect guide lists exactly which values its platform needs.
  • Payments documents for Step 3: business registration, bank statements, ID for each owner, and financial statements. Payments onboarding has the full list.
  • Avalara credentials, only if the merchant calculates tax on their own Avalara (AvaTax) account: the account ID and license key, plus the Avalara company code, which Fluid needs before it can commit orders to Avalara. Without them, Fluid calculates tax for the store (Step 4).
  • A Firecrawl API key, if you copy the merchant’s site with the clone skill in Step 7. Without one, capture the pages with fluid theme crawl, which runs through Fluid’s own Firecrawl account, and build the theme with the Fluid CLI.

What does the merchant need to do?

An agent does most of the work. A person has to act at only these points. Tell the merchant about them at the start, so nothing stalls while you wait.

How do you launch a Fluid store with an AI agent?

Nine steps take a new company from signup to a launched store. Steps 2 to 6 and 9 each hand off to a guided setup.

Step 1: Sign up, confirm the email, and sign in

Install the Fluid CLI and the plugins the guided setups use:
Then sign the merchant up. Check the points in Agent signup with them first, starting with their consent:
fluid signup makes the unauthenticated POST /api/company call that Agent signup describes, and sends it once. If it fails, its error says whether to run it again. It prints the company with its fluidShop, and the two fluid login steps that sign in to it. Those are the two-step sign-in below, except that the second step uses --name <subdomain> instead of --yes, so it never replaces a CLI profile that already has the company’s name. Without the CLI, make the call yourself as that page shows.
Merchant action: confirm the signup. Fluid emails a confirmation link to the address you signed up with. The merchant opens it and presses Sign in to confirm the signup, or confirms it by signing you in to the Fluid CLI with --shop, below. Don’t build further until they do one or the other: until then the store isn’t served, and Fluid may hold back the theme and payment account setup until confirmation. A signup that isn’t confirmed within 14 days may be removed, and its subdomain freed.
Keep the company’s id and fluidShop from the output (company.id and company.fluid_shop in the API’s response). The storefront starts serving at https://<subdomain>.fluid.app once the merchant confirms the signup, on Fluid’s default theme. Until they confirm, that address does not resolve to the store, so don’t share it with them yet. Sign the CLI in to the merchant’s company in one of two ways:
Run fluid whoami to confirm the CLI is signed in to the right company.
What the merchant’s sign-in gives you. The CLI holds the merchant’s own admin session for this company, with no narrower scope: you can do whatever they can do in the admin. The session lasts up to 45 days. To keep it shorter, the merchant can set a session length at Settings → Login & Identity (https://admin.fluid.app/settings/session) before signing you in. The setting applies to sessions started after it changes.
Every guided-setup command prints JSON, so you read each result the same way at every step. Commands that change live configuration need --yes. Use each guide’s step commands. The interactive walk commands are for people at a terminal.

Choose the markets

Decide where the merchant sells and in which languages before you go further. Payments onboarding (Step 3) and the countries and languages setup (Step 4) both use this list.
  • Countries: start from where the merchant ships today. Look at their website’s shipping and returns pages, currency and country selectors, and the addresses on their checkout.
  • How they operate in each country: run fluid countries atlas <iso> for each country. It describes the three ways to sell there: shipping in from abroad, selling locally through a local entity, or charging in US dollars. Pick the one that matches how the merchant ships and where their legal entities are.
  • Languages: use the languages their current site is published in, plus the main shopping languages of each country. fluid translations languages lists every language Fluid supports and its code.
List your choices in the summary you send the merchant with the preview (Step 8), so they can change them before launch.

Step 2: Connect an existing back office (optional)

Skip this step if the merchant has no existing direct-sales platform. Fluid Connect links a merchant’s direct-sales back office, which is usually their commission engine, to Fluid. The back office stays the system of record for members, orders, and genealogy. Records sync both ways on a schedule. Follow the guided setup for the merchant’s platform:

Exigo

Install, add credentials, map data, and choose sync settings.

InfoTrax

Install, add credentials, map data, and choose sync settings.

ByDesign

Install, add credentials, map data, and choose sync settings.

Pillars

Install, add credentials, map data, and choose sync settings.
Do this step early. The first sync runs while you work through the rest. The back-office credentials include passwords. If the merchant is with you, have them enter the credentials themselves with the guide’s walk, for example ! fluid connect walk exigo in Claude Code. The walk asks for each value and hides passwords and tokens as they’re typed, so they stay out of your context and the shell history. Otherwise, save exactly what the merchant gives you with the guide’s credentials step. Never guess or reuse credentials.
If Step 2 stalls, for example while you wait for credentials, carry on with Steps 3, 4, 6, and 7. Hold only Step 5 until the sync has run, so you don’t create products or customers the back office is about to bring in.

Step 3: Prefill payments onboarding

One form covers payments for every market the merchant sells in. The merchant sees it at Settings → Onboarding. Once it’s submitted, Fluid’s team reviews it and applies to payment processors for the merchant. Follow the Payments onboarding guided setup, and split the work like this:
  • You fill in what you can confirm from the merchant’s website and public records. That covers the basics, the legal entity, the countries you chose in Step 1, and the underwriting answers. fluid payments onboarding show lists every required field that’s still missing.
  • The merchant provides their bank accounts, the details and ID documents of each owner, and their financial statements. Don’t source these from scraped or guessed data.
  • The merchant submits. Submitting accepts Fluid’s payments terms in the merchant’s name, so the merchant does it, never you. If they signed in to the CLI in Step 1, they run fluid payments onboarding submit --accept-terms --yes themselves. If you’re using an API token, submit changes nothing and returns ready_to_submit with a submitUrl: send that link to the merchant, who opens the form and submits it. A merchant who’d rather answer the questions themselves can run fluid payments onboarding walk after signing in with fluid login.
The storefront and preview don’t wait for payments approval. Processors review the application after submission, so keep building. The CLI calls the Onboarding API. Use that API directly if you’re not using the CLI.

Step 4: Open countries and languages

Open each country you chose in Step 1, in the way you chose to operate there, with the Open a country guided setup. It sets up the country from Fluid’s Country Atlas, including currency, tax display, checkout defaults, languages, and the agreements a storefront there needs. Then translate the storefront into each language you chose with the Add a language guided setup. It reports what’s untranslated, machine-translates it, and confirms nothing is left.

Tax

A new store calculates tax from the start, so it needs no tax step. Each country you open uses Fluid’s tax calculation, which works from the business location, the customer’s address, and the tax rules that apply there. Opening the country already set how its prices show tax. If the merchant calculates tax on their own Avalara (AvaTax) account, connect it over the API in this order:
  1. Save the credentials with Create or update a merchant Avalara account slot: the account ID as username, the license key as password, the environment (sandbox or production), and the company_code. Fluid needs a company code on the slot or on the country before commits can be turned on, and it also picks the company when the account holds more than one. Then check them with Test a merchant Avalara connection. The first environment you save becomes the active one, and Fluid refuses the Avalara tax mode until one is active.
  2. Switch the company to Avalara with Set the tax class for a company. Fluid turns on commits only for a country that uses Avalara, so do this before step 3. The switch also clears each country’s tax strategy.
  3. Set each country’s Avalara options, such as committing US and Canadian orders to Avalara, with Update a company country. Set the shipping tax code and the products left out of tax with Update the merchant Avalara tax settings.
The merchant sets up the AvaTax account itself, including where they collect tax, in Avalara. Whoever calculates the tax, the merchant registers with the tax authorities where they collect it. Fluid doesn’t do that step. The Taxes help page explains each tax setting.

Step 5: Set up the catalog and store settings

If you connected a back office in Step 2, much of the catalog and customer data arrives from the sync. List what’s already there before you create anything, so you don’t make duplicates. Set up the rest over the API, in the same order as the admin’s Getting Started page: Each linked page holds the request and response schema. Lists on the same resources show what already exists. To add storefront pages, such as an about page or a page for the compensation plan, use the Create a page guided setup. It creates each page with its own template and publishes it.

Step 6: Connect social sales channels

Which path you take depends on whether the merchant already has accounts on these channels:
  • No account yet: the merchant creates the account on the channel, then connects it as below.
  • An existing account: connect it to Fluid with the guided setup for that channel.
TikTok Shop connects US seller accounts only. Before products publish there, a Fluid warehouse has to be linked to the shop’s TikTok warehouse. fluid channels warehouse tiktok <tiktok-warehouse-id> --yes sets it. If the command fails because the warehouse isn’t linked, link it in the admin as the TikTok Shop guided setup shows.

TikTok Shop

Connect, choose the warehouse and products, and fix rejections.

Meta

Facebook and Instagram: connect a catalog, choose products, and fix rejections.

Google Merchant Center

Google Shopping and YouTube: connect, choose products, and fix disapprovals.
YouTube Shopping uses the products Fluid sends to Google Merchant Center. The merchant links their YouTube channel to Merchant Center in Google, and YouTube’s eligibility rules apply. Fluid has no separate YouTube connection. Fluid also sells through Pinterest and Amazon. These channels don’t have a guided setup yet. To connect Pinterest or Amazon, use the API: Start the Pinterest connect flow or Start the Amazon Seller Central consent flow.
Merchant action: approve Fluid on each existing account. Connecting an account the merchant already has takes one browser step. The merchant signs in to the channel as an admin of the account and approves Fluid’s access. You start the connection and check it from the CLI before and after.

Step 7: Copy the merchant’s current site into a theme

Build the store as a Fluid theme, not a headless front end. The theme keeps merchant editing, FairShare credit, routing, SEO, menus, and translations working. See Why build on a Fluid theme. A preview is far more convincing when it looks like the merchant’s own site. Copy the current site into an unpublished Fluid theme, so you have something to preview without changing what shoppers see.

Use the clone skills (fastest)

Fluid publishes agent skills for this in the fluid-claude-skills repository:
  • fluid-theme-clone crawls the source site, rebuilds each page as Fluid theme sections, uploads the images, and compares screenshots against the original.
  • fluid-theme-refine runs after a clone and fixes visual differences until the pages match.
  • fluid-product-admin-import imports products, collections, pages, policies, and store settings from the existing site. Use it when the merchant has no back office to connect in Step 2.
Install them into your agent’s skills folder:
The clone skill needs Node 18 or later, the Fluid CLI, Playwright with Chromium (for its screenshot comparisons), an API token for the merchant’s company, and a Firecrawl API key for crawling. The skill calls the API with the token directly, so if the merchant signed in to the CLI in Step 1, ask them for a token here too. Then ask your agent something like:
The skill creates the theme as a draft and never publishes it unless you ask.

Copy it by hand with the Fluid CLI

If you’re not using the skills, build the theme with the Fluid CLI:
fluid theme dev serves the theme at http://127.0.0.1:9292 with live reload. Recreate the source site’s pages as sections and templates. The theme developer guide covers how they fit together. Run fluid theme skills install to give your agent Fluid’s theme review and settings skills as well. When the pages look right, push to a new unpublished theme:
Don’t run fluid theme push --publish or push to the live theme until the merchant approves. Either one changes what shoppers see.

Import the navigation

A cloned theme still shows the starter theme’s menu until you replace it. After the products, collections, and pages exist, rebuild the source site’s header menu through the menu API, linking each item to the matching Fluid record. Then confirm the header renders it. Leave the country and language selector in the header. Shoppers use it to switch markets. Manage navigation menus walks through the import.

Step 8: Test checkout and share the preview

Place a test order

Before you send the preview, place one test order to show checkout works. A new company has a test card gateway, so the order needs no browser and no real card, and it doesn’t wait for payments approval. With the CLI signed in as the merchant, run it first without --accept-agreements:
If the store has required agreements, this stops with AGREEMENTS_NOT_ACCEPTED, lists their titles, and places nothing. Read the titles to the merchant, and once they agree, run it again with the flag:
If the store has no required agreements, the first run places the order, so don’t run the second. --product takes the product.id that fluid products create printed in Step 5, and a draft product works. It buys one unit, ships to a built-in US address, pays with the test card 4242 4242 4242 4242, and prints the order’s id and number. Outside the US, pass the merchant’s address with --address, since tax is quoted for it: without one the command refuses with ADDRESS_REQUIRED. It takes a JSON object with address1, city, and postal_code, plus state and address2 when the address has them, for example --address '{"address1":"100 King St W","city":"Toronto","state":"ON","postal_code":"M5X 1A9"}'. The country is the company’s default, or pass --country. The command needs @fluid-app/fluid-cli-payments 0.1.148 or later: if the CLI says it’s an unknown command, rerun the Step 1 install.
  • It only pays the test gateway. Before anything is paid for, it checks that every payment method the cart offers is a test card on the test gateway, all on one payment account, and it reads the cart again just before the order completes. Otherwise it stops with a code and places nothing, for example NOT_TEST_GATEWAY, or NO_PAYMENT_ACCOUNT, which can mean the merchant hasn’t confirmed the signup yet.
  • The buyer is the signed-in merchant. The order uses their email, so it needs the merchant’s own sign-in from Step 1. With an API token it stops with PERSON_SIGN_IN_REQUIRED.
  • It accepts the store’s agreements as the buyer. If the store has required agreements, it stops with AGREEMENTS_NOT_ACCEPTED without --accept-agreements. The flag accepts them in the merchant’s name, so pass it only after the merchant has heard their titles.
  • The order is real, though no money moves. The merchant gets the confirmation email, order webhooks fire, inventory is adjusted, and the order shows in sales reports until it’s refunded. Refund and cancel it in the admin after the merchant has seen it.
  • Each run places a new order. If it fails with ORDER_OUTCOME_UNKNOWN, look in the admin for an order from the merchant’s email at that time before you run it again.
Without the CLI, or when you’re signed in with an API token, follow Place a test order instead: build a cart for one of the products, check the cart offers only the test gateway, get a test card token, attach it, and complete the checkout. If the cart offers any live payment method, stop and don’t place the order.

Share the preview

Get the new theme’s id from List application themes. Then build the preview URL on the store’s own address:
The link opens the storefront with the unpublished theme applied. The merchant sees their own site running on Fluid, with their own products, while shoppers still see the live theme. In the admin, Copy Preview URL on the theme’s card in Themes gives the same link. Send the merchant:
  • The preview link, and the live store at https://<subdomain>.fluid.app.
  • The test order’s number, so they know checkout works and which order was a test.
  • A short list of what’s set up: synced data, the countries you opened and how each one operates, the languages, sales channels, enrollments, and the theme.
  • What’s left for them: their details for the payments form, their submission, approvals for any channel accounts they already have, and a credit card when they’re ready to launch.

Step 9: Add a card, publish, and connect the domain

Merchant action: add a credit card. When the merchant is ready to launch, they add a card at Settings → Billing (https://admin.fluid.app/settings/billing). Usage is billed from there. Don’t enter card details for them.
Once the merchant has approved the preview, finish the launch:
  1. Make the approved theme live with Update an application theme, setting active to true. That is what the admin’s Publish button does, and shoppers see the theme right away. Publish a theme on its own doesn’t switch the live theme: it only publishes a theme’s latest content.
  2. To use the merchant’s own domain, follow the Custom domain guided setup. The merchant adds the DNS records it reports at their DNS provider, and you check the domain until it’s connected.
Make the theme live only after the merchant says so. It changes what every shopper sees.

Frequently asked questions

Can an AI agent set up an ecommerce store by itself?

Almost entirely. On Fluid, an agent can create the company, connect the back office, open countries, set up the store and its sales channels, and build the preview, following Fluid’s guided setups. The merchant has to act at these points:
  • At the start, they confirm their email address and sign in to the Fluid CLI, or create an API token for you.
  • If they have a back office, they share its credentials.
  • They provide their bank and ownership details and submit the payments form.
  • They approve Fluid on each social channel account they already have.
  • They approve the preview.
  • When they’re ready to launch, they add a credit card.

How long does it take to launch a store on Fluid?

About 20 minutes of agent work for a working store and preview. Payment processors review the payments application after the merchant submits it. The store and preview don’t wait for that review.

Do I need a credit card to try Fluid?

No. Fluid bills by usage, so an agent can build and preview the store first. The merchant adds a card at Settings → Billing when they decide to launch.

What is the best way to show a merchant their new store before they pay?

Copy their current website into an unpublished Fluid theme, then send them the theme’s preview link. They see their own site running on Fluid, with their own products. Nothing goes live until you make the theme live, after the merchant approves it.

Is Fluid an ecommerce platform for direct sales and MLM companies?

Yes. Fluid is built for brands that sell through reps, distributors, affiliates, and ambassadors. It attributes each sale to the right person and syncs with commission engines such as Exigo, ByDesign, Pillars, and InfoTrax.

Does Fluid replace my commission engine?

No. Fluid Connect syncs the commission engine you already use. Fluid handles the storefront, checkout, payments, and attribution, and sends orders back to the commission engine. See Works with your commission engine.

Can a Fluid store sell internationally?

Yes. One Fluid store can sell in many countries, and Fluid handles both the commerce and the payments:
  • Commerce: each country has its own currency, tax mode, fulfillment warehouse, and shipping fee, set up from Fluid’s Country Atlas. You choose which products and content are available in each country and translate them into each language. Shoppers switch country and language on the storefront.
  • Payments: one payments onboarding form covers every market. For each country, the merchant sets the currencies and the legal entity that serves it, and shoppers pay with local payment methods.

What’s the difference between international commerce and global payments on Fluid?

International commerce decides what a shopper in each country sees and pays: the products available to them, the language, the currency, the tax, and the shipping. Global payments decides how that money is collected: the local payment methods and processors, the settlement currency, and the legal entity that receives the funds. A store needs both to sell in a new country.

Can Fluid sell on social media?

Yes. A Fluid store can list its catalog on TikTok Shop, Facebook and Instagram through Meta, and Google Merchant Center. The merchant needs an account on each channel. Existing accounts connect through a guided setup. Each platform’s review of every product comes back to Fluid, so rejected products can be fixed in one place. Reps can also share any product link, and FairShare credits the sale to them.

Can I copy an existing website into Fluid?

Yes. The fluid-theme-clone agent skill rebuilds an existing site as an unpublished Fluid theme. You can also rebuild it by hand with the Fluid CLI.

Next steps