Akeneo

Akeneo is a Product Information Management (PIM) platform that centralizes and enriches your product catalog data. It organizes everything from product attributes and families to channels and locales, making it the single source of truth for your product content.

Connecting Akeneo to Coupler.io lets you pull that catalog data into your reporting and analytics tools without writing a single line of code. Here's what you get:

• Full catalog visibility — export products, categories, families, attributes, and more into spreadsheets or data warehouses

• Multi-channel analysis — see which products are published to which channels and locales

• Automated refreshes — keep your reports up to date on a schedule you control

• AI-ready data — send catalog data to ChatGPT, Claude, Gemini, or other AI destinations for content generation or analysis

Prerequisites

Before connecting, make sure you have:

• An active Akeneo account (any edition including Community)

• Your Akeneo instance URL (e.g., https://yourstore.cloud.akeneo.com)

• A client ID, client secret, username, and password from an Akeneo API connection with sufficient read permissions

To create API credentials in Akeneo, go to System → API connections and create a new connection. Make sure the connection role has read access to the entities you want to export.

Quick start

Start with the Products entity — it's the most data-rich and will immediately show you whether your credentials and instance URL are set up correctly.

1

Create a new data flow in Coupler.io. Log in to Coupler.io, go to the Data Flows section, and click Add data flow. Search for Akeneo and select it as your source.

2

Enter your Akeneo API credentials. You'll be asked for your Akeneo instance URL, client ID, client secret, username, and password. These come from your Akeneo API connection under System → API connections.

3

Select the entity you want to export. Choose from Products, Categories, Families, Attributes, Channels, and more. You can add multiple sources to the same data flow to pull several entities at once.

4

Choose your destination. Pick where you want the data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.

5

Run the data flow. Click Run to trigger a manual sync. Once it completes successfully, your Akeneo data will appear in the destination you chose.

Available entities

Entity	What it contains
Products	Full product records with attributes, descriptions, images, and metadata
Categories	Category tree structure and hierarchy
Families	Attribute groups that define shared product structure
Family variants	Variant axes like size, color, or model within a family
Attributes	Individual data fields describing product characteristics
Attribute groups	Organized collections of related attributes
Association types	Cross-sell, up-sell, and substitution relationship definitions
Channels	Distribution channels such as web, mobile, or marketplace
Locales	Language and regional settings per market
Currencies	Pricing currencies across markets and channels
Measure families	Units of measurement (weight, length, volume, etc.)

Akeneo data overview

Akeneo exposes a rich set of catalog management entities through its API. In Coupler.io, each entity is available as a separate source you can add to a data flow — either individually or combined using Join, Append, or Aggregate transformations.

Entities at a glance

Entity	Best used for
Products	Catalog exports, content audits, channel readiness checks
Categories	Category tree analysis, hierarchy mapping
Families	Understanding product structure and completeness rules
Family variants	Variant management, size/color/model breakdowns
Attributes	Attribute audits, PIM governance reporting
Attribute groups	Grouping and display order analysis
Association types	Mapping cross-sell and up-sell relationships
Channels	Channel coverage and publishing scope
Locales	Market and language coverage reporting
Currencies	Pricing scope by market
Measure families	Unit consistency checks across attributes

Products

Core product fields

Field	Description
identifier	Unique product SKU or code
family	The family this product belongs to
categories	List of categories the product is assigned to
enabled	Whether the product is active
created	Date the product record was created
updated	Date the product record was last modified
associations	Linked products (cross-sells, up-sells, substitutions)
values	All attribute values for this product (name, description, price, images, etc.)

Categories

Category fields

Field	Description
code	Unique category identifier
parent	Parent category code (null for root)
labels	Localized category labels by locale

Families and family variants

Family fields

Field	Description
code	Unique family identifier
attributes	List of attributes belonging to this family
attribute_as_label	Which attribute is used as the product label
attribute_as_image	Which attribute is used as the main image
labels	Localized family names

Family variant fields

Field	Description
code	Unique variant identifier
family	Parent family code
variant_attribute_sets	Axes and attributes at each variant level
labels	Localized variant labels

Attributes and attribute groups

Attribute fields

Field	Description
code	Unique attribute identifier
type	Data type (text, number, boolean, image, price, etc.)
group	Attribute group this attribute belongs to
localizable	Whether the value varies by locale
scopable	Whether the value varies by channel
labels	Localized attribute names

Channels, locales, and currencies

Channel fields

Field	Description
code	Unique channel identifier
currencies	Currencies enabled for this channel
locales	Locales enabled for this channel
category_tree	Root category used by this channel

Common entity combinations

• Products + Families — Join on family code to enrich product records with family-level attribute rules

• Products + Categories — Join on category codes to build a full hierarchy view of your catalog

• Attributes + Attribute groups — Join to produce a complete attribute map with grouping context

• Channels + Locales + Currencies — Join to document full market coverage per channel

• Products from multiple Akeneo instances — Use Append to combine catalogs from different environments (e.g., staging vs. production)

Use cases by role

Ecommerce managers

• Export the full product catalog to Google Sheets for content review and bulk editing planning

• Track which products are enabled vs. disabled across categories

• Identify products missing key attributes before a channel launch

Data analysts

• Join Products with Families and Attributes in BigQuery to build a normalized product data model

• Aggregate product counts by category, family, or channel for catalog health dashboards in Looker Studio

• Use Append to compare catalog state across time by running periodic snapshots

Content teams

• Pull product values (descriptions, names, images) into Google Sheets for copywriting workflows

• Send product data to Claude or ChatGPT via an AI destination to generate or improve product descriptions at scale

• Filter by locale to review translated content completeness per market

Platform-specific notes

• Product values are returned as nested objects — each attribute value is keyed by attribute code, locale, and channel scope

• Localizable and scopable attributes will have multiple entries in values — one per locale/channel combination

• The associations field in Products contains arrays of associated product identifiers grouped by association type

• Akeneo Community Edition may have rate limits that affect large catalog exports — see the Common Issues article for guidance

• Family variants define the axes (e.g., color, size) but the actual variant product models are returned as part of the Products entity

Akeneo common issues

Connection issues

Invalid credentials or authentication failure

Akeneo uses a combination of client ID, client secret, username, and password — not just an API key. Double-check all four fields in your data flow settings. A single incorrect character will cause authentication to fail.

Also confirm that the API connection in Akeneo (System → API connections) is still active and hasn't been regenerated since you set up the data flow.

Instance URL not recognized

Make sure you're entering the full base URL of your Akeneo instance, including https://. For cloud instances it typically looks like https://yourstore.cloud.akeneo.com. Do not include a trailing slash or any path after the domain.

Missing data

Products are missing from the export

Akeneo only returns products the API connection's role has permission to read. Check the role assigned to your API connection under System → API connections → Edit and confirm it has read access to products and the relevant catalog scope.

Also note that disabled products are included in the API response by default — if you're seeing fewer records than expected, check whether filters are being applied upstream in Akeneo.

Attribute values are empty or null

Attribute values in Akeneo are locale- and channel-scoped. If an attribute is localizable or scopable, its value will only appear for the specific locale/channel combinations where it has been filled in. Missing values simply mean the field hasn't been populated in Akeneo for that scope — this is not a Coupler.io issue.

Family variants or categories return no records

If you haven't created any family variants or populated your category tree in Akeneo, these entities will return empty results. Verify the data exists in your Akeneo instance before troubleshooting the connection.

Permission errors

403 Forbidden when accessing certain entities

The API connection role in Akeneo controls access per entity type. If you can pull Products but not Channels or Locales, the role may be missing read permissions for those entities. Go to System → Roles in Akeneo, find the role tied to your API connection, and enable read access for the entities you need.

Data discrepancies

Product count in Coupler.io doesn't match Akeneo UI

The Akeneo UI may show counts that include product models (parent records for variants), while the API may return them separately or combined depending on your query. Check whether you need both the Products and Family variants entities to capture the full picture.

Also confirm that the API role's catalog scope isn't restricted to a subset of categories, which would reduce the visible product set.

Rate limits

Data flow times out or returns partial data on large catalogs

Akeneo's API enforces rate limits, especially on Community Edition instances. Very large catalogs (tens of thousands of products with many attribute values) can hit these limits during a full sync.

If you're experiencing timeouts, try splitting your data flow into multiple sources — for example, one flow for Products and a separate flow for Attributes and Families. This reduces the load per run.

Akeneo Cloud (Growth and Enterprise editions) generally have higher rate limits than self-hosted Community Edition instances.

Akeneo FAQ

What credentials do I need to connect Akeneo to Coupler.io?

You need four things: a client ID, client secret, username, and password from an Akeneo API connection, plus your Akeneo instance URL. Create the API connection in Akeneo under System → API connections. Make sure the role assigned to the connection has read access to the entities you want to export.

Can I export product variants from Akeneo?

Yes. Variant structure is defined through the Family variants entity, which describes the axes (e.g., size, color) and attribute sets at each variant level. The actual variant product records themselves are returned as part of the Products entity. Pull both entities and join them on the family code to get a complete picture.

Why are product attribute values showing as nested or complex data?

Akeneo stores attribute values in a structured format keyed by attribute code, locale, and channel scope. This means a single product can have dozens of value entries if it has many localizable or scopable attributes. This is normal Akeneo API behavior — you may want to use Coupler.io's Aggregate transformation or process the data further in your destination (e.g., BigQuery) to flatten it.

How do Families relate to Attributes in Coupler.io?

Families define which attributes a product should have and which are required for completeness. Attributes define the actual data fields. In Coupler.io, you can add both as sources in the same data flow and use the Join transformation on the attribute code to build a combined view showing each attribute alongside its parent family.

Can I pull data from multiple Akeneo instances into one destination?

Yes. Add each Akeneo instance as a separate source within the same data flow, then use the Append transformation to combine the records. This is useful if you run separate Akeneo environments for different regions, brands, or staging vs. production.

Can I send Akeneo product data to an AI tool like ChatGPT or Claude?

Absolutely. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Products export directly to one of these tools — for example, to generate product descriptions, translate content, or audit catalog completeness using a prompt.

Why does my product count in Coupler.io differ from what I see in the Akeneo UI?

This usually comes down to two things: the catalog scope of your API connection role (which may restrict access to certain categories) and how product models vs. simple products are counted. Check the role permissions in Akeneo and consider pulling both the Products and Family variants entities for a complete count.

For a full breakdown of what each Akeneo entity contains, see the Data Overview article. If you're hitting API errors or missing records, check the Common Issues article.