How do I reconnect an Amazon account if the connection expires?
Learn how to reconnect an expired Amazon account connection in MerchantSpring and restore data syncing.
MerchantSpring connects to Amazon accounts using secure API authentication. Occasionally, this connection may expire due to Amazon’s security policies, permission changes, or account authorization updates.
When this happens, MerchantSpring may temporarily lose access to retrieve marketplace data until the connection is re-authorized.
Reconnecting the account restores MerchantSpring’s ability to retrieve sales, financial, advertising, and product data.
Common Reasons a Connection May Expire
Amazon connections may expire for several reasons, including:
- Amazon security token expiration
- Changes to Seller Central or Vendor Central permissions
- Password or account security updates
- Amazon API authorization updates
- Revoked application permissions
These events require the account to be reconnected to restore API access.
How to Reconnect Your Amazon Account
- Navigate to Settings → Channels
- Locate the Amazon account connection
- If the connection has expired, the status may show Disconnected or Reconnect Required
- Click Reconnect
- Follow the Amazon authorization prompts
- Confirm access permissions
- Complete the authentication process
Once completed, MerchantSpring will resume syncing data automatically.
What Happens After Reconnection
After reconnecting the account:
- MerchantSpring will verify API permissions
- Data syncing will resume during the next sync cycle
- Any missed data will typically be retrieved through a backfill process
Historical reporting will remain intact.
Notes:
- Reconnecting does not delete historical data.
- Advertising credentials may require separate authorization depending on your Amazon account structure.
- Data may take some time to refresh after reconnection.
Troubleshooting
If reconnection fails:
- Confirm you are using the correct Amazon account
- Verify the account has sufficient permissions
- Ensure Amazon login authentication completes successfully