Guided setup

Each guided setup walks one configuration task from start to finish: what to run, what each result means, and what to do next. Every guide follows the same structure, so you can follow it by hand, script it with the Fluid CLI, or hand it to a coding agent.

Launch a whole store

To set up a new company from scratch, start with these two. Agent signup creates the company. The Agent launch guide then runs the setups below in launch order, from connecting a back office to publishing the store.

Sales channels

Fluid sells through five sales channels from the same catalog, and Google’s channel can also reach YouTube. Each channel connects to an account the merchant owns on that platform.

Available setups

How the guides work

Each guide has the same sections: Before you start, Steps, What the status means, Troubleshooting, and Use the API directly. The steps run commands from a Fluid CLI plugin. Every command prints JSON, so a script or an agent reads a result the same way a person does. Steps that change live configuration ask for confirmation. Pass --yes once you have confirmed the change, for example after a person approves it. Status checks run once and return immediately. When a step depends on something outside Fluid, such as DNS propagation, run its check again later instead of waiting on it.

Run a guide from the CLI

The setup plugin reads these guides from the docs, so you can follow one from a terminal. Install @fluid-app/fluid-cli-setup, then: The <id> is the id in the guide’s setup block, such as custom-domain or open-a-country. fluid setup list prints each one.

For agents and tools

Each guide’s frontmatter carries a setup block that lists its steps in order. Each step has an id, a title, the command it runs (run), whether it changes live configuration (changes), and, for a step you repeat, the result that means it is done (done_when). The block matches the guide’s Steps section, so a tool can follow the steps without parsing the prose.