If you have older Amazon transactions stuck in Ready to sync — they show a loading spinner, nothing happens, and no error appears — it is almost always because they belong to Synder’s previous Amazon integration. Here is who this affects, how to check, and how to recover the transactions.
Who is affected
This affects accounts that connected Amazon before Synder’s upgraded Amazon integration (V2) and still have transactions that were imported but never synced on the older connection. If you connected Amazon recently, you are already on V2 and will not run into this.
How to check which Amazon integration you have
- Go to Platform transactions and open the Integration filter.
- Look at your Amazon integration name. If it says Amazon v2, you are on the new integration. If it does not say v2, you are most likely on the older integration.
- If you see two Amazon integrations with the same name, the one without v2 (sometimes labelled legacy) is the old one — that is where the stuck Ready to sync transactions sit.
Why old transactions won’t sync
- The V2 integration added complete payout and fee coverage, including unsettled transactions that appear as Pending until Amazon posts the settlement.
- On accounts that had the earlier integration, that older connection is kept for viewing only — it is no longer active for syncing.
- Any transactions imported but not synced before the upgrade are stranded: you can still see them, but they cannot be synced through the old integration.
How to recover the transactions
- In the old Amazon integration, filter for unsynced statuses (Ready to sync, Pending, Canceled, Scheduled, In progress) and note the date ranges.
- Switch to your Amazon v2 integration and run Historical Import for those same date ranges. This is self-serve — use the Import historical data function.
- Once the new transactions import and are ready to sync, archive the old stuck transactions to clean up your view.
Important: avoid creating duplicates
- The new integration will not warn you if you import a period that was already synced from the old one — it will import and sync those transactions again as duplicates.
- Only import periods that were never synced. Double-check which date ranges already synced before you import.
