> ## 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. > 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. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/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. > Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable. > 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. # Warehouses > Add your company's warehouse and fulfillment locations, keep their addresses up to date, and set each one active or inactive. Use the Warehouses screen to keep a list of your company's warehouse locations and their addresses. Products and bundles track their stock by warehouse. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Commerce**, select **Warehouse**. ## What's on the screen The **Add Warehouse** button is in the page header. Above the table are the **All**, **Active** and **Inactive** tabs, a sort menu and a search box. Sort by **Warehouse Name** or **Address**, or click either column header. Search finds warehouses by name or by any part of the address, including the country code. The table lists one row per warehouse: * **Warehouse Name**: the name you gave the warehouse. * **Address**: the street address, city, state, postal code and country code. * **Status**: an **Active** or **Inactive** badge. Click a row to open the warehouse. Each row's three-dot menu has **Edit** and **Delete**. If the table is empty, it shows **No warehouses yet** with an **Add Warehouse** button below it. This also happens when no warehouse matches your tab or search. Check the **All** tab or clear the search. ### Warehouse panel fields **Add Warehouse** and **Edit** open a side panel titled **Add Warehouse** or **Edit Warehouse**. In order, it has: * **Warehouse Name** (required). Each warehouse needs its own name. * **Country** (required): choose the country from the list. You can type to search the list. * **Street Address** (required). * **Street Address 2**: an optional second address line. * **City** (required). * **State** (required). * **Postal Code** (required). * **Active**: on by default for a new warehouse. Turn it off to make the warehouse inactive. The panel ends with **Cancel** and **Save**. If you leave a required field empty, a message such as **Postal code is required** appears under it when you click **Save**. ## Add a warehouse Click **Add Warehouse**. Choose a **Country** and fill in the other fields. You can leave **Street Address 2** empty. To add the warehouse as inactive, turn off **Active**. Click **Save**. You see **Warehouse created successfully** and the warehouse appears in the table. ## Edit a warehouse Click the warehouse's row, or choose **Edit** from its three-dot menu. The **Edit Warehouse** panel opens with the current details. Change the fields you need. To stop using the warehouse without deleting it, turn off **Active**. Click **Save**. You see **Warehouse updated successfully**. ## Delete a warehouse You can delete a warehouse only if it has no stock levels and no orders. A stock level counts even when its quantity is zero. If you try to delete a warehouse that's in use, you see an error that starts with **Failed to delete warehouse**, and nothing is deleted. To retire a warehouse that's in use, turn off **Active** instead. It stays on the list under the **Inactive** tab. Deleting a warehouse can't be undone. The shipping methods that use the warehouse are deleted with it, and any country that used it as its **Fulfillment Warehouse** is left without one. In the warehouse's three-dot menu, choose **Delete**. The **Delete warehouse?** dialog asks you to confirm. Click **Delete**. You see **Warehouse deleted successfully**. ## FAQ The stock table on a product's page and on a bundle's page lists only active warehouses. A variant's own page can still show an inactive warehouse if the variant already has stock levels recorded there. On the **Inventory** screen, the warehouse menu still lists inactive warehouses. Three settings screens let you pick a warehouse from this list. All three lists include inactive warehouses. * **Countries**: each country has an optional **Fulfillment Warehouse**. When you add a warehouse, it becomes the **Fulfillment Warehouse** of its country if that country is on your **Countries** screen and has no warehouse yet. See [Countries](/help/admin/settings/countries). * **Entities** (under **Company**): on an entity's **Entity Information** tab, each country under **Operating Countries** needs a **Warehouse**, the one that fulfills orders for that country. * **Shipping**: each shipping method needs a **Warehouse**. If you use **Fluid Rates**, click **Manage Shipping Methods** to see your methods. See [Shipping](/help/admin/settings/shipping). You see **Failed to save warehouse**, sometimes with the reason. The panel closes and your details aren't saved. Open the panel again, re-enter the details and click **Save**. The **Warehouse** item appears only if your role can view warehouses. Ask an admin who manages roles to edit your role's permissions: open the **Settings** card, then set **Warehouses** to **View only** or **Full access**. See [Roles](/help/admin/settings/roles). Each action depends on the **Warehouses** permissions on your role: * **Add Warehouse** needs **Add new warehouses** and **Edit warehouse details**. Without **Add new warehouses**, the **Add Warehouse** button doesn't appear, and an empty table shows **Nothing to show** instead of **No warehouses yet**. * **Save** on an existing warehouse needs **Edit warehouse details**. Without it, you can still open a warehouse, but the panel has no **Save** button. * **Delete** needs **Delete warehouses** and **Edit warehouse details**. Without **Delete warehouses**, **Delete** doesn't appear in the three-dot menu. Ask an admin who manages roles to edit your role's permissions: open the **Settings** card, then set **Warehouses** to **Full access**. To grant only some actions, they can click **Warehouses** and turn on the permissions listed above. See [Roles](/help/admin/settings/roles). ## Related pages * [Settings](/help/admin/settings) * [Countries](/help/admin/settings/countries) * [Shipping](/help/admin/settings/shipping) * [Roles](/help/admin/settings/roles)