Short answer
SPN is Amazon's Service Provider Network: a directory inside Seller Central where sellers look for outside help with accounts, advertising, catalog, images, compliance, taxes, shipping and more. An agency that wants to appear there, and to work inside its clients' Seller Central accounts the way Amazon now expects, registers in the Solution Provider Portal, verifies the identity of every person who will touch client accounts, and gets Amazon to approve the Seller Central roles its service needs. Only then can a seller grant it access, and only to those roles.
"Amazon solution provider network" is not an Amazon product name. It is what you get when the Service Provider Network and the Solution Provider Portal are blended into one phrase, which is easy to do, because since 2026 the second is the front door to the first. This guide separates the two, walks through registration and review, and then answers the question most agencies reach next: whether to request API access as well. Everything below was checked on 20 November 2026 against Amazon's service provider onboarding documentation and the Service Provider Network page for sellers.
Four names that agencies mix up
- Service Provider Network (SPN). The catalog sellers browse. Sellers reach it in Seller Central under Apps and Services, Explore Services.
- Solution Provider Portal (SPP). Amazon's portal for everyone who serves sellers from outside: developers who call the Selling Partner API and service providers who work in Seller Central. Amazon's terminology page defines "solution provider" as covering both groups. Registration, identity checks, role approval, seller authorizations and SPN listings all live here.
- Service Provider Central. The older system for SPN members. Amazon is moving existing providers to SPP through an assisted migration and contacts each of them with its own deadline.
- Selling Partner Appstore. Where public software applications are listed: the software counterpart to SPN, with its own review.
Advertising adds a fifth name. The Amazon Ads Partner Network is a separate program with its own console, run by Amazon Ads rather than by the selling side. We cover it in our Amazon Ads Partner Network guide. A PPC agency usually needs both.
What the network lists and how sellers use it
On 20 November 2026 Amazon's seller-facing page names eighteen service categories: account management, accounting, advertising optimization, cataloging, compliance, enhanced brand content (A+ Content), excess inventory, FBA preparation, imaging, international returns, international shipping, IP Accelerator and brand protection, manufacturing, storage, sustainability, taxes, training, and translation for global selling.
A seller searches by location, target marketplace and service type, narrows the list by the provider's location, language and average rating, and compares providers on verified reviews, completed service requests, specialties and reference prices. Contact goes through a Contact Provider button that shares the seller's details with you, and the seller follows the request from an SPN dashboard. Amazon says it vets providers and monitors their performance, says just as clearly that it does not endorse any of them, and leaves the contract between you and the seller. For sellers the network costs nothing beyond their selling account.
For an agency this means a new listing competes on description and price until reviews arrive, and a retainer or percentage-of-spend model has to be expressed as a reference price a seller can compare.
What changed in 2026: access through authorization, not logins
For years agencies worked in client accounts as secondary users: the seller invited an employee's email address, ticked permissions, and the agency logged in like staff. Amazon is replacing that. Its Solution Provider Portal FAQ describes the new model:
- sellers choose explicitly which provider gets access;
- access covers only the Seller Central roles that Amazon approved for your service;
- an authorization lasts 365 days and can be renewed;
- sellers can revoke it at any time from the Manage Services page in Seller Central.
When a client reauthorizes under the new flow, it replaces all earlier access to that account. Roles you were never approved for, or that are not open to service providers at all, stop working at that moment. If a client does not reauthorize by the deadline in Amazon's notice, you lose access until the client starts a new authorization.
Amazon also closed the workaround. Its page on role eligibility for service providers says some Seller Central roles are reserved for the seller's own employees, and that an outsider cannot obtain them by being added as an employee or by any other method. The only supported route for anyone outside the seller's organization is SPP.
So get your roles approved before Amazon writes to your clients: while approval is pending, a seller sees every permission greyed out.
How an agency registers
Amazon's onboarding guide lists eight steps, the first of which is simply reading how the permission flow works. The requirements behind the rest: a legitimate business that serves Amazon sellers, a government-issued ID, business registration documents and bank statements for the company check, and a business model that fits Amazon's data protection rules.
- Create one SPP account for the company. One administrator registers on behalf of the whole business and chooses "I'm a Service Provider". If people already work in client accounts as secondary users, the administrator should sign up with the email address they use for Seller Central, because that address becomes the login for both systems.
- Verify identity. The identity guide asks for a government photo ID and a proof of address, such as a bank or card statement issued within the last 180 days, followed by an online identity check; the migration guide describes it as video verification. Names, dates and numbers must match the documents exactly, and the form cannot be edited after submission.
- Describe the service. On the Service Permissions form you pick one service category for the first submission; more can be added later with Add a service. You describe use cases as specific functions within that category and answer security questions about how you handle, share and protect Amazon data.
- Request roles. For each Seller Central role you choose None, View, Edit or Admin. Amazon's advice is to request only what the category needs, start small if unsure, and be ready to justify every role. Roles that expose personal data need extra detail on why you need it, how it is used and how it is protected.
- Invite employees. Each person joins the company account by invitation and completes their own identity check. Nobody creates a personal account.
- Connect sellers with an authorization link copied from the portal, or let them authorize you from your SPN listing.
- List the service in SPN, covered below.
What Amazon reviews, and how long it takes
Amazon does not publish a scoring rubric, but its pages show what it reads. The website guidelines apply to service providers as well as public developers, and several are stricter than agencies expect:
- the site must be public, finished, served over HTTPS and readable without a login;
- it must show your company name and at least one direct contact method;
- it must carry a privacy policy that covers how data is collected, used, stored, shared and deleted;
- it must state a pricing structure, and quote-based pricing should be described as such, ideally with sample scenarios;
- no unverifiable claims such as "best" or "#1", and nothing that suggests an endorsement by Amazon.
The rest of the review is the fit between category, use cases and requested roles. An advertising agency asking for order roles without a reason invites questions.
Timing: the role request page says review usually takes at least two weeks, other pages say up to ten business days, and the troubleshooting answer says to plan for five to ten. Plan for the longest. While a request is under review you cannot edit it. If Amazon asks a question through the support case, you have five days to answer; if you miss that window, your access level simply stays where it was. A denial can be appealed by submitting the request again with corrected information.
Getting listed
A listing requires at least one approved role. The listing guide splits categories in two:
- Self-service listing for Account Management, Advertising Optimization and Compliance. You write the listing yourself in SPP: name, category, contact and business details, a description and capabilities in plain language without marketing terms, and one to three banners between 1000 and 2000 pixels wide and 300 and 500 pixels high, in JPEG or PNG. Amazon reviews most listings within five to seven business days and usually publishes later edits within 24 hours.
- Guided listing for every other category. An Amazon representative contacts you through a support case and collects company details, logo and banners, a questionnaire and your specialties.
PPC and full-service agencies usually land in a self-service category, so write the listing as the guide asks: capabilities and measurable outcomes, not adjectives.
SPN and SP-API are two different permissions
An approved SPN role lets your people work inside a client's Seller Central. It does not let software call the Selling Partner API. For dashboards, automated reports or tools of your own you also need a developer profile and an application, which Amazon reviews separately. The same SPP account can hold both: under Settings, Solution Type Setup, you can tick Offer Services and Build applications together.
The developer side comes in two shapes, set out in Amazon's registration overview:
- Private. For applications that integrate only your own company. They are self-authorized, allow ten self-authorizations, and in Seller Central require a Professional selling account. A private application in the agency's own account is meant for the agency's own business, not for client accounts; where a client wants its own integration, it can be registered in the client's account.
- Public. For applications that serve other sellers, who authorize them through OAuth. Under the SPP agreement a public application has to appear in the Selling Partner Appstore. Before it does, a seller application can collect at most 25 OAuth authorizations; vendor applications have no such ceiling.
Restricted roles raise the bar on the developer side too. Five roles are marked restricted because they expose personal or sensitive data: the two tax roles (invoicing and remittance), Direct-to-Consumer Shipping, Selling Partner Support, and Professional Services. For a public developer that means a website review, a developer profile assessment and a data security assessment, including an architecture review with Amazon's SP-API Solutions Architecture team that can involve a screen-shared demo. Our PII access page describes our work on those reviews, and the guide to registering an SP-API application covers the form itself.
Build your own app, or use a data layer
Once the people side is settled, the question is how much software the agency should own. Four realistic setups:
- No API. Your team works in Seller Central under SPN authorization. Fine for small books of clients and hands-on services.
- A private application per client, registered in each client's account. Each client stays the developer of record, which some enterprise brands prefer, but you now maintain one integration per client.
- Your own public application. One OAuth flow for every client, an Appstore listing, and the full review. This is the route when the tool itself is part of what you sell, or when the logic is too specific to buy.
- A data layer. Someone else holds the Amazon applications and keeps the data fresh; you consume it.
The cost of option three is rarely the first API call. It is the review, rate limits, restated reports and deprecations; our Seller Central API guide lists what is being switched off now.
For option four, DataDoe, which our team engineers, is built with agencies in mind: each client opens an invitation link and approves its Seller Central, Vendor Central and Amazon Ads accounts on Amazon's own consent screen, so the agency never holds a client login, and the agency sets every client account to read-only or to read and write. Its page for agencies shows that flow, while its article comparing a data layer with raw SP-API sets the two approaches side by side.
A short checklist before you apply
- Pick the administrator and the email address that will become their login for SPP and Seller Central.
- Collect the ID, a proof of address under 180 days old and the business registration.
- Fix the website first: pricing structure, privacy policy, contact method, no superlatives.
- Map each service to one SPN category and the smallest set of roles it needs, and list every employee who will need an invitation.
- Decide separately whether you need API access, and if so, private or public.
Next step
Since 2020 Deltologic has built software on Amazon's APIs. If you are planning your own reporting or automation on top of client accounts, our page for agencies and marketplace integrations describe how we work. Send us your setup: how many client accounts, which marketplaces, and what you want software to do that your team does by hand today.
Frequently asked questions
What is Amazon SPN?
SPN is Amazon's Service Provider Network, a directory in Seller Central under Apps and Services, Explore Services, where sellers find third-party providers in eighteen categories, from account management and advertising optimization to taxes and translation. Sellers contract with the provider directly.
Is the Amazon Solution Provider Network the same as SPN?
Amazon has no program by that exact name. The Service Provider Network is the directory sellers browse; the Solution Provider Portal is where service providers and SP-API developers register, get roles approved and receive seller authorizations. In 2026 joining SPN runs through the portal.
How long does SPN approval take?
Amazon's pages give different figures: role review usually takes at least two weeks according to the registration guide, and up to ten business days according to other pages. A self-service listing is then reviewed in five to seven business days. Questions from Amazon must be answered within five days.
Does joining SPN give an agency SP-API access?
No. An approved SPN role lets your people work in a client's Seller Central. Calling the Selling Partner API needs a developer profile and a private or public application, which Amazon reviews separately, although both can sit in the same Solution Provider Portal account.