Nami

Hello there,

This issue should be fixed now with the dot release of 9.8.4. If there is any issue with the dot release, could you please report them in our GitHub issue?: https://github.com/woocommerce/woocommerce/issues/57760

Thank you again for your patience and understanding with this issue.

Hi there @paolofrulio ,

Thank you for writing to us about this!

We also recommend what @sooskriszta had already suggested. See this section of the documentation article.

WooCommerce’s core features for tax may not be sufficient for applying tax rates or actions based on complex conditional logic. In other words, there are limitations to WooCommerce’s ability to provide conditional tax rates or actions that comply with every local tax law.

We recommend looking into EU VAT Number extension available on our marketplace or any other EU VAT solution that fits your needs that may fulfill your needs.

As for the scenario that would require customers to take action, you may explore some options such as:

• Set up wholesale role or B2B platform (i.e. B2B for WooCommerce) to require certain information during Checkout flow based on a role
• Set up email automation to follow up with a customer (i.e. AutomateWoo)
• Set up conditional logic to make some fields/file attachment to appear (i.e. Conditional Checkout Fields for WooCommerce)

You may also check in with other local merchants who handle VAT similarly to your business and may seek their solutions as they would be most familiar with local regulations.

Thank you for writing to us about this.

Hi there @hackbit ,

Thank you for reaching out to us about this. We are incredibly sorry to hear about the issues you’ve observed with the version 9.4.0 of Stripe plugin.

Could you please reach out to us support via WooCommerce.com?: https://woocommerce.com/my-account/contact-support/ If you can also include the link to this post, that would be much appreciated.

This will help us further check on this issue moving forward.

In the meantime, our developer team has rolled out 9.4.1. which is the same code as 9.3.2 so your site may remain with 9.3.2 version without upgrading to 9.4.1 until our developer team has new release planned in the future.

Hi there,

Thank you so much for following up with us about this issue!

Sorry to hear that the issue has not been resolved even after updating to the latest Dot version release of 9.6.2.

I’ve checked the the site and I am able to observe the behavior where the button stays a default color until you select the variation option.

We’ve had some reports of this issue, and the issue tends to be caused by some third-party plugins. Could you please look to setting up a staging site and test this issue further?:

• Create a staging site
• Make sure the issue is observed on the staging site
• Deactivate all the plugins except for WooCommerce
  • If the issue is resolved, then it means there are conflicting plugins that are causing this issue on the frontend

If the issue persists to happen, it might have to do with theme:

• Switch the theme to Twenty Twenty-Four and observe the issue further
  • If the issue is resolved, then it’s best to reach out to the theme developer
  • If the issue is not resolved, please do let us know

In the meantime, you may also check to see if downgrading WooCommerce plugin may help this situation. You can download the previous version from this page: https://wordpress.org/plugins/woocommerce/advanced/ (Scroll down then select 9.6.0)

Thank you again for looking into this matter.

(Reference: I’ve posted issue summary and impacts in this GitHub thread.)

Thank you for following up @austinn123 !

There could be any number of reasons this might be happening. I hope to give you some pointers so you can carry out some troubleshooting.

Here are some direct steps you can take to tackle this:

1. Clear Object and Browser Cache:
   • If your site is using object caching (e.g., Redis, Memcached), clear the object cache from your hosting dashboard or caching plugin. Sometimes outdated backend values are cached.
   • Clear your browser cache or try viewing the backend in an incognito/private browser. (When you are modifying the site often, it’s possible hosting or caching is not totally in sync. It’s best to check things in incognito mode.)
2. Check Variation Stock Directly:
   • For variable products, ensure each variation has its stock quantities updated under the Variations section in WooCommerce > Products > Edit Product > Variations. Stock for the main product does not sync automatically to variations.
3. Ensure Database Sync:
   • Go to WooCommerce > Status > Tools and run the following tools to ensure database options and lookup tables are updated:
     • Regenerate Product Lookup Tables
     • Recount Terms, if applicable
4. Disable Persistent Caching and Test Live Stock Updates:
   • If you’re using a caching plugin or CDN (e.g., WP Rocket, Cloudflare), temporarily disable it and check for updates to backend stock when making changes or processing orders.
5. Create a Test Product:
   • Create a new test product and assign stock, then modify the stock directly after a manual adjustment in the backend or test order. Check if the issue persists for new products.
6. Error Logs:
   • Check WooCommerce logs via WooCommerce > Status > Logs and review any fatal error logs or stock-related entries. These might indicate why changes to stock values aren’t reflected.

If the issue persists after these steps, it might be best to set up a staging site, then further test under conflict tested state so you can tell if the issue is coming from any static elements (theme, plugin) or any dynamic element (caching, database, resource issue, etc.)

Thank you for looking into this!

Hi there @gavrielsgs ,

Thank you for following up with us about this!

It looks like you are working on the plugin PayPlus Payment Gateway https://wordpress.org/plugins/payplus-payment-gateway/

I understand you’ve reached out to a couple of support funnels, but have you had a chance to reach out to the Payment Gateway support team for this issue? (You may find their support page on their site: https://www.payplus.co.il/wordpress)

If they have ruled that there is an issue with WooCommerce plugin itself, please kindly request them to submit an issue on WooCommerce public repository https://github.com/woocommerce/woocommerce/issues.

Generally speaking, any developer who is implementing any integration is responsible to maintain and manage integration and compatibilities. However, it is possible that in the developmental process, developers find some technical issues.

For this, we need more specifics, such as what kind of integration is being worked on and which line of code is causing the interference, and how to address the issue in WooCommerce plugin core. These technical details are necessary for our developers to review any issue/enhancement.

To further clarify, the pop-up window based payment is not something that WooCommerce plugin itself handles. It is up to Payment Gateway plugin to handle these. However, as mentioned, if there is any issue that is evident to Payment Gateway developer, please request to report this 🙂

I hope this helps!