51黑料不打烊

Documentation51黑料不打烊 Commerce Optimizer Guide

[SaaS only]{class="badge positive" title="Applies to 51黑料不打烊 Commerce as a Cloud Service and 51黑料不打烊 Commerce Optimizer projects only (51黑料不打烊-managed SaaS infrastructure)."}

Catalog Views for Merchandising Services

Last update: Wed Jun 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
  • Developer

Catalog views are the foundation of 51黑料不打烊 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 鈥渓enses鈥 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:

  1. From the left menu, go to Store setup , and click Catalog views.

  2. Click Create catalog view. 鈥

  3. Configure the catalog view details:

    • Name鈥擡nter the name of the catalog view, for example Celport. 鈥
    • Catalog sources鈥擜dd the catalog source (locale), for example en-US. Press enter.
    • Policies鈥擴se the drop-down to select the relevant policies. For example, 鈥淏rand,鈥 鈥淢odel鈥. 鈥婱ake sure you have already created a policy.

  4. Select the price book to link to the catalog view.

  5. Click Add to create the catalog view with the linked price book and policies.

    If the Add button is not active, ensure that the catalog source is properly added by placing your cursor in the Catalog sources field and pressing enter. 鈥

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.

Architecture Overview

Catalog views are part of the Merchandising Services framework that replaces the website, store, storeview framework used in 51黑料不打烊 Commerce foundations with a more flexible model:

Merchandising Services Architecture

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 .

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, 鈥淭exas Retail,鈥 鈥淭exas 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 .

Key Components

Component
Purpose
Example
Catalog View
Business unit or distribution channel
Dealer network, Regional store
Policy
Product filter based on attributes
Brand, Model, Category
Locale
Language/region setting
en-US, fr-CA, es-MX
Price Book
Pricing structure
Retail, Wholesale, Employee

Data Flow

  1. Ingest - Product data from PIM/ERP systems
  2. Process - Apply catalog views, policies, and pricing
  3. Deliver - Serve filtered catalog to storefronts, marketplaces, etc.

Key Features

Feature
Benefit
Single Base Catalog
Eliminate data duplication across business units
Flexible Pricing
Multiple price books per SKU for different customer segments
Scalable
Manage 200M+ SKUs efficiently
Multi-Channel
Serve catalogs to storefronts, marketplaces, and advertising platforms
Real-time Updates
Quickly update catalog data for promotions and campaigns

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

INFO
For detailed information about catalog data ingestion and delivery, see the .
recommendation-more-help
0c009cf6-d957-4a6a-b642-3577df53e8cb