> ## 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 ; 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. # Inventory > See and change stock levels for each product variant in a warehouse, turn inventory tracking on or off, and export a warehouse's inventory to CSV. Use the **Inventory** screen to see how much stock each product variant has in a warehouse and to correct those counts. You can also choose which variants Fluid tracks and whether they keep selling when they run out. ## Where to find it In the admin sidebar, under **Commerce**, select **Inventory**. To open this screen, your role needs **View only** or **Full access** for **Inventory**. To change quantities, change tracking and selling settings, or delete inventory, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Inventory** is in the **Commerce** card. Open the card and set access from the **Inventory** area's menu, not the card's. ## What's on the screen Inventory is kept per warehouse. The screen opens on your company's first warehouse. The warehouse's name appears next to the **Inventory** title. Click it to open a list of your warehouses, with each one's city and country, and choose another. At the top of the page: * **Export** downloads the selected warehouse's inventory as a CSV file. * **Save Changes** appears when you've changed a quantity that you haven't saved yet. Use the **Search...** box to find items. It matches the product name, the variant name, the SKU, and the names of the product's tags and collections. The list shows 50 items per page. The list has these columns: * The product's image. * **Name**: the product's name, with the variant's name as a badge when the variant has one. * **SKU**: the variant's SKU, or **—** when it has none. * **Unavailable**: split into four categories: **Damaged**, **Quality control**, **Safety stock** and **Other**. * **Committed**: you can't edit this column. * **Available**: type a new total, or adjust it from the field's menu. * **On Hand**: the total of **Available**, **Unavailable** and **Committed**. You can also type a new total here. Click a product's image or name to open the product. Rows for variants that Fluid doesn't track are grayed out, and their quantity columns are empty. Each row's actions menu has **Track inventory** or **Stop tracking inventory**, **Continue selling when out of stock** or **Stop selling when out of stock**, and **Delete**. Select several rows to use the same actions from the table header's menu: **Start Tracking Inventory**, **Stop Tracking Inventory**, **Continue Selling When Out of Stock**, **Stop Selling When Out of Stock**, and **Delete**, labeled with the count, such as **Delete 3 Inventories**. ## Tasks Quantity changes stay on the page until you click **Save Changes**. Tracking, selling and delete actions save as soon as you confirm them. Click **Save Changes** before you change page, search, or switch warehouse. ### Change available or on-hand stock Click the warehouse name next to the title and choose the warehouse. In the item's row, click the **Available** or **On Hand** field, type the new total, and press Enter. When you change **Available**, **On Hand** updates to match. When you change **On Hand**, **Available** updates instead. Click the arrow next to the field instead. For **Available**, leave the first menu on **Adjust Available**. In **Adjust By**, enter the amount to add, or a negative amount to remove, and press Enter. Click outside the menu to apply it. **Available** and **On Hand** both change by that amount. Click **Save Changes**. A confirmation message appears. ### Move stock to unavailable Click the arrow next to the item's **Available** field. In the first menu, choose **Move to Unavailable**. Choose a **Reason** from the list every time: **Other**, **Damaged**, **Quality control** or **Safety Stock**. Then enter the **Quantity** and press Enter. You can't move more than the item's available stock. Click outside the menu. **Available** goes down and **Unavailable** goes up by the same amount; **On Hand** doesn't change. Click **Save Changes**. ### Manage unavailable stock Click the item's **Unavailable** value. The **Unavailable inventory** menu lists each category and its count. Click a category's count, then choose an action: * **Add inventory** adds units to the category. **On Hand** goes up too. * **Move to Available** moves units from the category back to **Available**. It appears only when the category has units. * **Delete inventory** removes units from the category. **On Hand** goes down too. Enter the **Quantity** and press Enter. To move or delete, you can't enter more than the category holds; the menu shows the limit. Click **Save Changes**. ### Turn tracking or out-of-stock selling on or off Open a row's actions menu and choose the tracking or selling action. To change several items, select their rows and use the table header's menu. In the dialog, click **Start Tracking**, **Stop Tracking**, **Continue Selling** or **Stop Selling**. A confirmation message appears. These settings belong to the product variant, so they apply in every warehouse, not only the one you're viewing. **Continue selling when out of stock** lets customers buy the variant even when its inventory reaches zero. ### Export inventory Click **Export**. Fluid downloads a CSV file named `inventory_export_` followed by today's date, with the selected warehouse's inventory. ### Delete inventory Choose **Delete** from a row's actions menu, or select several rows and choose **Delete** from the table header's menu. In the **Delete Inventory?** dialog, click **Delete**. Deleting removes the inventory record for the selected variants at this warehouse, and Fluid stops tracking their inventory there. This can't be undone. ## Frequently asked questions Fluid doesn't track inventory for that variant. To start tracking it, choose **Track inventory** from the row's actions menu. **Committed** is shown for reference only. Change **Available**, **On Hand** or **Unavailable** instead. **Save Changes** appears only after you change a quantity. If it still doesn't appear, or the rows have no tracking, selling or delete actions, your role doesn't have **Full access** for **Inventory**. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). Yes. Inventory is kept per warehouse, so your company needs at least one warehouse. Set one up on the [Warehouses](/help/admin/settings/warehouses) screen. ## Related pages * [Commerce](/help/admin/commerce) * [Products](/help/admin/products) * [Warehouses](/help/admin/settings/warehouses) * [Roles](/help/admin/settings/roles) * [We-Commerce](/concepts/we-commerce) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.