Shaun Kuschel a11n

Hi @timea4523 – If you’re located in the US, “Automated Taxes” uses the Store Address from the **WooCommerce > Settings > General** page as your ‘nexus’ location and charges taxes for any customers that are located in that same State, which can make it seem like it isn’t working when it actually is. However, if you’re experiencing a different issue that is preventing all taxes from being calculated and would like to troubleshoot the problem further, please feel free to open a ticket and we would be happy to assist further.

If your business has multiple nexus locations or needs to collect taxes in other States (either all the time or after a certain sales threshold has been met), you will need to use manual tax rates in WooCommerce core or a dedicated tax plugin that can handle complex tax requirements (like Stripe Tax or AvaTax, for example).

Hi @clarereynolds1979!

If you are wanting to create orders in ShipStation and then export them to WooCommerce, that isn’t possible currently. The ShipStation Integration plugin only works the opposite way, exporting orders that are created in WooCommerce to ShipStation.

Hey @mindykatzen – When a shipping label is purchased, nothing is currently added to the Order Notes, other than the automated note when Order Status changes to “Completed”, if that box is checked when purchasing the label.

The tracking number(s) is currently added to the Shipment Tracking widget, rather than the Order Notes, so it sounds like you might be looking for the shipping label meta? Can you share a bit more more info about what you’re wanting to achieve?

Do you just copy and paste this reply to all the negative comments??

No, not at all. Before sending the previous response, I attempted to look for any support history from WooCommerce.com tickets based on the little information I can see from your account on here but only found other topics (nothing related to ShipStation), so it must have been a different account that I wasn’t able to locate.

If you don’t mind sharing the ticket numbers from any of the interactions that you didn’t hear back from us, I would greatly appreciate that info. There shouldn’t be any situations where our team doesn’t follow-up and I’d like to investigate/address what happened in those cases.

Hi @slimfitholsters – Thanks for sharing this info with us. I’m sorry to hear about the issues you’ve been experiencing, both with regard to the orders not syncing to ShipStation and the difficulties getting in contact with their team. However, if you are interested in troubleshooting this issue with our team, you can open a ticket on the Support page on WooCommerce.com (https://woocommerce.com/my-account/contact-support/) and we would be happy to take a look at the sync problem with you. When creating the ticket on our Support page, you can scroll past the “Get instant AI help” section and submit a “Technical Support” request with “ShipStation for WooCommerce” selected in the “Product” dropdown. Once that has been done, reply to this review and let me know what the ticket number is. Thanks!

Hey @harleec! Sorry for the delay getting back to you but I hope you had a Merry Christmas (if you observe the holiday).

Can you try temporarily deactivating any security plugins (like MalCare, for example) and see if that helps with the 400 error?

Regarding the missing dependencies, can you try deactivating and deleting the WooCommerce Shipping extension and then re-installing a fresh copy of the plugin (which you can download from the main page here on www.ads-software.com).

Let us know how it goes. Thanks!

Hey @harleec!
We are working on improvements to the advance rate fetching flow, so we appreciate your feedback.
Regarding the issue you noticed in the Query Monitor scripts section about the missing dependencies, are you still seeing that after updating to version 1.3.1?
As for the 400 error, try going to the WooCommerce > Settings > Shipping > WooCommerce Shipping page, clicking the “Edit” link for your Origin Address at the bottom of that page, make sure all the required fields have been filled out, and re-save/re-validate. After doing that, let us know if you continue to see that 400 error.
Thanks!

Hey @plcexchange!

It sounds like you might have been part of the invite-only beta group that had access to UPS shipping labels. We sent out emails back in July that the beta was being shut down, as we’re currently working on carrier updates in the WooCommerce Shipping extension to replace that old beta functionality and expand that offering. We aren’t ready to announce the new features just yet but are hard at work getting those updates ready for release in the very near future. More to come on this soon!

Although UPS labels don’t currently work in the WooCommerce Shipping extension, we have re-enabled the UPS beta functionality in the WooCommerce Shipping & Tax extension to help make sure that merchants continue to have access during this peak holiday shopping season. So, if you were previously able to purchase UPS shipping labels as part of the beta, you can switch to WooCommerce Shipping & Tax while we finish working on the carrier updates for the WooCommerce Shipping extension.

To make this switch, you just need to deactivate the WooCommerce Shipping extension and active WooCommerce Shipping & Tax. However, if you run into any issues switching to WooCommerce Shipping & Tax or getting UPS shipping labels to show, please let us know.

Thanks!

– Shaun

• This reply was modified 3 months, 3 weeks ago by Shaun Kuschel a11n.

Hi @cleslie577,

Can you give us some more info about what you are specifically referring to?

I believe that the ‘old plugin’ you mentioned is “WooCommerce Shipping & Tax”, which certainly meets that criteria since it was created back in 2016. That is one of the reasons that we created “WooCommerce Shipping” extension, as this new extension is being built with new code (since a lot has changed over the last 8 years).

Another reason that we’re decoupling the shipping and tax functionality into their own plugins (starting with “WooCommerce Shipping”, and releasing “WooCommerce Tax” in the near future) is to allow us to focus more on each of those vital aspects of ecommerce separately and create better individual products.

While the legacy “WooCommerce Shipping & Tax” will be retired at some point in the future, it hasn’t been removed and is available for download/use.

Regarding what you mentioned about ‘forcing users to go to another plugin that charges a subscription’, I’m not sure what you are referring to, as “WooCommerce Shipping” works exactly like “WooCommerce Shipping & Tax” always has- which is to say that it is also a free plugin and doesn’t require a subscription to use. The only thing you pay for are the individual shipping labels that are created, which are provided at a discounted rate.

I hope this info helps clarify the situation but if you have any other feedback or insight to share, we would greatly appreciate it.

Thanks!

Hey @annonnimmo – Thanks for feedback. To make sure we understand your concerns correctly, can you elaborate on what you don’t like about the WordPress.com connection?

Also, can you clarify what you were referring to about staying away from independent developer’s plugins as well?

Thanks!

Hey @jskarioki,

Thanks for sharing that error message. Are you still seeing that error currently? If so, does it appear to be happening on all orders or just a specific one?

I took a look at your site’s connection to our servers and didn’t see any issues there, so it would also be helpful if you can share what info is in the “last_name” field for the destination address when that error appears.

As for the previous version of the plugin (1.1.4), if you want to see if that makes a difference, you can download it here.

Let us know what you find out. Thanks!

Hey @aumjosh,

I did a number of tests with Stripe and WooCommerce Shipping (version 1.1.4) but Stripe worked as expected, as seen in this example.

We would like to investigate this further. Can you provide us with more information about the Stripe integration that you’re using on your site? You can either share that info here or create a ticket on WooCommerce.com, if you’d prefer that method.

Thanks.

Hey @signalhealth,

I saw that you created your own thread for that question, which is very much appreciated. We will follow-up with you there shortly.

Thanks!

Hi @seedslocker,

After digging into this further, we found an issue that could cause the problem you described and are working on a solution that will be included in an update very soon.

Thanks again for bringing this to our attention!

Hey @seedslocker,

Thanks for clarifying. The actual performance shouldn’t be any different between the two plugins, so I wonder if the delay might have something to do with this being the first attempt using the new plugin. If you see any delays with the label generation process on your next order, please let us know.

Thanks.