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

# Countries

> Add the countries your company sells in and set each one's mode, currency, fulfillment warehouse, shipping fee, business tax ID and 3DS setting.

Use the Countries screen to manage the countries your company sells in. You can add a country, change its settings, or delete it.

## Where to find it

In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Commerce**, select **Countries**.

## What's on the screen

The **Add Country** button is in the page header. The table lists one row per country:

* **Country**: the country's flag and name. A country can also show a badge:
  * **Default**: your default country.
  * **No test gateway**: the country is in test mode, but it has no test gateway it can use. See [What does the No test gateway badge mean?](#no-test-gateway)
* **Tax Mode**: how tax is calculated for the country, such as **Fluid's Tax Solution** or **Free Tax**. This column appears only when your company's tax calculation is set to **Per Country** on the [Taxes](/help/admin/settings/taxes) screen.
* **Currency**: the currency code the country uses.
* **Fulfillment Warehouse**: the warehouse assigned to the country, or a dash if none is set.
* **Shipping/Handling Fee**: the country's fee, shown with its currency symbol.
* **Last Updated**: when the country was last changed, for example **Today** or **3 days ago**. Changes 30 or more days old show the date.

Use the sort menu or the search box above the table. Search finds countries by name, currency or warehouse.

Click a row, or choose **Edit** from its actions menu, to open the **Edit Country** panel. The actions menu also has **Delete**.

### Country panel fields

**Add Country** and **Edit Country** open the same panel. From top to bottom, it has:

* **Mode**: choose **NFR**, **OTG** or **USD**. New countries start on **NFR**. Under the buttons, the panel describes the selected mode:
  * **NFR** (Not For Resale): sample-only, no local commerce.
  * **OTG** (On The Ground): full commerce with a local entity.
  * **USD**: cross-border selling settled in US dollars.
* **Country** (required): the country to add. You can't change it after the country is saved.
* **Currency** (required): the currency the country uses. Each option shows a currency code and name.
* **Fulfillment Warehouse**: choose one of the warehouses on the [Warehouse](/help/admin/settings/warehouses) screen.
* **Shipping/handling Fee**: a number, in the currency you choose for the country. If the [Shipping](/help/admin/settings/shipping) screen is set to **Flat Country Rates**, this is the fee charged for orders shipped to this country.
* **Default Country**: a switch. Turn it on to make this your company's default country.
* **Business tax ID number**: the country's tax registration number, such as a VAT, GST or EIN number. You can also edit it on the [Taxes](/help/admin/settings/taxes) screen.
* **Enable 3DS**: choose **Enabled** to turn on 3D Secure authentication for card payments on orders to this country, where your payment gateway supports it. Choose **Disabled** to use normal card authorization without a country-level 3DS requirement. New countries start on **Disabled**.
* **Legal Disclaimer**: a reminder that business laws vary by country, and that your business must comply with this country's legal requirements. For some countries, it also summarizes local direct-selling rules. For others, it suggests you consult local legal experts.

The panel ends with **Cancel** and **Save**. If you leave **Country** or **Currency** empty, a message such as **Currency is required** appears under the field and the panel stays open. If the save fails for another reason, the panel closes and **Failed to save country** appears with details.

<Note>
  If you don't see **Add Country**, **Delete** or **Save**, your role can view countries but can't change them. An admin who manages roles can set **Company Countries**, in the **Settings** category card, to **Full access**. See [Roles](/help/admin/settings/roles).
</Note>

## Add a country

<Steps>
  <Step title="Open the panel">
    Click **Add Country**.
  </Step>

  <Step title="Choose a mode">
    Under **Mode**, click **NFR**, **OTG** or **USD**.
  </Step>

  <Step title="Select the country and currency">
    Choose the **Country** and its **Currency**.
  </Step>

  <Step title="Set the optional fields">
    If you need them, choose a **Fulfillment Warehouse** and enter a **Shipping/handling Fee** and a **Business tax ID number**. Turn on **Default Country** only if this country should become your default. Under **Enable 3DS**, choose **Enabled** or **Disabled**.
  </Step>

  <Step title="Save">
    Click **Save**. You see **Country updated successfully!** and the country appears in the table.
  </Step>
</Steps>

## Edit a country

<Steps>
  <Step title="Open the country">
    Click the country's row, or choose **Edit** from its actions menu. The **Edit Country** panel opens.
  </Step>

  <Step title="Change its settings">
    Update any field except **Country**, which is locked.
  </Step>

  <Step title="Save">
    Click **Save**. You see **Country updated successfully!**
  </Step>
</Steps>

## Delete a country

<Note>
  You can't delete a country if any order has a shipping address in that country, or if any subscription uses it. You also can't delete it while products are still sold there. The error message names up to five of the products that block the delete.

  To clear products, turn off **Enable** for the country on each product's variants, save the product, and try again. See [Choose which products sell in a country](#product-availability-by-country).
</Note>

<Steps>
  <Step title="Choose Delete">
    In the country's actions menu, choose **Delete**.
  </Step>

  <Step title="Confirm">
    The **Delete Country** dialog asks you to confirm. Click **Delete**. If the delete works, you see **Country deleted successfully!** If it fails, you see **Failed to delete country** with the reason.
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="Where do I set tax for a country?" id="country-tax-settings">
    Apart from the **Business tax ID number**, a country's tax settings are on the [Taxes](/help/admin/settings/taxes) screen, not here. In the Settings sidebar, under **Commerce**, select **Taxes**. In the **Per-Country Tax Configuration** card, choose **Edit Tax Settings** from the country's actions menu.
  </Accordion>

  <Accordion title="Do I need a country before I create products?" id="country-before-products">
    Yes. On a new product, **Create Product** stays grayed out while your company has no countries.
  </Accordion>

  <Accordion title="How do I choose which products sell in a country?" id="product-availability-by-country">
    You set this on each product, per variant, not on the Countries screen. A new variant starts with every country turned off.

    <Steps>
      <Step title="Open the product">
        In the admin sidebar, under **We-Commerce**, go to **Storefront** > **Products** and open the product.
      </Step>

      <Step title="Show a variant's countries">
        In the **Variant Pricing** card, click the arrow at the end of the variant's row to show its country grid. On a saved product, the first variant's grid is already open.
      </Step>

      <Step title="Turn countries on or off">
        Use the **Enable** switch on each country's row. The variant's **Available In** column shows the countries that are on.
      </Step>

      <Step title="Save the product">
        Click **Save**.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Why can't I see Countries in the Settings sidebar?" id="countries-missing">
    The **Countries** item appears only if your role has **View only** or **Full access** for **Company Countries**, in the **Settings** category card. Ask an admin who manages roles to set it. The separate **Country Markets** permission doesn't control this screen. See [Roles](/help/admin/settings/roles).
  </Accordion>

  <Accordion title="What does the No test gateway badge mean?" id="no-test-gateway">
    The country is in test mode, but no test gateway can serve it. While test mode is on for your company, card payments for the country are blocked.

    To clear the badge, open the Settings sidebar. Under **Payments**, select **Payment Routing**. There, assign a test gateway that can serve the country, or take the country out of test mode.
  </Accordion>
</AccordionGroup>

## Related pages

* [Settings](/help/admin/settings)
* [Taxes](/help/admin/settings/taxes)
* [Warehouse](/help/admin/settings/warehouses)
* [Shipping](/help/admin/settings/shipping)
* [Roles](/help/admin/settings/roles)
