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

# Cart.com Best Practices

Get clean, reliable Cart.com exports — tips on joining order entities, filtering by date, and avoiding sync pitfalls.

## Recommended setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Join order entities for complete reporting</strong></td><td>Orders alone won't give you a full picture. Add Order items and Order payments as sources in the same data flow, then use the Join transformation on Order ID to build a single enriched order report.</td></tr><tr><td><strong>Set a meaningful start date</strong></td><td>Use the date picker to set your start date to the beginning of your current reporting period — typically the start of the month or quarter. Pulling all historical data every sync is slow and rarely necessary.</td></tr><tr><td><strong>Use Append for multi-store setups</strong></td><td>If you operate more than one Cart.com store, create a source for each store in the same data flow and use the Append transformation to merge their Orders or Products into one unified table.</td></tr></tbody></table>

## Data refresh and scheduling

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Match refresh frequency to entity volatility</strong></td><td>Orders and Order statuses change frequently — sync these hourly or a few times per day. Products and Addresses change less often, so daily syncs are usually enough.</td></tr><tr><td><strong>Run a successful manual sync first</strong></td><td>Before enabling a schedule, run the data flow manually and verify the output. Check that row counts match your expectations and that joins are resolving correctly.</td></tr></tbody></table>

## Performance optimization

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Split large historical pulls by date</strong></td><td>If you need years of order history, create separate data flows with different start dates (e.g., one per year) and Append the results. This avoids timeout issues on very large datasets.</td></tr><tr><td><strong>Send aggregated data to AI tools</strong></td><td>When using AI destinations like ChatGPT, Claude, or Gemini, use the Aggregate transformation first to summarize orders by day or product category. Sending raw row-level data to an AI tool is less effective than sending a pre-summarized report.</td></tr></tbody></table>

## Common pitfalls

{% hint style="danger" %}
Don't assume the Orders entity contains everything you need. Order totals, line items, and payment details live in separate entities — always join them intentionally.
{% endhint %}

{% columns %}
{% column %}

### Do

* Join Order items to Orders on Order ID for SKU-level revenue analysis
* Use a start date on every data flow to scope your pull
* Store API keys securely and rotate them if team members leave
* Verify your data flow output with a manual run before scheduling
  {% endcolumn %}

{% column %}

### Don't

* Pull the full product catalog on every sync if only orders have changed
* Rely on Customers carts as a historical record — it only reflects current state
* Use the same API key across multiple environments (staging and production)
* Skip the start date on large stores — you'll pull years of data unnecessarily
  {% endcolumn %}
  {% endcolumns %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/ecommerce/cart/best-practices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.