> 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/commercetools/faq.md).

# FAQ

<details>

<summary>What entities can I export from Commercetools?</summary>

Coupler.io supports five Commercetools entities: Customers, Orders, Payments, Products, and Discount codes. Each entity is set up as a separate source within a data flow, and you can combine them using Join or Append transformations.

</details>

<details>

<summary>How do I find my Commercetools API credentials?</summary>

Go to your Commercetools Merchant Center and navigate to **Settings → Developer settings → API clients**. Create a new client with the view scopes you need, and copy the Client ID, Client Secret, Project Key, and Region. Note that the Client Secret is only shown once — save it immediately.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

You control this with the start date setting. Use the date picker to set any past date — Coupler.io will pull all records created from that date onward. There's no hard limit enforced by Coupler.io, but very large date ranges on busy stores may take longer to complete on the first run.

</details>

<details>

<summary>Can I combine data from Orders and Payments in one export?</summary>

Yes. Add both Orders and Payments as sources within the same data flow, then use the Join transformation to link them on the order ID field. This gives you a unified view of order state and payment status in a single destination sheet or table.

</details>

<details>

<summary>Can I consolidate data from multiple Commercetools projects?</summary>

Yes. Create a separate source for each project (each with its own API credentials) and use the Append transformation to stack the results into one destination. This is useful if you run separate regional storefronts or brand projects within Commercetools.

</details>

<details>

<summary>Why do product prices look like very large numbers?</summary>

Commercetools stores monetary values as integers in the smallest currency unit (cents for USD/EUR). A value of `9900` means $99.00. Divide price fields by 100 in your spreadsheet or BI tool to display them correctly.

</details>

<details>

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

Yes. When choosing a destination in Coupler.io, you can select AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. This is useful for tasks like generating product descriptions from catalog data or summarizing order trends.

</details>

<details>

<summary>Does Coupler.io support incremental syncs for Commercetools?</summary>

Yes. After your initial run, Coupler.io pulls only new or updated records based on the start date and internal sync state, rather than re-importing everything from scratch each time.

</details>

{% hint style="info" %}
For details on available fields and metric combinations, see [Data Overview](/sources/category/ecommerce/commercetools/data-overview.md). For connection errors and permission issues, visit [Common Issues](/sources/category/ecommerce/commercetools/common-issues.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/commercetools/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.