Goal

Thanks to the application, you can:

• import assets from a Bynder environment to an Akeneo PIM, and get the Bynder metadata
• import data from Akeneo to Bynder.metadata
• link a same asset to many products or product models (using the skus or codes)

The data exchanges use the API of both applications.

In the configuration of the application, you can set some filters to create assets in the right Akeneo asset family. the configuration will be used and send each asset in the corresponding asset family.

The link between the asset and the product can be created thanks to the Akeneo native “Product link rule” feature. With the application you can easily connect a same asset to many products/product models.

Automatically import visuals

The assets in the PIM will be created using only URLs and the binary will be left on Bynder side.

Thanks to this:

• We will display the product images in the PIM product list and product page.

• We will send to the channels the information and the binaries will be still on Bynder CDN.

• You can use the Akeneo Product Link Rules to automatically link an asset to a product : Documentation of the Product Link Rules

More information can be found : here

Asset for many products

If you want to assign a same asset to many different products but the Akeneo native feature is not enough for you, you can use the « Multiple Products Association » feature of the App.

It’s simple :

• In Bynder, fill a metadata with the SKUs you want to associate to your asset
• Let the App link the asset to theses products using the metadata information.

If you need more information, look at this web page : here

Automatically fill Bynder metadata

To enrich the filters into Bynder, you can use the application and configure it so your assets in Bynder will have some information from Akeneo.

You will have the possibility to create new filters into Bynder.

Features

The connector can be used for many purposes.

You can see below the main features.

FROM AKENEO TO BYNDER

Feature: Send Product IDs to Bynder

Objective : to be able to select values from Akeneo data (product data master)

How to : Send SKUs, Product Model Codes or other product information from Akeneo to a Bynder meta property which can be used in Bynder

Characteristic :

• It is possible to filter products or product models so as not to send all the data but only the desired ones
• This uses external references for Bynder which allows special characters not to be transformed
• This allows the use of a Multi Select in Bynder with auto completion.

FROM BYNDER TO AKENEO

Feature : Send assets to Akeneo

Objective : Create or update assets in Akeneo

How to : Send assets created or modified since the last processing.

Characteristic :

It is possible to filter the desired assets based on the meta properties entered in Bynder.

• It is possible to choose in which asset family each asset is sent based on the meta properties entered in Bynder.
• It is possible to retrieve and send to Akeneo the information of the meta properties.
• It is possible to use Regex for filters and also to extract data from meta properties (useful when you want to get data from filename for example).
• This treatment can be launched in partial mode (since the last success) or total (no date filter)
• This only handles URLs and not binaries to use Bynder's CDN

Feature : Automatic asset link

Objective : Automatically link an asset to one or more products.

How to : Use information contained in Akeneo assets to link them to products.

Characteristic :

• It is possible to link an asset to several products, or several assets to a product
• It is possible to manage the localization or channel for the link with the product (be careful, a scoped or localized Asset collection attribute cannot currently be used as the main media of a product. This is a limitation on the Akeneo side).
• It is possible to manage an automatic order
• It is possible to link an asset only if no other asset is already present
• It is possible to remove a link if the asset is no longer attached to the product
• It is possible to use a product attribute instead of the identifier to manage the automatic link search (example: make a link based on the brand)
• It is possible to filter products to avoid making a link (functionality linked to the previous functionality)
• It is possible to put a default value on the products (this allows to tag the updated products)
• Processing can be launched completely (all assets are processed) or partially (only updates since the last successful launch)

Feature: Send data from Akeneo to Bynder

Objective : Update Bynder with product information (and have more comprehensive filters in Bynder)

How to : Use information in asset-related products

Characteristic :

• It is possible to choose a product attribute, a locale, a channel and send the information to Bynder
• It is possible to choose whether multiple data should be concatenated or whether we only keep the last value

Feature : Send data to reference entities

Objective : Send a URL to a ref entity record

Characteristics :

• It is necessary to indicate the destination entity reference, the asset filtering conditions
• It is also possible to send, in addition to the URL, metadata to the records.

Feature: Delete assets

Objective : Remove assets from Akeneo if they are no longer present in Bynder or if they meet certain criteria.

Characteristics :

• It is possible to create a mapping by Akeneo asset family
• It is possible to indicate conditions (example delete Akeneo assets if they are tagged as Archived in Bynder)

CONFIGURATION

Feature: Connection management

Goal: To be able to easily configure the same connection for multiple jobs

How: a space centralizes all connections and their settings

Characteristics :

• It is possible to create, modify, delete a connection
• It is possible to test a connection and update it if necessary

Known limitations

Due to the Akeneo’s cache system and the Bynder URLs not modified when the asset is modified, if a new version of an asset is updated in Bynder, in Akeneo, the thumbnail will not be updated.

If an asset is updated, the thumbnail in the PIM is not updated.

Performance

Between 75 and 100 assets updated / minute