> 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
Connect Cart.com orders, products, and customer data to Google Sheets, BigQuery, or AI tools via Coupler.io. No coding needed.
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 |
## Cart.com data overview
Cart.com exposes seven entities through Coupler.io, covering your full store operation — from product listings and customer records to granular order line items and payment transactions.
## Entities at a glance
| Entity | Best used for |
| --------------- | ------------------------------------------------------ |
| Customers carts | Customer profiles, cart activity, segmentation |
| Orders | Revenue reporting, order volume, fulfillment tracking |
| Order payments | Payment method analysis, transaction reconciliation |
| Order statuses | Fulfillment funnel, status change tracking |
| Order items | Product-level sales, SKU performance, basket analysis |
| Products | Catalog management, pricing audits, inventory tracking |
| Addresses | Geographic reporting, shipping zone analysis |
## Customers carts
#### Fields
| Field | Description |
| ---------------------- | ----------------------------------------- |
| Customer ID | Unique identifier for the customer |
| Email | Customer email address |
| First name / Last name | Customer name fields |
| Created date | When the customer record was created |
| Updated date | Last modification timestamp |
| Cart items | Products currently in the customer's cart |
## Orders
#### Fields
| Field | Description |
| --------------- | ------------------------------------------ |
| Order ID | Unique order identifier |
| Customer ID | Links to the customer who placed the order |
| Order date | Date and time the order was placed |
| Order total | Total order value |
| Subtotal | Pre-tax, pre-shipping total |
| Tax amount | Tax applied to the order |
| Shipping amount | Shipping cost |
| Discount amount | Discounts or coupon values applied |
| Currency | Order currency |
## Order items
#### Fields
| Field | Description |
| ------------- | ------------------------------- |
| Order item ID | Unique line item identifier |
| Order ID | Parent order reference |
| Product ID | Links to the product record |
| Product name | Name of the product |
| SKU | Product SKU |
| Quantity | Units ordered |
| Unit price | Price per unit at time of order |
| Line total | Total value for that line item |
## Order payments
#### Fields
| Field | Description |
| ---------------- | --------------------------------------- |
| Payment ID | Unique payment transaction identifier |
| Order ID | Associated order reference |
| Payment method | Method used (e.g., credit card, PayPal) |
| Payment status | Current status of the payment |
| Amount | Payment amount |
| Transaction date | When the payment was processed |
## Order statuses
#### Fields
| Field | Description |
| ------------ | --------------------------------------------------- |
| Status ID | Unique status identifier |
| Order ID | Associated order |
| Status label | Human-readable status name (e.g., Pending, Shipped) |
| Updated date | When the status was last changed |
## Products
#### Fields
| Field | Description |
| --------------- | ----------------------------- |
| Product ID | Unique product identifier |
| Product name | Display name |
| SKU | Stock keeping unit |
| Price | Listed sale price |
| Cost price | Internal cost (if available) |
| Inventory count | Current stock level |
| Category | Product category |
| Status | Active, inactive, or archived |
| Description | Product description text |
## Addresses
#### Fields
| Field | Description |
| ---------------- | -------------------------------- |
| Address ID | Unique address record identifier |
| Customer ID | Linked customer |
| Address type | Billing or shipping |
| Street | Street address |
| City | City |
| State / Province | State or province |
| Country | Country code |
| Postal code | ZIP or postal code |
## Useful entity combinations
* **Orders + Order items** — Join on Order ID to see which products drive the most revenue
* **Orders + Order payments** — Join on Order ID to reconcile revenue with payment transactions
* **Order items + Products** — Join on Product ID to enrich line items with current catalog data
* **Customers carts + Orders** — Join on Customer ID to compare cart activity with completed purchases
* **Multiple stores** — Use Append to combine Orders from different Cart.com accounts into a single report
## Use cases by role
{% tabs %}
{% tab title="Ecommerce managers" %}
* Track daily and weekly order volume trends using the Orders entity
* Monitor fulfillment pipeline by pulling Order statuses and spotting where orders stall
* Build a revenue dashboard in Looker Studio by joining Orders and Order items
{% endtab %}
{% tab title="Finance teams" %}
* Reconcile payments against orders by joining Order payments with Orders
* Export transaction data to Google Sheets or Excel for accounting review
* Analyze discount impact by comparing discount amounts to order totals
{% endtab %}
{% tab title="Merchandising & catalog" %}
* Audit your product catalog by pulling the Products entity into a spreadsheet
* Identify top-selling SKUs by joining Order items with Products
* Spot out-of-stock or inactive products before they affect orders
{% endtab %}
{% endtabs %}
## Platform-specific notes
* The **start date** parameter filters data by record creation or order date — set it to avoid pulling your entire historical dataset on every sync
* Cart.com's API may return paginated results for large catalogs; Coupler.io handles pagination automatically
* The **Customers carts** entity reflects current cart state — it does not retain historical cart snapshots
* Order statuses represent the latest state per order; use scheduled syncs to capture transitions over time
## Cart.com common issues
### Connection issues
My API key isn't being accepted
Double-check that you've copied the full API key from Cart.com — it's easy to accidentally include a trailing space or miss a character. Also confirm that the API key belongs to an account with developer or admin-level access. Keys tied to limited-permission accounts may be rejected by the API even if the format looks correct.
Coupler.io says the connection failed but my API key looks correct
Cart.com API keys can be scoped to specific store environments (e.g., staging vs. production). Make sure the key you're using matches the store environment you want to pull data from. If you recently regenerated the key, update it in your Coupler.io data flow source settings.
### Missing data
Some orders aren't showing up in my export
Check the **start date** parameter in your data flow. If you've set a start date that's too recent, older orders will be excluded. Use the date picker to extend the range backward. Also note that Cart.com may have a short delay before very recent orders appear via the API.
Order items or payments are missing for some orders
Order items and order payments are separate entities in Coupler.io. If you're only pulling the Orders entity, you won't automatically get line items or payment details — you need to add Order items and Order payments as separate sources in your data flow, then use the Join transformation to connect them on Order ID.
The Products entity is missing some catalog items
Inactive or archived products may not be returned by the Cart.com API depending on your store's API configuration. Check whether the missing products are set to an inactive or draft status in your Cart.com admin panel.
### Permission errors
I'm getting a 403 Forbidden error
This usually means the API key doesn't have permission to access the requested entity. In Cart.com, confirm that the API user or role associated with the key has read access to the data you're trying to export. You may need to ask your store admin to update the API key's permissions.
### Data discrepancies
Order totals in Coupler.io don't match what I see in Cart.com
Order totals in the Orders entity reflect the values at the time of the API response. If an order was edited, refunded, or had a discount applied after the initial export, re-run your data flow to get the updated values. Scheduled syncs will keep totals current going forward.
Customer cart data looks stale or doesn't match the live cart
The Customers carts entity returns the current cart state at the moment of the API call. It does not store historical snapshots. If you need to track cart changes over time, set up frequent scheduled syncs and append results to a destination table.
### Rate limits
My data flow is timing out or returning partial results
Cart.com's API enforces rate limits that may slow down large data pulls. If you're syncing a large product catalog or many months of orders, try narrowing the start date to reduce the volume of records fetched per run. Coupler.io handles pagination automatically, but very large datasets may require splitting into multiple data flows by date range.
## Cart.com FAQ
Can I combine orders, order items, and payments in a single report?
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.
How far back can I pull Cart.com data?
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.
Does Coupler.io support incremental sync for Cart.com?
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.
Can I pull data from multiple Cart.com stores into one sheet?
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.
What destinations can I send Cart.com data to?
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.
Why does the Customers carts entity not show historical cart data?
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.
Can I use Cart.com data with AI tools in Coupler.io?
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.
{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](#cart-com-data-overview) article. For help with sync errors or missing records, check [Common Issues](#cart-com-common-issues).
{% 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 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.md?ask=&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.