Seller Forums
Sign in
Sign in
user profile
Sign in
user profile
Jeniffer_Amazon

Important Notice: Third-party developers using Amazon MWS Orders, Reports, and Merchant Fulfillment API sections must migrate to Selling Partner API by July 31, 2022

UPDATE: This announcement has been updated to reflect the extended migration date of July 31, 2022.

What is changing?

As we mentioned in our October 2020 Selling Partner API (SP-API) launch announcement, all public applications will need to migrate to the new service. Effective July 31, 2022, all third-party developed applications authorized by selling partners in the Marketplace Appstore (“public applications”) must be integrated with the Selling Partner API (SP-API) and support for Amazon MWS Orders, Reports, and Merchant Fulfillment Network (MFN) sections will be discontinued.

Developers whose SP-API applications use Direct-to-Consumer Fulfillment, Tax, Shipping, or Reports use cases must also use a new access protocol (a Restricted Data Token) for some operations and report types in the Orders, MFN, Shipping, and Reports sections. See the ‘Use case details’ below for the specific operations and report types affected.

We are focused on providing the necessary information, tools, and assistance needed to successfully migrate your app to SP-API. If your app needs to be migrated to SP-API, we will automatically create a support case for you to communicate with us directly and send you a follow up email with additional details.

We’ve also been listening to developer feedback and have re-evaluated the requirement for client-side encryption for the Reports and Feeds APIs. We have determined the existing server-side encryption we provide meets or exceeds the industry standard and will be removing the client-side encryption requirement to access reports and submit feeds in new versions of the APIs; making integrating with SP-API easier. Developers who have integrated with the current version of the Reports and Feeds API can continue without interruption.

Why is this changing?

The launch of SP-API represents the next generation API for programmatic access to Amazon features for sellers. All new development is occurring in SP-API and this includes several enhanced data protection and security features. Amazon takes protecting customer data seriously. This change is being made to ensure developers are using the latest technology and features for the benefit of both sellers and customers.

Who is affected?

Amazon MWS developers whose applications are authorized by selling partners in the Marketplace Appstore using the Orders, Reports, or Merchant Fulfillment APIs.

SP-API developers whose applications are authorized by selling partners in the Marketplace Appstore using the Orders, Reports, Shipping, or Merchant Fulfillment APIs.

Developers using other Amazon MWS sections or sellers who directly integrate with Amazon MWS do not need to take action at this time.

Which marketplaces are affected?

This affects all marketplaces.

What action is required?

If you have an Amazon MWS-based application that is affected by this change, you must update your application to integrate with the Selling Partner API (SP-API) by SJuly 31, 2022 to avoid service disruption.

If you have a hybrid- or SP-API based application that is affected by this change, you must update your application to use the Restricted Data Token (RDT) via the Tokens API by July 31, 2022 to avoid service disruption.

We recommend that you start integrating with SP-API immediately and complete your migration from Amazon MWS to SP-API as early as possible.

Use case details

Developers whose SP-API applications use Direct-to-Consumer Fulfillment, Tax, Shipping, or Reports use cases must also use the new Tokens API for select operations and report types.

These SP-API operations will require the use of the Restricted Data Token (RDT) via the Tokens API to make a successful API call:

  • Orders
    • getOrderBuyerInfo
    • getOrderAddress
    • getOrderItemsBuyerInfo
  • Shipping
    • getShipment
  • Merchant Fulfillment (MFN)
    • getShipment
    • cancelShipment
    • cancelShipmentOld
    • createShipment
  • Reports
    • getReportDocument (for specified report types)

The SP-API report types that will require the Restricted Data Token (RDT) are:

  • GET_AMAZON_FULFILLED_SHIPMENTS_DATA_INVOICING
  • GET_AMAZON_FULFILLED_SHIPMENTS_DATA_TAX
  • GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_SHIPPING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_INVOICING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_TAX
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_SHIPPING
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_INVOICING
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_TAX
  • GET_ORDER_REPORT_DATA_SHIPPING
  • GET_ORDER_REPORT_DATA_INVOICING
  • GET_ORDER_REPORT_DATA_TAX
  • GET_EASYSHIP_DOCUMENTS
  • GET_GST_MTR_B2B_CUSTOM
  • GET_VAT_TRANSACTION_DATA
  • SC_VAT_TAX_REPORT

All Amazon MWS Reports will be deprecated as previously mentioned. Accessing the correlating report types for these Amazon MWS reports in SP-API will require the use of the new access protocol via the Tokens API and Restricted Data Token (RDT):

  • _GET_AMAZON_FULFILLED_SHIPMENTS_DATA_
  • _GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_
  • _GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_
  • _GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_
  • _GET_FLAT_FILE_ORDERS_DATA_
  • _GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT_
  • _GET_GST_MTR_B2B_CUSTOM_
  • _GET_ORDERS_DATA_
  • _GET_VAT_TRANSACTION_DATA_
  • _GST_MTR_B2B_
  • _SC_VAT_TAX_REPORT_

These Amazon MWS report types will be deprecated and are not available in SP-API:

  • _GET_CONVERGED_FLAT_FILE_ORDER_REPORT_DATA_
  • _GET_CONVERGED_FLAT_FILE_SOLD_LISTINGS_DATA_
  • _GET_XML_ALL_ORDERS_DATA_BY_LAST_UPDATE_
  • _GET_XML_ALL_ORDERS_DATA_BY_ORDER_DATE_
  • _GET_XML_VAT_INVOICE_DATA_REPORT_

For more information

We are providing the following resources to aid your migration:

  • SP-API Migration Guide - This step-by-step guide is to help you migrate from Amazon MWS to SP-API.
  • SP-API Developer Guide - This guide has been updated to include the new access protocol in the Authorization section.
  • Tokens API Reference - This is a new reference for the Tokens API and includes the operations for the new access protocol (RDT).
  • Tokens API Model - This swagger model describes the operations you can use in the Tokens API.
  • Tokens API Use Case Guide - This is a new guide describing the new access protocol for the Direct-to-Consumer Fulfillment, Tax, Shipping, and Reports use cases.

These resources provide preview information about the new version of the Reports and Feeds API that will be released in Summer 2021 to help you create or adjust integrations that do not require client-side encryption for reports or feeds as you migrate to SP-API:

  • Reports API Model - This swagger model describes the operations you can use in the new version of the Reports API that will be released this summer.
  • Reports API Reference - This is the reference guide for the new version of the Reports API that will be released this summer.
  • Feeds API Model - This swagger model describes the operations you can use in the new version of the Feeds API that will be released this summer.
  • Feeds API Reference - This is the reference guide for the new version of the Feeds API that will be released this summer.

Frequently Asked Questions (FAQs)

I use a third-party application that is integrated with Amazon MWS. Does this impact me?

No, at this time there is no change or action needed from selling partners who have authorized a third-party application to use Amazon MWS on their behalf.

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

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

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

Is Amazon MWS going away? If so, when?

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.

Is the Amazon MWS Products section affected?

No, this change does not affect Amazon MWS Products section.

How can I get more information and stay up to date on SP-API?

Where can I ask questions of other developers already using SP-API?

Visit us on GitHub at https://github.com/amzn/selling-partner-api-docs/issues to view developer community questions about SP-API or post your own.

Open a support contact with Amazon via one of these links:

507 views
0 replies
Tags:Reporting
20
Reply
0 replies
There are no more posts to display
user profile
Jeniffer_Amazon

Important Notice: Third-party developers using Amazon MWS Orders, Reports, and Merchant Fulfillment API sections must migrate to Selling Partner API by July 31, 2022

UPDATE: This announcement has been updated to reflect the extended migration date of July 31, 2022.

What is changing?

As we mentioned in our October 2020 Selling Partner API (SP-API) launch announcement, all public applications will need to migrate to the new service. Effective July 31, 2022, all third-party developed applications authorized by selling partners in the Marketplace Appstore (“public applications”) must be integrated with the Selling Partner API (SP-API) and support for Amazon MWS Orders, Reports, and Merchant Fulfillment Network (MFN) sections will be discontinued.

Developers whose SP-API applications use Direct-to-Consumer Fulfillment, Tax, Shipping, or Reports use cases must also use a new access protocol (a Restricted Data Token) for some operations and report types in the Orders, MFN, Shipping, and Reports sections. See the ‘Use case details’ below for the specific operations and report types affected.

We are focused on providing the necessary information, tools, and assistance needed to successfully migrate your app to SP-API. If your app needs to be migrated to SP-API, we will automatically create a support case for you to communicate with us directly and send you a follow up email with additional details.

We’ve also been listening to developer feedback and have re-evaluated the requirement for client-side encryption for the Reports and Feeds APIs. We have determined the existing server-side encryption we provide meets or exceeds the industry standard and will be removing the client-side encryption requirement to access reports and submit feeds in new versions of the APIs; making integrating with SP-API easier. Developers who have integrated with the current version of the Reports and Feeds API can continue without interruption.

Why is this changing?

The launch of SP-API represents the next generation API for programmatic access to Amazon features for sellers. All new development is occurring in SP-API and this includes several enhanced data protection and security features. Amazon takes protecting customer data seriously. This change is being made to ensure developers are using the latest technology and features for the benefit of both sellers and customers.

Who is affected?

Amazon MWS developers whose applications are authorized by selling partners in the Marketplace Appstore using the Orders, Reports, or Merchant Fulfillment APIs.

SP-API developers whose applications are authorized by selling partners in the Marketplace Appstore using the Orders, Reports, Shipping, or Merchant Fulfillment APIs.

Developers using other Amazon MWS sections or sellers who directly integrate with Amazon MWS do not need to take action at this time.

Which marketplaces are affected?

This affects all marketplaces.

What action is required?

If you have an Amazon MWS-based application that is affected by this change, you must update your application to integrate with the Selling Partner API (SP-API) by SJuly 31, 2022 to avoid service disruption.

If you have a hybrid- or SP-API based application that is affected by this change, you must update your application to use the Restricted Data Token (RDT) via the Tokens API by July 31, 2022 to avoid service disruption.

We recommend that you start integrating with SP-API immediately and complete your migration from Amazon MWS to SP-API as early as possible.

Use case details

Developers whose SP-API applications use Direct-to-Consumer Fulfillment, Tax, Shipping, or Reports use cases must also use the new Tokens API for select operations and report types.

These SP-API operations will require the use of the Restricted Data Token (RDT) via the Tokens API to make a successful API call:

  • Orders
    • getOrderBuyerInfo
    • getOrderAddress
    • getOrderItemsBuyerInfo
  • Shipping
    • getShipment
  • Merchant Fulfillment (MFN)
    • getShipment
    • cancelShipment
    • cancelShipmentOld
    • createShipment
  • Reports
    • getReportDocument (for specified report types)

The SP-API report types that will require the Restricted Data Token (RDT) are:

  • GET_AMAZON_FULFILLED_SHIPMENTS_DATA_INVOICING
  • GET_AMAZON_FULFILLED_SHIPMENTS_DATA_TAX
  • GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_SHIPPING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_INVOICING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_TAX
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_SHIPPING
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_INVOICING
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_TAX
  • GET_ORDER_REPORT_DATA_SHIPPING
  • GET_ORDER_REPORT_DATA_INVOICING
  • GET_ORDER_REPORT_DATA_TAX
  • GET_EASYSHIP_DOCUMENTS
  • GET_GST_MTR_B2B_CUSTOM
  • GET_VAT_TRANSACTION_DATA
  • SC_VAT_TAX_REPORT

All Amazon MWS Reports will be deprecated as previously mentioned. Accessing the correlating report types for these Amazon MWS reports in SP-API will require the use of the new access protocol via the Tokens API and Restricted Data Token (RDT):

  • _GET_AMAZON_FULFILLED_SHIPMENTS_DATA_
  • _GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_
  • _GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_
  • _GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_
  • _GET_FLAT_FILE_ORDERS_DATA_
  • _GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT_
  • _GET_GST_MTR_B2B_CUSTOM_
  • _GET_ORDERS_DATA_
  • _GET_VAT_TRANSACTION_DATA_
  • _GST_MTR_B2B_
  • _SC_VAT_TAX_REPORT_

These Amazon MWS report types will be deprecated and are not available in SP-API:

  • _GET_CONVERGED_FLAT_FILE_ORDER_REPORT_DATA_
  • _GET_CONVERGED_FLAT_FILE_SOLD_LISTINGS_DATA_
  • _GET_XML_ALL_ORDERS_DATA_BY_LAST_UPDATE_
  • _GET_XML_ALL_ORDERS_DATA_BY_ORDER_DATE_
  • _GET_XML_VAT_INVOICE_DATA_REPORT_

For more information

We are providing the following resources to aid your migration:

  • SP-API Migration Guide - This step-by-step guide is to help you migrate from Amazon MWS to SP-API.
  • SP-API Developer Guide - This guide has been updated to include the new access protocol in the Authorization section.
  • Tokens API Reference - This is a new reference for the Tokens API and includes the operations for the new access protocol (RDT).
  • Tokens API Model - This swagger model describes the operations you can use in the Tokens API.
  • Tokens API Use Case Guide - This is a new guide describing the new access protocol for the Direct-to-Consumer Fulfillment, Tax, Shipping, and Reports use cases.

These resources provide preview information about the new version of the Reports and Feeds API that will be released in Summer 2021 to help you create or adjust integrations that do not require client-side encryption for reports or feeds as you migrate to SP-API:

  • Reports API Model - This swagger model describes the operations you can use in the new version of the Reports API that will be released this summer.
  • Reports API Reference - This is the reference guide for the new version of the Reports API that will be released this summer.
  • Feeds API Model - This swagger model describes the operations you can use in the new version of the Feeds API that will be released this summer.
  • Feeds API Reference - This is the reference guide for the new version of the Feeds API that will be released this summer.

Frequently Asked Questions (FAQs)

I use a third-party application that is integrated with Amazon MWS. Does this impact me?

No, at this time there is no change or action needed from selling partners who have authorized a third-party application to use Amazon MWS on their behalf.

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

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

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

Is Amazon MWS going away? If so, when?

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.

Is the Amazon MWS Products section affected?

No, this change does not affect Amazon MWS Products section.

How can I get more information and stay up to date on SP-API?

Where can I ask questions of other developers already using SP-API?

Visit us on GitHub at https://github.com/amzn/selling-partner-api-docs/issues to view developer community questions about SP-API or post your own.

Open a support contact with Amazon via one of these links:

507 views
0 replies
Tags:Reporting
20
Reply
user profile

Important Notice: Third-party developers using Amazon MWS Orders, Reports, and Merchant Fulfillment API sections must migrate to Selling Partner API by July 31, 2022

by Jeniffer_Amazon

UPDATE: This announcement has been updated to reflect the extended migration date of July 31, 2022.

What is changing?

As we mentioned in our October 2020 Selling Partner API (SP-API) launch announcement, all public applications will need to migrate to the new service. Effective July 31, 2022, all third-party developed applications authorized by selling partners in the Marketplace Appstore (“public applications”) must be integrated with the Selling Partner API (SP-API) and support for Amazon MWS Orders, Reports, and Merchant Fulfillment Network (MFN) sections will be discontinued.

Developers whose SP-API applications use Direct-to-Consumer Fulfillment, Tax, Shipping, or Reports use cases must also use a new access protocol (a Restricted Data Token) for some operations and report types in the Orders, MFN, Shipping, and Reports sections. See the ‘Use case details’ below for the specific operations and report types affected.

We are focused on providing the necessary information, tools, and assistance needed to successfully migrate your app to SP-API. If your app needs to be migrated to SP-API, we will automatically create a support case for you to communicate with us directly and send you a follow up email with additional details.

We’ve also been listening to developer feedback and have re-evaluated the requirement for client-side encryption for the Reports and Feeds APIs. We have determined the existing server-side encryption we provide meets or exceeds the industry standard and will be removing the client-side encryption requirement to access reports and submit feeds in new versions of the APIs; making integrating with SP-API easier. Developers who have integrated with the current version of the Reports and Feeds API can continue without interruption.

Why is this changing?

The launch of SP-API represents the next generation API for programmatic access to Amazon features for sellers. All new development is occurring in SP-API and this includes several enhanced data protection and security features. Amazon takes protecting customer data seriously. This change is being made to ensure developers are using the latest technology and features for the benefit of both sellers and customers.

Who is affected?

Amazon MWS developers whose applications are authorized by selling partners in the Marketplace Appstore using the Orders, Reports, or Merchant Fulfillment APIs.

SP-API developers whose applications are authorized by selling partners in the Marketplace Appstore using the Orders, Reports, Shipping, or Merchant Fulfillment APIs.

Developers using other Amazon MWS sections or sellers who directly integrate with Amazon MWS do not need to take action at this time.

Which marketplaces are affected?

This affects all marketplaces.

What action is required?

If you have an Amazon MWS-based application that is affected by this change, you must update your application to integrate with the Selling Partner API (SP-API) by SJuly 31, 2022 to avoid service disruption.

If you have a hybrid- or SP-API based application that is affected by this change, you must update your application to use the Restricted Data Token (RDT) via the Tokens API by July 31, 2022 to avoid service disruption.

We recommend that you start integrating with SP-API immediately and complete your migration from Amazon MWS to SP-API as early as possible.

Use case details

Developers whose SP-API applications use Direct-to-Consumer Fulfillment, Tax, Shipping, or Reports use cases must also use the new Tokens API for select operations and report types.

These SP-API operations will require the use of the Restricted Data Token (RDT) via the Tokens API to make a successful API call:

  • Orders
    • getOrderBuyerInfo
    • getOrderAddress
    • getOrderItemsBuyerInfo
  • Shipping
    • getShipment
  • Merchant Fulfillment (MFN)
    • getShipment
    • cancelShipment
    • cancelShipmentOld
    • createShipment
  • Reports
    • getReportDocument (for specified report types)

The SP-API report types that will require the Restricted Data Token (RDT) are:

  • GET_AMAZON_FULFILLED_SHIPMENTS_DATA_INVOICING
  • GET_AMAZON_FULFILLED_SHIPMENTS_DATA_TAX
  • GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_SHIPPING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_SHIPPING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_INVOICING
  • GET_FLAT_FILE_ORDER_REPORT_DATA_TAX
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_SHIPPING
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_INVOICING
  • GET_FLAT_FILE_ORDERS_RECONCILIATION_DATA_TAX
  • GET_ORDER_REPORT_DATA_SHIPPING
  • GET_ORDER_REPORT_DATA_INVOICING
  • GET_ORDER_REPORT_DATA_TAX
  • GET_EASYSHIP_DOCUMENTS
  • GET_GST_MTR_B2B_CUSTOM
  • GET_VAT_TRANSACTION_DATA
  • SC_VAT_TAX_REPORT

All Amazon MWS Reports will be deprecated as previously mentioned. Accessing the correlating report types for these Amazon MWS reports in SP-API will require the use of the new access protocol via the Tokens API and Restricted Data Token (RDT):

  • _GET_AMAZON_FULFILLED_SHIPMENTS_DATA_
  • _GET_FLAT_FILE_ACTIONABLE_ORDER_DATA_
  • _GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_
  • _GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_
  • _GET_FLAT_FILE_ORDERS_DATA_
  • _GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT_
  • _GET_GST_MTR_B2B_CUSTOM_
  • _GET_ORDERS_DATA_
  • _GET_VAT_TRANSACTION_DATA_
  • _GST_MTR_B2B_
  • _SC_VAT_TAX_REPORT_

These Amazon MWS report types will be deprecated and are not available in SP-API:

  • _GET_CONVERGED_FLAT_FILE_ORDER_REPORT_DATA_
  • _GET_CONVERGED_FLAT_FILE_SOLD_LISTINGS_DATA_
  • _GET_XML_ALL_ORDERS_DATA_BY_LAST_UPDATE_
  • _GET_XML_ALL_ORDERS_DATA_BY_ORDER_DATE_
  • _GET_XML_VAT_INVOICE_DATA_REPORT_

For more information

We are providing the following resources to aid your migration:

  • SP-API Migration Guide - This step-by-step guide is to help you migrate from Amazon MWS to SP-API.
  • SP-API Developer Guide - This guide has been updated to include the new access protocol in the Authorization section.
  • Tokens API Reference - This is a new reference for the Tokens API and includes the operations for the new access protocol (RDT).
  • Tokens API Model - This swagger model describes the operations you can use in the Tokens API.
  • Tokens API Use Case Guide - This is a new guide describing the new access protocol for the Direct-to-Consumer Fulfillment, Tax, Shipping, and Reports use cases.

These resources provide preview information about the new version of the Reports and Feeds API that will be released in Summer 2021 to help you create or adjust integrations that do not require client-side encryption for reports or feeds as you migrate to SP-API:

  • Reports API Model - This swagger model describes the operations you can use in the new version of the Reports API that will be released this summer.
  • Reports API Reference - This is the reference guide for the new version of the Reports API that will be released this summer.
  • Feeds API Model - This swagger model describes the operations you can use in the new version of the Feeds API that will be released this summer.
  • Feeds API Reference - This is the reference guide for the new version of the Feeds API that will be released this summer.

Frequently Asked Questions (FAQs)

I use a third-party application that is integrated with Amazon MWS. Does this impact me?

No, at this time there is no change or action needed from selling partners who have authorized a third-party application to use Amazon MWS on their behalf.

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

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

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

Is Amazon MWS going away? If so, when?

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.

Is the Amazon MWS Products section affected?

No, this change does not affect Amazon MWS Products section.

How can I get more information and stay up to date on SP-API?

Where can I ask questions of other developers already using SP-API?

Visit us on GitHub at https://github.com/amzn/selling-partner-api-docs/issues to view developer community questions about SP-API or post your own.

Open a support contact with Amazon via one of these links:

Tags:Reporting
20
507 views
0 replies
Reply
0 replies
0 replies
Quick filters
Sort by
There are no more posts to display
There are no more posts to display

Similar Discussions

Similar Discussions

Go to original post