# Adding support for multi-currency
In this article, you will learn how to implement multi-currency in Nosto. When the implementation is complete, you will be able to display product prices (in any feature) in different currencies.
Prior to the multi-currency implementation, ensure that the Nosto tagging is correctly in place. Some of the tagging must be slightly amended to support multi-currency.
## Shopify Multi-Currency
For instructions on integrating with Shopify's multi-currency, please go [here](https://docs.nosto.com/shopify/features/multi-currency-support).
## Changes to the product tagging
The product page tagging must be amended to denote the primary currency code of the product. Typically, most retailers have a primary currency which is the default currency of the inventory.
For example, a US-based retailer who sells in Euros (EUR) and Sterling Pounds (GBP) would have US Dollar (USD) as the primary currency while Euro (EUR) and Sterling Pounds (GBP) would be secondary currencies whose exchange rates would need to be sent via an API.
```js
nostojs(api => {
api.setTaggingProvider("products", [{
...
variation_id: "USD"
}])
})
```
or via DOM tagging
```markup
...
...
...
USD
```
Ensure that a span element with the class `variation_id` is added as a child of the `nosto_product` element within the product page tagging.
> **Note:** The code in the `variation_id` element must remain static, regardless of the currency active on-site. This is the primary currency of your catalog. Although `variation_id` element often has the same currency code as in the `price_currency_code` element and may seem redundant, they support different use cases and both need to be tagged.
### Do child-products (SKUs) support multi-currency?
Yes. Prices for all SKUs will automatically be converted using the same logic. As long as your SKUs are tagged, no additional changes are needed.
### What about the prices in the cart and the order tagging?
The cart and order tagging can be left as-is but the prices must be in the customer's currently active currency. For example, a customer shopping in Swiss Francs (CHF) should have all the cart items tagged in Swiss Francs (CHF). Failure to do so will result in incorrect prices in any triggered mails such as abandoned cart or order followup.
## Specifying the active currency
Once you have amended the product tagging, an additional DIV element must be added to all the other pages (including the product page itself). The tag should not be encapsulated in the `nosto_product` DIV tag. The information sent in the tag refers to the currency active of the customer.
```js
nostojs(api => {
api.setTaggingProvider("variation", "USD")
})
```
or via DOM tagging
```markup
USD
```
For example, on the site of a US-based retailer who sells in Euros (EUR) and Sterling Pounds (GBP), if the customer changes the currency to Sterling Pounds (GBP), the `nosto_variation` element should show `GBP`. If the customer changes the currency to Euros (EUR), the `nosto_variation` element should show `EUR`.
## Sending the exchange-rates
In order to send the exchange rate multipliers to Nosto, you will need to use [our exchange-rates API](https://docs.nosto.com/techdocs/~/revisions/pPsVnJQEjRQ7xlJwnAYO/apis/rest/other/updating-rates-using-the-rates-api). Below is a small snippet of what the payload looks like.
```javascript
{
"rates":{
"GBP":{
"rate":0.77,
"price_currency_code":"GBP"
},
"EUR":{
"rate":0.91,
"price_currency_code":"EUR"
}
},
"valid_until":"2015-02-27T12:00:00Z"
}
```
In the example above, `0.77` is the exchange rate from US Dollars (USD) to British Pounds (GBP) and `0.91` is the exchange rate from US Dollars (USD) to Euros (EUR).
The `valid_until` entry defines the expiration date. When the expiration date is reached, the exchange rates won't be applied anymore and prices will be hidden for all the secondary currencies to prevent displaying outdated prices.
When recommendations are served, then exchange rates are dynamically applied to the product prices to reflect the active currency.
## Enabling multi-currency from the admin
Once the tagging changed have been done and the API implemented, you need to configure and enable it from your admin panel under **Settings** > **Other** > **Multi-Currency**. Toggle the **Use Multiple Currencies** and **Use Exchange Rates** switches on and set the variation ID of the primary currency via the input field and toggle on the exchange rates switch.
> **Note:** Ensure that the Variation ID of the primary currency matches the value sent via the `variation_id` element in the product tagging.
You will also need to configure the price formatting for your primary and secondary currencies.
### Integration with search/category merchandising (universal)
The search/category merchandising (universal) API supports specifying the variation ID in requests using the `variationId` property of the [products object](https://search.nosto.com/v1/graphql?ref=InputSearchProducts).
If specified, the selected variation's specific properties automatically replace the corresponding values in the top-level product. All features (e.g., merchandising rules, facets, filters, sorting) work with the selected variation's values automatically when the variation ID is provided.
For Nosto code editor integrations, please refer to a [simplified version of this process](https://docs.nosto.com/techdocs/~/revisions/pPsVnJQEjRQ7xlJwnAYO/implement-search/implement-search-using-code-editor/implementing-search-page#multi-currency).
## Reviewing your changes
Once you enabled multi-currency and made an API call, you can review the exchange rates received by Nosto by navigating to **Settings** > **Other** > **Multi-currency**.
You can also preview the product prices for different currencies by navigating to **Tools** > **Products** and choosing a product.
You will see one or more dropdowns that contain the prices and price calculation for the currency.
When you have reviewed your set-up, Nosto updates in real-time product prices for all the currencies and display the appropriate currency to the right target groups of users. You’re all set and ready to go live with our features.
## See also
To learn more about the `api.setTaggingProvider` usage, please refer to the [official API documentation](https://nosto.github.io/nosto-js/interfaces/client.API.html#settaggingprovider).