> 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.md).

# Commercetools

Commercetools is a cloud-native, headless commerce platform used by mid-market and enterprise brands to manage their product catalog, orders, customers, and payments. It provides a flexible API-first approach to building commerce experiences across any channel.

Connecting Commercetools to Coupler.io lets you pull your store data into spreadsheets, BI tools, or AI assistants — without writing a single line of code.

**Why connect Commercetools to Coupler.io?**

* Sync orders, customers, products, payments, and discount codes into Google Sheets, Excel, BigQuery, Looker Studio, or AI destinations like ChatGPT, Claude, or Gemini
* Combine multiple entities — for example, join orders with payments to track revenue and fulfillment in one view
* Schedule automatic refreshes so your reports always reflect the latest store data
* Append data from multiple Commercetools projects into a single destination for consolidated reporting

## Prerequisites

Before connecting, make sure you have:

* A Commercetools account with at least one active project
* A **Client ID**, **Client Secret**, **Project Key**, and **Region** for your project — these come from an API client you create in the Commercetools Merchant Center
* The API client must have read scopes for the entities you want to export (e.g., `view_orders`, `view_customers`, `view_products`)

## Quick start

{% hint style="success" %}
Create your API client in the Commercetools Merchant Center under **Settings → Developer settings → API clients**. Give it only the view scopes you need — this keeps access minimal and secure.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io** and select **Commercetools** as the source.
{% endstep %}

{% step %}
**Enter your API credentials.** You'll need your Client ID, Client Secret, Project Key, and Region. These are available on the API client detail page in the Merchant Center.
{% endstep %}

{% step %}
**Select the entity** you want to export — Customers, Orders, Products, Payments, or Discount codes.
{% endstep %}

{% step %}
**Set a start date** using the date picker to control how far back Coupler.io pulls data.
{% endstep %}

{% step %}
**Choose your destination** — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination such as Claude, ChatGPT, or Gemini.
{% endstep %}

{% step %}
**Run the data flow manually** to confirm everything is connected and data is loading correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity         | Description                                                           |
| -------------- | --------------------------------------------------------------------- |
| Customers      | Contact details, preferences, and account data                        |
| Orders         | Line items, pricing, shipping, and fulfillment status                 |
| Payments       | Transactions, payment methods, and processing status                  |
| Products       | Catalog data including descriptions, pricing, and inventory           |
| Discount codes | Promotional codes, discount rules, usage counts, and validity periods |


---

# 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.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.