Skip to main content

Overview

The Store page is the grid a shopper browses. The Product page is one product in detail, and it is where a shopper makes any choice the product requires before it can be bought. Both read their configuration from a Store Settings record.

Prerequisites

  • A Store Settings record exists, with Store Page URL and Product Page URL set.
  • Your products meet the storefront requirements — see Preparing Products for the Store.

Place the Pages

1

Create the Store page

In Experience Builder, create a page at the path you put in Store Page URL (for example /store) and drag FS Portal - Store onto it.
2

Create the Product page

Create a page at the path you put in Product Page URL (for example /product) and drag FS Portal - Store Product Detail onto it. The component reads which product to show from the productId URL parameter, which the Store adds for you.
3

Publish

Click Publish.
Both pages work for guests as well as members, so long as your Experience Cloud guest user profile grants access. See Enabling Guest Portal Users.

Browsing the Store

Each tile shows the product image with its badge, the name, the short description, and the price. A shopper who qualifies for a better price sees Your Price with the list price struck through; a guest sees the list price alone.
Search and category filter work together — searching narrows within the selected category rather than replacing it.

Adding to the Cart from a Tile

Clicking Add to Cart on a tile does one of three things, depending on the product: Prices are recalculated as the shopper works. Crossing a quantity tier reprices the tile on the spot, so the figure they see is the figure they will be charged, before tax.
Switching currency with items in the cart clears the cart. The shopper is warned and must confirm first, because prices and product availability both depend on currency.

The Product Page

The page shows the product’s image, its categories (unless Hide Categories is on), its name, and its Description — the longer text, where the tile used Short Description. Below that sit whatever choices the product requires. For a subscription that is the Subscription Plan, defaulting to the product’s default plan. The shopper sets a quantity and clicks Add to Cart. A quantity above the product’s Max Quantity Per Item does not fail — it spills across multiple cart lines, each capped at that limit.
Categories shown here are the portal-visible ones only, as a comma-separated list. A product in three categories where only one is portal-visible shows just that one.

Product Availability Is Consistent

A shopper who opens a product’s URL directly sees exactly what the grid would have offered. Both surfaces apply the same eligibility test, so an inactive product, a tax product, one set to Staff, one without a UUID, and one with no standard price book entry are all unreachable by direct link too — the page reports the product is unavailable rather than showing something the shopper cannot buy.

Limitations and Common Pitfalls with Store and Product Pages

  • Sorting by price uses the displayed price. A product whose price varies by subscription plan sorts on the price shown on its tile, which may not be the plan the shopper eventually picks.
  • Search does not match category names. A shopper searching for a category name finds nothing unless the words also appear in a product’s name or description — use the category pills.
  • Only one category filters at a time. There is no multi-select.
  • Max Visible Category Pills caps at 8. A higher number silently falls back to 8.
  • Results Per Page has no upper guard. A large number puts the whole catalogue on one page and slows the first render.
  • The Product page needs its productId parameter. Linked without it, there is no product to show — always link through the Store, or use Product Page URL so the parameter is appended for you.
  • Prices exclude tax everywhere in the Store. Tax is calculated at checkout, so the final total can be higher than the cart’s.