A Plugin Lost Authorization
Sometimes a plugin that was working stops because the source platform revoked its access. Here is how to identify the issue and reconnect the plugin.
How you find out
Commerce Kitty creates a notification when a plugin's authorization is rejected. You will see the bell icon turn red and the notification will name the affected plugin. The plugin's detail page also shows an authorization error.
Why authorizations expire
A plugin can lose its authorization for several reasons, none of which mean Commerce Kitty did anything wrong:
- You changed your password on the source platform. Some platforms invalidate existing OAuth tokens when the password changes.
- The platform forced a re-auth after a security event or scope update.
- You manually disconnected the app on the source platform. Common when reviewing connected apps in your settings.
- The token expired. Some platforms issue tokens with a fixed lifetime that requires periodic renewal.
- The platform credentials changed, such as rotating an Amazon SP-API refresh token.
Step 1. Open the plugin
From the notification, click through to the plugin. Or open Configuration → Plugins and find it in the list. The plugin will show an authorization error at the top of its detail page.
Step 2. Click Reauthorize
Most plugins have a Reauthorize action right on the plugin detail page. Click it. Commerce Kitty starts a fresh OAuth flow with the source platform, which means you will be redirected to log in and grant access again.
Use the same account you used originally. Connecting a different account creates a new connection rather than fixing the existing one.
Step 3. Approve the access request
The source platform will show you a screen asking you to approve Commerce Kitty's access. Approve every permission it asks for. If you only approve some permissions, certain features will fail later.
For Amazon, this is the SP-API authorization screen and the permissions are determined by your seller-app role. For Etsy, it is the Etsy app authorization page. For Shopify, you are creating or re-creating an admin API access token.
If a plugin asked for new permissions on the source platform, you will need to approve those new ones too. Read the consent screen instead of clicking through it.
Step 4. Verify the connection works
After the OAuth flow completes, you are redirected back to Commerce Kitty. The error on the plugin detail page should be gone. Sync should resume within a few minutes.
Test it by waiting a few minutes and then checking if new orders or product changes are flowing through.
If reauthorization keeps failing
Sometimes reauthorization fails repeatedly. The usual causes:
- Wrong account. You logged into a different account on the source platform than the one the plugin was originally connected to. Log out of the platform first, then start the reauthorization again.
- Browser session issue. Cookies or cached login state can interfere. Try the reauthorization in a private or incognito window.
- The app on the source platform was deleted. If you removed the integration from the source platform's app management screen, you cannot reauthorize. Delete the plugin in Commerce Kitty and create it from scratch.
- The credentials changed. If your platform requires fresh credentials (a new SP-API refresh token, a new API key, etc.), enter them in the plugin form before reauthorizing.