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

# FAQ

<details>

<summary>Which SP-API region should I choose?</summary>

Choose the region that matches where your Seller Central account is registered: North America, Europe, or Far East. This determines which marketplaces Coupler.io can load for you — picking the wrong region means your actual marketplaces won't appear in the dropdown.

</details>

<details>

<summary>Why does Coupler.io redirect me to Amazon to connect?</summary>

Amazon Seller Central uses Amazon's own authorization flow (OAuth) to grant third-party apps like Coupler.io access to your seller data. You'll sign in to Amazon and approve the connection there rather than entering an API key directly in Coupler.io.

</details>

<details>

<summary>Can I export data from multiple marketplaces in one data flow?</summary>

Each data flow is connected to one region and one marketplace at a time. If you sell in multiple marketplaces, set up a separate data flow per marketplace and use Coupler.io's Append transformation to combine them in your destination.

</details>

<details>

<summary>What's the difference between Orders and the "all orders data" reports?</summary>

Orders is a direct API entity that returns structured, incremental order data filtered by last-update date — it's the best choice for regular scheduled syncs. The "all orders data" reports (by order date or by last update) are Amazon-generated report exports with a similar but not identical field set, intended for bulk historical exports rather than frequent incremental syncs.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

Most entities support up to 2 years of history if you leave the start date blank. The V2 settlement report is an exception — Amazon only allows a 90-day lookback for that specific report, regardless of what start date you configure.

</details>

<details>

<summary>Why do the Vendor forecasting reports return no data for my account?</summary>

"Vendor forecasting (fresh)" and "Vendor forecasting (retail)" are built for Amazon's Vendor Central program, which is separate from standard Seller Central marketplace selling. If you're a marketplace seller rather than a Vendor Central vendor, these two reports won't return usable data.

</details>

<details>

<summary>Why doesn't List financial events have a clear ID column?</summary>

Amazon returns financial events as nested lists (shipment charges, fees, direct payments, and similar) rather than one row per transaction with a single ID. Use the posted date and the related financial event group ID to organize and join this data downstream.

</details>

<details>

<summary>How current is the data after a sync?</summary>

Each sync reflects a snapshot at the time the data flow runs — there's no real-time streaming. Report-based entities add extra lag because Amazon generates the report asynchronously before Coupler.io can download it, so they can lag behind the Orders or Order items entities even when run at the same time.

</details>

<details>

<summary>Can I use Amazon Seller Central data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send orders, financial events, or inventory data directly to these tools to generate summaries or ad-hoc analysis.

</details>

{% hint style="info" %}
For the full list of available entities and what each one contains, see [Data Overview](/sources/category/ecommerce/amazon-seller-central/data-overview.md). For connection errors, rate limit issues, or empty reports, check [Common Issues](/sources/category/ecommerce/amazon-seller-central/common-issues.md).
{% 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 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/faq.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.