SP-API Migration Frequently Asked Questions

General Migration Topics

Is it mandatory to migrate from Amazon MWS to SP-API?

Select to expand the answer.

You are only required to migrate to SP-API if your integration supports a use case that has been (or is about to be) deprecated in Amazon MWS.

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 this use 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.

If you do not support these use cases, no action is required at this time.

I see several due dates posted for migrating from MWS to SP-API. How do I know which ones apply to my application?

Select to expand the answer.

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 Seller Central Partner Network (ASCPN). We will be sending direct communication via email and Seller Central cases to all public MWS developers affected by this, which will help confirm the actions your organization needs to 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

If you have a private application that is only used by your organization and it is not authorized by other Amazon Selling Partners, you are not required to migrate to SP-API this year.

Is Amazon MWS going away? If so, when?

Select to expand the answer.

Yes, over time the legacy Amazon MWS sections will be deprecated and you will need to migrate to SP-API to continue service. Amazon has chosen a phased deprecation for Amazon MWS, and we will notify you when we deprecate sections of Amazon MWS and give you time and resources to help with migration.

What does "support for Amazon MWS Orders, Reports, and Merchant Fulfillment Network (MFN) sections will be discontinued" mean?

Select to expand the answer.

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.

Private applications can continue to successfully call the specified sections after July 31, 2022 and are not required to migrate at this time.

I am a Selling Partner with a private Amazon MWS application used only by my organization, and want to integrate with SP-API. How do I do this?

Select to expand the answer.

Please note, the Migration notice is currently directed to third-party developers with public Amazon MWS or SP-API applications. Selling Partners with private applications are not required to make these updates by July 31, 2022. However you can still take action to integrate at this time if you chose to.

The steps for a private application to integrate with SP-API are not too different from the guidance provided for third-party applications. Follow the same steps provided in the Amazon MWS to Selling Partner API Migration Guide, excluding Steps 6 and 7.

Note: In Step 4. Implement an authorization workflow, you'll use the Self authorization workflow mentioned in the Selling Partner API Developer Guide.


Account and Access Topics

My Seller Account has been deactivated. How can I proceed with migration?

Select to expand the answer.

Please contact Seller Central Support to request your account be re-activated at Get Support.

I am not able to see the “Edit app”, “Developer apps”, or “Register app” options to select in my Seller Central account. What do I do?

Select to expand the answer.

Please ensure the Seller Central account you are logged into is the account your MWS/SP-API application is associated with. This should be the account your organization submitted for your Developer Registration and Assessment Form / Developer Profile.

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 Selling Partner API. Individual level accounts are not eligible. You can view your selling plan type and the marketplace information under “Your Services” in Account info on your account information page.

How do I apply for SP-API access or update the SP-API roles I have access to?

Select to expand the answer.

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.

I am unable to move forward in my migration because my Developer Profile case or Amazon Seller Central Partner Network (ASCPN) Listing case is still pending review.

Select to expand the answer.

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

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

I am trying to update my Amazon Seller Central Partner Network (ASCPN) Listing, but my app is showing as “Suppressed”. Can it be reactivated?

Select to expand the answer. 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”.

I received an email about migration requirements from the email address “[email protected]” but am not able to reply to this email alias. What do I do?

Select to expand the answer.

Please note that the email alias [email protected] 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.

I was informed that I may have received a message about migration requirements in my Seller Central account. How can I access my support case log?

Select to expand the answer.

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.

I am aware that I need to set up an AWS account, but do I need to pay for this account?

Select to expand the answer. AWS IAM service has no cost associated to it. AWS account setup requires you to enter a payment method, however 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.

Migration Technical Support Topics

A list of General SP-API FAQs and troubleshooting solutions is available here.

How do I convert my existing app to include the new SP API?

Select to expand the answer.

In Step 3 of the Amazon MWS to Selling Partner API Migration Guide, when you select Edit App you can choose MWS and SP-API as the API Type for hybrid scenarios.

Amazon MWS authorizations are not affected when you make this selection. If you decide to create a new app, it can only integrate with SP-API.

Note: If you recently submitted an update to your Appstore Listing details and do not see the Edit App button; your Appstore Listing may be under review or pending translation. This will prevent you from making any updates until we post your updated Listing details.

Will current MWS API requests continue working if I switch the app to the hybrid application (Amazon MWS and SP API)?

Select to expand the answer.

Yes, Amazon MWS operations will continue to work with a hybrid app. Even after we publish the hybrid app, the only thing that changes is the authorization workflow that switches to Oauth from AppStore and nothing affects the MWS calls or authorizations. 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.

Can I use the reports_2021-06-30 or the feeds_2021-06-30 models for my migration? Is the new version of Reports API or Feeds API available in production?

Select to expand the answer.

The reports_2021-06-30 and the feeds_2021-06-30 APIs are available to use in applications.

See 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.

I need help on one of the steps listed in the Migration Guide, what other resources are available to me?

Select to expand the answer.

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

Are Migration documents in GitHub available in other languages?

Select to expand the answer.

We have various translations available for migration documents in different languages including

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

These documents are posted here.

Are there any additional resources available for Chinese developers?

Select to expand the answer.

Yes! From now through December 31, 2022, Amazon Web Services (AWS) 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 AWS account: http://s.v-event.cn/v8/114

To request support from AWS China, please visit the SP-API migration solution website and fill out the contact form: https://aws.amazon.com/cn/campaigns/sp-api-contact-us/

For more information, you can call the AWS China support team at: +86 1010 0866.

I am receiving an error code, how do I proceed?

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

Can I set up a test application to begin SP-API development in a sandbox setting?

Select to expand the answer. Yes, you can create a secondary application and can designate it as sandbox or test app.

📘

Didn't help?

If you didn't see your question or the answer didn't resolve the issue you're encountering, open a Support Case and we'll help you troubleshoot.