VAT is displayed wrong with Cache (Litespeed cache)

  • Resolved uncharted83

    (@uncharted83)


    4 years, 5 months ago

    I have the issue that VAT appears to display randomly.

    For example:

    1. I visit the page incognito with IP from Sweden. I see 25% Vat.

    2. I close the browser window. I change VPN to Germany.

    3. I open a new incognito window and visit the same page. The price is correct, but it say incl. 25% VAT. (This is the shopmark from Germanized plugin)

    4. If I click and look at the product level, this often corrects itself. But not always.

    If I deactivate Litespeed Cache, the problem goes away.

    I am using the setting: Customer based: “Location”
    Before I used “location with cache support. But this give me a problem with re-direction and makes the page load 2 times. So instead I switched to “location” combined with the plugin: WooCommerce Price Based on Country (Basic)
    where I apply: Load product prices in the background.

    This appears to solve my previous problem, but show the wrong VAT at random.

    How do I solve this?

    The page appear, and the price is correct. But under it

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author vendidero

    (@vendidero)

    4 years, 5 months ago

    Hi there,

    If I deactivate Litespeed Cache, the problem goes away.

    Yes, this seems to be a caching-related issue. Germanized uses Woo functionality to determine the current VAT rate. Maybe you should hide the actual tax rate from showing (Germanized settings > taxes) up to bypass the issue.

    Cheers

    Thread Starter uncharted83

    (@uncharted83)

    4 years, 5 months ago

    Ok, but I was told I am required to show the applied tax rate for customers in Germany?

    Plugin Author vendidero

    (@vendidero)

    4 years, 5 months ago

    Hi there,

    please consult a lawyer if in doubt – as far as I know it is not required to show/display the actual tax rate on the product pages.

    Cheers

    Thread Starter uncharted83

    (@uncharted83)

    4 years, 5 months ago

    Regrettably, while testing without the Tax-shop mark on product listing pages (product loop) I see that on the next level, as in a single product page, the problem exist even there.

    So, as for example.

    I visit through incognito with an IP address from Brussels. I see VAT 21%.
    I close the window, switch IP to Germany. I open up incognito and enter the shop.
    I see VAT 21% again.

    In this case, I have turned off cache in Litespeed (but I have other optimization settings on. I am also connected to Quick.Cloud CDN.

    Plugin Author vendidero

    (@vendidero)

    4 years, 4 months ago

    Hi there,

    well, as I said: Germanized does not do any magic here. We do only use WooCommerce functionality to determine the tax rate based on your current session/customer data. Which location is being used depends on your Woo settings and/or geolocation settings. We are using the same logic Woo uses when going to the cart/checkout (for the first time) without specifying the billing/shipping address – so please try that as well (but be aware that many cache-solution might exclude cart/checkout from being cached). Find the code used to determine the tax rate for a product here: https://github.com/vendidero/woocommerce-germanized/blob/master/includes/abstracts/abstract-wc-gzd-product.php#L570

    For those customized setup you may need help from a specialist. Caching WooCommerce the right way is a very hard thing to do as a lot of information needs to be retrieved dynamically based on the current customer’s session.

    I guess it would really be better to disable the output of the actual tax rate in your case as this output will always need to be cache-excluded (as it depends on the current customer’s session).

    Cheers

    Thread Starter uncharted83

    (@uncharted83)

    4 years, 4 months ago

    Thank you so much for your answer.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘VAT is displayed wrong with Cache (Litespeed cache)’ is closed to new replies.