Migration FAQ

MWS will no longer be available for use after March 31, 2024. Amazon has chosen a phased deprecation for Amazon MWS, and we have publicly announced migration due dates for both third-party public app developers and private app developers.

SP-API offers all developers a number of improvements over Amazon MWS, such as modernized, JSON-based REST API design standards, OAuth2.0 selling partner authorization using Login with Amazon, and a test endpoint - the most requested feature in MWS. In addition to all legacy functionality previously provided in Amazon MWS and new API capabilities for sellers, SP-API supports the first ever APIs for Amazon vendors – all through the same API control plane and authorization mechanisms. Going forward all new API functionality will be built in SP-API, with updates to MWS only to support business critical changes until MWS is deprecated. Having all developers integrated with SP-API will provide the best experience for both Selling Partners and developers.

Refer to the What is the Selling Partner API? for more information about SP-API.

Yes. Private MWS Developers who own Amazon MWS Developer ID and Access Keys and are using MWS Merchant Fulfillment, Orders, or Reports API sections must migrate these sections to SP-API by August 31, 2023 to prevent business disruption. Additionally, private MWS developers using all other MWS API sections must be fully migrated to SP-API by March 31, 2024.

Private developers who decide to not to integrate with SP-API can authorize a third-party application from the Amazon Selling Partner Appstore to replace their Amazon MWS private integration.

Yes. The first phase of Amazon MWS deprecation began April 6, 2021, for Orders, Reports, and MFN sections for all public applications authorized by selling partners in the Marketplace Appstore. You must migrate by July 31, 2022 to prevent business disruption.

Additionally, all public applications authorized by Selling Partners, using the MWS Products API, must migrate to SP-API by September 30, 2022.

All public applications authorized by Selling Partners, using all other MWS API sections, must be fully migrated to SP-API by December 31, 2022.

A public developer builds and offers publicly available applications that are used by other companies.

A public application is a publicly available application that is used by other companies.

1. Log in to your Amazon selling account on Seller Central as the primary account holder. Choose Settings and then choose User Permissions.
2. Choose Amazon MWS Developer Access Keys and then choose Visit Developer Credentials.
3. On the Developer Central page, choose MWS credentials and then choose View.

The Amazon Selling Partner Appstore is a one-stop shop where sellers can discover trusted apps to help grow and manage your business. The Selling Partner Appstore connects sellers with Amazon approved third party software partners who can help you start and grow your business online from automated pricing to listing tools. Many apps focus on automating previously time-consuming and tedious daily tasks like product research, filling out tax forms, or building customized reports.

If you have a private Amazon MWS Developer ID and Access Keys that call the Merchant Fulfillment (MFN), Orders, or Reports API sections, then you must create and operate a private Selling Partner app to integrate these sections. This must be completed by August 31, 2023.

Note: If you have a hybrid or SP-API based private application that requires restricted data, you must update your application to use a Restricted Data Token (RDT) via the Tokens API by August 31, 2023. You can view a list of affected operations here.

If you have a private Amazon MWS Developer ID and Access Keys that use any other MWS API sections, then you must create and operate a private Selling Partner app that is integrated with SP-API by March 31, 2024. This includes applications using the following MWS API sections:

* Feeds API
* Finances API
* Fulfillment Inbound Shipment API
* Fulfillment Inventory API
* Fulfillment Outbound Shipment API
* Products API
* Recommendations API
* Sellers API
* Subscriptions API
* Push Notifications Schemas

Private developers who decide not to integrate with SP-API can authorize a third-party application from the Amazon Selling Partner Appstore to replace their Amazon MWS private integration.

Note: In 2022, we are focusing migration efforts on third-party public applications that are authorized by Amazon Selling Partners that may also be listed in the Amazon Selling Partner Appstore. More information about third-party migration can be found in this announcement.

In 2022, we are focusing migration efforts on third-party public applications that are authorized by Amazon Selling Partners that may also be listed in the Amazon Selling Partner Appstore. We will send direct communication via email and Seller Central cases to all public MWS developers affected by this, which will help confirm the actions your organization must take. Below are the conditions that apply to public MWS developers who will need to migrate to SP-API:

• If you have an Amazon MWS-based public application that uses the Merchant Fulfillment Network (MFN), Orders, or Reports API, you must update your application to integrate these sections to SP-API by July 31, 2022.

• If you have a hybrid or SP-API based public application that requires restricted data, you must update your application to use a Restricted Data Token (RDT) via the Tokens API by July 31, 2022. You can view a list of affected operations.

• If you have an Amazon MWS-based public application that uses the Products API, you must update your application to integrate with Catalog Items and Listings Items in SP-API by September 30, 2022.

• If you have an Amazon MWS-based public application that uses any other MWS API section, you must update your application to be fully integrated with SP-API by December 31, 2022. This includes applications using the following MWS API sections:

  • Feeds API
  • Finances API
  • Fulfillment Inbound Shipment API
  • Fulfillment Inventory API
  • Fulfillment Outbound Shipment API
  • Recommendations API
  • Sellers API
  • Subscriptions API
  • Push Notifications Schemas

Private MWS Developers: For information about private developer migration, refer to Amazon Marketplace Web Service (MWS) end-of-life dates

Discontinuing support means that API calls from private Amazon MWS Developer ID and Access Keys that use the specified sections of Amazon MWS, will not be successful after August 31, 2023.

Calls to all other Amazon MWS sections (operations and paths) will continue to be successful on and after August 31, 2023, as they are today.

Discontinuing support means that API calls from public applications using the specified sections of Amazon MWS will not be successful after July 31, 2022.

Calls to all other Amazon MWS sections (operations and paths) will continue to be successful on and after July 31, 2022, as they are today.

Visit the Amazon Selling Partner Appstore and type in keywords to search for applications based on name or supported functionality. You can also refine your search by languages supported, Marketplaces supported, pricing type, and other search filters. On the homepage, you can also see a list of categories to explore in addition to personalized app recommendations.

If you have access to the original code files of your application, you can contract another external developer company to help you migrate your MWS app to SP-API, or request that they help create a new app with SP-API.

Additionally, you have the option to find a third-party app solution to replace your private Amazon MWS integration. You must take action before the posted due dates, based on your MWS API usage, to avoid business disruption. We encourage you to visit the Amazon Selling Partner Appstore, to review over 2,000 vetted apps that offer various automation solutions for your business needs.

Your app will continue to work with MWS as usual during migration. We will not remove MWS access from your account until the posted due dates, or until you confirm you have completed the necessary actions to migrate/replace your MWS app functionality (whichever comes first).

Access to MWS Merchant Fulfillment Network (MFN), Orders, and Reports API selections will be unavailable for all private developers after August 31, 2023.

All other MWS API sections will be unavailable for all apps after March 31, 2024.

If you decide not to create and own a private Selling Partner app, or do not want to migrate to SP-API, you also have the option to find a third-party app solution to replace your current business automation services. We encourage you to visit the Amazon Selling Partner Appstore, to review over 2,000 vetted apps that offer various automation solutions for your business needs.

One other option you can take is to search online for external companies that offer contracted developer services to help you migrate your app from MWS to SP-API, or create a new private SP-API app.

AMTU/Listing Loader will maintain access to MWS for all functionality until August 31, 2023. After this date, the AMTU tool will be deprecated. More information will be posted on the AMTU Help Page as it becomes available.

Note: Important Information for AMTU users submitting Automotive Aftermarket Catalog Exchange Standard (ACES) fitment feeds:
Automotive selling partners and third party data providers who submit fitment data through AMTU need to migrate to a new tool for ACES feed submission on or before 04/01/2023. Please follow the instructions on the Providing and adding fitment data page.

If you use the MWS Reports API to get Amazon Pay and Amazon Pay related reports, you are not required to migrate to SP-API. We have released the new Amazon Pay Reports API, which replaces the previous Amazon MWS Reports API. If you currently access Amazon pay reports via the MWS Reports API, you must migrate to the new Amazon Pay Reports API. For detailed instructions, refer to Migrate from MWS Reports.

Communications will be sent later this year for any additional actions Amazon Pay developers must take.

If you have a hybrid (MWS/SP-API) application:

1. We will convert your hybrid SP-API app to a SP-API only app. Note: Your app must be in Published status.
2. We will block your ability to accept new seller MWS authorizations after your app is converted to SP-API only. Note: This action will not be taken if your app type is still hybrid.
3. We will remove your access to all MWS API sections.

Note: Alternatively, you can use the Convert a Public Amazon MWS Application into a Selling Partner API Application tutorial to convert your application from hybrid to SP-API. Please allow up to 15 business days for this change to publish.

If you have a MWS application:

1. We will block your ability to accept new seller MWS authorizations.
2. We will remove your access to all MWS API sections.

We’ll notify you 2 days before we take make any modifications to your MWS access, and you'll receive a confirmation message when changes are complete.

Please contact Selling Partner Support to request your account be re-activated at Get Support.

If you already have access to MWS, you do not need to apply for access in SP-API, unless you want access to new roles in SP-API.

All existing MWS developers, with active MWS keys and assigned access roles in MWS, already have access to the equivalent roles in SP-API, allowing you to get started with your migration.

If you want to add new SP-API roles to your account, you can submit an update to your SP-API Developer profile anytime by visiting the Seller Central URLs page and then choosing the URL for your region. Choose Appstore, then Develop Apps, View Profile, and finally choose Register to add roles to your account.

You can also learn more about SP-API roles and find more information to get started with your integration through video guides in Seller University.

Submit or update your Developer Profile at the developer registration page.

You can also learn more about SP-API roles and find more information to get started with your integration through video guides in Seller University.

You should also be logged in as the primary user of the account. Secondary users of the account may not have the same permissions as determined by the primary user.

You must also confirm your account is currently a Professional Selling Account. Only Professional Selling Accounts can register to develop or integrate with MWS or SP-API. Individual level accounts are not eligible. Navigate to your account information page and select Your Services in Account info to view your selling plan type and the marketplace information.

Depending on the information you submitted in your Developer Profile, it may take our Developer Support teams several days to respond after completing the evaluation. Continue to monitor the case for updates.

Note for public developers: if you recently submitted a new Selling Partner Appstore Listing, you may not be able to make additional updates until the details have been reviewed by our Developer Support team and published.

The AWS Identity and Access Management (IAM) service has no cost associated to it. AWS account setup requires you to enter a payment method, however you will not incur any cost by using IAM. If you are going to use any other AWS resources however, those will incur a charge per AWS pricing.

You may edit an app that is in Suppressed status by selecting Edit app from the drop-down menu. Once you submit your updates, your app listing status will change to Edit pending review.

All existing MWS developers with active MWS keys already have access to the equivalent roles in SP-API which allows you to start migration. The steps for a private application to integrate with SP-API are provided in the tutorial Create a private Amazon MWS application into a Selling Partner API application.

The Amazon Selling Partner Appstore, is available without logging in, allowing prospective sellers to discover solutions. Current Amazon sellers will also be able to find the Amazon Selling Partner Appstore in the top menu of the Seller Central navigation bar and will be directed to the store by selecting Find Apps.

Visit the Amazon Selling Partner Appstore and enter in keywords to search for applications based on their name or supported functionality. You can also refine your search by Average Customer Review ratings, languages supported, Marketplaces supported, pricing type, and other filters. On the Selling Partner Appstore home page, you can also see a list of categories to explore in addition to recommended apps your business may find useful.

You can select the detail pages for these app to further learn about the features and descriptions of the app services provided.

Once you find an app that works for your business, choose Authorize Now on the top right corner of the app detail page. You are directed to a confirmation page you must submit to allow the third-party app access to your Selling Partner account and related data for your business automation needs.

You may de-authorize an app at any time in the Manage your apps page of your Seller Central account.

Refer to Viewing your application information and credentials for more information.

Note that the email alias dev-reg-notice@ does not accept incoming emails. You can reply to the message through the case in your Seller Central account that is associated with your MWS application.

To access your case log, sign into the Seller Central account that is associated with your Amazon MWS Access Keys. On the Seller Central gateway page, at the Manage Your Case Log widget, select View your case log. Note that you must be the primary account holder to view this page.

For more information, see the Seller Central Case Log Guide.

To access your case log, sign into the Seller Central account that is associated with your Amazon MWS Access Keys. On the Seller Central gateway page, at the Manage Your Case Log widget, select View your case log. Note that you must be the primary account holder to view this page.

For more information, see the Seller Central Case Log Guide.

If your application is actively retrieving data from the MWS Merchant Fulfillment, Orders, and Reports API sections, you will continue to have access to these sections through August 31, 2023. After this date, you will receive a notice informing you about when your account will officially lose access to retrieve data from these three sections. After this date, we will send a notice informing you about when your account will officially be blocked from retrieving data from these three sections.

If you submitted a Migration Plan Form, we will not block access to MWS without further confirmation from you.

Your access will only be removed before the August 31, 2023 migration due date in the following scenarios:
• You have confirmed that you have completed migration and/or confirmed your app no longer requires access to the Merchant Fulfillment, Orders, and Reports API sections sections.
• You have not actively retrieved data from the Merchant Fulfillment, Orders, or Reports API sections for over 90 days. As a reminder, you should only retrieve information that is necessary for your app's functionality. You may refer to our Acceptable Use Policy for more information.

In all scenarios we will send a notice, a minimum of 14 days ahead of time, about changes to the Seller Central account that is associated with your MWS credentials.

The Selling Partner API on AWS Quick Start configures an AWS Identity and Access Management (IAM) role to streamline your SP-API onboarding. In addition, it provides a sample AWS Lambda function to demonstrate AWS best practices for SP-API integration. After deployment, use the sample function to test connectivity to SP-API endpoints.

We launched several videos in Seller University that provide further guidance on the migration steps listed in the Migration Guide.

For the accounts your company has in other regions, you can authorize the created app without the need of connecting with Developers ID (which are no longer used by SP-API), using the Seller Central authorization workflow. Refer to Registering your Application for more information.

Review the SP-API Errors FAQs page for a list of common error codes and troubleshooting solutions.

Yes, you can create a secondary application and can designate it as sandbox or test app. Refer to Selling Partner API sandbox for more information.

Refer to the Tutorial: Create a private Selling Partner API application

Refer to the Tutorial: Convert a public MWS application into a Selling Partner application

Yes, Amazon MWS operations will continue to work with a hybrid app. After you publish your hybrid app, MWS calls and authorizations continue to function; however, the authorization workflow changes to an OAuth authorization workflow that the selling partner initiates from the Amazon Selling Partner Appstore. Existing Amazon MWS authorizations can be migrated to SP-API using the Selling Partner API for Authorization only after the hybrid app is published. More information is available in the Authorization API Use Case Guide.

Refer to the Reports API Reference v2021-06-30/Reports API Use Case Guide v2021-06-30 or the Feeds API Reference v2021-06-30/Feeds API Use Case Guide v2021-06-30 for more information.

• German
• Chinese
• Japanese
• French
• Italian
• Spanish
• Portuguese
• Turkish
• Dutch

These documents are posted in GitHub.

Yes! From now through December 31, 2022, Amazon Web Services China will provide free one-to-one consultation for customers who speak Chinese and are interested in migrating their app integration to SP-API. Our technical experts will help tailor a migration solution suitable for your business development.

You can also get a $200 credit once you sign up for an Amazon Web Services account.

To request support from Amazon Web Services China, visit the SP-API migration solution website and fill out the contact form.

For more information, you can call the Amazon Web Services China support team at: +86-1010-0866.

Starting July 1st, 2023, extension requests can be submitted by selecting the 'Create a case with Developer Support' option on the Get Support page and selecting the API type 'Migration Extension Request' in the form. Your business will need to provide detailed information to explain the reason for the request. Once you submit the form, a support case will be created within your Seller Central account. This case will be used to follow up on the request, including asking for more information if needed. We may respond to your case within five business days.

⚠️

Important

• Submitting an extension request does not guarantee an approval. Requests are evaluated on a case by case basis and may be denied or partially approved.
• Extension requests should only be submitted one time. Carefully evaluate the time period for which you will request the extension, and assess the actions you can realistically complete during this time frame.
• If you have multiple MWS accounts, you only need to submit one extension request form. If you have multiple Amazon accounts with MWS Developer IDs associated to your business that this request should also apply to, you can include those additional Developer IDs within the form.

If you were not able to complete your migration to SP-API for these sections and need more time to migrate, you have until October 1, 2023 to submit an extension request to temporarily regain access to these sections.

To submit an extension request, visit the Get Support page, choose Create a case with Developer Support, and then select the API type Migration Extension Request on the form.

Your business will need to provide detailed information to explain the reason for the request. Once you submit the form, a support case will be created within your Seller Central account. This case will be used to follow up on the request, including asking for more information if needed. We will respond to your case within five business days.

If the extension is approved, access to these MWS sections will be reinstated within five business days.

⚠️

Important

• Submitting an extension request does not guarantee an approval. Requests are evaluated on a case-by-case basis and may be denied or partially approved.
• Only submit one extension request at a time. Carefully evaluate the time period for which you will request the extension, and assess the actions you can realistically complete during this time frame.
• If you have multiple MWS accounts, you only need to submit one extension request form. If you have multiple Amazon accounts with MWS Developer IDs associated with your business, that this request should also apply to, you can include those additional Developer IDs within the form.

Extension timelines should be a list of any organizational and technical tasks that your business will take to complete migration within the requested extension time frame. This may include internal meetings, sprints, code development, testing periods, and launch milestones. Remember to add a completion date for each task you include.

If you receive this error message when trying to submit an extension request, the seller account you are using to submit the request falls under one of the following categories:

• MWS credentials for this account may have been deactivated due to inactivity in accordance with the Acceptable Use Policy.

• The account has MWS credentials, but is not able to retrieve data from MWS as it does not have active MWS self-authorization in accordance with the Acceptable Use Policy.

• The account only uses the MWS Reports API to get Amazon Pay and Amazon Pay related reports, and is not required to migrate to SP-API. Amazon Pay users will not be affected by MWS access removal after the August 31, 2023 migration due date. If you access Amazon Pay reports via the MWS Reports API today, you must migrate to the new Amazon Pay Reports API. For detailed instructions, refer to Migrate from MWS Reports.

If you have another Amazon seller account with active MWS credentials assigned for which you would like a migration timeline extension, you must log in to that account to submit this form.

To find MWS credentials assigned to your seller account, log in to Seller Central and navigate to Developer Central.

If you need access to data for Merchant Fulfillment, Orders, and/or Reports functionalities, you can authorize a third-party app from the Selling Partner Appstore, develop an app with SP-API, or use data from Seller Central.

No, after August 31, 2023, the AMTU tool will be deprecated. AMTU/Listing Loader will maintain access to MWS for all functionality until August 31, 2023. More information is available on the AMTU Help Page.

To avoid any impact to your business, you can substitute the functions using AMTU by authorizing a third-party app from the Selling Partner Appstore, developing your own SP-API app, or using data on Seller Central.

No, we are not evaluating extension requests for this due date. We will post an update if this becomes available in the future.

All cases are evaluated on a case by case basis based on the information provided. Your business should plan accordingly for the due date provided in the case response. If you feel there was information missing from your original request, do not open a new case. You may comment on your existing extension request case within five days to provide this information, however there is no guarantee of a different outcome, and multiple requests may be denied.