Overview

Amazon is introducing the Solution Provider Portal (SPP), a single hub that will replace Seller Central and Vendor Central for all third‑party developers who use the Selling Partner API (SP‑API). The migration must be finished by July 31 2025, after which any developer that has not moved will lose API access, potentially disabling the tools sellers rely on for daily operations.

Key Points

• Unified hub launch — SPP consolidates every SP‑API activity into one dashboard, ending the need to toggle between Seller Central and Vendor Central.
• Account merging — Developers can combine multiple developer accounts, applications, and credentials into a single profile, reducing duplicate logins.
• Real‑time API analytics — A new monitoring panel shows call volume, latency, and error rates, letting providers spot performance issues early.
• Fine‑grained permissions — Teams can assign roles such as “read‑only,” “developer,” or “admin” to individual users, tightening security while supporting collaboration.
• Separate workspace — The portal isolates developer functions from regular seller or vendor tasks, preventing accidental changes to storefront settings.
• Hard deadline — The July 31 2025 cut‑off is non‑negotiable; failure to migrate means complete loss of SP‑API connectivity for the affected provider.

How the Migration Works

1. Initiate guided workflow — From Seller Central or Vendor Central, developers click the “Migrate to Solution Provider Portal” button, which opens a step‑by‑step wizard. Example: A developer with three applications (inventory sync, repricing, and analytics) launches the wizard and sees each app listed for transfer.
2. Consolidate accounts — The wizard prompts users to select the developer accounts they wish to merge; Amazon then creates a unified SPP profile and moves all associated credentials. Example: Two separate accounts, one for US marketplaces and one for EU, are merged, resulting in a single set of client IDs and secret keys.