Hi @sevans917,
It is unlikely that Fluid Checkout would affect the shipping rate amount as it does not do any calculation of this type.
Please check your TAX settings.
That is the only thing I think from the top of my mind that could affect the final amount of the shipping rate like this.
Also, please check if this happens only when Fluid Checkout is activated.
Leave all other plugins and the same theme, but deactivate Fluid Checkout for this test.
I’ll investigate this further on my side and reply to you with the results.
Best,
Diego
Hi @diegoversiani ,
When Fluid is deactivated, checkout summary displays correct shipping amount.
This order triggered an 8% sales tax on products and shipping, so there’s the reason the shipping fees are $0.79 more than the shipping rate.
However I would normally not expect the shipping rate to show with tax included. Tax is a separate line after products and shipping, in checkout summary.
If I disable Fluid and use Woocommerce checkout block, the shipping rate in steps is shown without tax.
-
This reply was modified 2 years, 8 months ago by
sevans917.
-
This reply was modified 2 years, 8 months ago by sevans917.
Hi @sevans917,
I tested a few scenarios with 8% tax and the amount charged for shipping is the same 10.69:
a. Blocksy + Fluid Checkout
b. Blocksy + WooCommerce Checkout Block
c. Blocksy + WooCommerce Native (shortcode)
It seems to me that the specific settings you are using for the taxes and how they should be displayed are causing this issue.
Although, it could be that Fluid Checkout is not prepared for your specific scenario.
** Could you send me some screenshots of the tax settings you are using on your website? **
If this information is private and you don’t want it publicly available here, you can blurry out the sensitive information. Otherwise, you can also send them to me at diego [at] fluidweb.co.
Best,
Diego
Hi @diegoversiani,
Today, after a few days away, and no site changes, the shipping rate is showing the correct amount and not adding in sales tax. So I suspect this issue was caused by something like cache, cookies or transients, and not having to do with settings.
If the issue recurs in the future I will let you know.
Regards,
Scott
