Skip to main content
Not yet available. This describes work in review, and details can change before it ships. Member pricing is the shipped behavior for one-time prices.
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 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:
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:
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 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 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.
  • 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