This guide is for administrators and solution evaluators who want to place a product list on an Experience Cloud page. It explains what the Product Lists - Record View component shows, when to use each configuration option, and how to set it up for either a specific Web Product List record or a buyer's favorites list.
What This Component Does
Product Lists - Record View displays products from a Web Product List on an Experience Cloud page.
It supports two common setup patterns:
- Record-driven: the component shows the Web Product List tied to the current page record.
- Buyer-specific by type: when there is no page record, the component can find a list for the signed-in buyer based on the selected List Type, such as Favorite.
If both a Record Id and a List Type are available, the component uses the Record Id.
When This Component Is A Good Fit
Use this component when you want to:
- Show one specific Web Product List on its own record page.
- Reuse one page for many buyers while showing each buyer a matching list.
- Create a My Favorites style page without building a separate page for each buyer.
This component is less suitable when shoppers need to browse multiple lists or choose between several lists on the page.
Experience Builder Properties
These are the properties you can set in Experience Builder.
| Property | Type | Default | What it does |
|---|---|---|---|
| Record Id | String | {! recordId } |
Uses the current page record. On a Web Product List record page, this is the usual way to tell the component which list to display. |
| List Type | String | Blank | Optional fallback used only when Record Id is not available. The available values come from the active values on the Type field of the Web Product List object. |
| Hide Footer | Boolean | false |
Hides the footer link back to the product list overview page. |
Important behavior:
- Leave Record Id as
{! recordId }on record pages. - List Type is ignored when Record Id is present.
- If Favorite does not appear in the List Type dropdown, confirm that Favorite is still an active picklist value on the Type field of Web Product List.
Set Up On A Web Product List Record Page
Use this setup when the page represents one specific Web Product List and should always show that list.
- Open your site in Experience Builder.
- Open the page that is backed by a Web Product List record.
- Add Product Lists - Record View to the page.
- Keep Record Id set to
{! recordId }. - Leave List Type blank.
- Set Hide Footer if you do not want to show the back link.
- Publish the site.
What to expect:
- The component title uses the Web Product List name.
- The component shows products related to that list.
- The footer link remains visible unless Hide Footer is enabled.
Set Up A Buyer's Favorites Page
Use this setup when the page is not tied to one Web Product List record and you want the page to resolve the signed-in buyer's favorites automatically.
- Open the target page in Experience Builder.
- Add Product Lists - Record View to the page.
- Leave Record Id empty, or use the component on a page that does not provide record context.
- Set List Type to Favorite.
- Choose whether to keep or hide the footer link.
- Publish the site.
Prerequisites:
- The signed-in buyer must be related to a Contact used in the storefront context.
- That Contact must have at least one Web Product List record with Type = Favorite.
How this mode behaves:
- The component looks up a matching list only when Record Id is not available.
- It finds the first matching Web Product List for the buyer's Contact and the selected type.
- It then shows that list name and its products.
- If no matching list is found, the component stays empty.
Recommendation:
- Keep one clear Favorite list per buyer Contact when possible. If multiple matching Favorite lists exist, only one is shown.
Choosing Between Record Id And List Type
Use Record Id when the page itself is the detail page for a specific Web Product List.
Use List Type when the page should resolve a buyer-specific list dynamically, such as Favorite.
Use Hide Footer when the page already includes enough navigation and the additional back link is unnecessary.
What Prospective Customers Should Know
For most evaluations, the key question is whether you need a shared page that automatically shows one buyer-specific list, or a page that always shows one fixed list.
- If you need a fixed list tied to a record page, use Record Id.
- If you need a shared page that shows each buyer their own matching list, use List Type.
This makes the component useful for experiences such as favorites, quick reorder, and buyer-specific saved lists.
Troubleshooting
The component is blank on a record page
Check that:
- The page is receiving a Web Product List record context.
- Record Id is still set to
{! recordId }. - The current list has related products to display.
The component is blank on a favorites page
Check that:
- List Type is set to Favorite.
- The signed-in buyer is related to the expected Contact.
- That Contact has at least one Web Product List with Type = Favorite.
- Favorite is still active on the Type field of Web Product List.
The component shows the record page list instead of the configured type
This is expected. When Record Id is available, it takes priority over List Type.
Summary
Product Lists - Record View lets you place a product list on an Experience Cloud page in two ways: by using the current Web Product List record, or by resolving a buyer-specific list such as Favorite. For record pages, keep Record Id set to {! recordId }. For a favorites page, leave Record Id empty and set List Type to Favorite.