Shaun Kuschel a11n
Forum Replies Created
-
Hey all – Yeah, there was a temporary issue that was causing that error to occur but it should be resolved now. We’re continuing to monitor the situation but please let us know if you that error moving forward.
Hi @smiley58! Thanks for taking the time to post this review and share that feedback! It is greatly appreciated!
If there is anything else that we can assist with now or in the future, please do not hesitate to reach out to our Support team and let us know!
Hey Peter,
Thanks for that clarification and GIF showing the weights not updating when saved package template are selected or changed. That behavior is not expected. I was able to replicate it when the weight unit of measure that is selected for the Total Shipment Weight in the label UI is different than the store’s default weight unit that is set on the WooCommerce > Settings > Products page.
For example, in your GIF the store is using
kgbut in the label UIgis selected for weight unit. I suspect the issue might have something to do with the weight unit conversion. Can you try doing some tests withkgselected in the label UI and let me know if the Total Shipment Weight is correctly updated when saved package templates are initially selected or changed? To clarify, this is the setting I’m referring to.As for your question about where you can view the preset packages, currently those saved templates can only be added or deleted from within the label UI. There isn’t a separate page with package settings at this time, so where the packages were created shouldn’t be related to this issue (though, that’s a great question). However, the devs are working on adding the package settings to a dedicated page in a future update, so they can be managed outside of the label UI but it’s not quite ready for release.
Hey @parzival111 – Thanks for following up and trying those suggestions.
After digging into this further, the problem appears to be related to manually added or adjusted “Weight Per Unit” amounts in the customs form for cross-border shipments, which are not automatically updated to reflect the current/modified values.
By default, the Total Shipment Weight is calculated based on the individual weights specified on the Shipping tab of the edit product pages + the weight of the empty package. If products have accurate weights added, the Weight Per Unit fields will automatically be populated with those values and the Total Shipment Weight will be correctly calculated.
If products do not have weights added at all or if the product weights are incorrect, those amounts need to be manually added/adjusted in the Weight Per Unit fields of the customs form, as that information is required and needs to be accurate. However, if the Weight Per Unit amounts are manually modified, the Total Shipment Weight also needs to be manually modified to ensure the package weight is accurate.Since it sounds like the expected behavior is to have the Total Shipment Weight be automatically updated to reflect the current Weight Per Unit values, I’ve created a bug report for the developers to investigate further.
In the interim, the best approach to ensure that the Total Shipment Weights are correct (and calculated automatically) is to make sure that all products have accurate weights added on the Shipping tab of the edit product pages. If that isn’t possible for some reason and the Weight Per Unit values need to be manually adjusted in the customs form, the Total Shipment Weight should also be manually adjusted to reflect those changes.
Hey @indanvil – Thanks for sharing that feedback here and in the ticket with our team.
Although we’d love to support every store, there are some highly regulated products that we aren’t able to at this time. However, it’s important to us that WooCommerce can still be used even if the plugins we develop aren’t available. To that end, we constantly work with our partners to provide more options to users, like Square for CBD sites, and are always happy to provide alternative options as well (like AvaTax and TaxJar).
Also, we greatly appreciate the info and suggestion you shared about detailing any restrictions or limitations and I’m working with our docs team to make that info more clear.
If we can assist with anything else, please do not hesitate to reach out to our Support team and let us know.
Forum: Reviews
In reply to: [WooCommerce Tax (formerly WooCommerce Shipping & Tax)] Yay for No JetpackHi @jollygreen! Thanks for feedback!
Jetpack was initially required to utilize the secure connection to our servers for the rate calculations but we were able to remove that dependency a while back (in version 2.4.0), after creating a new way to use the same secure connection with WordPress.com accounts.
Forum: Plugins
In reply to: [ShipStation for WooCommerce] V4.7.0 and 4.7.1 crash our website on CheckoutThanks, @highrollerusa.
We just released version 4.7.2 of the ShipStation Integration plugin. Can you try updating to that latest version (preferably on a staging copy of your site first, before updating your live site) and let us know if that fixes the issue?Forum: Plugins
In reply to: [ShipStation for WooCommerce] V4.7.0 and 4.7.1 crash our website on Checkout@highrollerusa – Are there any fatal error logs on the WooCommerce > Status > Logs page?
Forum: Plugins
In reply to: [WooCommerce Shipping] Ability to generate PS Form 5630 USPSHey @mspeptides! Thanks for sharing that info and clarifying the need for PS Form 5630 generation/SCAN.
https://woocommerce.com/feature-request/usps-shipment-confirmation-acceptance-notice-scan-for-shipping-labels/Forum: Plugins
In reply to: [ShipStation for WooCommerce] V4.7.0 and 4.7.1 crash our website on CheckoutHey @highrollerusa – Thanks for bringing this to our attention and sharing the workaround involving downgrading to version 4.6.1.
We’re investigating the issue but can you share a bit more info about the site setup? Specifically, is that site using the GoDaddy Payments plugin?Forum: Plugins
In reply to: [WooCommerce Shipping] Incorrect Value for UPS ShipmentHey Tim! Thanks for bringing this to our attention.
To help make the label process a bit more efficient for cross-border shipments, the plugin pre-populates the “Value Per Unit” field in the label UI with the product cost from the order but it doesn’t currently convert that value in situations where a different currency was used to pay for the order (like PLN in this case), so I’ve passed this info along to the developers to investigate.
For the time being, the best temporary workaround would be to manually adjust the amount in the “Value Per Unit” field for any cross-border shipment that was paid for with any currency other than USD. For clarity, this is the field I’m referring to: https://d.pr/i/R11Iw3
If you have any feedback or suggestions about the preferred behavior in situations like this, please feel free to share it here and I’ll relay it to the devs.
Thanks!Forum: Plugins
In reply to: [WooCommerce Shipping] Error Message purchasing a shipping labelHey @editoratthr,
Do you currently have your store currency set to USD in the Currency Options section on the WooCommerce > Settings > General page?
Also, if you use a multi-currency plugin on your site (or anything that might affect the
woocommerce_currencyfilter), try temporarily deactivating those plugins and re-test to see if that resolves the error.If the conflict test fixes the problem, reach out to the developer of the plugin that seems to be the issue and let them know about the error.
Let us know what you find out!
Forum: Reviews
In reply to: [WooCommerce Shipping] Excellent Plugin and SupportHey @timthefoolman! Thanks for sharing that detailed list of the items that contributed to your rating. That’s super helpful and very much appreciated!
Forum: Reviews
In reply to: