Name: Identifying the Basic Product Variants in SAP Commerce Cloud
Uploaded: 2024-6-3
Duration: 193 s
Description: In this video, you will learn how basic product variants are supported in SAP Commerce Cloud.

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div>In this video, you will learn how basic product variants are supported in SAP Commerce Cloud.</div></div></div></div></div>

Identifying the Basic Product Variants in SAP Commerce Cloud

In this video, I’ll tell you how basic product variants are supported out-of-the-box in SAP Commerce Cloud.  In general, product variants are products of identical design and functionality, but with different size, color, etc.  For example, a base product “T-Shirt” has two color variants: black and white.  But first of all, in SAP Commerce, you need to distinguish between a base product and a variant product.  Let’s open the product cockpit in the backoffice, and do a search for “M25687”.  You can see that several results are returned.  Specifically, a base product called “T-Shirt Men Playboard Skull SS” is identified by the single gray cuboid; while the variants of the base product are identified by a multi-cuboid icon in the status column.  So, what exactly does this mean?  In SAP Commerce, product variants simplify the process of managing your products by allowing you to create variant products related to a base product.  Variants are intended to cover a small number of variations from a base product, e.g. different colors, sizes, or fits.  To create product variants, you need to first create a base product and set a variant type on that base product.  Then you will be able to create variant products based off the base product.  Base products that have variants only exist to facilitate the creation of those variants, because you wouldn’t want to sell jeans without a size.  This means, if you are using variant products the base product cannot be purchased.  The VariantProduct type is used to select style, size, color, etc., but in a hierarchical way. And actual purchasable Stock Keeping Units, or SKUs, correspond to the selected Variant Product on the lowest level.  For example, you can see that the base product here is the Men’s short sleeve shirt.  It is viewable, but not purchasable, on the storefront.  I can select the intermediate style variant: black.  But it is still not purchasable.  Only finally, when I select the size, e.g. small,  can I then purchase this item, namely a small black shirt.  From a technical perspective, the implementation of basic variant products has the following structure.  A regular product has its variants if the variants property is not null.  And all those variants are of the type VariantProduct, in this example, StyleVariantProduct.  The two styles, Red and Blue are on the next level. And each of those has a collection of next-level variants,  this time of the type SizeVariantProduct.  And finally, the blue style variant product has three next-lavel variants that correspond to 3 sizes: small, medium and large.  Since this is a two-tier variant model, the second variant type has a null value for its variantType property,  and an empty collection for its variants property.