Skip to content

Configuration

This is where GeoSync Pro comes to life. In a few minutes you'll enable currency localisation — showing each guest prices in their local currency based on the country we detect from their IP address — pick a fallback currency, and map the countries you sell to. Every control lives under Addons → GeoSync Pro → Currency.

GeoSync Pro Currency configuration tabAddons → GeoSync Pro → Currency

Who is affected

Only guest (logged-out) visitors on a public IP are localised. Logged-in users always keep their own profile currency — GeoSync Pro never overrides their choice. Private or localhost IPs (like 127.0.0.1 or 192.168.x.x) can't be geolocated, so test in a logged-out or incognito window.

1. Enable Currency Localisation

Open Addons → GeoSync Pro → Currency and turn on Enable Currency Localisation. This is the master switch: when it's on, GeoSync Pro auto-detects each guest's country and sets the client-area currency to match. When it's off, WHMCS behaves normally and nothing is localised.

Requires an active license

Currency localisation only runs while your license is active. If a license lapses the feature pauses until it's active again — see Licensing.

2. Set the Default Currency

Choose a Default Currency. This is the safe fallback: it's used whenever a visitor's country cannot be detected or has no mapping configured below. Pick the currency that makes the most sense for the bulk of your traffic (often your primary storefront currency).

3. Add Country-to-Currency Mappings

The Country-to-Currency Mappings table is the heart of your setup. Each row pairs one country with the currency that country's visitors should see, in two columns:

ColumnWhat to enter
Country CodeAn ISO 3166-1 alpha-2 code — the two-letter country code, e.g. IN for India, GB for the United Kingdom, JP for Japan
CurrencyThe WHMCS currency those visitors should see

Click Add Mapping to add a row, fill in both fields, and repeat for every country you want to target. Use the remove control on a row to delete a mapping you no longer need.

The single EU rule

Instead of adding 27 separate rows for the European Union, add one mapping with the country code EU. This single EU rule applies your chosen currency to visitors from all 27 EU member states at once — a fast way to serve, say, EUR across the whole bloc. Add specific country rows (like SE for Sweden) alongside it if particular EU countries need a different currency; a specific country match takes precedence.

Currencies must exist in WHMCS

Every currency you map has to already exist and be active in WHMCS under Setup → Payments → Currencies. The Active WHMCS currencies reference table on this tab shows exactly which currencies are available so you can map with confidence. If a mapped currency isn't set up in WHMCS, guests can't be switched to it.

4. (Optional) Hide the Currency Switcher

Turn on Hide Currency Switcher if you'd rather guests didn't override the currency you've localised for them. When enabled, it hides the currency selection dropdown and the registration page's currency field for logged-out visitors — logged-in users are unaffected.

Third-party themes and order forms

The built-in hide works with the standard WHMCS templates Six, Twenty-One and Nexus. If you use a third-party theme or order form (for example Lagom), you may also need to disable the switcher in that theme's own settings. GeoSync Pro warns you on-screen when your active template or order form isn't one of the defaults.

Registration-page auto-switch

On the registration form, currency updates automatically the moment a visitor changes their country selection — so the prices they're about to sign up for always match the country they say they're in, without a page reload.

Save and verify

Save your changes (you'll see "Settings saved successfully."). To confirm localisation is working, browse your client area in a logged-out or incognito window from a public IP — you should see prices in the currency mapped to your country, or your Default Currency if there's no match.

Where to go next

Documentation for the Relyweb app catalogue.