Catalog views
A catalog view defines the products and pricing that a storefront can retrieve. In Adobe Commerce as a Cloud Service instances provisioned with the Composable Catalog Data Model (CCDM), catalog views use the same catalog foundation that powers Adobe Commerce Optimizer.
Catalog views combine catalog sources, policies, and price books to define a storefront’s catalog context. Policies determine the available product assortment. Merchandising rules control how products within that assortment are promoted and ranked, and can apply across all catalog views or be tailored to a specific view. See Create a merchandising rule.
Commerce Foundation remains the source of truth for products and prices. Product and price data synchronize one way to CCDM through native Adobe Commerce as a Cloud Service integration, with no separate connector installation or App Builder app. Website, store, and store-view configuration remains in Commerce Foundation, which also manages cart, checkout, promotions, customers, orders, and payments.
How catalog views work
A catalog view brings together catalog data and configuration for a storefront context. It can be used to represent a business unit, brand, region, or other storefront experience.
- Catalog sources provide product data for catalog experiences.
- Policies filter product data for a catalog view.
- Price books provide pricing data associated with a catalog view.
Catalog views do not replace the website, store, and store-view structure in Adobe Commerce as a Cloud Service. Commerce Foundation continues to manage that structure and transactional operations.
Catalog data synchronizes one way from Commerce Foundation into CCDM. CCDM supports storefront catalog experiences and product discovery. Commerce Foundation continues to handle cart, checkout, promotions, customers, and orders.
Before you start
Before configuring a catalog view:
- Confirm that the Adobe Commerce as a Cloud Service instance uses CCDM.
- Confirm that the catalog data required for the storefront has been populated and synchronized.
- Identify the catalog source, policies, and price books needed for the storefront context.
- Determine whether you need to create B2C catalog views manually or review B2B catalog views generated by native synchronization.
Create a catalog view for a B2C implementation
Use this workflow when the B2C implementation requires catalog views to be configured manually.
- Sign in to the Commerce Admin in Unified Experience, and select the Adobe Commerce as a Cloud Service instance provisioned with CCDM.
- In the left navigation, go to Catalog > Catalog Views.
- Select Create catalog view.
- Enter a name for the catalog view.
- Select the catalog source or sources for the storefront context.
- Associate the relevant policies with the catalog view.
- Associate the relevant price books with the catalog view by configuring price book availability.
- Create the catalog view.
B2B catalog views
For B2B implementations, native synchronization generates catalog views, policies, and price books from the B2B configuration in Commerce Foundation. Manage the underlying B2B catalog and company relationships in Commerce Foundation rather than manually creating duplicate structures in CCDM.
For setup instructions, see Create a shared catalog and Assign companies to a shared catalog.
After configuring the B2B relationships:
- Confirm that synchronization has completed.
- Review the generated catalog views, policies, and price books in Commerce Admin in Unified Experience.
- Verify that the storefront displays the expected product assortment and pricing for the company.
- Test add-to-cart, cart, and checkout to confirm that product availability and transaction pricing match the intended B2B configuration.
Price books and checkout
Price books provide the pricing data available through a catalog view. In Adobe Commerce as a Cloud Service, Commerce Foundation remains the source of truth for prices, and pricing data synchronizes to CCDM through native integration. When configuring a catalog view, use the applicable synchronized price books rather than independently authoring prices in CCDM.
Cart and checkout use Commerce Foundation pricing. Verify that displayed storefront prices match the applicable cart and checkout prices.
Review and validate a catalog view
After configuring a catalog view, verify the complete storefront experience:
- Confirm that the intended catalog data is synchronized.
- Confirm that the catalog view is associated with the intended policies and price books.
- Check that the storefront returns the expected product assortment.
- Verify displayed pricing against the corresponding Commerce Foundation pricing.
- Test add-to-cart, cart, and checkout.
For B2B implementations, also confirm that the catalog structures generated by synchronization match the intended company and catalog configuration.
Troubleshooting
Products are missing from the storefront
- Confirm that the instance uses CCDM.
- Confirm that catalog data has synchronized.
- Check that the storefront is using the intended catalog context.
- Review the policies associated with the catalog view.
The displayed price is unexpected
-
Confirm that the intended price book is associated with the catalog view.
-
Check that the price data is synchronized and consistent with Commerce Foundation.
See Price books for the website and customer-group pricing mappings.
-
Validate the price again in cart and checkout.
CCDM catalog screens are not visible in Commerce Admin
Confirm that the selected instance uses CCDM and that you are accessing Commerce Admin in Unified Experience. An instance running catalog services v1 does not have the CCDM administration screens.