Catalog filtering
Set up catalog filters to entitle our customers to a subset of the catalog. Catalog filters can also be used as one of the price rule conditions when we are determining prices for the set of catalog entries our customers are entitled to.Manage the catalog filters in Management Center provides you with the following business benefits:
- Provides flexible filtering criteria.
- Supports reusability across stores and contracts.
- Supports search engine-based dynamic catalog filtering, based on the Solr search solution.
We can create catalog filters to filter your master catalog only. We cannot create catalog filters for a sales catalog.
Catalog filtering criteria
When you create catalog filters, we can combine one or more filtering criteria to achieve your business goals.- Category-based criteria
- We can include or exclude categories from the catalog. If you include a category, all catalog
entries and subcategories under this category are included, unless you explicitly exclude the catalog entry or category. For example, if you include the Fasteners parent category in your filter,
by default, the Nuts, Bolts, and Screws subcategories are also included. However, we can explicitly
exclude the Nuts subcategory.
When a subcategory or catalog entry is included in the catalog filter, its parent category becomes browsable. Otherwise, customers cannot browse to the categories and catalog entries that you included in your filter.
- Category-based criteria with conditions
- We can apply conditions on the categories that are added to the catalog filter. The condition
can specify attribute dictionary attributes or catalog entry properties. By default, we can specify
the following catalog entry properties: part number (code), manufacturer part number, and
manufacturer name. For example, we can include all products that are manufactured by IBM in your filter.
To apply a condition on a certain category, we must first define a condition group. A condition group is a group of one or more attribute dictionary attributes and catalog entry properties conditions. A category can have one or more condition groups, and each condition group can contain one or more attribute dictionary attribute and property conditions. To learn more about conditions in catalog filters, see Attribute dictionary attribute and property conditions in catalog filters.
- Catalog entry-based criteria
- We can include or exclude specific catalog entries. The catalog-entry-based criteria takes precedence over the other filtering criteria. For example, assuming Product A is under Category A, if you exclude Category A and include Product A in the catalog filter, Product A is still included in the catalog filter.
Catalog filter usage: Product entitlement
When you assign a catalog filter to a contract, the customers shopping under the contract can browse, search for, and purchase the catalog entries that are defined in the catalog filter. For example, in a B2B business model, we can create catalog filters, and then assign different catalog filters to each business contract. The customers shopping under the specific contract can see and purchase only the catalog entries that they are entitled to.
The following diagram illustrates an example of a catalog filter product entitlement usage.
We can assign catalog filters to different types of contracts. For more information, see Catalog filter assignment and contracts.
Catalog filter usage: Price rules
Use a catalog filter in a price rule condition to define a set of catalog entries to price a certain way. We must specify the catalog filter in the Catalog Condition element in the price rule. The following diagram illustrates how we can use catalog filters to mark down the catalog entries in the Nuts and Bolts categories by 10% and 20%.
Limitations
- Catalog entry properties and attribute dictionary attributes that have different values in different languages are not supported.
- Attribute dictionary attributes that have assigned values, rather than predefined values, are not supported in the filter conditions.
- Attributes that are not stored in the attribute dictionary are not supported because they are not shared by multiple catalog entries.
- Catalog filtering does not support workspaces or content versioning.
- There is no migration tool to migrate existing catalog filters in WebSphere Commerce Accelerator to the Catalog Filter and Pricing tool.
Notes
- When you assign a catalog filter that is created in the Management Center to a contract, this catalog filter overrides any WebSphere Commerce Accelerator catalog filter.
- If you do not have a Management Center catalog filter assigned to the contract, the WebSphere Commerce Accelerator catalog filter is used instead.
Related concepts
Catalog Filter and Pricing tool
Catalog filter assignment and contracts
Catalog filter uploads
Related tasks
Manage catalog filters
Uploading catalog filter data
Creating catalog filter data in CSV format
Use catalog filters
Manage price rules
Related reference
Attribute dictionary attribute and property conditions in catalog filters
File format for uploading catalog filter data
Scenarios for using catalog filters