# akeneo/module-magento2-connector-community

> Akeneo Connector for Adobe Commerce

`composer require akeneo/module-magento2-connector-community`

Canonical URL: https://packagento.com/akeneo/module-magento2-connector-community

## At a glance

- **Vendor**: akeneo (https://packagento.com/akeneo.md)
- **Latest version**: 105.1.2 — released 2025-12-09
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/akeneo/module-magento2-connector-community and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require akeneo/module-magento2-connector-community:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

Akeneo Connector for Adobe Commerce

## README

Akeneo Connector for Adobe Commerce/Magento is a module that allows you to export your catalog data and structure from Akeneo PIM to Adobe Commerce/Magento through API calls. This version of the connector is designed to work with Akeneo PIM Community Edition. It could either work with Magento Open Source or Adobe Commerce.

You can discover Akeneo Connector on the [Akeneo Marketplace](https://marketplace.akeneo.com/extension/akeneo-connector-magento-2-community-edition) or on the [Magento Marketplace](https://marketplace.magento.com/akeneo-module-magento2-connector-community.html).

#### Documentation:

Akeneo Connector complete documentation is available [here](https://help.akeneo.com/magento2-connector/v100/).

Akeneo API complete documentation is available [here](https://api.akeneo.com/).

#### How to download and install the connector:

Akeneo Connector install guide is available [here](https://help.akeneo.com/magento2-connector/v100/articles/download-connector.html).

#### Features:

With Akeneo Connector for Adobe Commerce/Magento, you can import:
* Categories
* Families
* Attributes
* Options
* Product Model
* Family Variant
* Products

#### Compatibility

| Magento / Adobe Commerce | PHP     | Akeneo Connector | Maintained     |
|--------------------------|---------|------------------|----------------|
| \>= 2.3.7 && < 2.4.4     | \>= 7.4 | 103.X.X          | EOL            |
| \>= 2.4.4 && < 2.4.7     | \>= 8.0 | 104.X.X          | Bug fixes only |
| \>= 2.4.7                | \>= 8.2 | 105.X.X          | Current        |

The [akeneo/api-php-client](https://github.com/akeneo/api-php-client) requires [psr/http-message](https://github.com/php-fig/http-message) >= 2.0.

For any issue with the *psr/http-message* package, use Akeneo Connector 104.X.X.

#### Requirements:

* Akeneo PIM >= 3.2 (CE & EE) | Akeneo EE features are not included in this version of the Connector
* Magento Open Source and Adobe Commerce >= 2.3.7
* Database encoding must be UTF-8

#### Migration:

If you want to migrate from previous PIMGento 2 connectors, please follow our [migration guides](https://help.akeneo.com/magento2-connector/v100/articles/upgrade-connector.html).

#### About us

Our team has been working in the e-commerce industry for over 10 years. As we were helping brands to grow their online businesses, we realized that they were all struggling with complex or archaic systems to manage product information.

We founded Akeneo in 2013 with the idea that products are the most important assets in a company and that many merchants lack a tool to help them manage and leverage this crucial asset. Merchants needed a tool that was designed for marketers and flexible enough to be integrated with any third-party application.

Akeneo PIM integrates with Adobe Commerce/Magento platform via a powerful Connector historically built by its Gold Solution Partner, Agence Dn'D, a true expert in implementing the joint solution.

Akeneo and Adobe Commerce/Magento solutions are a logical fit as they are both Open Source, share the same technology stack, and count many joint customers benefiting from the combined value proposition.

Akeneo now partners with Agence Dn'D on Akeneo Connector for Adobe Commerce/Magento, to provide the best customer experience to Magento Open Source or Adobe Commerce merchants looking for a compelling product experience that will improve their revenue.

#### About Agence Dn'D

Founded by lovers of innovation and design, [Agence Dn'D](https://www.dnd.fr) assists companies in the creation and development of customized digital (open source) solutions for web and E-commerce since 2004.

## Changelog

#### Version 100.1.0 :
* Initial Akeneo Connector Release

#### Version 100.1.1 :
* Fix attribute mapping key

#### Version 100.2.1 :
* Add website mapping from select or multiselect attribute in Akeneo
* Use native Magento serializer
* Fix proxy class injection in command construct
* Fix association import when result is empty
* Fix url_key mapping and generation

#### Version 100.2.2 :
* Fix issue when importing associations
* Improve attribute option import

#### Version 100.2.3 :
* Fix identifier column type in temporary product import table
* Fix missing where statement on delete in website association feature
* Fix product website request if attribute is not filled in Akeneo
* Fix duplicate node in config.xml file
* Add check on family label to prevent import error on duplicate labels in Akeneo

#### Version 100.2.4 :
* Fix import command description
* Convert uppercase attribute mapping to lowercase
* Set import job response after step finish events

#### Version 100.2.5 :
* Improve configurable attributes feature with specific types

**Warning :** *After updating connector to this version, please check the `Configurable` configuration under the `Products` section in the Akeneo Connector configuration and update the `Type` column of your mapping with the appropriate value if necessary.*

#### Version 100.2.6 :
* Add check to prevent the creation of attributes and options with empty admin label
* Fix product association deletion with differential product import

#### Version 100.3.0 :
* Remove Akeneo attribute group import from connector (https://help.akeneo.com/magento2-connector/v100/articles/where-attributes.html#where-to-find-my-attribute-groups-in-magento-2)
* Remove automatic mapping for attributes "price", "special_price" and "cost" (https://help.akeneo.com/magento2-connector/v100/articles/what-data.html#attribute-types)
* Add metric as product variant and unit concatenation feature (https://help.akeneo.com/magento2-connector/v100/articles/05-configure-products.html#metric-attributes)
* Update wording for configurable product attribute mapping

#### Version 100.3.1 :
* Fix product image name that should not exceed 90 characters since Magento 2.3.3

**Warning :** *After updating connector to this version, all image names will be renamed. To know more, please consult documentation (https://help.akeneo.com/magento2-connector/v100/articles/06-import-images-configuration.html)*

* Remove unused "file" column on log grid
* Move API client call from construct
* Fix category URL issue adding -1, -2 to url-key when category had same name but not same parent category

#### Version 100.3.2 :
* Fix Object Manager usage
* Fix category URL request missing "parent_id" select

#### Version 100.3.3 :
* Fix error on price attribute import
* Fix category attribute set getter to prevent mixed id in case of data migration
* Fix metric import when metric attribute code contains uppercase characters
* Add product model batch size and request size to prevent MYSQL errors (https://help.akeneo.com/magento2-connector/v100/articles/05-configure-products.html#product-model-batch-size-and-product-model-update-length)

#### Version 100.3.4 :
* Fix product URL rewrite generation to prevent duplicate entry errors
* Fix product URL generation for configurable product in case of mapping with url_key

#### Version 100.4.0 :
* Add automatic mapping for existing attributes, attribute options and products in Magento (https://help.akeneo.com/magento2-connector/v100/articles/existing-magento.html)
* Add entities check in connector entities table before import

#### Version 100.4.2 :
* Add support for file attributes import (https://help.akeneo.com/magento2-connector/v100/articles/05-configure-products.html#import-file-attributes)
* Add feature to apply default status to new products (https://help.akeneo.com/magento2-connector/v100/articles/05-configure-products.html#default-product-status)

_(Changelog truncated for .md surface. Full history on https://packagento.com/akeneo/module-magento2-connector-community.)_

## Recent Versions

| Version | Released |
|---|---|
| 105.1.2 | 2025-12-09 |
| 105.1.1 | 2025-12-09 |
| 105.1.0 | 2025-05-27 |
| 104.3.18 | 2025-04-10 |
| 105.0.1 | 2025-04-09 |
| 104.3.17 | 2024-12-17 |
| 104.3.16 | 2024-10-24 |
| 104.3.15 | 2024-10-24 |
| 104.3.14 | 2024-09-25 |
| 104.3.13 | 2024-09-18 |

Showing 10 of 120 versions. Full release history on https://packagento.com/akeneo/module-magento2-connector-community.

## Dependencies

### Require

| Package | Constraint |
|---|---|
| akeneo/api-php-client | 11.4.0 |
| http-interop/http-factory-guzzle | ^1.0 |
| magento/framework | >=102.0.0 |
| magento/module-backend | >=100.0.1 |
| magento/module-catalog | >=100.0.1 |
| magento/module-eav | >=100.0.1 |
| magento/module-store | >=100.0.1 |
| nyholm/psr7 | ^1.5 |
| php | >=8.0 |
| symfony/http-client | ^5\|^6\|^7 |

## Quality

Latest release (105.1.2) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Pass | Pass | – | – |
| 2.4.8 | – | Pass | not tested | – |
| 2.4.9 | – | – | not tested | not tested |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Warning | 318 | 318 warnings (ruleset: Magento2) — 156 auto-fixable with phpcbf |
| PHPMD | Warning | 130 | 130 rule violations (CyclomaticComplexity:25, NPathComplexity:25, ExcessiveMethodLength:22, UnusedLocalVariable:16, ExcessiveClassComplexity:9) |
| Cpd | Pass | 0 |  |
| Composer validate | Info | 7 | valid; 7 advisory notes (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | 177 | 177 | – | – |
| 2.4.8 | – | 182 | 182 | – |
| 2.4.9 | – | – | 183 | 183 |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | Pass | 0 |  |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["akeneo/module-magento2-connector-community"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

akeneo is a Magento 2 vendor on Packagento. See https://packagento.com/akeneo.md for their full catalogue.