How to Show WooCommerce Prices in AED, SAR and Other Gulf Currencies
How to show WooCommerce prices in AED, SAR, QAR, KWD, BHD and OMR from one base currency, with the right rounding, checkout currency and caching.
Home / Blog / WooCommerce Multi-Currency
WooCommerce Multi-Currency
Guides for WooCommerce stores that sell across the Gulf and beyond: showing prices in AED, SAR and other currencies, rounding converted prices, choosing the checkout currency, VAT-inclusive pricing, geolocation, and keeping it all working with page caching.
What this category covers
A shopper in Riyadh opens a store based in Dubai and sees prices in dirhams. They can convert in their head, or open a calculator, or leave. Many leave. WooCommerce multi-currency removes that step by showing a price in the visitor's own currency, but it also opens a set of questions every store owner runs into: which rate to use, how to round, which currency the card is actually charged in, and why some visitors see the wrong price after you turn on caching.
This category is about WooCommerce multi-currency done properly for stores in the UAE, Saudi Arabia and the rest of the GCC. The guides are written for store owners, marketing managers and the developers who look after WooCommerce sites. They explain the decisions first, in plain language, and then show how to set them up.
What decisions does a multi-currency store need to make?
Before installing anything, it helps to answer these questions. Each has its own article:
| Decision | Options | What it affects |
|---|---|---|
| Which currencies to show | Only the markets you sell to, or a wide list | Clarity of the switcher, rate upkeep |
| Where rates come from | Typed by hand, or updated automatically | Price accuracy, how often prices move |
| How to round | No rounding, whole numbers, charm prices, nearest 5 or 10 | How "real" a converted price looks |
| Which currency to charge | The customer's currency, or always the store currency | Gateway support, refunds, bank fees |
| How to pick the first currency | Store default, or by visitor country | First impression, caching setup |
| How tax is shown | Prices including or excluding VAT | What the shopper sees versus what they pay |
Why do converted prices look wrong?
A product at 199 AED converted at the day's rate becomes an awkward number in another currency, with decimals no local store would print. Shoppers notice. Our rounding guide shows the common approaches: rounding to whole numbers, rounding up so you never lose on conversion, charm pricing that ends in .99, and rounding to the nearest 5 or 10 for higher-priced items. It also covers when to give up on conversion for a product and set a fixed price in that currency instead.
Which currency should the checkout charge in?
This is the question that causes the most confusion, because "showing" and "charging" are different things. A store can display prices in Saudi riyals and still charge the card in dirhams, or it can charge in riyals if the payment gateway and your bank account support it. Each choice has consequences for exchange fees, refunds and what the customer sees on their card statement. Our checkout currency article walks through the options and the questions to ask your payment provider before you decide.
How does geolocation pick a currency?
Showing each visitor their own currency on the first visit is convenient, but it depends on knowing their country. WooCommerce can look this up with its MaxMind geolocation database, and sites behind Cloudflare can read the country Cloudflare passes along. Both have limits: visitors on VPNs, travellers and company networks can be placed in the wrong country, so a visible switcher is still needed. Search engine crawlers also need care, so they index prices in the store currency rather than a random one.
Why do shoppers see the wrong price with page caching?
Page caching saves a copy of each page and serves it to the next visitor. If the first visitor chose euros, the cached copy shows euros, and the next visitor from Abu Dhabi sees euros too. This is the most common multi-currency bug we see. The fix is to make the cache keep a separate copy per currency, usually based on a cookie, or to update prices in the browser after the page loads. Our caching guide covers the setup for common caching plugins and how to test it.
How should VAT appear on prices?
The UAE and Saudi Arabia both have VAT, at different rates, and consumer pricing in the region is generally shown including tax. WooCommerce can store prices with or without tax and display them either way. Our VAT article explains the settings that decide what a shopper sees in the catalogue, cart and checkout. Tax rules change and depend on your business, so confirm the current requirements with your accountant or the tax authority.
How do you set up a multi-currency store step by step?
Whichever plugin you use, the order of work is roughly the same. Doing it in this order avoids most of the problems we are asked to fix later:
- Decide the store currency. This is the currency you price products in, report sales in and usually get paid in. Change it before you add products, not after.
- Add only the currencies you sell to. A short list is easier for shoppers and easier for you to keep accurate.
- Set rates and rounding. Check a handful of real products in each currency and adjust rounding until the prices look like ones a local store would print.
- Set fixed prices where it matters. Best sellers and products shown in ads deserve a deliberate price in each main currency.
- Choose the checkout currency. Confirm with your payment provider which currencies it can charge and settle.
- Configure caching. Make sure the cache keeps one copy per currency, then test with two browsers.
- Place the switcher. Put it where shoppers look for it, usually in the header and near the price on product pages.
- Place a test order in each currency. Check the order email, the admin order screen and a refund before you announce the change.
How do you check that prices are right after launch?
Exchange rates move, products change and plugins update, so a store that was right on launch day can drift. A short monthly check catches most issues: open a few product pages in each currency in a private window, compare one converted price against the current rate, add a product with a coupon to the cart and confirm the discount converted correctly, and look at your latest orders to see which currencies customers actually use. If a currency gets almost no orders, consider removing it to keep the switcher simple.
It also helps to keep a short note of every setting you chose and why: the rounding rule, which products have fixed prices, which currency the gateway charges. When someone else takes over the store, or when you review prices a year later, that note answers questions nobody remembers.
Where Ston Currency fits
We built the Ston Currency Switcher for WooCommerce stores in the region, and it is free. It lets shoppers see and pay in their own currency while you keep managing every price in your store currency.
- As many currencies as you need, each with a rate typed by hand or updated automatically twice a day, and an optional extra fee to cover conversion costs.
- Rounding rules (none, whole number, round up, charm prices, nearest 5 or 10) and full format control for symbol, position, decimals and separators.
- Fixed prices per currency on any product or variation.
- A default currency per country, using Cloudflare or the WooCommerce MaxMind database.
- Checkout in the customer's currency, or always in the store currency if your gateway needs it. Coupons, spend limits and shipping costs are converted too.
- Works with the block cart and checkout and HPOS, and keeps a separate cached copy per currency with WP Rocket and LiteSpeed Cache.
Setup details are on the Ston Currency technical page.
What these guides do not cover
We do not give tax, accounting or legal advice, and we do not compare payment gateways. Where an article depends on a gateway feature or a tax rule, we tell you what to check and with whom.
Where to start
If you are adding currencies for the first time, start with how to show WooCommerce prices in AED, SAR and other Gulf currencies. If you already have a switcher and some visitors see the wrong currency, go straight to the page caching guide. The newest articles appear first in the list above.
Related topics on the blog: Elementor scroll animation for product pages with motion, and Elementor client handover for handing a finished store to the client's team.
Frequently asked questions
Does WooCommerce support multiple currencies by default?
WooCommerce uses one store currency. Showing and charging in other currencies needs a plugin or a payment setup that supports it.
Can I set my own price in each currency?
Yes, with a plugin that supports fixed prices per currency. This is useful for key products where a converted price would look odd.
Will a currency switcher work with WP Rocket?
It can, if the plugin tells the cache to keep a separate copy per currency. Test by switching currency in one browser and opening the page in a private window.
Which currency will the customer be charged in?
That depends on your settings and your payment gateway. Some stores charge in the shopper's currency, others always charge in the store currency and show the converted price for reference.