> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluid.app/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract.
> Authenticate with the header Authorization: Bearer <token>; public storefront read endpoints require no auth.
> To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible.
> After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch.
> Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null.
> When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination.
> Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile.
> The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country).
> api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract).
> Successful responses wrap the resource payload alongside a top-level integer status and a meta object.
> Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other.
> For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces.
> Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings.
> Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties.
> Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables.
> A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation.
> The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations.
> Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check.
> Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times.

# Categories

> Create product categories, choose which products they hold and in what order, and set each category's status, countries, theme template and SEO.

Use the **Categories** screen to group products into categories for your storefront. Each category has its own title, description, image, product list and storefront settings.

## Where to find it

In the admin sidebar, under **Storefront**, select **Categories**.

<Note>
  To open this screen, your role needs **View only** or **Full access** for **Categories**. To create, edit or delete categories, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Categories** is in the **Commerce** card. Open the card and set access from the **Categories** area's menu, not the card's.
</Note>

## What's on the screen

The **Add Category** button is at the top of the page. Below it is the list of categories.

* The **All**, **Published**, **Scheduled**, **Draft** and **Archived** tabs filter the list by status.
* Use the search box to find a category by name.
* Sort the list by **Name** or **Date Modified**. Until you choose a sort, the newest categories are first.

The list has these columns:

* **Preview**: the category's image, or an empty frame if it has none.
* **Name**: the category's title.
* **Status**: **Published**, **Draft**, **Archived**, or **Scheduled** with the date and time it goes live.
* **Countries**: **All** when the category is available in every country you sell in. Otherwise, the flags of the countries it's limited to, with a count such as **+3** for the rest.
* **Date Modified**: when the category last changed.

Click a category to open it. Each row's actions menu has **Edit** and **Delete**. To delete several categories, select their rows; the selection's menu shows the count, such as **Delete 3 categories**.

A banner above the list offers a new version of the table. Click **Try it** to use it, or **Switch back** to return. The new table adds **Status** and **Country** filters. Your choice is remembered on that device.

## Create a category

<Steps>
  <Step title="Start a new category">
    On the **Categories** screen, click **Add Category**. The **Create Category** page opens.
  </Step>

  <Step title="Enter the details">
    In the **Category Details** card, enter a **Title**. Add a **Description** if you want one; the editor has formatting tools such as bold, lists and links.
  </Step>

  <Step title="Add an image">
    Under **Media**, click **Select Image** and choose or upload an image. JPG, PNG, GIF, WebP, BMP and SVG files up to 10 MB are supported.
  </Step>

  <Step title="Add products">
    In the **Associated Products** card, click **Add Products** and select the products you want. There's no limit on how many products a category holds. Drag products to set the order they appear in on your storefront.
  </Step>

  <Step title="Set the status">
    In the **Status** card, choose a status. A new category starts as **Published**, so choose **Draft** if it isn't ready. See [Status options](#status-options).
  </Step>

  <Step title="Set the other cards">
    Optionally, limit the **Countries**, choose a **Theme Template**, and edit **SEO And Link Sharing**. See [Cards on the category page](#cards-on-the-category-page).
  </Step>

  <Step title="Create the category">
    Click **Create Category**. A confirmation message appears and the category's page opens.
  </Step>
</Steps>

<Tip>
  Fill in the **Metafields** card after you create the category, from the category's page.
</Tip>

## Edit a category

<Steps>
  <Step title="Open the category">
    In the list, click the category, or choose **Edit** from its actions menu. The **Category Details** page opens.
  </Step>

  <Step title="Make your changes">
    Change the fields and cards you need, add or remove products, or drag products into a new order.
  </Step>

  <Step title="Save">
    Click **Save**. A confirmation message appears when the category is saved.
  </Step>
</Steps>

The title at the top of the page shows the category's name and a badge with its current status.

### Status options

The **Status** card has four options:

* **Published**: live and visible to the public.
* **Draft**: hidden from public view.
* **Scheduled**: goes live automatically at a date and time you choose. Pick the date and time, then click **Schedule Activation**. The card then shows the scheduled date.
* **Archived**: retired and hidden from public view.

<Warning>
  Scheduling isn't a privacy setting. A scheduled category is reachable by direct link before its scheduled date. The date controls when it appears in listings and becomes available for search engines to index.
</Warning>

### Cards on the category page

* **Metafields**: values for any metafields your company has defined for categories. Each value has its own **Save** button. To define metafields, see [Metadata Definitions](/help/admin/settings/metadata-definitions).
* **Countries**: the countries where the category is available. Leave it on **All Countries** to make it available in every country you sell in, including countries you add later. Choose countries to limit it to those.
* **Theme Template**: the template from your active theme that displays the category. If none is chosen, the theme's default category template is selected for you. If your theme has no category templates, choose **Create Template** to add one.
* **SEO And Link Sharing**: how the category appears in search results and shared links. See [Edit SEO and link sharing](#edit-seo-and-link-sharing).
* **Fluid Connect**: appears only when your company has a connected [Exigo](/setup/connect-exigo), [InfoTrax](/setup/connect-infotrax), [ByDesign](/setup/connect-bydesign) or [Pillars](/setup/connect-pillars) droplet, and links to that droplet.
* **Analytics**: the category's **Shares**, **Page Speed** and **Content Compliance**. Click a metric to see its details. You can request a new page speed or compliance scan from its details; results can take a few minutes.

### Edit SEO and link sharing

<Steps>
  <Step title="Open the panel">
    In the **SEO And Link Sharing** card, click **Edit**.
  </Step>

  <Step title="Edit the search text">
    Edit the **Title Tag** and **Meta Description**. They start from the category's title and description. The suggested lengths are 70 characters for the title tag and 160 for the meta description.
  </Step>

  <Step title="Set the image and preview">
    Add or replace the **SEO Image**. Use the **Preview** menu to see the category as a **Google Search Result**, a **Text Message** or on **X (formerly Twitter)**.
  </Step>

  <Step title="Set the URL and visibility">
    The **URL** field shows the category's address. Turn on **Use custom slug** to edit the **URL Slug**; otherwise the slug is made from the title. Turn off **Search engine visibility** to keep the category out of Google and other search engines.
  </Step>

  <Step title="Close the panel and save">
    Click **Done**, then click **Save** on the category page.
  </Step>
</Steps>

**Done** is grayed out until the **Title Tag** has at least 3 characters and the **Meta Description** has at least 5.

### Other actions on a saved category

* **Preview** opens the category on your storefront in a new tab.
* **Translations** opens the category's **Category Title**, **Description** and **Category Image** in each of your active languages. Save your translations from that panel. To manage languages, see [Languages](/help/admin/settings/languages).
* **Reset Cache**, in the **Actions** menu, clears the storefront's cached copy of the category.

## Delete a category

<Steps>
  <Step title="Choose Delete">
    In the list, choose **Delete** from the category's actions menu. To delete several, select their rows and choose the delete option that shows the count, such as **Delete 3 categories**.
  </Step>

  <Step title="Confirm">
    In the confirmation dialog, click **Delete**.
  </Step>
</Steps>

You can also open a category and open the **Actions** menu and choose **Delete Category**, then click **Delete Category** to confirm. You return to the list.

<Warning>
  Deleting a category can't be undone.
</Warning>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why is Create Category grayed out?" id="create-category-disabled">
    Enter a **Title** in the **Category Details** card. **Create Category** is available once the category has a title.
  </Accordion>

  <Accordion title="Why don't I see Preview?" id="no-preview">
    **Preview** isn't on the **Create Category** page. It appears at the top of the category's page after you create it.
  </Accordion>

  <Accordion title="What does All mean in the Countries column?" id="countries-all">
    The category isn't limited to particular countries. It's available in every country your company sells in, including countries you add later.
  </Accordion>

  <Accordion title="Why don't I see Add Category, or why can't I edit a category?" id="no-add-or-edit">
    Your role can view categories but doesn't have **Full access** for **Categories**. Without it, a category's page opens read-only, with no **Save** button. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles).
  </Accordion>
</AccordionGroup>

## Related pages

* [Storefront](/help/admin/storefront)
* [Products](/help/admin/products)
* [Collections](/help/admin/collections)
* [Countries](/help/admin/settings/countries)
* [Category hierarchy](/storefront/category-hierarchy)
* [Country availability](/storefront/country-availability)
* [SEO](/storefront/seo)
* [Slugs and URLs](/storefront/slugs-and-urls)
* [Visibility](/storefront/visibility)
* [Translations](/storefront/translations)
* [Metafields](/storefront/metafields)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.