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

# FAQ

<details>

<summary>Can I combine orders, order items, and payments in a single report?</summary>

Yes. Add all three as separate sources within the same Coupler.io data flow, then use the Join transformation to connect them. Join Orders to Order items on Order ID, and join that result to Order payments on Order ID. This gives you a single enriched table with product details and payment info alongside each order.

</details>

<details>

<summary>How far back can I pull Cart.com data?</summary>

Coupler.io uses the start date you set in the data flow configuration to determine how far back to fetch records. There's no hard limit imposed by Coupler.io, but very large date ranges may slow down the sync or hit Cart.com API rate limits. For large historical pulls, split the range across multiple data flows and use Append to combine the results.

</details>

<details>

<summary>Does Coupler.io support incremental sync for Cart.com?</summary>

Coupler.io fetches data from the start date you configure on each run. To keep your destination up to date without re-pulling everything, set your start date to a rolling window (e.g., the last 30 days) and use a destination that supports upserts or appends — like BigQuery — so new records are added without duplicating existing ones.

</details>

<details>

<summary>Can I pull data from multiple Cart.com stores into one sheet?</summary>

Yes. Create one data flow with a source for each Cart.com store (each with its own API key), then use the Append transformation to merge their data. This works well for Orders, Products, or any entity you want to compare across stores.

</details>

<details>

<summary>What destinations can I send Cart.com data to?</summary>

Coupler.io supports a wide range of destinations including Google Sheets, Microsoft Excel, BigQuery, Looker Studio, and AI tools like ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can also send data to other data warehouses or BI tools depending on your plan.

</details>

<details>

<summary>Why does the Customers carts entity not show historical cart data?</summary>

The Customers carts entity returns the current state of each customer's cart at the time of the API call. Cart.com doesn't expose a historical log of cart changes through its API. If you want to track cart changes over time, set up frequent syncs and append each snapshot to your destination table.

</details>

<details>

<summary>Can I use Cart.com data with AI tools in Coupler.io?</summary>

Yes. When you select an AI destination (like ChatGPT, Claude, or Gemini), Coupler.io sends your Cart.com data directly to that tool. For best results, use the Aggregate transformation to summarize data before sending — for example, total revenue by product category or daily order counts — rather than sending raw row-level records.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](/sources/category/ecommerce/cart/data-overview.md) article. For help with sync errors or missing records, check [Common Issues](/sources/category/ecommerce/cart/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/cart/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.