Name: An Introduction to Configurable Products - SAP Commerce Cloud
Uploaded: 2020-6-12
Duration: 282 s

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div>In this video, you will learn how customers can configure complex products on the storefront page thanks to out-of-the-box features of SAP Commerce Cloud.<br><ul><li>You will hear about configurator settings, 2 new data types, the extensibility of the feature, and more. </li><li>You will also hear about how configuration properties can be inherited in your product catalogs. </li><li>You will be able to see a specific example step-by-step of how configuration happens in Backoffice as well as on the storefront.</li></ul></div></div></div>

An Introduction to Configurable Products - SAP Commerce Cloud

In this video, I’ll tell you how configurable products are supported out-of-the-box in SAP commerce cloud. In general, configurable products are products that require additional information from the customer to complete the purchase flow For example, if I want to complete the purchase of a car,  I need to select which engine should be built into the car,  which color the car should have,  and many other properties of the car. Out-of-the-box in SAP commerce,  these configurable properties belonging to a certain product are called configurator settings.  They are linked to products and become available in shopping carts or placed orders. To support these, 2 new data types are implemented The configurator settings represent the actual configurable properties.  They are catalog aware. That means that they can be associated with the staged version for editing.  And then synchronized to the online version when ready.   In addition, they are highly extensible, to allow for the specific configuration requirements. The configurator settings are linked to a new category sub-type called a Configuration Category.  Instances of this configuration category can then group products or product variants together  and pass the configurator settings to those products. In an accelerator,  the sample websites already provide controls to start configuration from the product listing page  or in the product details page, which will be demoed later. This diagram here shows the out-of-the-box configuration. Let’s take a configuration category called Engraving It contains 3 configurator settings: the engraving text, the font name and the font size The engraving configuration category is associated with a camera product as its super category.  The camera product will then inherit all 3 configurator settings. Now let’s see what happens if the camera product has a variant product called green camera. In this case, the variant, as well, inherits all the configurator settings. However, there is one more point to note here.  If there is another variant product called red camera… And the red camera is assigned to another configuration category called Engraving Large, with a different configurator setting value,  then configurations will be merged with variant-specific configurations This means, the non-conflicted configurator settings are linked normally, and the conflicting property at the more specific level, in this case the variant product, will override the more general one, so that the font size now has the value of 24. Out-of-the-box, configurable products can be managed in backoffice.  We have provided an implementation called a TextFiledConfigurator You can observe this in the category node in the backoffice  Just search for the engraving category.  In that category, you can see 3 configurator settings of the type text filed configurator are assigned with default values. This category is a supercategory of the DSC-H20 camera That means that this camera, as well as all of its variants,  will become configurable products in the storefront Let’s have a look at this directly.  I’ll open the categories node in backoffice, and find the configuration category “Engraving”. In the general tab, you can see the 3 configurator settings are assigned. Also, in the “category structure” tab,  you can see the product “DSC-H20” is listed under the included products of the engraving category. Now, let’s go to the electronics store, and search for the DSC-H20 product. You can see that all DSC-H20 variants contain the “configure” button in the search results page. And If I click on one of the variants, for example, the red one I can also configure this product on the product details page. These are the 3 configurator settings, defined in the configuration category Engraving,  with the default values. I can go ahead and add this product to the shopping cart. Please note that although the product is now in the cart, I can’t yet proceed with the check-out.  That’s because the out-of-the-box implementation has one simple restriction:  None of the configurable properties must not be null, or empty.  I therefore need to complete the “engraved text” field in order to continue. The configurable product model is designed to be extensible.  The example we have just looked at serves as a starting point for defining more complicated use cases. That’s it for this video.  Thank you for watching.