Manage catalog view configuration
With the Adobe Commerce Optimizer Connector for B2B extension installed, the Catalog Views page lists the Adobe Commerce Optimizer catalog view projections created for custom shared catalog. A projection is the catalog view created when the connector synchronizes shared catalog data to Adobe Commerce Optimizer. The connector creates a separate projection for each store view in the shared catalog, so a shared catalog can have multiple catalog views. In storefront experiences, these catalog views are accessible only to companies assigned to the associated shared catalog.
For example, suppose Acme Industrial is assigned to one shared catalog, EU Business, which belongs to the EU Website. That website has two store views:
-
English (UK) -
German (Germany)
The connector projects the shared catalog into two Adobe Commerce Optimizer catalog views:
-
EU Business – English (UK) -
EU Business – German (Germany)
The company has English and German catalog views, but only one shared catalog assignment. Each store view displays data from its corresponding catalog view.
Both catalog views can share the same price book when they use the same website and customer-group pricing scope.
Catalog view authentication
The connector protects catalog views with restricted access keys. Adobe Commerce uses the private key to sign an access token for an authorized buyer. Before returning protected catalog data, Adobe Commerce Optimizer validates the token against the corresponding public key associated with the requested catalog view.
To configure the token lifetime or disable token issuance, see Services > ACO Catalog View.
You can review these catalog views and manage their assigned keys from either the shared catalog’s Catalog Views tab or the associated company’s Catalog Views section—both list the same catalog views and current key assignments. See Edit restricted access keys for the exact navigation path from each location.
To monitor shared catalog data synchronization to Adobe Commerce Optimizer, see Catalog view sync status monitoring.
Catalog views reference
The grid lists one row for each catalog view created when a shared catalog is synchronized to Adobe Commerce Optimizer. The grid is read-only apart from the key-assignment action. Catalog views are created and removed automatically as the connector synchronizes shared catalogs configured in Adobe Commerce. If a catalog is removed, there is a grace period before the corresponding catalog view and data are deleted.
To assign or unassign restricted access keys, see Assign keys to a catalog view.
Edit restricted access keys
Assign or unassign keys from a catalog view, not from the main Restricted Access Keys grid. You can make this change from either the shared catalog’s Catalog Views tab or the associated company’s Catalog Views section — both list the same catalog views and current key assignments.
A catalog view must have at least one key and can have at most three. If you try to assign a fourth key, the save fails with a message telling you to remove one first.
-
Open the Catalog Views grid for the catalog view you want to update, using one of the following paths:
- From the shared catalog — On the Admin sidebar, go to Catalog > Shared Catalogs. For the shared catalog, select General Settings from the Action column. Then, in the Shared Catalog Information panel, select Catalog Views.
- From the company — On the Admin sidebar, go to Customers > Companies. For the company, select Edit from the Action column. Then expand the Catalog Views section.
Both grids list the catalog views created for the shared catalog assigned to the company, including their assigned keys.
-
Select Edit Restricted Access Keys for the catalog view you want to update.
-
In the Access Keys field, select an unassigned key by the Key ID value.
Keys already assigned to a different catalog view are labeled accordingly.
-
Select Done to assign the key to the catalog view.
-
To remove a key from the Access Keys field, select the
xin the key name entry to remove it. -
Click Save.
For additional details, see Manage restricted access keys.