Creating SKUs

A SKU is a unique alphanumeric code that helps in identifying a specific product existing within a Taxonomy Node in a Catalog. Each SKU is defined using multiple attributes. Let us understand how to create SKUs in the following sub-sections.

For example, if we consider a node Watches which is the parent node and it consists of a child node Analog and Digital which is basically a category of Watches. The Analog and Digital node will contain SKUs for various types of analog watches as there will be multiple watches with different dial size, color and so on. All these products will be uniquely identified through SKU IDs.

Once you open the catalog, the SKU view is displayed in the middle panel of the screen, by default as shown below based on the node selected.

Figure 113: SKU view

In most cases, SKUs will be imported from the client’s database to PCC and then we will design the catalog around it. However, you can also add new SKUs, if required. Following are the sub-sections:

• Adding SKUs to a Node

• Importing SKUs

Adding SKUs to a Node

You can create new SKUs to be added for a node if the imported files do not have a SKU for any product.

To add a SKU to a node:

1. Select the node for which the SKU is to be added. Click the SKU tab and then click the Add SKU icon. For example, consider a SKU to be created for the Watches node. The complete taxonomy path is Accessories>Watches which is visible on the top of the dialog box as well.

The information to be added for a SKU is divided into 3 panels.

SKU Information – This is the first panel.

2. Enter the SKU Item ID. It should be a unique ID specific to each product. Let’s say Wat02158. If the ID entered already exists, an error is displayed while adding the SKU as shown below.

3. Enter the SKU Title. The title should indicate the product in some way. For example, the following is a screenshot of how the title will be displayed on a website when you hover the mouse on the product.

Figure 114: SKU title sample

The following is a sample of the details added.

SKU Titles can also be generated based on the formula associated with the SKU. Refer section Auto Generating SKU Title for more details on how to create formulas and auto generate SKU titles.

4. Click Add SKU to add multiple SKUs as shown below.

5. Click the newly added SKU to add details as shown below.

6. Click the Remove SKU icon next to the SKU to remove any of the SKU added.

7. Attributes – This is the second panel. All the attributes added for the SKU will be listed here.

   There are 3 options available to add attributes. You can add:

• SKU Attributes from the Attribute master list

• Schema Attributes defined for the selected node

• Attributes from the Attribute Groups defined, if applicable

8. Click Add Attributes and the options available for adding SKU attributes are displayed as shown below.

Case 1: You can add schema attributes defined for the node which are relevant for the SKU being created.

Click Add Schema Attributes and the following is displayed.

Click Select Existing Schema Attributes and a list of existing schema attributes for the selected node is displayed.

Figure 115: Add existing schema attributes

A list of all added schema attributes for the node is displayed. This helps to easily add attributes that are relevant for the SKU defined by the curation action of “schema definition “when designing the structure of the catalog as mentioned in section 0 Adding Schema using Astro Intelligent Data Model Configurator

The PCC catalog administrator often struggles to define schema attributes and constraints effectively, typically lacking a data-driven decision-making process.

Astro Intelligent Data Model Configurator provides intelligent help and recommendation from the system on how to set up the schema for each node in the catalog. This option will only be available when Astro is enabled for the catalog.

The Astro Intelligent Data Model Configurator performs data profiling of existing SKU data in the catalog/taxonomy to come up with recommendations based on pre-defined thresholds. You will be navigated to a screen with the recommendations along with the underlying data analysis that led to the recommendations.

To add schema attributes using Astro Intelligent Data Model Configurator:

1. Follow steps 1 to 3 as mentioned in section Creating a Taxonomy Structure using Astro. The Astro icon is now enabled in the Schema view as shown below.

2. Select the node in the taxonomy panel for which you need to add schema attributes. For example, we have a node Casual Pants for which we need to add schema attributes as shown below.

If there are Global Attributes in the attribute master, it will appear by default for every schema of the node.

3. Click on Astro Intelligent Data Model Configurator.

You’ll land on Astro Intelligent Data Model Configurator for Node > “node name”.

4. There are two tabs displayed i.e. Recommended Schema Attributes and the other for Non-Recommended Attributes with counts. The default toggle will be Recommended Schema Attributes.

A list of schema attributes suitable for the node selected is displayed. In this case, since the node selected was Casual Pants, attributes such as Color, Prize, and so on are displayed.

5. You can see the Thresholds that are set for the selected taxonomy with each parameter count as shown in the below image.

6. You can click   Modify thresholds, to edit or modify the thresholds for the schema.

The following pop-up with certain parameters gets displayed.

• Minimum Presence for Schema Inclusion: Here you can enter the minimum percentage required attributes for all SKUs within a taxonomy to be considered a schema attribute.

• Minimum Presence for Is Required: Here you can enter the minimum percentage of an attribute across all SKUs in a taxonomy required for a 'is-Required' schema constraint recommendation.

• Maximum Distinct Value Count for LoV Consideration: Here you can set maximum distinct values for a taxonomy-attribute combination needed for an Enforce-LOVs schema constraint recommendation.

• Maximum Distinct Value Count for UoM Consideration: Here you need to enter the maximum possible distinct units of measure found for a taxonomy-attribute combination which allows the schema design helper to suggest Enforce-UoM schema constraint recommendation.

Note: None of the threshold values can be left empty as it will throw error and you’ll not be able to proceed as the Re-run recommendations button will be greyed out.

7. Once you have added the thresholds, click Re-run recommendations and to retain the existing values click Cancel.

   You’ll get a refined list of Recommended & Non-Recommended schema attributes based on the threshold value.

   Following are the components on the Recommended Schema attributes:

    

   1. Attribute-> displays the attribute name along with the datatype such as ST (string) or IN (Integer) as shown in the below screenshot.

       

   2. Include Schema? -> This option is used to add bulk attributes in schema by checking/unchecking the checkbox near Include in Schema field label as shown in the screenshot below, this flag is a pre-requisite and needs to be checked to add the constraints. This flag needs to be checked if you need to add constraints.

       

      Here if they include schema is checked for parent and child node, its constraints will automatically reflect the parent node selection. You cannot have a different selection if the parent and child are selected or can make an individual selection for a child node if the parent is not selected.

      Note: If immediate parent is checked, you will not be able to uncheck the child node nor edit, only if you uncheck the parent, or if the parent is not recommended but recommended in child then the node level control is editable.

   3. Under Recommended for Constraints you can view various constraints such as Is required, Enforce LoVs, Enforce UoMs, Enforce Datatype, Enforce Min-Max value, Enforce Min-Max character Length. Each constraint will automatically be enabled depending on the threshold values that were set. For more information on why it is recommended can be seen in each cell when you hover over on the   icon as demonstrated in the below screenshot.

      

      If the constraint is not recommended, then it will say it is not recommended as demonstrated in the below screenshot.

       

   4. For constraints such as Enforce LoVs or UoMs, they are aggregated from the SKU attribute value for that node. You can select all or handpick and then the count will be seen.

   5. For Enforce Min/Max value or character length, the predefined value is based on the SKU data which will be initially displayed. You can click on the  (eye) icon to edit the values.

       

   6. You can see the node structure and hierarchy upon clicking on the  (eye) icon near the taxonomy node name as shown below.

       

   7. The Non-Recommended Attributes tab is a read-only list of attribute names and the reasons they weren't recommended as shown in the below screenshot. No actions can be taken on this page.

8. Once all the constraints are set & reviewed then click Save.

   You’ll see a pop up as Updating Schema Attributes for the node “name” and land on the Schema tab as shown in the screenshot below.

Adding Schema Attributes to a Node. The schema attributes deemed applicable for all products in this node are displayed, hence this provides a quick and easy way to select all the schema attributes which should be authored for the SKU. Let us select Dial Width and Brand.

You can select all or any attribute as required.

9. Click Add to SKU and the SKU attributes are added as shown below.

Case 2: You can add any attribute from the attribute master list that is relevant for the SKU and which is not part of the schemas defined for the node.

1. Click Add Attributes   and then click Add SKU Attributes and the following is displayed.

2. Type the name of the attribute and a list of matching attributes based on the keyword entered is displayed. Select the attribute. For example, let us add an attribute Strap Width.

3. The datatype for the attribute is populated next to the attribute name here. Similarly, you can add more attributes, if needed by clicking Add SKU Attributes.

Case 3: You can add attributes from the attribute groups if relevant for the SKU being created.

1. Click Add Attributes    and then click Add Attributes from Attribute Groups and the following is displayed.

2. Click Select Attributes From Attribute Groups and a list of attribute groups created is displayed.

Figure 116: Add attributes from attribute groups

When you select the attribute group, all attributes present in that group will be added as SKU attributes. Here, we have Products and Dial Parameters which are applicable for Watches. Hence, we will select both.  You can select multiple attribute groups applicable for the product.

3. Click Add to SKU and all attributes present in the selected group will be added.

There is a toggle option in the second panel to view all attributes or attributes in an attribute group. By default, All is selected and all attributes added for a SKU are visible.

Let us assume we have added attributes from an attribute group and we need to filter attributes, that is, view attributes from the attribute group only. It is possible that attributes from multiple attribute groups have been added. If you want to view / change values of attributes from a particular attribute group, this option will enable you to filter attributes by selecting the relevant attribute group.

Move the toggle to Attribute Groups and click the Show Group Attributes icon to view a list of attribute groups added for this SKU.

In this case, there are 2 attribute groups. Since there are multiple groups added, all will be displayed here and you can select the required group.

4. Click Product and then click Filter. The attributes will be filtered and only those attributes present in the attribute group selected will be displayed as shown below.

All these attributes belong to the attribute group Product.

It is possible that a SKU has multiple attributes and if you want to navigate to any attribute directly instead of scrolling through the list, there is an option which enables you to select the attribute to be viewed.

5. Click the Go to an Attribute icon on the upper-left corner of the second panel and a list of attributes added is displayed.

6. Click the attribute name and you will be navigated to that attribute as the page will be scrolled automatically.

7. Click the Remove Attribute icon next to the attribute added to remove it , if not required.

   Once the attributes have been added, you need to add values to these attributes.

   SKU Attribute Values – This is the third panel. All the values for the SKU attributes will be added here. This panel is aligned with the second panel as each attribute has an option to add values respectively.

Double-click to add the attribute values next to the attribute added.

In case of schema attributes added, you can populate values from schema using the Show Suggestions icon which displays the LoVs and UoMs, if defined while creating the schemas.

Let us add value for a schema attribute Brand. Double-click to add the value and the following is displayed.

8. Click the Show Suggestions icon to view the list of values.

In this case, select Casio and then click Populate Selected. You can manually add values, if needed.

9. Click Add and the value is added for attribute Brand as shown below.

Similarly, the Show Suggestions icon will also appear for UoMs if they have been defined for the schema attributes. In this case, UoM is not applicable and hence it is not added. However, the following is a sample of how a UoM list will populate.

You can add multiple values and UoMs as applicable for an attribute.

In case of attributes being added from the master list as well as attribute groups, double-click the cell to add the values and UoMs as needed.

10. Click the Edit this value(s) icon next to the value added or double-click on the value to make any changes in the values.

An attribute can have multiple values as well. If a SKU attribute has multiple values, only one SKU value will be shown and the other values will be shown as ‘+ Number' in the next line which means if there are 2 values for an attribute then the first value will be shown and below it , it will show +1. Following is a sample for attribute Strap Width.

The SKUs added in a node will have similar properties. In such a case, while adding multiple SKUs, you can also copy attribute values of a SKU to all SKUs added using the Apply attribute option. For example, we have created a SKU Wat02158 and we have added another SKU Wat05698. We can copy the attribute values of SKU Wat02158 to SKU Wat05698.

Select SKU Wat02158 and click the Apply attribute(s) and value(s) to all the SKUs icon as shown below.

This option is useful in cases where 2 or more SKUs have similar attributes and values. Thus, instead of manually selecting the attributes, you can use this option to copy all the attributes and values from 1 SKU to another SKU in a single click and then make the minor changes in values or attributes as applicable.

The following message is displayed.

This option will copy the SKU values to all the SKUs added. You cannot select a specific SKU here.

11. Click Apply To All and the attributes and values are copied to other SKUs. In this case, to SKU Wat05698.

12. Click Add SKU once all the SKU attributes and values have been added. However, if there is any validation error based on the Schema Constraints set for schema attributes, an error is displayed as follows.

Here, it shows the count of validation errors as 1. The SKU is added with validation failures as shown in the figure below.

Hover the mouse on the icon and it displays ‘SKU Has Validation Failures’.

13. Click and the Schema Constraints Validation For SKU Wat02158 is displayed as shown below.

Here, the Validation Failure Message is displayed stating that ‘Is Required’ for attribute Strap Material, that is, this attribute should be added and currently we have not added this attribute for the SKU. The system will allow us to not add any required attribute. However, based on the schema constraints set for Strap Material, it will display a validation error as it is a required attribute and it should have been added.

You need to edit the SKU and add this attribute.

Make the changes and then click Save. The SKU is updated successfully and the validation error is resolved.  The SKU is now updated and indicated by as shown below.

All the attributes added along with the values are listed in separate columns for the SKU added.

The SKUs added are displayed in the SKU view as shown below.

Figure 117: SKUs added in the SKU view

You can hover the mouse on the Attribute Details icon displayed next to each attribute value to view basic details about the attribute, the name, datatype of the attribute, the Metadata associated with that attribute and so on as shown below.

SKU validation can happen any time, during authoring or while changing a constraint, data type and so on. Validation messages indicate whether a SKU data conforms to the standards/constraints defined while adding schemas. All the added SKUs for the respective nodes are visible in the SKU view.

The following table lists the various icons used in the SKU panel to indicate the type of information added for a SKU.

However, if the review mode is turned on for user action Review user actions of adding or deleting a SKU while adding/editing a domain, you cannot add the SKUs directly as it will be assigned to a reviewer. In this case, while adding a SKU, a message is displayed as follows.

Figure 118: Action under review message

A green icon is now displayed next to the SKU which indicates that approval to add the SKU is pending as shown below.

Depending on the action taken by the reviewer, the value will be approved/rejected /aborted as explained in section 19.4 Reviewing the User Actions Assigned.

Auto Generating SKU Title

A SKU ID is a unique ID specific to each product which is usually a combination of alphabets, numbers and special characters. However, a SKU title conveys some information about the product. For example a title for a product such as a watch could be ‘Black Analog Watch’. This gives clarity just by reading the title that the watch is black in color and the display is not digital, that is, it displays the time through hands on a dial. A website selling watches could have multiple categories of watches and defining a title manually for each and every type of watch could be tedious as well as there could be inconsistencies in the titles.

PCC enables you to define and configure formulas which can be utilized to define data population rules for generating a SKU Title. In this case, the title is ‘Black Analog Watch’. Black could be an attribute value for Color whereas Analog Watch could be the value for an attribute such as ‘Description’. Formulas support string operations like concatenation, sub-strings, etc., along with arithmetic expressions with standard operators and basic functions using which you can create the required formulas. You can then select the SKUs and apply the required formula. The SKU Title will be automatically generated based on the formula associated with the SKU.

A detailed description on how to create formulas and the various actions that can be performed on them is provided in Formula Master.

SKU Titles can be automatically generated by selecting the nodes containing SKUs to which the formula should be applied. Refer section 6.3.1.11 Auto generating a SKU Title for details on how to auto-generate SKU titles.

Importing SKUs

The SKU Import functionality in PCC is purely additive in nature, that is, the imported data file may contain only partial information about a SKU, and that partial information will be incrementally added to the SKU if it already exists in the catalog.

A detailed description of the various functionalities available in Import are detailed in chapter Import Catalog.