Curcy

Dear VillaTheme Team,

I hope you are doing well.

I am currently using your CURCY plugin together with WooCommerce and I have encountered a structural issue regarding currency switching and tax calculation. I would like to ask whether there is a built-in solution or recommended approach for handling taxes based on currency rather than customer location.

**Current Setup:**

* WooCommerce store with international customers
* CURCY for multi-currency (EUR, CHF, etc.)
* Google Merchant Center feeds per country (e.g. Switzerland with CHF and net prices)

**The Problem:**
In WooCommerce, taxes are determined based on the **customer’s location (shipping address)**, while CURCY switches prices based on **currency / billing context**.

This leads to inconsistencies, especially for Switzerland:

* Swiss customers (shipping to Switzerland) → CHF net pricing (correct)
* Swiss customers with German shipping address → CHF gross pricing (also correct)
* Googlebot / Merchant Center → often detected as non-Swiss location → CHF gross pricing (incorrect for feed validation)

However, for Google Merchant Center:

* The feed for Switzerland must show **CHF net prices**
* The landing page must show **exactly the same price**

Because CURCY does not influence the tax logic, the same product can appear:

* Net in some cases
* Gross in others
* Even when the currency is CHF

This causes **price mismatch errors** in Google Merchant Center.

**Question:**

Is there any possibility within CURCY to:

1. Link currency to tax behavior (e.g. CHF → automatically apply Swiss tax rules / net pricing)?
2. Force a specific tax location based on selected currency?
3. Provide hooks, filters, or settings to control tax display when currency is switched?
4. Prevent AJAX/JS from overriding server-side tax calculations in such cases?

**Goal:**
To ensure that when the currency is set to CHF (especially via feed URLs like `?wmc-currency=CHF`), the shop consistently displays **net prices**, independent of geolocation or bot detection.

This is crucial for compliance with Google Merchant Center requirements.

At the moment, this requires custom workarounds, but a native solution in CURCY would be significantly cleaner and more robust.

I would really appreciate your guidance on whether this can be handled with existing features or if there is a recommended best practice.

Thank you very much for your support.

Best regards Keser