> ## 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.

# Products

> Create and edit products and bundles, set up variants, pricing, inventory and subscription plans, and choose where each product is sold.

Use the **Products** screen to manage your catalog. You create products and bundles here, set up their variants, prices and stock, and choose where each one appears.

## Where to find it

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

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

## What's on the screen

**Add Product** is at the top of the page. It opens a menu with **New Product** and **New Bundle**.

* The **All**, **Active**, **Draft**, **Archived** and **Bundles** tabs filter the list. **Active** lists products that are published or scheduled.
* The search box finds products by name, description or URL slug. It doesn't search SKUs.
* The filter panel has **Status**, **Bundles Only**, **Availability** (**In Stock**), **Country Availability**, **Category** and **Collection**. Click **Apply Filters** to use them.

The list has these columns:

* **Product**: the product's main image.
* **Name**: the product title. You can sort by it.
* **Status**: **Published**, **Scheduled**, **Draft** or **Archived**.
* **Price**: the product's price.
* **SKU**: the SKU of the product's default variant.
* **Date Modified**: when the product last changed. You can sort by it.

Click a product to open it. Each row's actions menu has **Edit** and **Delete**. To delete several products, select their rows and use the table header's menu. Its delete action shows the count, such as **Delete 3 products**.

A banner above the list lets you try a new version of the table. Click **Try it** to switch, and **Switch back** to return.

## Create a product

<Steps>
  <Step title="Start a new product">
    Click **Add Product**, then **New Product**. The **Create Product** page opens.
  </Step>

  <Step title="Add the details">
    In the **Product Details** card, enter a **Product Title** (up to 255 characters). Add a **Short Description** and a **Description** if you want them.
  </Step>

  <Step title="Add media">
    Click **Select Media** and choose up to 10 files at a time. Supported formats are JPG, PNG, GIF, WebP, BMP, SVG, MP4 and MOV, up to 10MB each. The first item must be an image; a video can't be the featured media. Drag items to reorder them.
  </Step>

  <Step title="Set the SKU and stock">
    In the **Inventory** card, enter the **SKU** and **Barcode (UPC)**. To track stock, check **Track Quantity**, then enter **Available** or **On Hand** for each warehouse. Changing one also changes the other. After you check **Track Quantity**, **Keep selling when out of stock** and the warehouse table appear; check **Keep selling when out of stock** if you want to allow backorders. **Limit Subscription Quantity** sets a **Subscription Max Quantity** and a **Max Quantity Per Person**.
  </Step>

  <Step title="Set prices">
    In the **Variant Pricing** card, click the arrow at the end of a variant's row to show its countries. Turn on each country where the product is sold and enter its prices. Use **Search Countries** to find a country.
  </Step>

  <Step title="Choose status and channels">
    In the **Status** card, a new product starts as **Draft**. In the **Publish Options** card, choose where it shows: **Storefront**, **Mobile App**, **Portal Shop** and **Share Tab**. All four are on for a new product.
  </Step>

  <Step title="Organize it">
    Under **Tax Categories**, choose a **USA Tax Category** and an **International Tax Type**. Under **Product Organization**, choose **Collections**, a **Category** and **Tags**. You can type a new tag name to create it.
  </Step>

  <Step title="Create the product">
    Click **Create Product**. It stays grayed out until the product has a title and the page has finished loading. The product's page opens when it's created.
  </Step>
</Steps>

The **Inventory** card only appears while the product has a single variant. Once you add variants, set SKUs and stock on each variant's page. Only active warehouses are listed.

## Edit a product

<Steps>
  <Step title="Open the product">
    In the list, click the product. The **Product Details** page opens.
  </Step>

  <Step title="Make your changes">
    Change any card. To offer subscriptions, click **Manage Subscription Plans** in the **Subscription Plans** card, turn on the plans you want, and click **Done**. A plan's menu has **Set as default plan**.
  </Step>

  <Step title="Save">
    Click **Save**. It's grayed out until you change something. If you leave the page with unsaved changes, the admin asks you to confirm.
  </Step>
</Steps>

**Preview** opens the product on your storefront once it has a URL. **Translations** opens a grid where you translate the **Product Title**, **Short Description**, **Description**, **Features** and images into your active languages.

To publish later, choose **Scheduled** in the **Status** card and pick the date and time it should go live.

## Add variants

<Steps>
  <Step title="Choose a variant type">
    In the **Variant Pricing** card, click **Add Variant Type** and choose **Color**, **Size**, **Material**, **Pattern** or **Create Manually**.
  </Step>

  <Step title="Enter the options">
    Fill in **Variant Type (e.g. Color, Size)** and the **Variant Options (e.g. Purple, Large)**, then click **Save**. Fluid creates a variant for each combination of options.
  </Step>

  <Step title="Save the product">
    Click **Save** at the top of the page, or **Create Product** if the product is new.
  </Step>

  <Step title="Open a variant">
    Click a saved variant's row to open its **Variant Details** page. Clicking a variant you haven't saved yet only shows its countries.
  </Step>
</Steps>

The variant page has these cards:

* **Status**: **Active** (available for purchase) or **Inactive** (hidden from customers).
* **Options and Variants**: every variant of the product. Click one to switch to it.
* **Variant Details**: **Display Name** (optional; replaces the generated title for customers), **SKU**, **Barcode (UPC)** and the variant's **Media**.
* **Pricing**: one row per country, with **Enable**, **Price**, **Subscription Price**, **Wholesale Price**, **Wholesale Sub**, **Compare Price**, **QV**, **CV**, **COGS**, **Shipping** and your company's points. Use **Search countries** to find a row.
* **Inventory**: **Track Quantity**, **Keep selling when out of stock**, **Subscription Only**, **Limit Subscription Quantity** and **Limit Quantity Per Person**, plus the warehouse table.
* **Shipping & Measurements**: **Physical Product** or **Digital Product or Service**, **Country of Origin** and **Harmonized System (HS) Code**. Physical products also have **Weight** (lb, kg, g or oz) and **Height**, **Width** and **Length** (In, cm, mm or ft).
* **Variant metafields**.

Click **Save** to keep your changes.

## Duplicate, archive or delete a product

Open the product and click the actions menu at the top of the page. Roles with view-only access don't see this menu.

* **Duplicate** makes a copy and opens it.
* **Archive** hides the product from your sales channels. An archived product shows **Unarchive** instead, which makes it active again.
* **Delete** removes the product. Deleting can't be undone.

Each of these except **Duplicate** asks you to confirm. If the product is part of a bundle, the archive confirmation names the bundle. Saving a status change to **Draft** or **Archived** on such a product also warns you first. Click **Save anyway** to continue or **Go back** to keep editing.

## Create a bundle

<Steps>
  <Step title="Start a new bundle">
    Click **Add Product**, then **New Bundle**. The **Create Bundle** page opens.
  </Step>

  <Step title="Add the details">
    Enter a **Bundle Title** and the other details, as for a product.
  </Step>

  <Step title="Add groups">
    In the **Bundle Groups** card, add a **Static** group for items that are always in the bundle, or a **Customizable** group for items the customer chooses. Add at least one item to each group.
  </Step>

  <Step title="Create the bundle">
    Click **Create Bundle**. A bundle needs at least one group, and every group needs at least one item.
  </Step>
</Steps>

Bundles appear on the **Bundles** tab.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why can't I find a product by its SKU?" id="search-by-sku">
    The search box matches product names and descriptions, not SKUs. Search by name, or use the filters.
  </Accordion>

  <Accordion title="Why is Create Product grayed out?" id="create-product-disabled">
    The product needs a **Product Title**. If you've entered one, wait for the page to finish loading.
  </Accordion>

  <Accordion title="Why don't I see the Inventory card?" id="no-inventory-card">
    The product has more than one variant. Open each variant from the **Variant Pricing** card and set its stock there.
  </Accordion>

  <Accordion title="How do I change a product's SEO?" id="product-seo">
    On the product's page, find the **SEO And Link Sharing** card and click **Edit**. You can set the **SEO Image**, **Title Tag** and **Meta Description**, use a custom **URL Slug**, or turn on **Block search engine crawlers**. Then click **Save** on the product page.
  </Accordion>

  <Accordion title="How do I make a product available in another country?" id="country-availability">
    In the **Variant Pricing** card, click the arrow at the end of the variant's row, or open the variant and use its **Pricing** card. Turn on the country, enter its prices, and save.
  </Accordion>
</AccordionGroup>

## Related pages

* [Storefront](/help/admin/storefront)
* [Inventory](/help/admin/inventory-levels)
* [Categories](/help/admin/categories)
* [Collections](/help/admin/collections)
* [Subscription Plans](/help/admin/settings/subscription-plans)
* [Warehouses](/help/admin/settings/warehouses)
* [Taxes](/help/admin/settings/taxes)
* [Metadata definitions](/help/admin/settings/metadata-definitions)
* [We-Commerce concepts](/concepts/we-commerce)
* [Storefront SEO](/storefront/seo)
* [Storefront translations](/storefront/translations)


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