> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/ecommerce/akeneo/faq.md).

# FAQ

<details>

<summary>What credentials do I need to connect Akeneo to Coupler.io?</summary>

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.

</details>

<details>

<summary>Can I export product variants from Akeneo?</summary>

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.

</details>

<details>

<summary>Why are product attribute values showing as nested or complex data?</summary>

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.

</details>

<details>

<summary>How do Families relate to Attributes in Coupler.io?</summary>

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.

</details>

<details>

<summary>Can I pull data from multiple Akeneo instances into one destination?</summary>

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.

</details>

<details>

<summary>Can I send Akeneo product data to an AI tool like ChatGPT or Claude?</summary>

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.

</details>

<details>

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

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.

</details>

{% hint style="info" %}
For a full breakdown of what each Akeneo entity contains, see the [Data Overview](/sources/category/ecommerce/akeneo/data-overview.md) article. If you're hitting API errors or missing records, check the [Common Issues](/sources/category/ecommerce/akeneo/common-issues.md) article.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/ecommerce/akeneo/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.