> 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/adobe-commerce-magento/faq.md).

# FAQ

<details>

<summary>Can I connect multiple Magento stores or store views to Coupler.io?</summary>

Yes. Each Magento store instance (with its own base URL) needs its own source in Coupler.io. You can then use the **Append** transformation to combine data from multiple stores into a single destination dataset. If you're working with store views within the same Magento instance, the data already includes a `store_id` or `store_name` field you can use to filter or segment.

</details>

<details>

<summary>Where do I find my Adobe Commerce API token?</summary>

Go to your Magento admin panel and navigate to **System > Integrations > Add New Integration**. Give it a name, set the resource access to the entities you need (e.g., Sales, Catalog, Customers), and save. Magento will display an **Access Token** — copy that and paste it into Coupler.io. Keep it secure and don't share it.

</details>

<details>

<summary>Which API version should I use?</summary>

Most Magento 2.x stores use `V1`. You can confirm this in your Magento admin under **System > About Magento** or by checking the [Adobe Commerce REST API documentation](https://developer.adobe.com/commerce/webapi/rest/). Enter the version exactly as shown (e.g., `V1`) in the API Version field in Coupler.io.

</details>

<details>

<summary>Does Coupler.io support incremental sync for Adobe Commerce?</summary>

Coupler.io uses the start date you configure to filter records — entities with `created_at` or `updated_at` fields (like Orders, Customers, and Invoices) support date-based filtering. Reference entities like Directory countries or Tax classes don't change often and are typically pulled in full each sync.

</details>

<details>

<summary>Can I pull abandoned cart data?</summary>

Yes — the **Carts** entity includes both active and abandoned carts. Abandoned carts are those that were created but never converted to an order. You can join Carts with Customers on `customer_id` to analyze which customer segments abandon most frequently.

</details>

<details>

<summary>How do I get a full inventory report with product names, not just SKUs?</summary>

Pull both the **Inventory source items** and **Products** entities, then use Coupler.io's **Join** transformation to combine them on the `sku` field. This gives you quantity and stock status alongside product names, prices, and categories.

</details>

<details>

<summary>Why does my order count in Coupler.io differ from the Magento admin?</summary>

The most common reasons are: (1) your start date excludes older orders, (2) you're filtering by a specific store view that doesn't include all orders, or (3) canceled or archived orders may be handled differently. Check your start date and confirm there are no status filters applied. See [Common Issues](/sources/category/ecommerce/adobe-commerce-magento/common-issues.md) for more detail on data discrepancies.

</details>

<details>

<summary>Can I send Adobe Commerce data to AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route product performance data, customer segments, or order trends directly to these tools for analysis, forecasting, or generating merchandising recommendations.

</details>

{% hint style="info" %}
Looking for details on which fields are available per entity? Check the [Data Overview](/sources/category/ecommerce/adobe-commerce-magento/data-overview.md) article. For connection errors or missing data, visit [Common Issues](/sources/category/ecommerce/adobe-commerce-magento/common-issues.md). For setup tips and multi-store patterns, see [Best Practices](/sources/category/ecommerce/adobe-commerce-magento/best-practices.md).
{% 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/adobe-commerce-magento/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.