ShipStation Improvements and Bug Fixes (June 28 - July 9)

[SuperMgr-Sarah]

Improvements

• ShipStation now supports saving multiple Tax IDs and adding them to shipments in bulk or with automation for accounts in all countries!
  
  
  Review the ShipStation International Settings help article for details!
• We’ve also added a SKU field to the shipment’s Customs Declarations so you can list individual SKUs for each declared item on your customs forms.
  
  (We will soon be adding a Weight field for the individual declarations as well!)
• We’ve added an Advanced Preview mode to ShipStation’s In-Cart Delivery Options feature. Advanced mode allows you to preview rates for specific addresses rather than just by postal code and has an improved preview layout.
  

Open API

• ShipStation has added the ability to POST SellerPackageTypes to our Open API. This mean, you now have the ability to add, edit, and delete custom package types with an API call.

Integrations

• ShipStation now integrates with the Australian carrier, Toll Priority.

Bug Fixes

• Fixed an issue where the Paid Date erroneously displayed one day earlier than the order date for some orders.
• Fixed an issue where changes to a store’s Branding tab were not saved even though a success message appears after saving.
• ShipStation now gives a warning when an ITN number may be required for a shipment over $2500 and provides a space to enter the ITN.
  
• Fixed an issue where filters did not load as criteria for automation rules.
• Fixed an issue that caused automation rules not to save correctly when using numeric filters.
• Fixed the default filter for Recent Shipments and Recent Fulfillments to show 14 days of records instead of only 7 days.

Integrations

• We released a fix for eBay’s new integration so orders now properly import the Paid Date.
• ShipStation now sends the carrier code “Asendia” back to Amazon when shipping with either Asendia or Globegistics services.
• ShipStation now displays an error message when an Amazon connection authentication token expires.
• Fixed an issue for New Zealand  accounts so Courier Post tracking numbers now properly link to the Courier Post tracking page.
• For Australia-based accounts, delivery instructions are now added as customer notes for orders from NETO marketplaces and AU Post MPB accounts can now successfully create international labels.
• We fixed an issue for Groupon Goods stores so weight units now import correctly from the marketplace.
• Fixed issue that occurred when clicking the Send to Fulfillment button with multiple orders selected in the grid results in a blank page.
• Resolved an error for Tophatter shipment notifications: “The following parameters are required but were not provided: service_type.” ShipStation now sends the correct values in the service_type field to Tophatter.

Mobile

• Fix issues in the iOS version of the mobile app:  
• You can now swipe left through order details after sorting the Orders list
• The mobile UI now updates as soon as any update occurs on an order

[masonfabian]

Fixed an issue where changes to a store’s Branding tab were not saved even though a success message appears after saving.

Great fix! I remember a community member posted about this issue recently glad to see it resolved.

[a51]

Seems there has been an update to the visual of the Chose carrier drop down - with no color variation on the roll over, or check mark of what is chosen very challenging .. can we have the old drop downs back? please or some kind of check mark of what is chosen.. We have multiple USPS /FED Ex and UPS accounts and a quick visual would be very helpful 

[SuperMgr-Sarah]

@a51 Thanks for your feedback. We did update the design of the Service drop-down so it conforms with the other drop-down menus used throughout the app. 

The roll over color change should still occur, though it is more subtle than in the prior version of the menu (it's a light blue background rather than a darker green). The different providers should also be more clearly sectioned (each provider in the list has a grey background and is aligned to the left while its associated services are indented right).

However, I am looking into the checkmark situation, as it is very useful to be able to see which service from which account is the currently selected option. I'll post an update here when I have an answer for you!

[SuperMgr-Sarah]

@a51 I've confirmed the missing checkmark is a bug and we've escalated it to the right team. I don't have an ETA on when this will be fixed, but I don't imagine it will be long. 

Thanks for reporting this and for your patience!

[a51]

Thank you for the updates, a more distinct highlight colors would also be helpful that gray is pretty light .. 

[a51]

One additional question about recent updates? was this part of it? 

When you go to look at order items nothing shows? and if you have to scroll to find items in the order? kind of pain and if you not in the right spot on the screen it doesn't scroll very frustrating .. When use to be right there and only time you had to scroll was if multiple items didn't fit in screen 

  

 

[SuperMgr-Sarah]

@a51 No, that should not be happening. I checked with our support team and we don't have any reports of this either. I also checked a few of my test accounts and did not see this issue in any of them. So it could mean a browser cache issue (maybe). 

Just in case, I flushed your account cache on our side. If you log out and back into your account and the issue is still happening, try clearing your browser cache or logging into your ShipStation account in an incognito/private  browsing session. 

If it is STILL happening, I recommend contacting ShipStation support for further assistance. 

[a51]

OK - this is happening for multiple account log ins .. for weeks. we have done all the recommend solutions... 

[SuperMgr-Sarah]

@a51 My only other idea is that there could be a browser extension interfering with your ShipStation display. But if you disable your extensions and it is still occurring, we'd definitely want support to assist. Getting a few screen shots and maybe a display of your browser dev tools while the page loads could help if we need to escalate the issue to Senior support or our dev team. 

[joebunting]

Hi! - with DHL Ecommerce AU, they require a SKU for international shipments. This does work, but we use our own pre-defined customs information for international customs declerations - we need the ability to set the pre-defined default SKU, currenly, with every shipment we need to enter the default SKU in the international customs field before we can print the label - really not ideal. - Is there a way to fix this with automation rules? 
Thanks! 

[SuperMgr-Sarah]

Hello!

I'm going to check with our product team on this for sure. There is no automation rule action currently to add a pre-defined SKU to customs declarations, and as far as I know the only way to automate that is to set your International Settings to "Create declarations from order items". 

But, since you are using the pre-defined values setting instead, there is no SKU field to enter a pre-defined SKU into. The SKU field for customs declarations is fairly new in ShipStation and this could be somewhat of an edge case that didn't come up previously, so I'm checking with our product team to see what options are available here. 

Thanks for bringing this up and I'll let you know what I hear back. 

[joebunting]

@SuperMgr-Sarah - Thanks for looking into this! yes I do think its probably an edge case.

I did try to create declearations from order items, but alas, our product titles are too long to be accepted most are over 50chars, so we get another error. We're stuck between a rock and a hard place.

Apprecaite you looking into this, looking foward to hearing back.

[SuperMgr-Sarah]

@joebunting - With this additional information I might actually have a solution for you (will take a little bit of work on your end, but not too much).

If you fill in the Customs tab of your product details with the description, declared value, and country of origin, you could switch your settings back to create customs for ordered items and ShipStation would then automatically add the SKU to the SKU field in the customs declarations. 

Basically, when the Description field in the Customs section of your product record contains a value, ShipStation will use that value instead of the product name as the description for the customs declaration, so you can retain your product name but ensure the customs description is less than 50 characters. You can also use the CSV import method to bulk update all of your products in one go so you don't have to manually enter these details one by one. 

Here is an image of the Customs section of the product details (in my personal test account): 

And this is what populated in the customs declarations for the order when I created an international order (with ShipStation set to create customs from order items): 

If you think this will work for you, my suggestion is to export your product list from ShipStation (go to the Products tab, click Export, and choose to export ALL records). This will download as a CSV file. You can then enter the description, value, and country values for all your products into the CSV: 

Save the file and import back into ShipStation (this time just click the Import option on the Products tab). 

If you've never done this process before, I recommend reviewing the "Update Products in Bulk" section of our Update Product Records help article. It provides all the steps of the process with some additional details and descriptions.

Let me know if this works for you or if I still need to follow up with our product team about the possibility of adding a SKU field to the "pre-defined" international settings.

[joebunting]

@SuperMgr-Sarah - Thanks for taking the time to look over this. Unfortunately, this wont really work for us - we use the SKU's in our order processing step, and we have a very large range of products - most of which are imported to SS at the time of sale. 

We're still stuck at this point - seems like the only solution for us would be to have the ability to add a pre-defined SKU for customs. 

Are you able to escalate this?

Thanks,

[SuperMgr-Sarah]

Hi @joebunting, 

Yes, I sure can. I'll create a ticket in our support system and send it up - you should receive a confirmation email about this ticket once submitted so you can reference it if needed. 

Just to set expectations, I can't guarantee that after reviewing it the product team will decide to implement this. And, since we are nearing code freeze I wouldn't expect them to be able to review until early next year. So for now, don't expect any changes in the UI or your workflow. However, you've explained your use case clearly so that will be helpful. Thanks!