When orders don't import or shipment notifications aren't properly received, it can really hurt productivity. After all, these are some key features of what make ShipStation great! Below are some of the more common error messages you'll see in ShipStation. Whether it's a result of a connection issue within ShipStation, an out-of-date plugin on the selling channel's end, or some other third thing, we want to make sure that you get back up and shipping as quickly as possible!
And, as with any other error or issue, if you are unable to resolve something or you just want to let us know about something you found, do not hesitate to contact our support team.
(400) Bad Request: This error is typically seen during the shipment notification back to the selling channel or is a result of an invalid character being present in the order feed. Think of this as the computer saying "Does not compute" when trying to process a request. Common reasons for this error are:
- You split an order into two orders and your selling channel doesn't recognize the Order ID that is trying to be updated.
- If there is a special or unsupported character in the order feed, this can also cause a (400) Bad Request error to be transmitted. For instance, if the phone number importing for an order shows "512-48@-#282" instead of "512-485-4282".
(401) Unauthorized: This error typically means "invalid credentials". If you see it, verify that the credentials used to connect the selling channel are up to date:
- If you see this error, try reconfiguring the store's connection to ShipStation.
- If this doesn't correct the error, there may be an IP block that is prohibiting ShipStation from communicating with your selling channel. Whitelist ShipStation's URLs to see if this allows the connection to work properly.
(403) Forbidden: If you see this error, this means something is denying the request being made. For instance:
- If you are receiving this when trying to import orders into ShipStation, it tends to mean there is something rejecting our request. You can try reconfiguring the store's connection to ShipStation, and if that doesn't resolve the issue, take a look within your selling channel/hosted cart to make sure that there are no security plugins, etc. that may be interfering with the integration.
- You may have orders importing just fine into ShipStation, but you are getting this (403) forbidden error when trying to send the shipment notification back to the selling channel. This can be caused by a security plugin interfering with the integration as well. For instance, if you are integrated with a system like WooCommerce, they can be sending the orders to us just fine, but when the shipment notifications are sent back, a security plugin could be redirecting the shipments to another location in your WordPress account.
(404) Not Found: This is a very common error. If you come across it, there are a few things to look out for:
- Sometimes, it can be an issue with an updated URL that ShipStation needs to be contacting to pull in orders, if there have been any updates on your store's end, definitely try reconfiguring the store's connection to ShipStation.
- If that doesn't resolve the issue, it could be that you connect your store to ShipStation using a plugin. If this is the case, make sure that the plugin is properly installed and up to date. This is another common reason that this error is transmitted.
- Another common reason that this error can come up is if your store is not live, or is in maintenance mode. Make sure that your store is live. Try visiting the URL you are trying to connect. If it cannot be accessed, chances are we cannot connect to it.
(429) Too Many Requests: If you're running into this error, it typically means you are being throttled by the system you are trying to reach from ShipStation:
- This is commonly seen when sending shipment notifications back to the marketplace. For instance, certain selling channels and carts limit the number of calls that you can make to their system per hour. So if you are shipping 300 shipments an hour, this can push you over that limit. To get around this limitation, we recommend batching your shipments. This is how our system will consolidate the shipment notifications for a large group of shipments into a single call. So instead of notifying Shopify with 300 individual shipment notifications, we will send Shopify a single notification of 300 shipments.
- While Shipment notifications are the larger culprit of causing the (429) error, another cause can be refreshing your stores to pull in new orders. Typically, any system event is seen the same way as far as throttling is concerned. So whether sending a shipment notification back to the selling channel or just seeing if there are any new orders to import into ShipStation, you could be throttled. Also, some selling channels break up the way orders import into ShipStation. So a single order could be brought in from 4 different requests to your selling channel.
- If you do receive the (429) Too Many Requests error, typically the only way to resolve this is to play the waiting game. The throttling can be lifted after 5 minutes or up to an hour or more. Check the selling channel's documentation directly to see what the specific request limit is.
(500) Internal Server Error: This is an error message that comes up if the server that hosts the system you are trying to reach is either down or is simply unable to be reached currently:
- If you've recently migrated servers, you may need to try reconfiguring the store's connection to ShipStation.
- If that doesn't work, make sure that your SSL certificate is up to date. You may need to reach out to your web-host or the developer that set up the connection to make sure that everything is correct.
(502) Bad Gateway:This pretty much means there is incorrect communication or a bad request between two systems that are communicating. It's like ShipStation going for a high five when your system reaches out to shake hands. If it happens, try again. If it still doesn't work, there are a few things to try:
- This may just be a temporary issue on one of the two system's ends, but if it doesn't clear up, reconfiguring the store's connection to ShipStation can help.
(504) Gateway Timeout: If you receive this error, it generally means that when servers that are trying to communicate with each other, a request is too large to be handled:
- If you have a hosted cart and you receive this error when trying to import orders, especially if it is when it is for a small number of orders, you may need to increase the timeout value for your server. So it is advised to reach out to your web-host or the developer that built your website to verify everything is properly configured.