Quote from Alex Dovlatov on April 27, 2026, 12:15

Hello Tas

Good news — what you need is fully supported.

To force a specific currency based on the Polylang language URL, use this ready-made snippet: https://currency-switcher.com/switch-currency-with-language-change

This gives you exactly the behavior you described: each URL always shows one fixed currency, GeoIP is not involved, and Google Merchant Center will have no issue with it.(test it please on your side to avoid conflicts with another plugins)

For currency-specific pricing per product, FOX has a Fixed Prices feature (see tab Advanced) — you can set a fixed price in each currency directly on the product level. This is stored in product meta and is completely independent of any dynamic detection.

Regarding your currency count: the free version supports up to 2 currencies. Since you need USD, EUR and CAD, you will need the Pro version https://currency-switcher.com/downloads

 

Quote from Umit on April 27, 2026, 12:30

Hello,

Thank you very much for your quick and helpful response — that's great news!

I will test the snippet from https://currency-switcher.com/switch-currency-with-language-change on my staging environment before deploying it to production, to make sure there are no conflicts with my other plugins.

I also have one additional question:

Since I am targeting multiple countries (USA, Belgium, France, Canada) with different language URLs in Polylang, the "Welcome currency" option in FOX is causing me an issue. It forces all first-time visitors and search engine crawlers (Google, Bing, etc.) to see the same currency on their first visit, regardless of the URL they land on.

For example, if my Welcome currency is set to USD and a Belgian visitor lands directly on /fr/ (French URL), they see USD on their first page load before the Polylang URL detection kicks in. This creates a brief mismatch between the URL language and the displayed currency, which is exactly what Google Merchant Center flags as misrepresentation.

My questions:
1. Is there a way to completely disable or bypass the "Welcome currency" feature so that the currency is determined ONLY by the URL/language from the very first page load?
2. Is there a hook or filter I can use to override the welcome currency based on the URL before it is applied?
3. In FOX Pro, does this behavior change? Can the welcome currency be set per language/URL natively?

I want to ensure that:
- / (English) → USD from the very first visit (no other currency shown briefly)
- /fr/ (French) → EUR from the very first visit
- /en-ca/ → CAD from the very first visit
- /fr-ca/ → CAD from the very first visit

Thank you again for your help. Looking forward to your response.

Best regards,
Tas Umit

Quote from Alex Dovlatov on April 28, 2026, 11:14

Hello Tas

The Welcome currency feature does not have a disable button, but your concern is fully solvable with a simple filter snippet.

The way Welcome currency works internally: on the very first visit it calls get_option('woocs_welcome_currency') to decide what to show. WordPress fires a standard filter at that exact moment, so you can intercept it and return the correct currency based on the URL before it is ever applied to the session.

Add this to your theme's functions.php or a custom plugin:

add_filter('option_woocs_welcome_currency', function($value) {
    $uri = $_SERVER['REQUEST_URI'] ?? '';
    if (strpos($uri, '/fr-ca/') !== false) return 'CAD';
    if (strpos($uri, '/en-ca/') !== false) return 'CAD';
    if (strpos($uri, '/fr/')    !== false) return 'EUR';
    return 'USD';
});

This runs inside the Welcome currency block itself, so there is no brief mismatch — the correct currency is set from the very first page load, regardless of which URL the visitor or Google bot lands on.

This behavior is identical in the free and Pro versions. The only difference between them is the number of currencies allowed.

Please test on staging first as always.

p.s. one important note for testing: the Welcome currency logic only fires on the very first unique visit per browser session. If you reload the page or visit again in the same browser, it will not fire again. To properly test this snippet, use different browsers or a VPN to simulate a fresh first visit each time — otherwise you will not be able to tell whether it is working correctly.

Welcome!