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

# Common Issues

## Connection issues

<details>

<summary>Authorization fails or is denied when connecting</summary>

This usually means the Amazon account used to authorize doesn't have permission to grant third-party application access in Seller Central. Confirm you're signing in with the account owner or a user with admin-level access, and that you approve the consent screen fully — a partial or cancelled authorization will send you back to Coupler.io without a valid connection.

</details>

<details>

<summary>Marketplace dropdown is empty after selecting a region</summary>

Marketplaces are loaded based on the SP-API region you select (North America, Europe, or Far East). If your account isn't registered in the region you picked, no marketplaces will load. Check which region your Seller Central account actually operates in and switch to that region.

</details>

## Missing data

<details>

<summary>A report entity returns no rows</summary>

Several Amazon reports only contain data when a specific condition applies in Seller Central — for example, the listings FYP report only returns rows for listings Amazon has actually flagged, and cancelled listings reports are empty if you haven't cancelled any listings. An empty result is often correct, not a connection problem. Check the equivalent report in Seller Central directly if you want to confirm.

</details>

<details>

<summary>Vendor forecasting reports return no data</summary>

"Vendor forecasting (fresh)" and "Vendor forecasting (retail)" are built for Amazon's Vendor Central program, not standard marketplace selling. If your account is a Seller Central seller account rather than a Vendor Central vendor account, these two report types won't return usable data.

</details>

## Rate limits and sync speed

<details>

<summary>Orders (or Order items) syncs are slow or time out</summary>

Amazon's SP-API enforces strict rate limits on the Orders and Order items endpoints — considerably tighter than most other Amazon endpoints. Large date ranges, frequent scheduled runs, or running multiple Amazon Seller Central data flows at the same time will all extend how long an Orders sync takes. Narrow your date range and avoid running several Amazon data flows simultaneously if syncs are timing out.

</details>

<details>

<summary>Report-based entities take a long time to complete, or occasionally fail</summary>

Report entities (anything other than Orders, Order items, and the two financial event entities) go through Amazon's own report generation pipeline: Coupler.io requests the report, waits for Amazon to finish processing it, then downloads it. Processing time depends on Amazon's queue and the size of the report, and can occasionally fail on Amazon's side. If a report-based sync fails, re-running it is usually sufficient — this is an Amazon-side processing outcome, not a persistent connection issue.

</details>

## Date range errors

<details>

<summary>V2 settlement report fails with an older start date</summary>

Amazon only allows a 90-day lookback for the V2 settlement report, regardless of the start date you configure for the data flow. If your start date is older than 90 days, request a shorter range for this entity specifically, or use the ledger detail/summary reports for older history.

</details>

## Data discrepancies

<details>

<summary>Settlement or ledger totals don't match the Seller Central dashboard</summary>

Coupler.io exports reflect the state of your account data at the moment the data flow runs, while Seller Central's dashboard can reflect activity that hasn't yet closed into a settlement period. Compare totals against a completed settlement period rather than an in-progress one, and re-run the data flow if you need the most current snapshot.

</details>

{% hint style="warning" %}
If you regularly hit rate limits on Orders or Order items, avoid scheduling multiple Amazon Seller Central data flows to run at the same time — stagger them so they don't compete for the same API quota.
{% 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/common-issues.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.