Amazon: (502) Bad Gateway Error
Update on How ShipWorks Connects to Amazon
Amazon announced that as of July 31, 2022 the Amazon Marketplace Web Service (MWS) API was deprecated and replaced with their Selling Partner API (SP-API). This means that ShipWorks customers currently importing orders from Amazon will need to have migrated ShipWorks to the SP-API prior to that date.
Merchants who have not yet upgraded to the latest version of ShipWorks, which automatically uses the Amazon SP-API, will encounter errors when uploading shipment information to Amazon or when attempting to download orders from Amazon.
The Error
The remote server returned an error: (502) Bad Gateway
When the Error Occurs
-
When downloading orders from Amazon
-
When uploading shipment details to Amazon
-
When uploading Amazon shipment details to ChannelAdvisor
How to Fix the Error
-
Upgrade to the latest version of ShipWorks. For detailed steps on how to upgrade ShipWorks, please see our 'How Do I Upgrade ShipWorks?' help article.
-
The latest version of ShipWorks automatically connects to Amazon using the SP-API.
-
Be sure to update all ShipWorks workstations.
-
-
Manually update Amazon for orders missing shipment details due to the 502 bad gateway error.
-
Manually Update Shipment Information: Follow the steps in our Tips & Tricks: Manually Update Online Shipment Details help article for the orders that need to be updated.
-
Filter the Amazon Orders: If you need to filter Amazon orders that have been shipped, follow the steps in the Creating the Filter section of our Amazon: Automate Tracking Updates help article.
-
Still Need Help?
Please feel free to reach out to one of our awesome Technical Support Representatives in St. Louis. We are happy to help.
Have a comment to share about this article? We'd love to hear from you. You must be logged in to your Support Portal account to leave a comment.
Comments
0 comments