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

# Data Overview

Amazon Seller Central data in Coupler.io comes from two sources: a small set of core SP-API endpoints (Orders, Order items, financial events) and a much larger library of Amazon-generated reports (inventory, fees, settlements, listings, and more). Here's what's available and how the two differ.

## Entities overview

| Entity                                        | What it contains                                                                                                                              |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Orders                                        | Order ID, status, fulfillment channel, sales channel, order total and currency, Prime/business order flags, delivery window, shipping address |
| Order items                                   | Order item ID, ASIN, seller SKU, quantity ordered/shipped, item price, item tax, promotion IDs                                                |
| List financial event groups                   | Financial event group ID, processing status, fund transfer status, original/converted totals, beginning balance                               |
| List financial events                         | Nested event lists (shipment charges, fees, direct payments) with posted dates — no single row-level ID                                       |
| FBA storage fee charges                       | ASIN, FNSKU, monthly storage fee amounts per fulfillment center                                                                               |
| AFN inventory (+ by country)                  | Seller SKU, fulfillment channel SKU, on-hand/reserved/inbound quantities, storage country                                                     |
| Restock & inventory planning reports          | Inventory age, sell-through context, replenishment recommendations                                                                            |
| Removal, reimbursement, and returns reports   | Removal order IDs, reimbursement reasons, return dispositions                                                                                 |
| Ledger detail and summary reports             | Date, FNSKU, ledger line items and balance rollups                                                                                            |
| V2 settlement report                          | Settlement ID, settlement start date, orders/refunds/fees/reserves tied to a payout cycle                                                     |
| Listings reports (active/inactive/all/legacy) | Listing ID, SKU, offer status and attributes                                                                                                  |
| Seller feedback data                          | Date, rating, buyer comments                                                                                                                  |
| Vendor forecasting reports                    | Vendor Central procurement forecasts (fresh or retail programs)                                                                               |

## Metrics and dimensions

#### Orders

| Dimension           | Description                                            |
| ------------------- | ------------------------------------------------------ |
| Order status        | Pending, shipped, cancelled, and other order states    |
| Fulfillment channel | Whether Amazon (FBA) or the seller fulfilled the order |
| Sales channel       | The Amazon storefront the order came through           |
| Order total         | Order value and currency                               |
| Last update date    | Timestamp used to filter orders incrementally          |

#### Financial events

| Dimension                  | Description                                                             |
| -------------------------- | ----------------------------------------------------------------------- |
| Processing status          | Whether a financial event group is open or closed                       |
| Original / converted total | Settlement amount in original and account currency                      |
| Posted date                | When a financial event was recorded — used as the filterable date field |

#### FBA inventory reports

| Dimension          | Description                                                    |
| ------------------ | -------------------------------------------------------------- |
| Seller SKU / FNSKU | Your SKU and Amazon's fulfillment network SKU                  |
| Fulfillment center | Where the inventory is physically stored                       |
| Storage country    | Country where FBA inventory is held (AFN inventory by country) |

## Common entity combinations

* **Orders + Order items** — Join on order ID to get a full line-item view of every order, including SKU-level pricing and quantities.
* **List financial event groups + List financial events** — Use the group as the settlement-period anchor, then drill into individual charges and fees within it.
* **AFN inventory data + FBA storage fee charges** — Join on SKU to see which slow-moving inventory is driving your storage costs.
* **Merchant listings data + Merchant cancelled listings data** — Compare active vs. cancelled listings to track catalog health over time.
* **V2 settlement report + List financial events** — Reconcile a payout total against the individual charges and refunds that produced it.

## Use cases by role

{% tabs %}
{% tab title="Operations and fulfillment" %}

* Export **Orders** and **Order items** to track fulfillment status and shipment timing
* Pull **AFN inventory** and **FBA inventory planning** reports to monitor stock levels and avoid stranded inventory
* Use **restock inventory recommendations** to plan replenishment shipments
  {% endtab %}

{% tab title="Finance and accounting" %}

* Export **List financial events** and the **V2 settlement report** to reconcile payouts against orders, fees, and refunds
* Use **ledger summary view data** for balance rollups across reporting periods
* Track **FBA storage fee charges** and **FBA reimbursements** to monitor cost and recovery trends
  {% endtab %}

{% tab title="Catalog and listings management" %}

* Compare **merchant listings data** against **merchant cancelled listings data** to catch unintentional deactivations
* Use the **listings FYP report** to find and fix listings with quality or compliance issues
* Pull **XML browse tree data** to map your catalog against Amazon's category taxonomy
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* **Region and marketplace are linked** — Select your SP-API region (North America, Europe, or Far East) first; Coupler.io then loads only the marketplaces available in that region for your account.
* **Orders is a strict rate-limited endpoint** — Amazon's SP-API allows roughly one Orders request per minute and one Order items request every 2 seconds. Large date ranges or frequent scheduled runs on the Orders entity will take longer to sync than other entities because of this.
* **Orders and Order items are incremental by last-update date, not a fixed snapshot** — re-running the same or an overlapping date range will re-fetch any order that was updated in that window (for example, a status change on an older order). This is expected behavior for a mutable resource, not duplicate data.
* **Report entities go through Amazon's async report pipeline** — Coupler.io requests the report from Amazon, waits for it to finish processing, then downloads it. Processing time varies with report size and Amazon's own queue, so report-based entities can take noticeably longer to sync than Orders or Order items, especially over wide date ranges.
* **Default lookback is 2 years** — If you leave the start date blank, Coupler.io pulls up to 2 years of history for most entities. The **V2 settlement report** is an exception: Amazon only allows a 90-day lookback for this report, regardless of the start date you set.
* **Vendor forecasting reports need a Vendor Central account** — "Vendor forecasting (fresh)" and "Vendor forecasting (retail)" are built for Amazon's Vendor Central program and always return Amazon's current forecast snapshot; they don't support date filtering and won't return meaningful data for a standard marketplace Seller account.
* **List financial events has no single primary key** — records are nested event lists (charges, fees, payments) rather than one row per financial transaction; use the posted date and event group ID to organize this data downstream.


---

# 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/amazon-seller-central/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.