The Akeneo Connector for SFCC serves as a bridge between Akeneo PIM and SFCC B2C 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 SFCC B2C, clarifying the integration choices.
For a more detailed understanding of configuring the mapping and filtering of data using the SFCC Connector in Akeneo, 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, strong: SFCC B2C entities
- Right, Light : Akeneo entities
SFCC |
Akeneo |
||
|---|---|---|---|
| Catalog | N/A. The catalog pre-exists in SFCC and has to be filled in the connector general parameters. Akeneo can have a different data organization and the configuration of the connector will define the data pushed within the catalog. | ||
| Languages | Locales. If you have some localizable attributes (attributes that can have different values per locale): the Akeneo Connector will import the content of these attributes into the different languages of an SFCC product. | ||
| Pricebook - for reference price. PIM does not replace the ERP | Currencies and attribute used as default or reference prices within the PIM | ||
| Category | Main Category tree | ||
| Attributes | Note: families are not imported as the concept of family does not exist in SFCC. If you have some scopable attributes (attributes that can have different values per channel): depending on your channel configuration, the Akeneo Connector will import the attribute values of the defined channel. |
||
| Attribute types | |||
| Text | Text | ||
| Text area | Text area | ||
| Date | Date | ||
| Number | Number | ||
| Enum of strings | Simple select → (1) The connector imports all attribute options with their translations. | ||
| Flag on the enum | Multiple select | ||
| Boolean | Yes/No | ||
| Text attribute | Metric (does not exist in SFCC) | ||
| Images | Image | ||
| Imports the relative PIM path in a text attribute | File ( binaries import are only for images in SFCC) | ||
| Image asset binaries in content assets product link | Asset collection | ||
| Reference price in Pricebook as mentioned above | Price attribute (here, default or reference price, PIM is not an ERP). | ||
| Product ID or text attribute | Identifier | ||
| JSON structure | Table Attribute | ||
| JSON Structure and content asset | Reference Entity | ||
| Product | Product types (SFCC types) | ||
| Standard products | Products simple | ||
| Variation master | The way an Akeneo product model is mapped to SFCC depends on the Modelization of Product Model (akeneoModelImportType) site preference. Three modes are available: - Master-Variation: the root product model is imported as the Variation master. Sub-models (variation level 1) are not imported as separate SFCC objects. - Master-Group-Variation: the root product model is imported as the Variation master, and each sub-model (variation level 1) is imported as a Variation group. - Sub-Master-Variation: for product models with 2 levels of variation, the root product model is skipped and each sub-model (variation level 1) is imported as its own Variation master. Product models with a single level of variation are imported as in Master-Variation. |
||
| Variation group | - In Master-Group-Variation modelization with 2 levels of variation, variation groups are mapped to the Akeneo sub-models (variation level 1) - In Master-Group-Variation modelization with 1 level of variation, no variation group is created - In Master-Variation and Sub-Master-Variation modelizations, variation groups are not used |
||
| Variation product | - In Master-Variation modelization with 1 level of variation: variation product = Akeneo variation level 1 - In Master-Variation modelization with 2 levels of variation: variation product = Akeneo variation level 2, carrying the variation axes of both levels 1 and 2 (the hierarchy is flattened) - In Master-Group-Variation modelization with 1 level of variation: variation product = Akeneo variation level 1 - In Master-Group-Variation modelization with 2 levels of variation: variation product = Akeneo variation level 2 - In Sub-Master-Variation modelization with 2 levels of variation: variation product = Akeneo variation level 2, attached to the sub-model imported as Variation master. With 1 level of variation, the mapping is the same as Master-Variation |
||
| Associations | |||
| Product recommendation | Akeneo association | ||
| Product links | Akeneo associations | ||
| Set | Specific Family + Specific association type | ||
| Bundle | Specific Family + Specific association type | ||
| Product Options | N/A | ||
Feature coverage
You can also find the feature coverage on Akeneo app store.
SFCC Feature coverage
This section provides an overview of the principal features of SFCC B2C stated above.
| SFCC Feature | Supported by the Integration |
|---|---|
| Catalogs | Yes |
| Categories | Yes |
| Base product | Yes |
| Variation slicing | No |
| Variation group | Yes |
| Variation product | Yes |
| Standard product | Yes |
| Content assets | Yes |
| Product Bundle | Yes |
| Product Set | Yes |
| Option products | No |
Akeneo PIM Feature coverage
This section provides an overview of the Akeneo PIM features supported by the Akeneo connector for SFCC B2C. Note that the connector is customizable and can be changed to fit your needs.
| Akeneo PIM Feature | Supported by the Integration |
|---|---|
| Categories and enriched categories | Yes |
| Family and family variants | Yes |
| Simple products | Yes |
| Product models | Yes |
| Product variants on all levels (1 and 2) | Yes |
| Product statuses | Yes |
| 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 association (like upsell,cross-sell for instance), Association with quantities |
| Association level |
Yes Association at product and product model levels |
| Attributes value deletion | Yes |
| Asset | Yes |
| Asset structure: attribute type | Media file OR media link, prefix and suffix as media link property, text |
| Asset structure: attribute properties | Localizable attribute (value per locale), scopable attribute (value per channel) |
| Images | Yes |
| Videos | Yes |
Yes |
|
| Reference Entities | Yes |
| Reference Entities structure: attribute type | Image, text, number, single option, multiple options |
| Reference Entities structure: attribute properties | Localizable and scopable attributes (value per locale and channel) |
| Reference Entities level | Reference entities at the product level and product model level |
SFCC B2C Commerce connector 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 | No |
|
Product deletion
|
No eCommerce stays master on deletion |
| Empty values |
No |
| Full synchronization | Yes |
| Delta or differential synchronization | Yes |
| Manual synchronization | Yes |
| Scheduled synchronization | Yes |
| Synchronization logs | Yes |
| Monitoring |
Yes Within the connector |