Loading
Salesforce から送信されるメールは、承認済ドメインからのみとなります続きを読む

SKU Level or Product Variant Level Einstein Recommendations in B2C Commerce

公開日: Dec 15, 2025
説明

SKU (Product Variant) Level Recommendations is a customization feature and it is not a Generally Available Product Feature. What needs to be done in order to achieve SKU (Product Variant) Level Recommendations is outlined below:

  1. Einstein viewProduct activity: include product sku id
  2. Einstein recommendations request anchor: include product sku id
  3. A new Einstein viewProduct activity when a shopper selects a different size or shade
  4. A new recommendation request when a shopper selects a different size or shade
  5. Once changes are in production, open a new support ticket to have Einstein switch the site from Variation Master/Variation Group to Product Variant OR SKU.

 

Einstein recommendations work on the Variation Base (formerly known as MASTER) level by default. However, it is possible to set recommendations at the Product Variant / SKU level as per customer's business use case by enabling an appropriate configuration setting in the Einstein Configurator tool.

Einstein for B2C Commerce currently supports 3 use cases:

  • Recommendations only at the Variation Base level.
  • Recommendations only at variant product (i.e. SKU) level.
  • Recommendations at Variation Base and Variation Group levels.

 

Some Important Points to consider regarding the Product Variant/SKU level recommendations feature toggle:

  1. The switch is done at the site level, so all your recommenders will be at SKU level. Once we switch the from Master to SKU/Variant-level recommendations, this change will be enforced for the entire site/client ID. It is not possible to make this switch for specific recommenders.

  2. Changing the switch from Master to SKU is not an instant thing. Typically, when a switch is made from Master to SKU, it might take at least 1 day (~24 hours) for the changes to propagate.

  3. We think it might be possible to switch back. But we do not recommend customer(s) in playing around with these switches unless they have some critical business impact.

  4. Once we switch the recommendations from Master to SKU/Variant level recommendations, this change will be enforced for the entire site/client id. Its not possible to make this switch for a specific recommenders.

  5. Einstein Product recommendations can be tested in any lower environments within the same realm, provided the Catalog in the lower environments either has the same or subset of the catalog from Product instance. Because, the Catalog and Order feed Jobs are configured only in Production Instances. So, the catalog data in Einstein will only contain the Product and Catalog data that is sent from the Production instances.

  6. Disabling the Variation Group level settings will only affect Einstein product recommendations. The Variation Group functionality lets you choose the level of recommendations between MASTER and Variation Groups. Because of this, when a site has Variation Group enabled; MASTER products are always included in the Einstein product catalog. However, SKU level recommendation require MASTER products to not be in the catalog. But if a site has both, Variation Group and SKU(Product Variant) enabled, then MASTER products stay in the catalog and SKU level recommendations won't work as expected. These options only affect Einstein product recommendations The main thing here is that SKU level recommendations and Variation Group level recommendations are self-exclusive and cannot be enabled at the same time.
解決策

In order to recommend SKU (Product Variant) Level Recommendations instead of Master Variant or Variation Group products, the following pre-requisites need to be implemented:

  1. Einstein viewProduct activity: include product SKU ID.
    For the viewProduct event, please check the global Product Detail Page template for the <isobject object="${product}" view="detail"> statement.
    For variation product recommendations, the viewProduct activity is: ID: master's sku | SKU: SKU | Alt_ID : - | type: -

    For the viewReco activity, the matrix is the same as for viewProduct but only the ID and SKU are sent (alt_id and type are not).     When a shopper selects a different shade/size, it has to be master SKU in ID, the variant SKU in SKU should be passed and a new request should be triggered every time a different shade / size is selected.

    Help Topic: Common Recommendation Validator Errors in Commerce Cloud Einstein

  2. Einstein recommendations request anchor: include product SKU ID
    Navigate to the Recommendations Tab in the Commerce Cloud Einstein Recommendation Validator extension and verify the Anchor ID ( as product ID ) passed in the recommendations. If not, please ensure anchors are properly populated with the context-object attribute.

    For Product Display Pages (PDP)    , the Product id should display in Commerce Cloud Einstein Recommendation Validator next to ‘anchors’ on the Recommendations tab.     Example(s) for a PDP slot Tag:
    <isslot id=“pdp-you-may-like” description=“PDP You May Like” context=“global” context-object=“${pdict.Product}“/>
    OR
    <isslot id=“pdp-you-may-like” description=“PDP You May Like” context=“global” context-object=${pdict.Product.variant ? pdict.Product.variationModel.master : pdict.Product}“/>

    For Product Listing Pages (PLP) / Category Pages    , the Category ID should display in Commerce Cloud Recommendation Validator next to ‘anchors’ on the Recommendations tab. Example Category slot Tag:    <isslot id=“recomm-category-anchor” description=“Product page slot” context=“global” context-object=“${pdict.ProductSearchResult.category}“/>

    Help Topic: Validator Responses in Commerce Cloud Einstein

  3. A new Einstein viewProduct activity and viewReco activity when a shopper selects a different size or shade.
    For variation product, the viewProduct activity is: id: master’s sku | sku: SKU | Alt_ID : - | type: -

    For the viewReco activity, the matrix is the same as for viewProduct but only the ID and SKU are sent (alt_id and type are not). When a shopper selects a different shade/size, it has to be master SKU in ID, the variant SKU in SKU should be passed and a new request should be triggered every time a different shade / size is selected.

    Please refer to     Developer Considerations for Einstein Product Recommendations and Common Recommendation Validator Errors in Commerce Cloud Einstein (for viewProduct & viewReco events) to help you in your implementation.

  4. A new recommendation request when a shopper selects a different size or shade
    Ensure that a new request to CQuotient is triggered when the shopper selects a new product variant on a PDP page. For this, you can observe two different getRecommendations Einstein API calls in the Network tab of the browser e.g. https://e.cquotient.com/recs/Einstein-Site-ID/Recommender-Name?callback-CQuotient...

    If the above pre-requisites have been completed, please reach out to Commerce Cloud Support to enable the SKU (Product Variant) Level Recommendations feature toggle. Once the changes are implemented, please re-run the catalog and order feeds so that the changes are incorporated and Einstein activities are refreshed on your storefront.
ナレッジ記事番号
003876548
 
読み込み中
Salesforce Help | Article