(1) note: the default time will be set at 12AM.

(2) The connector imports all attribute options with their translations. Please note that options without a label in the language of the Adobe Commerce admin store won't be imported.

(3) As boolean attributes do not exist in Adobe Commerce, the connector converts those as simple select Yes/No attributes. If the value is null in the PIM, it will be set to “No” in Adobe Commerce.

(4) Since the 100.3.0 version of Akeneo Connector for Adobe Commerce, metric attributes can be imported as text attributes or select attributes if they are used as a variant, with or without the metric unit concatenated (see how to configure products)

(5) Since the 100.4.2 version of Akeneo Connector for Adobe Commerce, file attributes can be retreived from Akeneo PIM inside the Adobe Commerce media directory. Their path will be inserted in the corresponding text attribute (see how to enable file attribute import)

(6) Only available for Akeneo Connector for Adobe Commerce Enterprise Edition. As Adobe Commerce does not support the import of binary files other than images, the connector only import image asset binaries and image asset links (see how to configure images).

(7) Since Akeneo October 2021 Serenity updates, the Table attribute type has been added in the PIM.

Therefore, since the 102.1.4 version of Akeneo Connector for Adobe Commerce, you can now import table attribute data in Adobe Commerce.

As Adobe Commerce does not have a table attribute type, Akeneo Connector for Adobe Commerce can import table data into a Adobe Commerce text area attribute as a JSON structure.

JSON example:

[
             {
             "number": {
             "Per 100g": "10"
             },
             "text": {
             "Text Attribute": "Test text 1"
             },
             "yes_no": {
             "Yes No attribute": true
             },
             "average_nutritional_values": {
             "Average nutritional values": "Saturated fat"
             },
             "percentage_reference_intake": {
             "% of reference intake (per 100g or serving)": "10"
             }
             },
             {
             "number": {
             "Per 100g": "4"
             },
             "text": {
             "Text Attribute": "Test text 2"
             },
             "yes_no": {
             "Yes No attribute": false
             },
             "average_nutritional_values": {
             "Average nutritional values": "Sugars"
             },
             "percentage_reference_intake": {
             "% of reference intake (per 100g or serving)": "4"
             }
             }
             ]
             

The order of the column values is not managed by the Akeneo API yet, therefore the column order might not be reflected in the JSON structure.

In case of a table sub-attribute label update or a table sub-attribute option label update, every product previously imported with the old label value has to be re-imported in order to apply the changes.

If you still use an add-on that has been developed by Flagbit or Webkul company in order to manage "table" attribute type in your PIM, the connector is still compatible with these two extensions. To do so, please refer to our connector configuration documentation to know how to manage the "table" attribute type for these extensions.

(8) Reference entity select / multi-select attributes are created as select or multi-select in Adobe Commerce, and an additionnal "Text area" attribute can be created if enabled in the reference entity configuration.

Since the 102.6.0 version of Akeneo Connector for Adobe Commerce, you can import reference entity record labels and measurement attribute from table attributes in the JSON

Please note that attributes without a label in the language of the Adobe Commerce admin store won't be imported.

Mapping between your PIM and Adobe Commerce: 
Akeneo Connector for Adobe Commerce maps PIM categories with Adobe Commerce categories. 

The connector does not yet manage the Enriched Categories feature of the PIM, so for now it only imports PIM category title information into Adobe Commerce category.

Mapping between your PIM and Adobe Commerce: 
The connector maps PIM "products" with Adobe Commerce Simple products.

Mapping between your PIM and Adobe Commerce: 
The connector maps PIM "product model" as such:

PIM Product model with 1 level of variation:

• PIM product model common part with Adobe Commerce Configurable product
• PIM product model variation level 1 part with Adobe Commerce Simple product

PIM Product model with 2 levels of variation: As Adobe Commerce only manages only 1 level of variation, for PIM Product model with 2 levels of variation*, Akeneo Connector for Adobe Commerce concatenates attribute data from common and level 1 layer of product models.

The impact for mapping is as follows:

• PIM product models common part + variation level 1 are mapped with Adobe Commerce Configurable product
• PIM product models variation level 2 is mapped with Adobe Commerce Simple products