Magento API connector

On the configuration page you have two tabs, which are:

• Configuration

• Linked export profiles

Tab 1: configuration

The configuration tab contains settings for mapping product values, images, associations and attributes.

Attribute mappings

A → B mapping

Here you can remap product values ​​from attribute a to attribute b. Before you can start exporting, a number of ‘mappings’ are necessary. Mapping for the fields ‘sku, name, akeneo_status, visibility, weight & tax_class_id’ are hereby required (these are not removable). If no mapping is provided for these field, the connector will use standards. Other reserved attribute codes are: quantity_and_stock_status, category_ids, tier_price, price_view, gift_message_available, type_id. These cannot be mapped.

Special A → B mappings

Different values for configurable and simple products:
The mapping configuration allows you to map two different Akeneo attributes to one Magento attribute. This way it is possible to provide a different Magento value for configurable and simple products. You do this by adding a pipeline between the Akeneo attributes. Once a pipeline was added, the first attribute will be used for configurable products and the second one for the simples.

Range attributes:
Induxx has provided a new attribute type ‘range’. On this attribute three values will be stored. Min, max and increment. For this attribute it is possible to link these 3 values from one Akeneo attribute to three different Magento attributes. You do this by using a slash (/).

Reserved A → B mapping attributes

A few attribute codes are reserved for the connector. Because of this you cannot add these manually. Attribute(s) that are reserved:

• sku

• name

• weight

• visibility

• tax_class_id

• quantity_and_stock_status

• category_ids

• tier_price

• price_view

• gift_message_available

• akeneo_status

A → B mapping stock item attributes

It is also possible to add mapping on the product stock item attributes. A list of these attributes can be found here:

• qty

• is_in_stock

• is_qty_decimal

• use_config_min_qty

• min_qty

• use_config_min_sale_qty

• min_sale_qty

• use_config_max_sale_qty

• max_sale_qty

• use_config_backorders

• backorders

• use_config_notify_stock_qty

• notify_stock_qty

• use_config_qty_increments

• qty_increments

• use_config_enable_qty_inc

• enable_qty_increments

• use_config_manage_stock

• manage_stock

• low_stock_date

• is_decimal_divided

• stock_status_changed_auto
  
  

Association mapping

Here you can map Akeneo association codes on the existing Magento association types. You can choose which associations to use for cross-sell, upsell and related products.

Other settings

Except these mappings, a few other important settings are required. These are:

• A comma separated list of attribute codes you want to export to Magento. This list will be used for attribute and product value exporting. Don’t forget to add at least all the variant axe attributes here.

• A comma separated list of image attribute codes. This list will be used to export images to the image gallery. You can decide on each family which image you want to use as the main image in Magento -> ‘family attribute used as image’.

Save configuration

Since the grid quick export jobs are not configurable through the Akeneo’s export user interface, the existence of these jobs will be checked when saving this configuration. If the quick export job magento_api_quick_product_export does not exist, it will be created. The same logic will be applied for the magento_api_quick_export and magento_csv_open_queue jobs.

Tab 2: linked export jobs

On the second tab we find the linked export profiles. Each export profile can be linked once. The following export types are supported:

• magento export

• magento image export

• magento queue

All the current configuration settings will be applied to these export jobs.