MAGENTO INTEGRATION
Magento Akeneo Integration: Connectors, Cost and Timeline
Akeneo holds the product data and pushes it into Magento. Akeneo's own connector is free for Community users and quote-based for Enterprise. The work is mapping families, variants, channels and prices.
✦ WHAT SYNCS
What moves between Akeneo PIM and Magento.
| DATA | DIRECTION | NOTES |
|---|---|---|
| Categories | Into Magento | Akeneo's Community connector listing names categories among what it imports. The feature coverage page maps the Adobe Commerce Root Category to Akeneo's main category tree and says the connector imports all PIM category trees, depending on your category configuration (https://help.akeneo.com/en_US/connector-overview/adobe-commerce-connector-feature-coverage). |
| Families, attributes and options | Into Magento | Akeneo's feature coverage page (https://help.akeneo.com/en_US/connector-overview/adobe-commerce-connector-feature-coverage) describes how attribute types convert: text, number and identifier attributes become text fields, simple select and Yes/No become drop-downs, and image and asset collections become media images. Attributes and options without a label in the admin store language are not imported. |
| Product models and variants | Into Magento | Per Akeneo's feature coverage page (https://help.akeneo.com/en_US/connector-overview/adobe-commerce-connector-feature-coverage), product models map to configurable products, and simple products and variants map to simple products. Grouped and virtual products are supported. Downloadable products and gift cards are not. Multi-select attributes are listed as not supported as variation axes. |
| Products | Into Magento | The connector fetches data from the Akeneo API and inserts it directly into the Adobe Commerce database (Akeneo App Store). Price, special_price and cost are not imported by default and must be mapped manually, with global or website scope only. |
| Images and assets | Into Magento | Images, videos and PDFs are supported. Asset features are Enterprise Edition only, and the connector imports image asset binaries and image asset links. |
| Locales and channels | Into Magento | Per the feature coverage page (https://help.akeneo.com/en_US/connector-overview/adobe-commerce-connector-feature-coverage), locales map to Adobe Commerce store views and channels map to websites. A scopable value only loads if the product belongs to the channel's category tree. |
✦ THE API
The Akeneo PIM API.
| ASPECT | DETAIL |
|---|---|
| API type | Akeneo REST API v1 at /api/rest/v1 on your PIM host. Akeneo says v1 is the first and only version, and JSON is the only supported format. |
| Authentication | Create a connection in the PIM to get a client ID and secret and an API username and password, then request a token with a password grant on the OAuth token endpoint. Access tokens last 1 hour by default and refresh tokens 14 days. |
| Rate limits | Akeneo's REST API basics page does not state rate limits. Confirm limits for your edition with Akeneo. |
| Documentation | Akeneo PIM API docs (opens in a new tab) |
✦ CONNECTOR OPTIONS
Connector options.
| NAME | TYPE | NOTES | LINK |
|---|---|---|---|
| Akeneo Connector for Adobe Commerce (Community) | Native | Free on the Akeneo App Store. Imports categories, families, attributes, options, products and product models from Akeneo to Adobe Commerce, and only Community Edition features of Akeneo are supported. The listing shows versions 2.3.0 to 2.3.5, 2.4.0, 2.4.1 and 2.4.3 to 2.4.9. Packagist shows connector 105.1.2 (published December 9, 2025), which needs Adobe Commerce 2.4.7 or higher and PHP 8.2 or higher. Akeneo's compatibility page (https://help.akeneo.com/en_US/connector-overview/adobe-commerce-connector-compatibility-and-pre-requisites) says the Community connector has no support available, and that it works with Akeneo Community and Enterprise PIMs without the Enterprise features. | Vendor page (opens in a new tab) |
| Akeneo Connector for Adobe Commerce (Enterprise) | Native | Quote based. Adds assets and reference entities, which Akeneo marks as Enterprise Edition exclusive. The listing shows versions 2.4.0 to 2.4.9 and connector versions 105.15.0 and 104.18.0. Akeneo's compatibility page says 105.X.X needs Adobe Commerce 2.4.7 or higher and PHP 8.2 or higher, and 104.X.X is in maintenance-only mode. Enterprise users get corrective maintenance from their usual Akeneo Support contacts. | Vendor page (opens in a new tab) |
| Induxx Adobe Commerce Connector | iPaaS | Quote based, listed on the Akeneo App Store. Middleware that retrieves product data from Akeneo and publishes it to Adobe Commerce, with no server setup and no Magento-side plugins. Covers simple and configurable products, attributes and media, as a product-only sync or a full catalog export. The listing names no Magento version. | Vendor page (opens in a new tab) |
| Webkul Akeneo Connector | Extension | $299.00 on the Webkul store page (regular price $399.00), with optional add-ons: module installation +$59.80, Akeneo installation +$300.00, cron setup +$100.00. Exports products, categories and attributes from Akeneo to Magento, and the page says it can also import catalog data from Magento to Akeneo. Jobs run on cron or manually, with time-based filtering. Lists versions 2.4.x and Akeneo 7.x; bundle and grouped products need a separate add-on. | Vendor page (opens in a new tab) |
| Custom build (Akeneo REST and Magento REST) | Custom | A direct build on the Akeneo REST API. It covers what the connector does not: Akeneo's feature coverage page (https://help.akeneo.com/en_US/connector-overview/adobe-commerce-connector-feature-coverage) lists downloadable products and gift cards as unsupported and transformation as "No" in its connector capabilities table, while the overview (https://help.akeneo.com/magento2-connector/articles/trigger.html) lists transformation among the connector's jobs, so confirm with Akeneo what is covered. | Vendor page (opens in a new tab) |
✦ COST AND TIMELINE
Cost and timeline.
| LEVEL | SCOPE | TYPICAL RANGE | TIMELINE |
|---|---|---|---|
| Level 1 | Connector set up and configured | $3,000-8,000 | 2-4 weeks |
| Level 2 (this integration) | Custom API integration (orders, inventory, customers) | $10,000-25,000 | 4-8 weeks |
| Level 3 | Complex ERP sync (B2B pricing, multiple warehouses, middleware) | $25,000-75,000+ | 8-16 weeks |
Typical range, quoted after a scoping call.
An Akeneo catalog import is level 2. Families, attributes, variants, channels and prices have to be mapped per catalog, and Akeneo's overview (https://help.akeneo.com/magento2-connector/articles/trigger.html) puts maintenance and customizations with the integrator and offers Akeneo support for the core connector. Asset handling, many locales and custom product types raise the effort. Licenses are the small part of the bill: the Community connector is free, Webkul's is $299 and Enterprise and Induxx are quote based.
✦ WHERE THESE PROJECTS GO WRONG
Where these projects go wrong.
- Prices. Price, special_price and cost are not imported by default, and only global or website-scoped price attributes work, not store view prices.
- Variants. Product models become configurable products, and multi-select attributes cannot be variation axes. Test every family's variants before the first full import.
- Locales and channels. Locales map to store views and channels to websites. Attributes without a label in the admin store language are not imported.
- Unsupported types. Downloadable products and gift cards are not supported, and Akeneo's own tables disagree on bundles. Check them against your catalog.
- Deletions. Adobe Commerce stays master for deletions: removing a product in the PIM does not delete it in the store.
- Version lock. Connector 105.X.X needs Adobe Commerce 2.4.7 or higher and PHP 8.2 or higher. Older stores are on the 104.X.X branch, which gets bug fixes only.
✦ QUESTIONS MERCHANTS ASK
Akeneo PIM integration FAQ.
Is there an official Akeneo connector for Magento?+–
Yes. Akeneo publishes the Akeneo Connector for Adobe Commerce in two editions. The Community connector is free, supports Community Edition features only, and Akeneo's compatibility page says it has no support available. The Enterprise connector is quote based, adds assets and reference entities, and comes with support from Akeneo.
What does the connector import, and which way does data move?+–
From Akeneo to the store. Akeneo's feature coverage page describes importing PIM data into Adobe Commerce and says the store stays master on deletion. It imports categories, families, attributes, options, products and product models. Orders and stock are not on the list.
Which Magento and Akeneo versions are supported?+–
Connector 105.X.X needs Adobe Commerce 2.4.7 or higher and PHP 8.2 or higher. Connector 104.X.X covers 2.4.4 to below 2.4.7 on PHP 8.0 or higher and gets bug fixes only. Packagist lists Akeneo PIM 3.2 or higher for the Community connector. Webkul lists versions 2.4.x and Akeneo 7.x.
How often does it sync?+–
Akeneo's feature coverage page lists scheduled synchronization alongside full, delta and manual sync, with logs and monitoring, and the prerequisites ask you to confirm Magento cron jobs run as scheduled. It gives no fixed interval. Webkul runs jobs on cron or manually and sells cron setup as a $100 add-on.
Does the connector sync prices?+–
Not by default. Price, special_price and cost must be mapped manually, and only global or website-scoped price attributes work.
Do I need a custom build?+–
Not always. Use the free connector for a standard catalog. Akeneo's feature coverage page lists downloadable products and gift cards as unsupported, and transformation as "No" in its capabilities table. Catalogs that need them call for custom work or a paid connector.
✦ KEEP EXPLORING
Related integrations.
Magento Amazon Integration: Connectors, Cost and Timeline
Amazon rations how fast you can pull orders: getOrders is documented at 0.0167 requests per second with a burst of 20. Whether you buy an extension or build on the Selling Partner API, the integration has to work around those token buckets with notifications and feeds instead of polling.
Magento POS Integration: Connectors, Cost and Timeline
A POS integration is really a decision about who owns stock. Lightspeed, Square, Clover and Shopify POS each expose a different API with different limits, so the sync you build depends on which one is at your counter.
Magento Salesforce Integration: Connectors, Cost and Timeline
This page covers connecting Magento to Salesforce CRM, so sales and service teams see customers, orders and abandoned carts. Salesforce Commerce Cloud is a different product. Salesforce describes it as a platform for ecommerce, POS and order management, which makes it an alternative to Magento, not a link to it.
SOURCES
- Akeneo API: REST API basics (opens in a new tab)
- Akeneo API: Authentication (opens in a new tab)
- Akeneo App Store: Connector for Adobe Commerce (Community) (opens in a new tab)
- Akeneo App Store: Connector for Adobe Commerce (Enterprise) (opens in a new tab)
- Akeneo App Store: Adobe Commerce Connector by Induxx (opens in a new tab)
- Akeneo help center: What is the Akeneo connector for Adobe Commerce (opens in a new tab)
- Akeneo help center: Compatibility and prerequisites (opens in a new tab)
- Akeneo help center: Feature coverage (opens in a new tab)
- Packagist: akeneo/module-magento2-connector-community (opens in a new tab)
- Webkul: Akeneo Connector for Magento (opens in a new tab)