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

# Cart.com

Cart.com is an ecommerce platform that lets merchants manage their online store, product catalog, orders, and customer data in one place. It's built for growing brands that need a scalable foundation for direct-to-consumer selling.

Connecting Cart.com to Coupler.io lets you pull your store data into any destination — spreadsheets, data warehouses, or AI tools — on a schedule you control.

## Why connect Cart.com to Coupler.io?

* **Centralize your store data** — bring orders, products, payments, and customer records into one place for reporting
* **Combine entities** — use Join or Append transformations to link order items with orders, or payments with order statuses
* **Send data to AI tools** — analyze trends with ChatGPT, Claude, Gemini, or Perplexity without manual exports
* **Keep destinations fresh** — auto-sync to Google Sheets, Excel, BigQuery, or Looker Studio on a custom schedule

## Prerequisites

* An active Cart.com store account
* API key access (typically available to store admins or developers)
* Your Cart.com API key — find it in your store's developer or API settings

## Quick start

{% hint style="success" %}
If you want a combined order report, start with the **Orders** entity and use the Join transformation to bring in **Order items** and **Order payments** in the same data flow.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log into Coupler.io, go to the Data Flows section, and click **Add data flow**.
{% endstep %}

{% step %}
**Select Cart.com as your source.** Search for Cart.com in the source list and click to add it.
{% endstep %}

{% step %}
**Enter your Cart.com API key.** Paste the API key from your Cart.com store settings into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Choose an entity.** Pick the data you want to export — Orders, Products, Customers carts, Order items, Order payments, Order statuses, or Addresses.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to define how far back you want to pull data. This helps keep your first sync focused and fast.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data sent — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync. Review the results to confirm everything looks right before setting up a schedule.
{% endstep %}
{% endstepper %}

## Available entities

| Entity          | Description                                              |
| --------------- | -------------------------------------------------------- |
| Customers carts | Customer profiles and cart information from your store   |
| Orders          | Order details including totals, dates, and customer info |
| Order payments  | Payment transactions linked to orders                    |
| Order statuses  | Current and historical processing stages for orders      |
| Order items     | Individual line items and products within each order     |
| Products        | Product catalog with descriptions, prices, and inventory |
| Addresses       | Customer billing and shipping addresses                  |


---

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