Rule-based sales categories

Use rule-based sales categories in a sales catalog to help us create sales categories, which are a type of sales category that use a search-based, user-defined rule to find and automatically assign catalog entries to the category. Using rule-based sales categories for large or frequently changing categories, we can reduce the time needed to assign or update the catalog entries for the category.

We can configure rule-based sales categories so the rules are automatically reapplied after a specific time interval elapses since the last time the rule was reapplied. This configuration ensures that the categories always remain up-to-date and include the catalog entries that best match the rule for each category.

We can create and use rule-based sales categories for almost the same purposes that we use regular sales categories. For instance, in addition to displaying the categories in the storefront, we can also use the categories in promotions, marketing activities, and Commerce Composer widgets. We cannot use rule-based sales categories as parent categories or create versions of the categories.

When we use regular sales categories in a sales catalog, we must manually search for each catalog entry to assign to the category or remove from the category. With rule-based sales categories, however, we define search filter conditions that identify the catalog entries to assign to the rule-based sales category. We can base these search filters on catalog entry properties, attribute dictionary attributes that are for use in merchandising, and the parent sales and master categories for catalog entries.

We can still manually search for and assign specific catalog entries to the rule-based sales category similar to how we can assign catalog entries to sales categories. When we save and apply the rule, the catalog entries that match our search conditions and the catalog entries that we manually specified are assigned to the rule-based sales category. To find the catalog entries that match our search conditions, WebSphere Commerce search uses the search filters to retrieve the matching catalog entries. For example, we can create a rule-based sales category, "Clearance sale on dresses", which includes any dress that is marked for clearance." When creating a rule for the category, we can include the following search filter conditions to find catalog entries. Each search condition is used to find catalog entries that match the conditions:

• The catalog entry property "Manufacturer Name" matches one of the following values: "Gusso" or "Alibini".

• The master category that includes the catalog entry matches one of the following values: "Dresses".

• The catalog entry is assigned the attribute "Clearance" with a value that matches one of the following values: "Clearance".

Along with defining the search filter conditions for the category, we can define sort criteria to arrange how the catalog entries are sequenced in the category. The sort criteria applies to only the catalog entries that match the search filter conditions. The specific catalog entries that are directly assigned to the category must be sequenced manually.

By basing a search filter on the attribute, we can manage catalog entry assignments for the category simply by managing which catalog entries are assigned the attribute and then reapplying the rule. When we reapply the rule, the catalog entry assignments for the category updates. The current products assigned to the category are all removed. WebSphere Commerce search then finds the current products assigned the Clearance attribute, and the Catalogs tool automatically assigns the products to the category. Any product that is no longer assigned the attribute, no longer displays in the category.

(Enterprise) If the site uses an extended sites store model, we can create rule-based sales categories in our extended site store and inherit rule-based sales categories from the catalog asset store. We can create or place an extended site store rule-based sales category in both an extended site store or inherited asset store sales category. If our extended site store includes an inherited rule-based sales category, we can view the category within the extended site store, but we cannot edit the category or reapply the rule.

Rule-based sales categories in workspaces

If workspaces are enabled, we can create, manage, preview, and delete, rule-based sales categories in a workspace. When we are working with or approving changes for a rule-based sales category in a workspace, ensure that you review the behavior for these categories in a workspace:

• We can apply or reapply the rule for a category while we are working in a workspace.

• When the rule for a rule-based sales category is modified and applied in a workspace, we can view only the category in the change history for the workspace. The changes to the catalog entry assignments for the category do not display in the change history.

• When you undo changes for a rule-based sales category, you undo all changes that are made to the category in the workspace.

• When you approve the changes for a rule-based sales category, the rule for the category is identified as needing to be evaluated. Any configured time interval for reapplying the rule is ignored. The next time a rule evaluation and application process runs, such as when the search index is being updated, the rule is reapplied to the category.

• We cannot use quick publish to publish a rule-based sales category and the catalog entry assignments for the category to production.

• When the process to evaluate and apply the rule for rule-based sales categories runs, the job does not evaluate the rule for categories in a workspace. When you create or update catalog entries that match the rule for a category, the process to automatically reapply the rule to the category does not assign those catalog entries. To include those catalog entries, we must manually reapply the rule or wait until the task group that includes the catalog entries is approved. When the task group is approved, the job to reapply the rules runs automatically and then assigns new or changed catalog entries to the category.

Considerations and limitations

Before starting creating rule-based sales categories, ensure that you review the following considerations and limitations:

• Do not create rule-based sales categories or reapply the rule for the categories in your production environment. Applying the rule to a category in your production environment can affect performance. To update a category that is in your production environment with catalog entries that exist in only ythe production environment, request that an administrator copy the data into the authoring or staging environment. Then, run the rule in the authoring or staging environment and then have the administrator propagate the updated category to the production environment.

• We cannot use a rule-based sales category in a search filter condition for another rule-based sales category. If we use a sales category that includes both a rule-based sales category and a regular sales category as child categories, only the catalog entries from the child sales category can be included by the rule that we are defining.

• We cannot create or place a rule-based sales category as a parent category. Rule-based sales categories can exist in a sales catalog hierarchy only as child categories.

• We cannot manually assign catalog entries to a rule-based sales category by adding the catalog entries to the Catalog Entries List for the category. We can manually assign catalog entries to a rules-based sales category within the Add specific catalog entries to this category section of the properties view Rule tab for the category.

• We must use attribute dictionary attributes that are for use in merchandising when we select to use an attribute in a search filter condition.

• We must index catalog entries with WebSphere Commerce search before the catalog entries can be found and assigned to any rule-based sales category.

• We cannot create, update, or delete rule-based sales categories with any loading utilities, such as Catalog Upload.

• We cannot use content versioning with rule-based sales categories.

• We cannot link a rule-based sales category to another sales category.

• When workspaces are enabled, we cannot use quick publish to publish a rule-based sales category and the catalog entry assignments for the category to production. Request that an administrator publish your rule-based sales category data with the stagingprop utility and update the search index with the indexprop utility.

• We cannot include multiple categories in rule-based sales categories. This is due to the filter combining the categories using AND logic, which is more restrictive than OR logic. As an alternative, ask the site administrator to enable deep search sequencing, which is used to enhance the storefront by using Category-based browsing flows that customers can use to browse products.

Enable rule-based sales categories

By default, we can create, change, and delete rule-based sales categories and we can define the rule for a category, but we cannot apply the rule. To apply the rule that finds and assigns catalog entries to a rule-based sales category, an administrator must enable the evaluation and application of the rule.

After enabling the application of rules, an administrator can configure the rule evaluation process to automatically reapply the rule for each category after a specific amount of time elapses from the last time that the rule was reapplied. By having an administrator enable this behavior, you do not need to manually reapply the rule in the Catalogs tool to keep a rule-based category up-to-date.

See Enable rule-based sales categories.

Related concepts
Sales catalogs

Related tasks
Manage rule-based sales categories
Manage sales catalogs