Overview

Starting April 25 2022, Amazon will impose strict limits on the number of seller accounts that a third‑party application can connect to, and the Selling Partner Appstore will only display apps that are marked as public. The new caps differ for developers who register as public versus private data consumers, and the visibility rules will push private‑only tools out of the marketplace search results. Sellers who rely on external software for inventory, order, or advertising management must understand these changes to avoid service interruptions.

Key Points

• Authorization ceiling — A public‑type developer may request permission for up to 10,000 distinct seller accounts, while a private‑type developer is restricted to a maximum of 1,000 accounts per application.
• Tier‑based enforcement — If an app exceeds its allotted count, Amazon automatically blocks any further authorizations until the developer either reduces the number of linked sellers or upgrades to a higher tier.
• Public‑only marketplace — From the rollout date, only apps flagged as “public” in the developer console will appear in the Selling Partner Appstore’s search and category listings.
• Private app access — Private applications remain functional but can be reached only through direct invitation URLs; they will no longer be discoverable via the Appstore UI.
• 30‑day grace period — Private apps that were listed before the policy change keep their marketplace entries for 30 days, after which they must be resubmitted as public or removed entirely.
• Weekly compliance checks — Amazon reviews each developer’s authorization logs on a weekly basis and sends a warning email when usage reaches 90 % of the permitted threshold.

How Application Authorization Limits Work

1. Choose data‑access classification — During registration, the developer selects either “public” (e.g., a pricing analytics service that serves any seller) or “private” (e.g., a custom ERP built for a single enterprise).
2. Send authorization request — The app invokes the Selling Partner API’s endpoint with the seller’s MWS Auth Token; if the request would push the total beyond the developer’s limit, Amazon returns a 403 error stating “limit exceeded.”