> ## 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.
> 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/auth-v0.yaml covers the unversioned auth surface (/api/... paths — authentication, MFA, social auth, and token exchange); 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.

# Member subscription pricing

> Recurring prices become member-aware too. A recurring price belongs to a product and a plan, so every shell names the plan it was rendered for.

<Warning>
  Not yet available. This describes work in review, and details can change before it ships. [Member pricing](/themes/member-storefront/member-pricing) is the shipped behavior for one-time prices.
</Warning>

A one-time price belongs to a product. A recurring price belongs to a product **and a plan** — the same product can cost different amounts on a monthly plan and an annual one. Everything on this page follows from that.

Read [Member pricing](/themes/member-storefront/member-pricing) first. The rules there — visible text only, scalars everywhere else, the public price as the fallback — apply here unchanged.

## What becomes member-aware

Recurring price displays, when the plan can be determined:

```liquid theme={null}
{{ product.subscription_price }}

{% for plan in product.subscription_plans %}
  {{ plan.display_subscription_price }}
{% endfor %}
```

`subscription_price`, `display_subscription_price` and `unit_subscription_price` are recognised. The older top-level `{{ subscription_price }}` variable works too, so themes that print it need no edit.

## The plan is always named

A recurring shell is a **different element** from a one-time one, and it carries the plan:

```html theme={null}
<fluid-member-subscription-price
  data-product-id="9575"
  data-variant-id="10883"
  data-country-iso="US"
  data-subscription-plan-id="11"
>¥495</fluid-member-subscription-price>
```

**A display whose plan cannot be determined emits no shell at all.** It prints the public price and stays plain. Fluid does not fall back to the company default plan, because quoting the wrong plan's price is worse than quoting the public one.

### Why it is a separate element

A one-time price uses `<fluid-member-price>`. Reusing that element with a plan attribute would be smaller, and it would misprice.

Storefront runtimes are published independently of Fluid's servers, so a page can be served by a new server and hydrated by an older runtime. An older runtime does not know about plans: it would drop the attribute, ask for the **one-time** price, and write that into the recurring shell — the full price displayed as the discounted rate.

An unknown element is ignored instead. An older runtime leaves the public recurring price in place, which is correct, if not yet personalised.

## Which plans are quoted

Only plans the product actively offers. That is the same set the cart prices against, so the storefront never advertises a rate a buyer cannot select.

| Plan                            | Quoted                      |
| ------------------------------- | --------------------------- |
| Active, offered on this product | Yes                         |
| Inactive                        | No — the public price stays |
| Offered on a different product  | No                          |
| Product link deactivated        | No                          |

Plan type decides where the price comes from, and you do not need to care which: a percentage plan is computed from the member's own one-time price, and a fixed-amount plan is read from the configured recurring rate. Fluid picks the mechanism.

Bundles keep their existing range, as they do for one-time prices.

## Plan pickers work too

A plan picker usually renders its own price. It keeps every plan's price in its markup — on an `<option>`, a radio input, or in component state — and swaps the visible one as the shopper chooses, with no page load. That is why switching plans is instant.

A price shell cannot survive in an element like that: the picker's script owns it, and overwrites whatever the server put there.

So Fluid does not try to put a member price into it. **It updates the picker's own data instead, and lets the picker render.** Every plan on the page is priced once, when the page loads, so switching plans afterwards stays instant and costs no request.

This needs nothing from your theme. Fluid publishes what the section's prices belong to, and your picker already carries each plan's id, so there is no markup for you to add.

### If your picker keeps its prices somewhere unusual

Fluid also publishes each plan's **public** price. When it sees your theme render a price it recognises as public, it puts the member's price there instead — whatever your picker drew it from.

Two things to know:

* Two plans at the same public price cannot be told apart by their text, so neither is swapped. The public price shows for both.
* A price your theme computes itself, rather than one Fluid rendered, is not recognised and is not swapped.

## What to do, and what not to

The [same rules as one-time prices](/themes/member-storefront/member-pricing) apply. A plan picker that renders its own price is handled for you, as above — the rest of this is about not defeating that.

### Do

* **Print the recurring price and leave the element alone.**

  ```liquid theme={null}
  <p class="price">{{ product.subscription_price }}</p>
  ```

* **Give each plan its own display.** In a `{% for plan in product.subscription_plans %}` loop, print `{{ plan.display_subscription_price }}` inside the tile it belongs to. Each one resolves for its own plan.

* **Let the shell carry the plan.** Print the price where it is shown; do not move the value somewhere else first.

* **Check the plan id** on the shell in the HTML when a tile looks wrong. A tile showing another plan's id is a template problem, not a pricing one.

### Do not

* **Do not compute a plan's price in the browser** from a percentage or an amount. A computed price is not one Fluid rendered, so it cannot be recognised or replaced — and the plan types do not all work the same way. Print what Fluid gives you.
* **Do not hide the price and rebuild it from parts.** Splitting a price into currency symbol and digits, or rebuilding it from a number, leaves nothing recognisable to replace.
* **Do not cache prices across page loads.** They belong to one viewer and one session.
* **Do not assume a plan has a member price.** Inactive plans and plans a product does not offer are not quoted; the public price stands.
* **Do not reuse the one-time element** `<fluid-member-price>` for a recurring price, or hand-write either element.

## Test a recurring price

1. **Feature disabled.** Confirm the output matches the version before any member work. No shells.

2. **Guest, feature enabled.** Confirm the page looks identical, and that the shell in the HTML carries the plan id you expect.

3. **Signed-in member.** Confirm the recurring price swaps and the one-time price swaps independently — they are separate requests with separate answers.

4. **Two plans.** Confirm each tile shows its own plan's price, not one price repeated.

5. **Switch plans.** Confirm the price follows the selection, and that switching triggers no further requests — every plan is priced when the page loads.

Loading the page with JavaScript disabled is the quickest way to see what the server actually sent, which separates a rendering problem from a theme-script one.

## Troubleshoot

| Symptom                                                | What to check                                                                                                                                                 |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The price shows in the HTML but not in the browser     | A theme script is overwriting the element and Fluid could not recognise what it wrote. Compare the page with JavaScript disabled to see what the server sent. |
| No shell in the HTML at all                            | The plan could not be determined for that display. Confirm the product offers an active plan and that the display resolves one.                               |
| The recurring price never changes for a member         | Confirm they are signed in on this storefront and that their member type receives member pricing.                                                             |
| A plan shows the public price while others personalise | That plan is probably inactive, or not offered on this product. Neither is quoted.                                                                            |
| One plan personalises and another does not             | Two plans at the same public price cannot be told apart, so neither is swapped. Check whether their prices are identical.                                     |
| A bundle shows a range                                 | Expected. Bundles keep their range.                                                                                                                           |

## Related

* [Member pricing](/themes/member-storefront/member-pricing) — one-time prices, and the rules this page builds on.
* [Member greetings](/themes/member-storefront/member-aware-sections) — `{% member_name %}` and member-only content.