Page Context for Group Products
Hi All,
We use Salesforce Commerce Cloud as our eCommerce platform, which has up to three levels of ID for a product:
- SKU, which is unique in the catalogue and is specific to both colour and size.
- Variation Group, an ID that is shared across all sizes.
- Variation Master, which is shared across all colours and sizes.
It is possible that a user lands on a PDP that is based on variation master (size/colour not selected), or variation group (size not selected). At this point, the page is not specific to a SKU, so the only option is to use variation master or variation group.
How can we structure the product feed so that relevant (to the product) recommendations can be served on these group PDPs, without losing the ability to surface the most relevant variations to our users?
Thanks
Theo
-
Hi Theo,
Assuming that the Variation Master ID is not used as a SKU for any product, I suggest creating a "Master Product" in your product feed. The master product would have this Variation Master ID as its SKU. It should have the same categories, keywords, and other attributes as the rest of the products in this "master group", as well as all the mandatory product feed columns.
As an example, let's say that you have a shirt in two colors and two sizes:
SKU, name, categories, size, color, masterVariation, ...
01SB, T shirt, Shirts|Tshirts, S, Black, 01, ...
01LB, shirt, Shirts|Tshirts, L, Black, 01, ...
01SW, shirt, Shirts|Tshirts, S, White, 01, ...
01LW, shirt, Shirts|Tshirts, L, White, 01, ...What I am suggesting is that you add an additional row for the master product:
SKU, name, categories, size, color, masterVariation, isMaster,...
01SB, Tshirt, Shirts|Tshirts, S, Black, 01, false,...
01LB, Tshirt, Shirts|Tshirts, L, Black, 01, false,...
01SW, Tshirt, Shirts|Tshirts, S, White, 01, false,...
01LW, Tshirt, Shirts|Tshirts, L, White, 01, false,...
01, Tshirt, Shirts|Tshirts, Null, Null, 01, true,...This way, you can use the Variation Master ID as the page context data on the product page. Most strategies would work just fine on these pages (Similarity, Viewed Together, Affinity, etc...). The only strategies that may be affected are those that are dependent on Purchases, such as Purchased Together. The reason is that Variation Master ID is not supposed to be a purchasable product, as it's not a real product, so normally it wouldn't have purchase data.
You may want to add an additional column to the feed that marks those master products. This should help you exclude them, only include them, or target them specifically whenever needed (in the example above, I added the "isMaster" column.
To ensure that the implementation and data collection continues to work as expected, make sure to update the page context data with the product's SKU whenever the user selects a color/size.
Regards,
Kian Issa,
Dynamic Yield Support.
Please sign in to leave a comment.
Comments
2 comments