π‘ Got Questions We Missed?
If this FAQ doesn't cover your question, we'd love to hear from you! Scroll down and click "Give feedback about this article" to share your thoughts or ask your question.
Your input helps us improve and ensures we provide the answers you need. π
Connection and compatibility
Can SDM connect to any Akeneo PIM version?
Yes, Supplier Data Manager (SDM) can integrate with any version of Akeneo PIM that supports API access.
How does the Akeneo PIM Connector work?
The Akeneo PIM Connector in SDM serves two purposes:
- Configuration sync β The connector keeps your SDM workflow in sync with your Akeneo PIM structure (Families, Attribute Groups, Attributes, and more). The sync runs automatically on a configured schedule (weekly by default) and can also be triggered manually.
- Product push β When a job is finalized in SDM, the connector automatically sends the enriched product data back to Akeneo PIM via the API to create or update products. You do not need to build a custom output format.
See Akeneo Connector overview for a full explanation of how both processes work.
Can I input data from my PIM into SDM?
Yes, you can treat a PIM export as any other supplier file in SDM. This use case is not handled by the Akeneo PIM Connector itself, so you need to either manually download the export from your PIM and upload it to SDM, or use an SFTP server combined with an ETL tool to automate the process.
Note that while this is supported in the Extraction module, the Classification module does not use existing values from the supplier file. The AI will always suggest mapping products with Family and Categories at the classification step.
Configuration sync
How often does the connector sync my PIM configuration?
The sync runs automatically on a cron schedule configured during the connector setup. The default schedule is weekly, but it can be adjusted by your Akeneo business consultant or SDM integrator. You can also trigger a manual sync at any time from the SDM interface β see Can I manually trigger a PIM configuration sync? below.
Can I manually trigger a PIM configuration sync?
Yes. To synchronize the latest Akeneo PIM configuration into your SDM workflow immediately:
- In SDM, go to Workflows and open the workflow connected to Akeneo PIM.
- In the left navigation, click Settings and then select Connector.
- Click Synchronize.
SDM fetches the latest PIM structure immediately β no need to wait for the next automatic sync. Once complete, the page updates to show the new last sync date and a Done status.
To apply the updated configuration to a step you are currently working on, go back and edit the previous step. This resets the current step and loads the updated configuration.
How does the connector handle new Families sent by my supplier?
If a supplier sends a product that belongs to a new Family that does not yet exist in Akeneo PIM, the connector cannot sync it. SDM will block at the Classification step until the Family is added to the PIM and the configuration is re-synced.
Can I exclude specific attributes or attribute groups from the sync?
Yes. SDM admin users can exclude individual Attributes or Attribute Groups from the connector sync. To access this configuration:
- Open the workflow that has an Akeneo PIM Connector.
- Go to Settings (left navigation) > Akeneo PIM Connector > Attribute configuration tab.
- Select the Attributes or Attribute Groups to exclude, then click Synchronize to apply the changes.
Some Attributes cannot be excluded because they are required for SDM to function correctly β these display a warning icon (β οΈ):
- Identifier: Required for product identification (e.g., SKU)
- Variant Axis: Required for the variant product structure
- AI Source: Required for AI-powered features
- Dependency trigger: Required for dependency conditions
Product push
Can the connector push empty values to my PIM?
No. The Akeneo PIM Connector in SDM does not push empty values to Akeneo PIM. If a value is removed during the Normalization step, that Attribute is excluded from the update entirely β the existing value in PIM is preserved for that product.
Does the connector override existing product data in PIM?
Yes, with an important exception. The connector uses the mass-update and create endpoint, which means it overwrites existing Attribute values on a product when a new value is provided. However, empty SDM fields are never pushed, so they do not overwrite existing PIM data with blank values. Work with your Akeneo business consultant or integrator to confirm your validation rules before the first push.
Can I push my media URLs to an Akeneo media_link Attribute?
No. The media_link Attribute type is not currently supported by the Akeneo PIM Connector.
Attribute handling
Does SDM handle scopable Attributes?
Yes. For scopable Attributes in Akeneo PIM, SDM creates one version of the Attribute per targeted channel, appending the channel name: ${attribute_name}-${channel_name}.
For localizable Attributes, SDM creates one version per activated locale.
For Attributes that are both scopable and localizable, SDM creates one version for every channel/locale combination: ${attribute_name}-${channel_name}-${locale}.
When requirement levels differ across channels, SDM applies the highest requirement level across all channels for non-scopable Attributes.
What PIM Attribute types are not supported by the connector?
The following Akeneo PIM Attribute types are not supported:
-
pim_catalog_file(File upload) -
pim_catalog_product_link(Single Product Link)
For a full list of supported Attributes and their SDM equivalents, see PIM Attribute handling and limitations.
Can the connector populate Reference Entities?
Yes, the connector can update a Reference Entity value on a product. SDM models the Reference Entity as a select Attribute β only the record code and label are fetched from the Reference Entity, not the full record structure.
The connector syncs the catalog structure in read mode only. It cannot create or update Reference Entity attribute structures in Akeneo PIM from SDM.
Does the Akeneo PIM Connector handle Table Attributes?
Yes, with a workaround. SDM does not support PIM Table Attributes natively. Instead, the connector creates individual SDM Attributes for each cell in the table, following a naming convention such as attachments-row0-type. Your SDM integrator must configure the max_rows_per_table parameter to define the maximum number of rows. Contact your Akeneo business consultant or support contact at SDM to set this up.
See PIM Attribute handling and limitations for full details.
Does SDM support the pim_catalog_identifier Attribute?
Yes. The identifier Attribute is supported and set up as a simple string field with uniqueness rules. If the use_uuid_push option is enabled in the connector configuration, SDM uses the UUID endpoint (/api/rest/v1/products-uuid) instead of the standard identifier endpoint. See What you need to know before using the connector for details on push identifier options.