How should sellers offboard an Amazon service provider?
Separate the Seller Central authorization from the commercial relationship. Map the provider’s approved roles, countries, data, integrations, cases, campaigns, reports, listings, shipments, and recurring operations. Decide what must be completed, transferred, paused, or replaced before account access ends.
Amazon states that removing a service provider’s access is immediate and can stop automations or ongoing services, while removal does not cancel a separate contract or service request. Use a controlled cutover rather than treating the Remove action as the entire offboarding process.
Build an access and dependency register
- Record the provider’s legal name, service, authorization owner, start date, current expiration, countries, roles, and data scope.
- List automated processes, API or app dependencies, scheduled reports, campaigns, feeds, cases, reimbursement work, and shared evidence repositories.
- Assign a new internal owner for each active task, pending deadline, report, credential-free workflow, and decision history.
- Export only the business records the seller is entitled to retain and document the handoff location and retention owner.
- Separate Seller Central access removal from contract termination, invoices, open deliverables, and external data-deletion obligations.
- Define the cutover time, rollback contact, monitoring window, and proof that removal completed.
Transfer operations before removing access
Complete or reassign time-sensitive tasks first: open cases, shipment work, order exceptions, advertising changes, catalog submissions, compliance deadlines, and financial reconciliations. Verify that internal users can reach the necessary pages and that replacement automations use authorized ownership.
At the approved cutover, remove the provider through Manage Services. Then confirm that the provider no longer appears with active access, monitor critical queues and integrations, and record any failed process. If access must later be restored after removal or expiry, follow Amazon’s current authorization path rather than assuming the old authorization can be reactivated.
Use a service-provider offboarding checklist
- The seller account owner or administrator has approved the provider and scope being removed.
- Roles, countries, data, automations, open cases, deadlines, and dependencies are inventoried.
- Internal owners and replacement workflows are active before immediate access removal.
- Seller Central authorization and the external contract are handled as separate controls.
- Removal evidence and a post-cutover review of orders, feeds, ads, cases, and reports are preserved.
- Reauthorization is used only when the current Amazon workflow and active authorization permit it.
Scope and exceptions
Employee users, service providers, Selling Partner Appstore applications, SP-API developers, Brand Registry users, advertising users, and external contracts are not interchangeable access types. Removing one Seller Central provider authorization may not revoke separate permissions in other Amazon services or third-party systems.
Review Amazon’s current [service-provider removal guidance](https://sellercentral.amazon.com/help/hub/reference/external/G9GR9Q4U6U5DPMKW?locale=en-US), [reauthorization guidance](https://sellercentral.amazon.com/help/hub/reference/external/G3782ZCL2U67NSTB?locale=en-US), and the live Manage Services page. Do not share primary credentials or record authentication secrets in the offboarding file.
Related Amazon seller guides
- [Audit Seller Central user permissions](https://amazonmargincalculator.cloud/blog/amazon-user-permissions-audit)
- [Choose an Amazon service provider with a verifiable scope](https://amazonmargincalculator.cloud/blog/amazon-service-provider-network-selection)
- [Pilot an SP-API integration without losing data control](https://amazonmargincalculator.cloud/blog/amazon-sp-api-integration-control-pilot)