Catalog Views for Merchandising Services
Catalog views are the foundation of Adobe Commerce Optimizer Merchandising Services, enabling you to organize your product catalog by business structure, policies, and pricing. This flexible data model supports multi-brand, multi-business unit, and multi-language scenarios while maintaining operational efficiency.
What are Catalog Views?
Catalog views define how your product catalog is organized and displayed. They act as filters that determine:
- Which products are visible based on business structure (brands, regions, dealers)
- What pricing is shown through linked price books
- How products are filtered using policies (attributes like brand, model, category)
- What catalog source is used based on attributes like locale
Think of catalog views as different “lenses” through which customers see your catalog. For example:
- A dealer catalog view might show only products available to that specific dealer
- A regional catalog view might show products and pricing specific to a geographic area
- A brand catalog view might show only products from a particular brand
Create a Catalog View
In this section, you create a catalog view, select a policy, and a price book.
Before creating a catalog view, ensure you have:
-
Created policies to define product filters
-
Ingested price books for pricing
-
From the left menu, go to Store setup , and click Catalog views.
-
Click Create catalog view.
-
Configure the catalog view details:
- Name—Enter the name of the catalog view, for example
Celport. - Catalog sources—Select the catalog source (locale), for example
en-US. - Policies—Use the drop-down to select the relevant policies. For example, “Brand,” “Model”. Make sure you have already created a policy.
- Name—Enter the name of the catalog view, for example
-
Select the price book to link to the catalog view.
- Use all available price books-This option pulls pricing data from all available price books.
- Allow selected price books only-This option displays the Add allowed price books dialog where you can select which specific price book to use for the catalog view.
- Disable pricing-This option is not available at this time.
-
Click Add to create the catalog view with the linked price books and policies.
The Catalog views page updates to display the new catalog view.
After you complete these steps, the catalog view is now configured to display products and pricing based on your selected sources and policies.
Manage catalog view
Follow these instructions to update or view the properties of existing catalog views.
Edit catalog view
- On the Catalog views workspace, find the catalog view in the grid that you want to edit and click … to open the actions menu.
- Click Edit to access the catalog view editor.
- Update the name, catalog sources, policies, and price book information as needed.
- Save the changes.
Delete catalog view
-
In the Catalog views workspace, find the catalog view in the grid that you want to edit and click … to open the actions menu.
-
Click Delete.
When the confirmation dialog appears, click Delete.
View details
This option provides a quick way to see all the catalog view parameters, while staying on the Catalog views table.
On the Catalog views worksapce, find the catalog view in the grid that you want to edit and click the
From here you can see catalog view configuration details, such as:
- View ID
- Name
- Catalog sources
- Policies
- Date Created
- Data Modified
Some of these configuration settings are needed as you set up your storefront or use the data ingestion API.
Architecture Overview
Catalog views are part of the Merchandising Services framework that replaces the website, store, storeview framework used in Adobe Commerce foundations with a more flexible model:
How It Works
1. Data Ingestion
Catalog data from PIM, ERP, and other systems is ingested into the Merchandising Services framework. Each SKU contains locale information and product attributes that map to catalog views, policies, and locales. For more information about data ingestion, see the developer documentation.
2. Unified Base Catalog
The ingested data creates a unified base catalog in the Catalog Service data pipeline. This single source eliminates data duplication across business units.
3. Catalog Views
Multiple catalog views represent different business units (for example, “Texas Retail,” “Texas Retail Seasonal”). Locales, policies, and price books can be shared across catalog views for flexibility.
4. Multi-Channel Delivery
The filtered catalog data is delivered to various destinations including Edge Delivery Services storefronts, marketplaces, advertising platforms, and custom micro-storefronts. For more information about catalog data delivery, see the developer documentation.
Key Components
Data Flow
- Ingest - Product data from PIM/ERP systems
- Process - Apply catalog views, policies, and pricing
- Deliver - Serve filtered catalog to storefronts, marketplaces, etc.
Key Features
Use Cases
Multi-Brand Conglomerate
Challenge: Manage multiple brands, countries, and languages
Solution: Single catalog with catalog views for each brand/region combination
Automotive Parts Dealer
Challenge: 3,000 dealers with same products but different pricing
Solution: One catalog with dealer-specific catalog views and price books
Multi-Location Retailer
Challenge: Different pricing and inventory per location
Solution: Location-based catalog views with region-specific policies