Skip to main content
Coming soon: member storefront is in a limited pilot and is not yet generally available. This page describes the pilot release for companies that have it enabled, and details can change before general availability. Contact Fluid support to ask about enabling it for your company.
Member storefront brings signed-in members into the theme you already have. A member sees their own price and their own name in the same sections every visitor sees, and opens member-only pages that render inside the same theme. There is no second site to design and no separate portal to assign. It has two surfaces, and they work differently on purpose:
Member storefront features require enablement for your company. Until then the member helpers render their guest values, and the account subdomain keeps its current behavior.

Member-aware sections

Use member_price, member_name, and the member block to add member values to cached sections.

Member sites

Group member pages into sites, decide who sees each site, and give each its own layout and navigation.

Member page templates

Build the dashboard, sign-in, custom page, and layout templates that frame a member’s pages.

​
Why the two surfaces differ

Storefront pages are cached and served to everyone. If the server rendered one member’s price into a product grid, the cache would hand that price to the next visitor. Member-aware sections keep the server render identical for every viewer and move the personal part to the browser. See Member-aware sections. Member pages are private. They render on every request for the signed-in member, are never cached, and are never indexed. A guest who opens one is redirected to sign in. Because the render knows the member, member page templates read member directly and need no shells. See Member page templates.

​
What a member site is

A member site is an access rule and the set of pages it governs. A theme holds an ordered list of sites. Each site names the countries and member types it serves, the layout that frames its pages, and the menu that navigates them. A member resolves to exactly one site, is served that site’s pages, and receives a not-found response for every other site’s pages. See Member sites.

​
What ships with the theme

The root themes ship the product card with member_price and nothing else. Member page templates, the member layout, and member sites are yours to author. A company whose theme has no dashboard template receives a not-found response at the account subdomain root until one exists. Member sites travel with the theme. Duplicating a theme copies its sites and pages, and exporting a theme writes them to members_sites.json at the theme root so an import into another company can recreate them.

​
What member storefront is not

  • It does not replace or change the portal. Portal Definitions and Widget Packages are a separate product with separate contracts.
  • It adds no pricing rules. Every member price the SDK shows is a value the platform already resolves for that member.
  • It never puts member data into a cached page. The storefront render stays viewer-independent.

​
Next steps

  1. Add member_price to your product card and test the guest render. Start with Member-aware sections.
  2. Create a member layout and a dashboard template. Follow Member page templates.
  3. Add a member site in the theme editor, choose its rule and layout, and arrange its menu. Follow Member sites.