Product Recommendations setup

Product Recommendations displays relevant products to customers based on their browsing history and preferences, helping increase cross-selling. You must enable and configure this feature before adding it to your pages. Once configured, it displays as specific recommendation units that you can place on any page.

Configuration

Add this table to your document to configure the block:

product-recommendations
recId	2ed7ea09-d9bd-4691-91c3-2c0a6d4fd869 (example)
currentsku	crz-eco-tr-std-2017 (example)
currentprice	49.99 (example)

• recId: Recommendation unit ID from the Admin. Required for all pages.

• currentsku: Seed product SKU. Required on non-PDP pages for anchor-based recommendation unit types (for example, more-like-this, visual similarity, viewed-viewed, viewed-bought, bought-bought). On PDP pages, the boilerplate reads the seed SKU automatically from the Adobe Client Data Layer (ACDL).

• currentprice: Anchor product price (numeric). Required on non-PDP pages when the unit uses dynamic or relative price filter operators (Adobe Commerce Optimizer and Adobe Commerce as a Cloud Service only). Not required for static price filters—a fixed price range in the filter rule does not remove the need for a seed SKU on anchor-based types. On PDP pages, the boilerplate reads anchor price automatically from ACDL when needed.

When product context is required

Whether a seed SKU or anchor price is required depends on the recommendation unit type and the price filter operator, not on each other:

Unit type	Seed SKU	Anchor price
Anchor-based (more-like-this, visual similarity, viewed-viewed, viewed-bought, bought-bought)	Required	Only for dynamic or relative price filter operators
Context-free (most-viewed, most-purchased, and similar popularity or behavioral types)	Not required	Not applicable

A static price filter defines a fixed price range in the filter rule. It does not mean the unit can run without an anchor product. For example, a more-like-this unit with a static price filter returns no products when the seed SKU is missing, but returns results with the seed SKU alone—currentprice is not required.

Storefront block configuration

How you configure the block depends on the page type and unit type:

• PDP pages: Set only recId. The boilerplate supplies the seed SKU from ACDL product context. On Adobe Commerce Optimizer and Adobe Commerce as a Cloud Service it also sends the ACDL anchor price automatically; the backend applies it only when the unit’s filter uses a dynamic or relative operator.
• Non-PDP pages (PLP, cart, home, and so on): There is no product context on these pages. For anchor-based unit types, you must set currentsku in block config. Add currentprice only when the unit uses dynamic or relative price filter operators (Adobe Commerce Optimizer and Adobe Commerce as a Cloud Service only).
• Context-free unit types on any page: Set only recId. These popularity and behavioral units do not use a seed product.

Important

• Do not assume recId alone is enough on non-PDP pages. That applies to context-free unit types only. Anchor-based units on non-PDP pages require currentsku or they return no products.
• Do not omit currentprice on non-PDP pages just because the unit uses a static price filter. Static filters still need a seed SKU for anchor-based types; they do not need anchor price.
• Add currentprice on non-PDP pages only when the unit’s price filter uses dynamic or relative operators.

How to enable and configure Product Recommendations

The Product Recommendations block can be configured on each page through Document Authoring. Follow the step-by-step guide below to enable and configure Product Recommendations:

Create a recommendation unit

You must first create recommendation units in the Adobe Commerce Admin (PaaS) or Adobe Commerce Optimizer Admin (SaaS).

Adobe Commerce Optimizer Admin (SaaS)

The following steps apply to merchants using Adobe Commerce Optimizer or Adobe Commerce as a Cloud Service.

1. Log in to the Adobe Commerce Optimizer Admin.

2. On the Admin sidebar, go to Recommendations.

3. Follow the steps in the user guide to create a recommendation unit.

Note

For Adobe Commerce Admin (PaaS), follow the steps in the user guide to create a recommendation unit.

Get the recommendations unit ID

You can specify which recommendation unit to display on each page by using the recommendation unit ID.

1. Navigate to the Product Recommendations page in the Adobe Commerce Admin or Adobe Commerce Optimizer Admin.

2. Click the eye icon next to the recommendation unit that you’d like to display on your store.

3. Copy the Recommendation ID from the modal.

You will use this ID in the next step to configure the recommendations block.

Add and configure the recommendations block

You can configure each page to display a specific recommendation unit by setting its recommendation ID.

1. Open the page where you want to display the recommendation unit.

2. Create a new table in your document with the block name product-recommendations.

   For product detail pages, set the recId to match the recommendation unit ID from the previous step. For example:

   product-recommendations
   recId	2ed7ea09-d9bd-4691-91c3-2c0a6d4fd869

   Note

   PDP pages — set only recId for all unit types. The boilerplate reads seed SKU (and anchor price when needed) from ACDL.

   Non-PDP pages — anchor-based unit types — set recId and currentsku. For example, a more-like-this unit on a category page:

   product-recommendations
   recId	2ed7ea09-d9bd-4691-91c3-2c0a6d4fd869
   currentsku	crz-eco-tr-std-2017

   This applies even when the unit uses a static price filter. The seed SKU is required; anchor price is not.

   Non-PDP pages — dynamic or relative price filters — also set currentprice on Adobe Commerce Optimizer or Adobe Commerce as a Cloud Service:

   product-recommendations
   recId	2ed7ea09-d9bd-4691-91c3-2c0a6d4fd869
   currentsku	crz-eco-tr-std-2017
   currentprice	49.99

   Non-PDP pages — context-free unit types (most-viewed, most-purchased, and similar) — set only recId, same as on PDP.

Section metadata

Control the section styling, spacing, and layout that wraps your commerce block. All properties are optional:

section-metadata
Style	light (optional)
Padding	medium (optional)
Margin	small (optional)
Column Width	30% (optional)
Gap	small (optional)

Learn more

See the Section Metadata guide for all available values and the Page Metadata guide for SEO and caching options.