Create Options in Bynder
Feature availability: This feature is available in the job: Bynder x Akeneo - Create Bynder options from Akeneo product data (Bynder Akeneo Connector)
This job automatically creates and updates meta-property options in Bynder using data from Akeneo. Source data can include product and product model identifiers, as well as values from other Akeneo attributes.
Note: Only values attached to products are sent to Bynder, preventing unnecessary data transfer.
General Information
The configuration is split by product level to reflect Akeneo's catalog structure.
| Level | Akeneo equivalent | Technical definition |
|---|---|---|
| Product Model (Top level) | "Common" tab | Product Model without a parent |
| Product Model (Middle level) | "Middle" tab (when applicable) | Product Model with a parent |
| Product Variant | "Product" (in a family variant) | Product with a parent |
| Simple Product | "Product" (standalone) | Product without a parent |
Sending Product Identifiers
To include product identifiers, enable the "Send Product Identifier" option. Additional fields will appear:
| Field | Description |
|---|---|
| Label attribute – Code | Code of the attribute to use as the product label (typically the product title) |
| Label attribute – Channel | Channel code to use if the attribute is scopable |
| Label attribute – Locales | Locale codes to send to Bynder |
| Bynder property | Target meta-property in Bynder |
Tip: You can prefix the product label with its identifier in brackets by enabling "Prefix the label with the product identifier".
Filters
By default, the job processes all Akeneo products and product models. You can restrict this scope using filters.
⚠️ Filters must follow the Akeneo API format.
→ See the Akeneo filter documentation for syntax and available filter options.
Fallback Locales
If a translation is missing for a given locale, the connector can fall back to an alternative locale value.
For each locale, define which other locale should be used as a fallback when no value is available.
In the example above, if no fr_FR value exists for an attribute, the connector will use the en_US value instead.
Other Attributes
In addition to product identifiers and product model codes, you can send values from Select or Reference Entity attributes.
For each attribute mapping, configure the following:
| Field | Description |
|---|---|
| Attribute code | Code of the Akeneo attribute to send |
| Channel | Required if the attribute is scopable |
| Locale | Required if the attribute is localizable |
| Default label locale | Locale used for the default Bynder value |
| Reference entity attribute | Optional — lets you send a specific attribute value instead of the reference entity label |
| Bynder property | Target meta-property in Bynder |
Once the configuration is complete, launch the job to initialize your Bynder meta-property options.