When orders don't import or shipment notifications aren't properly received, productivity suffers. After all, these are some key features that make ShipStation great! 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 thing, we want to get you back up and shipping as quickly as possible!
Below are some of the more common error messages you'll see in ShipStation:
- (400) Bad Request
- (401) Unauthorized
- (403) Forbidden
- (404) Not Found
- (429) Too Many Requests
- (500) Internal Server Error
- (502) Bad Gateway
- (504) Gateway Timeout
Important: 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, please contact our support team!
(400) Bad Request: This error typically appears during the shipment notification back to the selling channel or as 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 comes from an invalid username and password. If you see it, verify that you are using an up-to-date username and password to connect the selling channel:
- To correct this error, try reconfiguring the store's connection to ShipStation.
- If this doesn't correct the error, there may be an IP block prohibiting ShipStation from communicating with your selling channel. Whitelist ShipStation's URLs to see if this allows the connection to work properly.
(403) Forbidden: This error 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. Try reconfiguring the store's connection to ShipStation. If that doesn't resolve the issue, look within your selling channel/hosted cart to ensure 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, the issue is an updated URL that ShipStation needs to be contacting to pull in orders. If your store updated recently, definitely try reconfiguring the store's connection to ShipStation.
- One common reason this error transmits could be that your store connects to ShipStation through a plugin. If this is the case, make sure that the plugin is properly installed and up to date.
- 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. With batches, our system consolidates 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 behind the (429) error, another cause can be refreshing your stores to pull in new orders. Typically, any system event may cause throttling. Send a shipment notification back to the selling channel or just check for new orders to import into ShipStation, and 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, often the best resolution is to wait. The throttle may lift after five minutes or after an hour. Check the selling channel's documentation directly to see their specific request limits.
(500) Internal Server Error: This error message emerges if the server that hosts the system you are trying to reach is either down or currently unavailable.
- If you've recently migrated servers, try reconfiguring the store's connection to ShipStation.
- If that doesn't work, ensure that your SSL certificate is up to date. You may need to reach out to your web-host or the developer who set up the connection to ensure that everything is correct.
(502) Bad Gateway: This error means there is a miscommunication or a bad request between two systems. Imagine mismatches like ShipStation responding with a postcard when your system sends a text message.
- If it happens, try again. It may just be a temporary issue on one end of either system.
- If it still doesn't work, try reconfiguring the store's connection to ShipStation.
(504) Gateway Timeout: This error generally occurs with requests that are too large to be handled between servers trying to communicate with each other:
- If you have a hosted cart and you receive this error when trying to import orders (especially when it is for a small number of orders), you may need to increase your server's timeout value. Ask your web host or website developer to verify that everything is properly configured.