CURCY eCommerce is a WooCommerce multi-currency and currency switcher plugin for WordPress, sold on CodeCanyon as “CURCY – WooCommerce Multi Currency – Currency Switcher” and developed by villatheme. It lets a store display product prices in more than one currency, convert those prices using manual or automatically refreshed exchange rates, and accept checkout in the currency the shopper selects. It suits store owners selling cross-border who want localised pricing without building a custom conversion layer, and it is a poor fit for stores that treat currency switching as a purely cosmetic display trick.
The plugin has been purchased more than 16,000 times and holds a 4.92 out of 5 rating across 187 reviews, which is a strong signal of stability for a CodeCanyon item in this category. It requires WooCommerce and a reasonably current WordPress install, and it ships with unminified source files in PHP, JavaScript and CSS for developers who want to extend it.
What the plugin actually does beyond swapping a symbol
At its simplest, CURCY changes the currency symbol shown next to a price. The more useful behaviour is what happens underneath. Exchange rates can be entered by hand or pulled automatically from an external rate provider on a schedule measured in hours, days, weeks or months. The vendor names VillaTheme’s own endpoint, Google Finance and Yahoo Finance as the available sources, and states that more providers will be added. An admin notification email can be sent each time a rate refresh runs, which matters on stores where a stale rate directly affects margin.
Three switching mechanisms are available, and they are not interchangeable. A currency bar can be placed in a theme location, a price switcher can sit next to the product price, or a shortcode can be dropped anywhere in content. Shortcodes also cover displaying live exchange rates and forcing product prices into a specific currency, which is useful for landing pages aimed at a single market.
Pricing control that goes past simple conversion
Converted prices rarely land on tidy numbers, so the plugin supports fixed prices per currency. A fixed price overrides whatever the exchange rate calculation produces, which is how stores avoid selling a product at an accidental loss in a currency that has moved. Formatting controls let the store control how the final figure is presented, and custom currency symbols mean the US dollar can render as USD, US$, or $ depending on context. Currencies that are not wanted on the front end can be hidden entirely.
Exchange fees can be layered permanently onto a rate. If a payment processor or bank charges a margin on conversion, adding that margin into the displayed rate means the store is not absorbing the difference on every order.
Detection, checkout and language
Automatic detection works from the visitor’s IP address to infer country, and the plugin maps countries to currencies. Detection operates at country level only; the vendor explicitly notes that states, provinces and regions within a country are not distinguished. Where detection feels too aggressive, an approximate price mode shows the store’s default currency as the main price with an estimated local figure underneath, which is a softer introduction than a forced switch.
On the checkout side, payment methods can be restricted per currency, a specific currency can be forced at the point the order is placed, and the selected currency can change when a customer edits their billing or shipping address. There is also handling for the case where a single product page and the checkout page would otherwise show different currencies. Currency selection can follow WPML or Polylang language, which keeps a translated site internally consistent.
Where CURCY fits, and where it does not
A store shipping to several countries with a single base currency is the obvious candidate. So is an agency building a localised storefront where the client wants prices shown in the visitor’s currency but settled in the merchant’s own. Fixed pricing per currency makes the plugin viable for stores with thin margins, where an automatically converted price could fall below cost. Stores already running WPML or Polylang get the most out of the language-to-currency mapping.
It is the wrong choice for a store that only needs a decorative switcher with no real conversion behind it. It is also a poor fit for heavily cached sites that rely on automatic geolocation detection, because the vendor states plainly that auto-detect country features may not work correctly behind caching and recommends testing the free version first. That is an honest warning rather than a hidden limitation, and it should be taken literally: on a full-page-cache setup, detection is the part most likely to misbehave.
One further caveat is technical rather than commercial. The plugin supports restricting the currency bar to specific pages through WordPress conditional tags, and it evaluates those tags using PHP’s eval() function. The vendor flags this as dangerous because it permits arbitrary PHP execution, and instructs users to enter only conditional tags that are validated or supplied by trusted developers. Any store that lets non-technical staff edit that field is accepting a real security risk.
Strengths and limitations
Strengths
- Manual and scheduled automatic exchange rates, with a choice of rate providers and an email notification on each refresh.
- Fixed prices per currency override calculated prices, protecting margin on volatile pairs.
- Permanent exchange fee markup so processor conversion costs are passed through rather than absorbed.
- Three switching interfaces plus shortcodes, giving control over placement without theme edits.
- Approximate price mode offers localised context without forcing a currency change.
- Checkout-level controls: per-currency payment methods, forced currency at order placement, and currency updates when the address changes.
- WPML and Polylang integration ties currency to language.
- Session-based storage as an alternative to cookies, which helps where cookie consent or caching interferes.
- Source files included, so the plugin can be extended or audited.
- Strong marketplace track record at 16,023 sales and a 4.92 rating.
Limitations
- Geolocation detection is unreliable behind page caching, a limitation the vendor acknowledges and does not solve.
- Country detection stops at national borders and cannot differentiate states or regions, which matters for large markets with regional pricing expectations.
- The conditional-tag field relies on eval(), creating a genuine code-execution risk if misused or exposed to untrusted editors.
- Only three exchange rate sources are named, and the vendor describes additional providers as future work rather than shipped functionality.
- Automatic rate updates run on a schedule measured in hours at best, so no setup is truly real-time.
- CSV import is limited to adding or changing fixed regular and sale prices; the vendor does not state broader bulk data handling.
How it compares with the wider multi-currency category
Multi-currency tools for WooCommerce generally fall into two groups. The first displays converted prices but settles everything in the store’s base currency, effectively treating other currencies as an informational layer. The second attempts true multi-currency checkout, where the customer is charged in the currency they selected. CURCY sits closer to the second group: it supports per-currency payment methods, a forced currency at order placement, and address-driven currency changes, which are the mechanics a store needs when the transaction itself is multi-currency.
Against lighter display-only plugins, CURCY carries more configuration surface. That is an advantage for stores with real cross-border pricing strategy and a disadvantage for stores that want a switcher installed in five minutes. Against fully managed currency services that handle conversion and settlement on the merchant’s behalf, the plugin keeps control and cost in the merchant’s hands but also keeps the responsibility there, including the job of choosing sensible rates and margins.
The fixed-price and exchange-fee features are the practical dividing line. A store that needs neither can probably use something simpler. A store that needs either will find that most of the lighter alternatives do not offer them.
Frequently Asked Questions
Does CURCY work with page caching plugins?
Partly. The vendor states that automatic country detection may not function correctly on sites or servers that use caching, and recommends testing the free version first. Currency switching itself is unaffected. The workaround is to rely on manual switching, language-based selection, or session storage instead of IP-based detection on cached sites.
Can customers actually pay in their own currency?
Yes, if the store enables it. The plugin allows payment methods to be selected per currency and can force a specific currency at the moment the order is placed. Whether a given payment gateway accepts that currency is a separate matter decided by the gateway, not by the plugin.
How does the plugin update exchange rates?
Rates can be set manually or refreshed automatically on a schedule of hours, days, weeks or months. The vendor names VillaTheme’s own service, Google Finance and Yahoo Finance as rate sources. The admin can also receive an email notification each time an automatic update runs.
Is CURCY compatible with WPML and Polylang?
Yes. Currency selection can follow the site’s WPML or Polylang language, so a translated page displays in a matching currency. The vendor also lists WPML among the plugin’s compatible software, alongside Elementor, Elementor Pro and Visual Composer for page-building compatibility.
Verdict
CURCY is worth buying for stores that sell across borders and need pricing decisions the store controls: fixed prices per currency, a conversion margin, and checkout that respects the currency the customer chose. The 16,023 sales and 4.92 rating support that it holds up in production, and villatheme has kept it updated against recent WordPress and WooCommerce releases. It is not the right purchase for a store that only wants a cosmetic switcher, nor for a fully cached site expecting reliable IP-based detection without testing. Anyone planning to use the conditional-tag field should treat it as developer-only territory given the eval() dependency. Stores that need none of the fixed-price or exchange-fee features can reasonably look at lighter options.
