Most frequently asked questions about the Connector
#How long will it take to synchronize 1000 products from Akeneo PIM to Magento (Full Load)?
It is difficult to give a precise time for this question because it depends on many parameters (catalog properties (i.e how many attributes per product? How many localizable attributes? How many pictures?...), server hardware power, server configuration, network capacity,...etc...).
As Akeneo Connector for Magento 2 is based on the same architecture as Pimgento 2 API, you could read this article from DnD company to get an idea of the Connector's performance.
#If we delete a product in Akeneo PIM, will it also be removed from Magento 2?
No. You should probably need some customizations to have this feature.
We think that it is better to never delete a product and use a specific enable/disable attribute state to manage obsolete products.
In Magento 2, the “status” attribute, which is used to say whether a product is enabled or not, takes the value 1 (enabled) or 2 (disabled) (and not 0 or 1 as a boolean)
If you really need to delete products, you will need to delete it manually in Akeneo PIM and Magento 2.
#If we remove a category from Akeneo PIM, will it be removed from Magento 2 after synchronization?
#If we change the category structure in Akeneo PIM (positioning, moving parent and sub categories), will it be changed in Magento 2 after synchronization?
#If we have a custom attribute for category in Magento 2, that custom attribute is mandatory, is there any issue when creating category from Akeneo PIM using Akeneo Connector for Magento2?
Yes because :
- Akeneo Connector will import all PIM categories
- The mandatory attribute will be empty (because PIM categories have no attributes).
- If you edit a Magento category, you will have to fill all mandatory attributes.
#If we remove some products from a category in Akeneo PIM, will those products be unassigned from the category in Magento 2 too?
No. It stays in the category. However, it is not re-imported if it is subsequently manually deleted.
#How Akeneo Connector for Magento 2 manage select attribute options?
For example, in Akeneo PIM, there is a simple select attribute: Color with these options: "Red", "Blue", "Black".
It will be synchronized by Akeneo Connector for Magento 2
If we remove the option "Red" from Akeneo and synchronize to Magento again:
1) Will that option Red also removed from Magento attribute option?
2) What happen for the products which had Red option before?
Akeneo Connector for Magento 2 doesn’t remove this option. You will need to remove it manually in Magento 2 (because it is probably link with some products).
3) If we change the option "Blue" to "Light Blue", will it be updated in Magento 2 after synchronization?
#If we have some "custom" product type in Magento, such as "Gift Cards". Those products don’t exist in Akeneo PIM, will those products be removed after synchronization because Akeneo PIM is the "master" source?
No. Akeneo Connector for Magento 2 keeps products that already exist in Magento 2.
#If we assign a product to some categories in Magento 2 only, not Akeneo PIM, will that product be removed from the categories after synchronization?
Yes. Pimgento keeps only Akeneo PIM categories. After synchronization, any manual addition is overwritten, any manual deletion is restored.
#Can we reset a value of an attribute in Magento 2 after synchronization from Akeneo PIM?
Example 1: There is a text attribute attribute: Promotional Message
- Today, we want to set it to in AkeneoPIM: "Discount 50%""
- Tomorrow, we want to set it to [empty] in Akeneo PIM.
If you clear the content of a text attribute (make it empty) in Akeneo PIM it will be synchronized by Akeneo Connector for Magento 2.
Example 2: There is a simple select attribute: Color
- Today, we want to set it to in AkeneoPIM: "Red"
- Tomorrow, we want to set it to empty in Akeneo PIM.
For simple select attribute type, you need to have a “none” option for this attribute to be able to reset it (because you can’t « unselect » a simple select). It will then be synchronized by Akeneo Connector for Magento 2.
Example 3: There is a multi select attribute: Promotion Campaign
- Today, we want to set it to “Black Friday” in Akeneo
- Tomorrow, we want to set it to blank in Akeneo
For multi-select, you can clean all option content in Akeneo PIM, it will be synchronized by Akeneo Connector for Magento 2.
#Compatibility with Magento 2 features
#Does Akeneo Connector support Bundle Product and Group Product?
101.2.0 version of the Akeneo Connector for Magento 2 and for Akeneo Edition
Growth Edition and
Serenity Edition, you can import "Grouped products" in Magento 2 (Documentation).
Akeneo Connector for Magento 2 doesn’t yet support Magento 2 "Bundle Products".
#Does Akeneo Connector support Virtual Product and Downloadable Product?
No, Akeneo Connector for Magento 2 doesn’t yet support Magento 2 "Virtual Product" and "Downloadable Product”.
#If we change the product name in Akeneo, will that change the url_key of the product in Magento after synchronization?
Yes. But you need to do a specific mapping for that with Akeneo Connector for Magento 2. Please refer to our documentation for this mapping.
#Does Akeneo Connector for Magento 2 supports UpSell/CrossSell synchronization from Akeneo PIM to Magento 2? Will that overwrite the Rule Based Relations for UpSell/CrossSell in Magento 2?
In Akeneo PIM you can have a Upsell/CrossSell product association and it will be synchronized by Akeneo Connector for Magento 2 with a Up-Sells, and Cross-Sells product relation at product level. Please refer to our documentation about this.
#Compatibility with Visual Merchandiser
#If we use Visual Merchandiser to assign products to a category by rules, will that be overwritten after synchronize with Akeneo PIM?
No. If you use automatic rules or manual position change of a product with Visual Merchandiser, Akeneo Connector for Magento 2 import does not reset these changes.
The association between products and categories will be overwritten by the Connector but the positioning will be preserved.
#If we configure Visual Merchandiser for a Category in Magento 2, will the Category get overwritten after synchronization?