Shipping Flat rate is rounded to Integer (No Decimals)

Can you submit a Systems Report by going to WooCommerce > Status > Get System Report and then come back here and paste it into a Code Block. Something tells me your settings in the main area aren’t set correctly.

Please also take a screenshot of that area if you can too bitte. Specifically this area

https://loom.com/i/d688f174eaa94f2fa5cadef03d6ccca6

As written in my original post, the settings in the main area are correct:

The system status you can also find in my original post:
https://gist.github.com/manyoumc/135d585915bc1ae62047f166384040a7

Also please notice, that another user in this forum has the same issue which indicates that is has something to do with the latest WooCommerce Update: https://www.ads-software.com/support/topic/incorrect-shipping-costs-after-update-8-4-0/

Hello @manyoumc,

I’m not sure if you received a notification of my reply here.

Just want to let you know a fix is already on the way in version 8.5.0 so I’ll be marking the thread as solved.

Feel free to keep replying to this thread or create a new one if you have any other questions!

Thank you!

Hello @manyoumc,

If you have a few minutes, we’d love if you could leave us a review: https://www.ads-software.com/support/plugin/woocommerce/reviews/

Thank You!

This topic is marked as resolved, but hopefully someone from Woocommerce is still reading this, because the issue isn’t resolved for us.

The shipping flat rate is still being rounded down to zero on the decimal.

It’s supposed to be resolved in the next update (8.5.0) but we’re still on version 8.4.0 and our shipping rates are still being billed inaccurately. This is costing us money and it’s been nearly two weeks now, so I’d love a solution to this problem. Thank you!

@catinka it’s been resolved for this OP. You need to post your own support ticket here per forum guidelines. Posting on a Resolved post does nothing to help you.

@serafinnyc, thank you, that’s good to know and I will post my own support ticket.
(It’s not necessarily resolved for the OP tho; the woo people just closed the ticket saying it will be fixed with the next update, but this update still isn’t here over a week later, so possibly the OP is still stuck with this issue as well.)

@catinka it was closed/resolved, because it’s a known bug as described by support. As stated it will be released in the next version, 8.5.0. It’s the joy of being in an open source framework sad to say. Gotta wait for these patches.