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

# Amazon Seller Central

Amazon Seller Central is the dashboard Amazon marketplace sellers use to manage orders, inventory, fulfillment, and payments. Coupler.io connects to Amazon's Selling Partner API (SP-API) so you can export orders, FBA inventory, financial events, and dozens of Amazon-generated reports without touching Seller Central's own report downloads.

**Why connect Amazon Seller Central to Coupler.io?**

* Pull orders, order items, and financial events on a schedule instead of downloading reports manually
* Access FBA inventory, fee, reimbursement, and settlement reports alongside your core order data
* Combine order and financial data using Coupler.io's Join and Aggregate transformations
* Send data to Google Sheets, Excel, BigQuery, Looker Studio, or AI destinations like ChatGPT, Claude, or Gemini
* Keep dashboards current with scheduled refreshes instead of re-running exports in Seller Central

## Prerequisites

* An active Amazon Seller Central account with permission to authorize third-party applications (this typically requires the account owner or a user with admin-level access)
* Knowledge of which SP-API region your marketplace belongs to — North America, Europe, or Far East
* For **Vendor forecasting** reports specifically: a Vendor Central account, not a standard marketplace Seller account (see [Available entities](#available-entities))

## Quick start

{% hint style="success" %}
Start with the **Orders** entity, North America region, and a 7-day date range to confirm your connection works before adding report-based entities or widening your date range.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow and click Connect.** In Coupler.io, click **Add data flow**, search for **Amazon Seller Central** as your source, and click **Connect**. You'll be redirected to Amazon to sign in and authorize Coupler.io's access to your seller account.
{% endstep %}

{% step %}
**Select a report type.** Choose the data entity you want to export — a core entity like Orders or Order items, or one of the Amazon report types (e.g., FBA inventory, settlement reports). See [Available entities](#available-entities) for the full list.
{% endstep %}

{% step %}
**Select your region.** Choose the SP-API region that matches your marketplace: North America, Europe, or Far East.
{% endstep %}

{% step %}
**Select your marketplace.** Once you've picked a region, Coupler.io loads the marketplaces (stores) available in your account for that region.
{% endstep %}

{% step %}
**Set your report period.** Use the date pickers to set a start and end date. If you leave the start date blank, Coupler.io defaults to 60 days back; leaving the end date blank defaults to today.
{% endstep %}

{% step %}
**Choose a destination.** Select where your data should go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI tool like Claude, ChatGPT, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync and confirm data is flowing correctly before scheduling automatic refreshes.
{% endstep %}
{% endstepper %}

## Available entities

### Core components

| Entity                      | Description                                                                      |
| --------------------------- | -------------------------------------------------------------------------------- |
| Orders                      | Orders in your marketplace with status, totals, and buyer or shipping context    |
| Order items                 | Line items per order — SKUs, quantities, prices, and item-level order attributes |
| List financial event groups | Settlement-oriented groups of financial activity for a balance or payout period  |
| List financial events       | Granular charges, fees, refunds, and other money events behind your settlements  |

### Reports — orders and shipping

| Entity                             | Description                                                                                                     |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| All orders data by order date      | Tab-delimited all-orders report filtered by the order purchase date                                             |
| All orders data by last update     | Tab-delimited all-orders report filtered by last update time — useful for catching changes since your last sync |
| Amazon fulfilled shipments data    | FBA (AFN) shipment detail — quantities shipped, tracking, and fulfillment-related fields                        |
| Actionable order data (shipping)   | Orders that need seller action for shipping, confirmation, or similar workflow steps                            |
| Order report data (shipping)       | Order-level shipping report focused on fulfillment status and shipment fields                                   |
| Archived orders data by order date | Older orders outside the standard all-orders window, filtered by order date                                     |
| XML all orders data by order date  | All-orders data in XML format, filtered by order date                                                           |

### Reports — FBA inventory and fees

| Entity                            | Description                                                                       |
| --------------------------------- | --------------------------------------------------------------------------------- |
| FBA storage fee charges data      | Monthly FBA inventory storage fees assessed per SKU and fulfillment center        |
| AFN inventory data                | FBA on-hand, reserved, and inbound inventory quantities by SKU                    |
| AFN inventory data by country     | FBA inventory quantities split by the country where inventory is stored           |
| FBA inventory planning data       | Planning-oriented inventory fields such as inventory age and sell-through context |
| Stranded inventory data           | FBA units in a fulfillment center without a buyable offer                         |
| FBA unsuppressed inventory data   | Manage Your Inventory style data for SKUs that are not search-suppressed          |
| FBA estimated fees data           | Estimated fulfillment and storage-related fees per SKU                            |
| Restock inventory recommendations | Recommended replenishment quantities and timing from Amazon's restock guidance    |

### Reports — FBA fulfillment and returns

| Entity                                             | Description                                                                               |
| -------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| FBA fulfillment removal order detail data          | Removal orders — disposals, liquidations, and return-to-seller requests for FBA inventory |
| FBA fulfillment removal shipment detail data       | Shipments that moved inventory out of fulfillment centers after a removal order           |
| FBA reimbursements data                            | Reimbursement events for lost, damaged, or otherwise adjusted FBA inventory               |
| FBA fulfillment customer returns data              | Customer returns received at Amazon fulfillment centers for your FBA SKUs                 |
| Returns data by return date                        | Return records keyed by return date, including disposition where available                |
| FBA fulfillment customer shipment promotion data   | Promotional discounts and related amounts applied on FBA customer shipments               |
| FBA fulfillment customer shipment replacement data | Replacement shipments Amazon sent to buyers for your FBA orders                           |
| FBA Send to Amazon (SNS) performance data          | Performance metrics for Send to Amazon inbound shipments and placement                    |
| FBA Send to Amazon (SNS) forecast data             | Demand forecast data supporting Send to Amazon inbound and placement planning             |

### Reports — financial and settlement

| Entity                           | Description                                                                      |
| -------------------------------- | -------------------------------------------------------------------------------- |
| Ledger detail view data          | Detailed ledger lines for cash-balance style reporting and reconciliation        |
| Ledger summary view data         | Summarized ledger balances and rollups over a reporting window                   |
| V2 settlement report (flat file) | Settlement flat file — orders, refunds, fees, and reserves tied to payout cycles |

### Reports — listings and catalog

| Entity                            | Description                                                                             |
| --------------------------------- | --------------------------------------------------------------------------------------- |
| Open listings data                | Snapshot of listings that currently have an active offer on the marketplace             |
| Merchant listings data            | Active merchant listings and offer attributes for SKUs you sell                         |
| Merchant listings (all data)      | Broad listings export covering active and inactive offers in one report                 |
| Merchant listings (inactive data) | Listings that are inactive or not currently available for purchase                      |
| Merchant listings (legacy layout) | Merchant listings in a legacy-compatible layout for older tooling or migrations         |
| Merchant cancelled listings data  | Listings that were cancelled or removed from your active catalog                        |
| Listings FYP report               | Listings surfaced in Fix Your Product with quality, compliance, or detail issues        |
| XML browse tree data              | Browse-node taxonomy (category tree) for mapping products to Amazon's catalog structure |

### Reports — feedback

| Entity               | Description                                                     |
| -------------------- | --------------------------------------------------------------- |
| Seller feedback data | Buyer feedback ratings and comments left on your seller profile |

### Reports — Vendor Central forecasting

{% hint style="warning" %}
These two reports require a **Vendor Central** account. If you sell through standard Amazon Seller Central (marketplace selling), these reports will return no usable data.
{% endhint %}

| Entity                      | Description                                                                      |
| --------------------------- | -------------------------------------------------------------------------------- |
| Vendor forecasting (fresh)  | Vendor Central fresh-item procurement forecast for perishable or fresh programs  |
| Vendor forecasting (retail) | Vendor Central retail procurement forecast for reorderable vendor-supplied ASINs |


---

# 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.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.