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

# 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


---

# 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/data-overview.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.