A catalog contains the products available for sale in your store. A catalog also contains information about how to organize those products for navigation menus and search facets in a shopper experience.
Catalogs with Product Content Management and Price Books
When using the Product Content Management (PCM) feature, before you create a catalog you define the following resources:
- Hierarchies - hierarchies and nodes for all the ways that you can categorize the products
- Products - product information, associated assets, and links to hierarchy nodes
- Price Books - prices for the products associated with the hierarchies
A catalog is a combination of hierarchies and a price book. The hierarchies determine which products appear in the catalog, that is, only the products that are associated with the selected hierarchies are included in the catalog. The price book contains the prices for each of the products in the catalog.
When a catalog is ready to be used in a store, you publish it. You can create and publish catalogs for different contexts and channels. You retrieve catalogs for your shopper experience by using the Catalog View API.
Catalogs with v2 Product resources
While catalogs were designed for use with Product Content Management services, you can use the Catalog View API to retrieve v2 Product resources. For example, if you do not see a need to migrate
pcm/products resources, but you want to speed up requests for products, you can use the read-only Catalog View service to retrieve the products.
The returned products are in the form of the v2 Product object, which includes prices. The returned v2 Brands, Collections, and Categories are structured into separate hierarchies. For example, the v2 Brand resources appear in a single Brand hierarchy where the nodes have the same names as the Brand resources.