The complete guide to connect Akeneo PIM to your online translation solution

#Known limits

#Only text attributes

Our suggested method allows your online translation solution to translate only textual attributes of Akeneo PIM products.

Among other PIM attributes, Akeneo PIM has a file attribute type that allows handling a binary file (CSV, DOC, DOCX, MP3 or PDF) associated with the product.

A possible improvement of your App could be also to take into account some of these files in order to translate them.

#Assets and Reference Entities

In the Akeneo PIM attribute type list, some specific attributes are used to associate data structures with PIM products. They also contain attributes that can be translated:


Let's talk about PIM assets first.

An asset can contain a media (an image, a video or a file) and can also contain some metadata.

It would be interesting to offer Julia to translate these metadata asset attributes and why not... some media.

You need to know that PIM assets can be used in 2 different ways with Akeneo PIM:

  • either by associating the PIM with a DAM solution: assets then come from this external solution,
  • or by creating these assets directly in the PIM.

In the first case, assets are usually translated directly in the DAM software. As a result, Julia doesn't need to translate her PIM assets because it has already been done by the DAM teams.

In the second case, it makes more sense: like products, the metadata of the assets may have originally been created in a source locale and Julia might want to translate them into other locales.

The main problem is that with the method we suggested, Julia can only indicate products that are to be translated (and not assets).

This is due to the fact that bulk actions aren't available on assets for now.

A workaround would be to manage the translation of asset metadata as you manage the single or multiselect attribute options.

By retrieving Julia's PIM products, you could also retrieve the information from the associated assets via asset collection attributes.

Moreover, since a given asset can be used for several products, it could lead to the translation of assets that have already been translated.

#Reference entities

Reference entity records also have localizable attributes and your App, just like for assets, could be legitimate to offer an associated translation service to Julia.

But for the same reasons as for assets, there is no bulk actions for reference entities / reference entity records.

You can therefore use the same workaround as for assets by translating all reference entities record related to the products Julia will indicate.