Gerhard Potgieter

Hi @njali909,

We are currently investigating solutions to bring this back very soon.

Hi @micasuh, thanks for the feedback, we definitely value it and are listening.

I want to highlight that apart from the customer address validation at checkout we are in final stages of testing, the next release will also contain a new improved auto address verification process in wp-admin that requires no interaction of any kind from you as a merchant, unless there is no way to automatically verify an address.

Hi @robotor, sorry to hear you feel this way. We are not forcing anyone to pay, in fact if you are a legacy user of the live rates functionality in WooCommerce Shipping & Tax you would have gotten an email last week with access to a free subscription to the USPS extension from WooCommerce.com to use with WooCommerce Shipping. You can also continue to use WooCommerce Shipping & Tax should you wish, just disable WooCommerce Shipping.

As mentioned here an in other threads before, the live rates functionality in WooCommerce Shipping & Tax have been deprecated for 6 years already, in that time it has not received any updates, yes if it works don’t touch it, but unfortunately the carriers are constantly updating their API’s and deprecating old ones, and USPS is an example of one that was recently deprecated and destined to be removed which will leave the live rates feature in WooCommerce Shipping & Tax broken as well.

As with in any sustainable business, and I am sure you do the same, you need to prioritise the things people pay for over the free ones. The USPS extension, and all other shipping method extensions on WooCommerce.com is in active development, receives regular updates, and carrier feature deprecations are handled well in advance.

“does not bring value” is a vast understatement.

Did you know that the labels you purchase through WooCommerce Shipping are actually a lot cheaper than going directly through the carrier? This fact alone, I would say, brings lots of value.

Say you just have to ship around 10 orders a month for your store, at an average saving of around $2 per shipping label that equates to a total saving of $240 over a year, which is more than enough to offset the cost of the USPS extension from WooCommerce.com.

That being said, that does not mean we are not looking into this for WooCommerce Shipping. We are constantly evaluating feedback and making decisions based on that, so keep an eye out for any announcements that may be made in the future.

Yes our execution may not have been perfect, but we are making efforts to accommodate stores that relied on live rates.

Hopefully our efforts are worth considering changing your reviews and views on the matter.

Glad to hear it is now working!

@harleec, great to hear it is working again.

Regarding address validation, it is not a mandatory step even though the message shows in red in the sidebar. You can purchase labels without validating the address. You’d also be glad to hear we have a feature almost ready that will add address validation at checkout when enabled, so the customer can then validate their address at checkout.

As for returning to the order screen, there is no auto return, but the quickest way is to just click the <- arrow top left, which will return you to the order edit screen, or are you referring to the order list screen containing all the orders?

I am marking this topic as resolved for now, happy to continue chatting about the other things.

Hi, just an update that since version 1.1.2 of WooCommer Shipping you can now specify the box weight when saving a new package (template) as well as the ability to delete saved packages.

while I understand that the current packages setup is not the best, we have taken the feedback into account and have a revamp in the works.

Thanks!

Hi @grangep, we just release 1.1.3 of Woocommerce Shipping which fixes this. Please give it a go and let us know if this resolves the issue.

Thanks!

Hi @biopharm, we just release 1.1.3 of Woocommerce Shipping which fixes this issue. Please give it a try and let us know if it works for you.

Thanks!

Hi @signalhealth, we just released 1.1.3 which fixes this issue. Please give it a try and let us know if it works for you.

Thanks!

Hi @mrclayton, we just released 1.1.3 of Woocommerce Shipping which should resolve the conflict issues. Could you give that a try and let us know if this fixes the issue for you?

Hi @robertmurdock153, we just released 1.1.3 of Woocommerce Shipping which resolves some conflict issues with other plugins. Could you give that a try and let us know if this fixes the issue for you?

Thanks!

Hi @raqimed, we just released 1.1.3 of Woocommerce Shipping which resolves some conflict issues. Could you give that a try and let us know if this fixes the issue for you?

Thanks!

Hi @harleec, we just release 1.1.3 which contains a compatibility fix with other plugins relying on an api. Could you give that a try and see if it resolves the issue for you? Please also clear your browser cache after updating to ensure the latest installed code is running.

If the issue persist I’d be happy to troubleshoot more with you to get to the bottom of this.

Please let me know.

Thanks!

Hi @jamescollins, apologies for the inconvenience caused. The fix is ready to be deployed, it should be live very soon.

Hi @raqimed

I ran some tests now and with WooCommerce Shipping 1.1.2, Amazon Payments, and PayPal Payments active I was able to make purchases through both Amazon Payments and PayPal Payments.

On the cart page all the buttons render.

On the checkout page it seems the Amazon Express Checkout button does not work, but even if I disable WooCommerce Shipping does this error happen. The console also indicate that the error lies in the Amazon Payments plugin.

I can also confirmed I was able to still pay using the Payment Option on the checkout page, the error with the express payments buttons seems to be related to blocks checkout and the Amazon Payments plugin.

Can you perhaps share what the error is you are receiving? Check the browser console and/or your error logs. My suggestion would still be to contact the Amazon Payments support team for assistance and I am not able to reproduce the error you describe locally, only the missing button but even with WooCommerce Shipping disabled.

Thanks!