Adobe Commerce Connector > Visibility status
The Mapping Component in the Magento Connector facilitates the seamless integration of product data between Akeneo and Magento. One of its critical features is the ability to map product visibility from Akeneo attributes to Magento’s visibility settings. This documentation outlines how the visibility mapping functions, the behavior when mappings are incomplete or invalid, and the default configurations used in such scenarios.
Functionality:
The connector allows users to map Akeneo attributes to Magento's visibility options. This enables dynamic control over product visibility on the Magento storefront based on data from Akeneo.
Magento Visibility Options:
1: Not Visible Individually
2: Catalog
3: Search
4: Catalog, Search
How to Configure:
In the connector configuration, select the Akeneo attribute you wish to map to Magento's visibility field.
Ensure that the attribute values correspond to Magento’s accepted visibility values (1, 2, 3, 4).
In scenarios where:
No visibility mapping is configured.
The mapped attribute does not exist in Akeneo.
The 'default_product_visibility' configuration in the database is not set.
The connector will apply the following default visibility settings:
Simple Products:
Product Models:
The visibility will default to 4 (*Catalog, Search*).
Product Models Variants:
The visibility will default to 1 (*Not Visible Individually*).
Purpose:
The `default_product_visibility` setting in the database provides a fallback visibility value when no valid mapping is provided.
Configuration Location:
This setting is stored in the database.
Behavior:
If `default_product_visibility` is set, its value will override the default visibility settings for both simple products and product models.
If `default_product_visibility` is not set, the connector defaults to the values mentioned above (4 for simple products, 1 for models).