The Akeneo integration for SAP Commerce Cloud serves as a bridge between Akeneo PIM and SAP Commerce Cloud, enabling the seamless exchange of product information between these two distinct systems.
Data model comparison table
Connecting two different systems requires making decisions on how data should be mapped. This high-level data model compares the Akeneo data model with Adobe Commerce, clarifying the integration choices.
For a more detailed understanding of configuring the mapping and filtering of data using the SAP Commerce Cloud integration, please refer to the section on how to set up and use the Connector. This section will provide you with comprehensive insights, guidelines, and step-by-step instructions on how to fine-tune the mapping and filtering processes, ensuring that your data synchronization is aligned with your specific requirements and business needs.
Legend
- Left, Black, strong: SAP Commerce entities
- Right, Light: Akeneo entities
SAP Commerce Cloud |
Akeneo |
||
|---|---|---|---|
| Catalog linked to staged and online stores |
One integration configuration is dedicated to a specific catalog in SAP CC. A catalog must be pre-existing and registered in the main configuration filter of the integration. It is based on one channel. |
||
| Languages and default language |
SAP Languages are represented by locales in Akeneo. Important: The default language set in SAPCC must be manually registered in the connector main configuration. |
||
| PriceRow |
Akeneo does not manage ERP pricing. Only default pricing. Default pricing attributes in Akeneo is mapped to PriceRows. |
||
| SuperCategories | Categories | ||
| Classifying categories | Family | ||
| Product | Product types | ||
| Product | Simple products | ||
| Base products | Product Models | ||
| Product Variation | Variation products level 1+2 | ||
| Categories | Variation Axis | ||
| Attributes | Attributes and extended attributes | Attributes | |
| Note: SAP Classification attributes and SAP Product type attributes | Depending of your configuration, attributes can be send to SAP classification attributes (PIM family replication) or to the SAP product type | ||
| Attribute types | |||
| Article Number | UUID Unique identifier | ||
| Localized:String | Identifier (SKU) | ||
| String | Text area | ||
| String | Text | ||
| Integer | Number | ||
| Date | Date | ||
| Yes/No | Boolean | ||
| Localized:String | Simple select | ||
| Categories | Attribute options | ||
| Collection<localized:String> | Multi-select | ||
| Variant or Classification (unit and value) |
Measurement. Unit are imported through impex and value mapped to umbers |
||
| Localized:string for Reference entities | As there are no concept of Reference Entity within SAP CC, the content is pushed as JSON in a Text Field. Need integration work to display it on the front-end | ||
| Localized:string for Table | As there are no concept of Tables within SAP CC, the content is pushed as JSON in a text area. Need integration work to display it on the front-end. | ||
| Media container | asset media link only within Akeneo PIM | ||
| Association | In SAPCC, associations are link between product, registered on the product backend page as target and source. In Akeneo, SAPCC association can be mapped to 1-way or 2-way associations. Association with quantity is not covered out-of-the-box on SAPCC so not covered in the integration. | ||
#PIM Feature coverage
This section provides an overview of the Akeneo PIM features supported by the Akeneo integration for SAP Commerce. Note that the integration is customizable and can be changed to fit your needs.
Feature |
Supported by the App |
|---|---|
| Categories | Yes |
| Enriched categories | No |
Family and family variants |
Yes |
Simple products |
Yes |
Product models |
Yes |
Product variants on all levels (1 and 2) |
Yes |
Product status |
No |
Attribute type as variation axes |
Yes Simple select, Reference Entity single link, Measurement, Yes-No, Multiple attributes used as variation axis |
Product association |
Yes 1-way or 2-way associations, no association with quantity as SAP CC out-of-the-box association do not cover quantity |
Association level |
Yes Association at product and product model levels |
Attributes value deletion |
No |
Asset |
Yes |
Asset structure: attribute type |
Media link only |
Asset structure: attribute properties |
No |
Images |
No |
Videos |
No |
No |
|
Reference Entities |
Yes Reference entities are pushed as JSON in a text area |
Reference Entities level |
Reference entities at product level and product model level |
Product Associations (cross-sell, up-sell) |
Yes |
#SAP Commerce Cloud integration capabilities and behavior
Important behavior about product deletion and empty values should be taken into consideration when integrating the connector.
Filtering |
Yes |
Mapping |
Yes Out-of-the-box filtering and advanced settings for default and custom entities |
Transformation |
Yes |
|
Product deletion
|
No eCommerce stays master on deletion |
Empty values |
No |
Pre-existing e-commerce catalog handle |
Yes Possibility to map pre-existing entities Refer to the installation article on pre-existing eCommerce |
Full synchronization |
Yes |
Delta or differential synchronization |
Yes |
Manual synchronization |
Yes |
Scheduled synchronization |
Yes |
Synchronization logs |
Yes |
Monitoring |
Yes |