Attributes

As a Category Manager or Product Manager, we can use Management Center to manage individual attributes within catalog entries or to manage attributes within the attribute dictionary. The attribute dictionary contains two types of attributes: attributes with predefined values and attributes with assigned values. We can reuse the attributes that are contained in the attribute dictionary across multiple catalog entries. We can assign attributes to catalog entries for use as defining attributes or descriptive attributes.

Attributes are used to describe or define a catalog entry. By default, each catalog entry has property fields available for specifying general information about the catalog entry. Business users, however, can add attributes to each catalog entry when the default general information properties are not sufficient for describing or defining the catalog entry.


Attribute value types

There are two different types of attributes – predefined value attributes and assigned value attributes. Predefined value attributes enforce a set of common attribute values that can be reused by multiple products consistently. For example, we can assign small, medium, and large as predefined values for a size attribute. We can also reuse the size attribute across multiple products instead of having to define sizes each time. Assigned values are specified individually for each product. An example is a length attribute where all your products have a unique length. We can use an assigned value attribute to specify unique lengths for each product.

Attribute dictionary supports inheritance where we can add and remove attributes to products and SKUs in asset stores and extended site stores. We can create local attributes and values in an extended site attribute dictionary. Your site can have multiple attribute dictionaries, each associated to a particular store. Each store, however, can have only one attribute dictionary.

(Enterprise)

Inheriting attributes in extended sites

The attribute dictionary can be inherited in extended sites along with the attributes and values it contains. After inheriting an attribute dictionary, we can still load our own attributes and predefined values into the attribute dictionary. We can also update inherited attributes with local values to customize the attribute dictionary to meet the needs for the store. Separate icons are created to help distinguish inherited attributes and predefined values from locally created attributes and values. Attributes that are created within the attribute dictionary in the current store are local attributes. Attributes that are created within the attribute dictionary in an asset store are considered to be inherited attributes by the extended site. We can assign both local and inherited attributes that are contained within the attribute dictionary to local catalog entries for use as defining or descriptive attributes. We cannot assign local or inherited attributes that are contained within the attribute dictionary to inherited catalog entries.

Local catalog entries are catalog entries that are created in the current store. For example, all catalog entries in a stand-alone store or a catalog asset store are local catalog entries. Inherited catalog entries are catalog entries that are created in the catalog asset store of the current store. For example, in extended site stores the products that are created within the catalog asset store are inherited catalog entries. Although it is possible to use catalog upload or the Data Load utility to assign local or inherited attributes to inherited catalog entries, this method is not recommended. These scenarios are not supported by the Solr Search or catalog filter features.

We can also create local predefined values for inherited attributes and assign these values to local catalog entries.


Related tasks
Manage attributes
Use the attribute dictionary
Use catalog entry attributes
Creating a "fixed price on individual catalog entries from a category" promotion
Creating a "fixed price on the subtotal of catalog entries" promotion
Creating a "fixed price on individual catalog entries" promotion
Specifying catalog attributes in promotion purchase conditions