If you see an Amazon error like “not authorized” for Printful, it’s usually tied to your SP‑API authorization, not a Printful issue. This means Amazon has stopped allowing the Printful app to access your seller account.
What causes this authorization error?
Here are the most common reasons your Printful access may have been revoked:
- Amazon SP‑API token expiration: Amazon OAuth tokens expire after 12 months unless you reauthorize.
- Seller revoked access manually: You may have removed Printful’s permissions under Settings → Apps & services → Manage your apps.
- Printful’s app lost confirmation under Amazon’s listing rules: Amazon requires third-party integrations to be listed in the Seller Partner Appstore or meet public app standards. Private apps may have limits.
- Legacy MWS deprecation issues: Amazon shut down MWS access entirely by July 2023. If your integration hasn’t migrated to SP‑API, it won’t work anymore.
What can I do to restore access?
Here’s a step-by-step plan to fix the issue and reconnect with Printful:
- Review your Amazon Seller Central settings
Go to Apps & services → Manage your apps to see if Printful is still listed and authorized. If not, you’ll need to reauthorize. - Re-authorize Printful via OAuth
In the Printful Dashboard, reconnect your Amazon store (via Stores → Amazon → Reconnect or Settings → Store settings → select your Amazon store → Marketplaces → Authorize). Follow the prompts to log in to Amazon and grant access. - Ensure SP‑API is used
Printful uses Amazon’s SP‑API. If you integrated long ago, double-check it hasn’t fallen back to deprecated MWS authorization. Modern tokens must match SP‑API rules. - Check for authorization limits
If you’re testing or using a “private” app, you may be limited to a certain number of accounts. Ask Amazon support if this is the case, and consider using the official public workflow. - Contact Amazon support if needed
If you can’t renew access or find Printful listed, reach out to Amazon Seller Support to clarify that you still use Printful and need SP‑API access permission restored.