Kokil Thapa - Professional Web Developer in Nepal
Freelancer Web Developer in Nepal with 15+ Years of Experience

Kokil Thapa is an experienced full-stack web developer focused on building fast, secure, and scalable web applications. He helps businesses and individuals create SEO-friendly, user-focused digital platforms designed for long-term growth.

Shopify Multi-Currency and Multi-Language Setup

By Kokil Thapa | Last reviewed: September 2026

Shopify Multi-Currency and Multi-Language Setup is the difference between a store that looks global and one that actually converts abroad. Visitors expect prices in their currency and copy in their language. Shopify gives you native tools for both, but the wiring spans Markets, Payments, theme strings, and SEO. This guide walks through a production-ready setup you can ship without guesswork. If you run a Shopify or cross-platform eCommerce build, treat internationalisation as architecture, not a post-launch patch.

What does Shopify Multi-Currency and Multi-Language Setup include?

At minimum, you need three layers working together. Markets define which countries see which prices and languages. Payments and currency conversion handle what the customer pays at checkout. Translation and theme localisation control every visible string, from product titles to cart labels.

Shopify replaced many older currency apps with Shopify Markets, bundled into most paid plans. Multi-language support lives inside the admin under Settings → Languages, with the free Translate & Adapt app for inline editing. Third-party apps still fill gaps—manual exchange-rate rules, professional translation workflows, or markets Shopify does not natively support.

On florist stores like Petals Qatar and Petals Nepal, currency and language choices directly affect trust. A QAR price with Arabic or English copy reads local. An NPR storefront with Nepali strings performs better than English-only for domestic buyers. The same Shopify store can serve both when Markets and translations are configured correctly.

Shopify International StackMarketsCountries and rulesPaymentsLocal currency checkoutLanguagesTranslate and AdaptOnline Store Theme + Liquidcurrency selector, locale URLs, translated stringsSEO: hreflang, canonicals, sitemaps
Shopify Multi-Currency and Multi-Language Setup layers: Markets, Payments, translation, theme, and SEO

Core components at a glance

  • Shopify Markets — country and region groups with pricing, domains, and language assignments.
  • Shopify Payments multi-currency — lets buyers pay in local currency when your store currency differs.
  • Translate & Adapt — official app for translating products, collections, pages, and theme content.
  • Theme localisation — JSON locale files and Liquid localization objects for UI strings.
  • Geolocation — Shopify's built-in country and currency redirect based on visitor IP.

How do you enable multi-currency on a Shopify store?

Multi-currency on Shopify is not a single toggle. You enable it through Markets and Shopify Payments, then decide whether prices are converted automatically or set manually per market.

Step 1: Confirm Payments and store currency

Your store currency is the accounting base—all reports roll up to it. Go to Settings → Store details and note the currency. Enable Shopify Payments under Settings → Payments. Without Shopify Payments in supported regions, local-currency checkout options are limited and you may need a third-party gateway plus an app.

Compare current rates against your base currency using the Nepal forex rates tool when you price NPR alongside USD or AED manually.

Step 2: Create and configure Markets

  1. Open Settings → Markets in the Shopify admin.
  2. Add a market for each region you sell to—e.g. Nepal, GCC, Australia.
  3. Under each market, enable Products and pricing and choose automatic conversion or fixed local prices.
  4. Turn on Local currencies so checkout shows QAR, NPR, AUD, or EUR instead of only USD.
  5. Assign a web presence: subdomain, subfolder, or dedicated domain per market if needed.
Example market structure (conceptual):

Primary market:  Nepal     → NPR, Nepali + English
Secondary:       Qatar     → QAR, English + Arabic
Secondary:       Australia → AUD, English

Store currency (reporting): USD

Step 3: Theme currency selector

Most Online Store 2.0 themes include a country/currency selector via the localization form. Confirm your theme exposes it in the header or footer. In Liquid, the canonical pattern uses Shopify's localization API:

{% form 'localization' %}
  <select name="country_code">
    {% for country in localization.available_countries %}
      <option value="{{ country.iso_code }}"
        {% if country.iso_code == localization.country.iso_code %}selected{% endif %}>
        {{ country.name }} ({{ country.currency.iso_code }})
      </option>
    {% endfor %}
  </select>
  <button type="submit">Update</button>
{% endform %}

Do not hard-code currency symbols in theme snippets. Use {{ cart.currency.iso_code }} and money filters so amounts stay consistent after market switches.

Multi-Currency FlowVisitorIP locationMarketRegion rulesPricingAuto or fixedCheckoutLocal payAutomatic conversionShopify rate + optional markupManual local pricesPer variant per marketCustomer sees local currency through checkout
Shopify multi-currency path from geolocation to local checkout pricing

Automatic vs manual pricing

ApproachBest forTrade-off
Automatic conversionFast launch, many countriesRates shift daily; psychological pricing harder
Manual local pricesFixed NPR/QAR/USD price pointsMore admin work when catalog is large
MixedHero markets manual, rest automaticRequires clear internal documentation

For WooCommerce-to-Shopify moves, map existing currency rules before cutover. A structured Shopify migration from WooCommerce checklist prevents checkout surprises on day one.

How do you set up multiple languages on Shopify?

Language setup is separate from currency. A Nepali buyer may still want NPR.prices with English product copy, or Arabic script with QAR. Shopify supports up to 20 published languages on standard plans; Shopify Plus raises limits for complex catalogues.

Add and publish languages

  1. Go to Settings → Languages.
  2. Click Add language and choose Nepali, Arabic, French, or your target locale.
  3. Install Translate & Adapt from the Shopify App Store if prompted.
  4. Translate products, collections, pages, policies, and theme strings.
  5. Click Publish when each language reaches acceptable coverage.

For Nepali content, type directly in Unicode or convert romanized text with a romanized Nepali to Unicode converter before pasting into the admin. Shopify stores UTF-8 correctly when your theme fonts include Devanagari glyphs—verify on mobile, not only desktop.

URL structures and language switchers

Shopify generates locale-prefixed URLs such as /ne or /ar depending on your domain settings. Use the theme language selector—same localization form pattern as currency:

{% form 'localization' %}
  <select name="locale_code">
    {% for language in localization.available_languages %}
      <option value="{{ language.iso_code }}"
        {% if language.iso_code == localization.language.iso_code %}selected{% endif %}>
        {{ language.endonym_name }}
      </option>
    {% endfor %}
  </select>
  <button type="submit">Update</button>
{% endform %}

Theme JSON locale files live under locales/—for example en.default.json and ne.json. Export and version-control these when you customise button labels or cart messages. Deeper custom content may use Shopify metafields per language if Translate & Adapt does not cover a field.

Language PipelineSourceDefault localeTranslateAdapt appTheme JSONLocale filesLive/ne /arProducts, pages, policies, checkout stringshreflang tagsPer locale URLTranslated metaTitle and description
Multi-language workflow from default content through Translate and Adapt to live locale URLs

Broader Unicode and font guidance for South Asian locales appears in our Nepali language support for web apps article. Many rules apply directly to Shopify themes.

Should you use Shopify Markets or third-party apps for international selling?

Native Markets covers most stores in 2026. Reach for apps when you need features Shopify still handles poorly—complex B2B price lists per country, ERP-driven exchange rates, or translation memory across ten thousand SKUs.

When native tools are enough

  • You sell to fewer than twenty countries with standard B2C checkout.
  • Shopify Payments is available in your payout country.
  • Translate & Adapt covers your content volume.
  • You want one admin, one theme, and minimal monthly app fees.

When to add apps or custom code

Wholesale or B2B international pricing often pairs Markets with a B2B app—see our Shopify B2B wholesale setup guide for overlap pitfalls. Custom storefronts built on Hydrogen or headless stacks pull locale and currency from the Shopify Admin API (use version 2026-07 or later) via the Storefront and Admin API patterns documented for app developers.

Compare platform-level international features in the Magento 2 vs Shopify vs WooCommerce comparison. Magento multi-store still wins some enterprise scenarios; Shopify wins time-to-market for most SMB and mid-market brands.

Markets vs AppsUse Shopify MarketsAdd third-party appsStandard B2C, few countriesERP sync, complex B2B tiersShopify Payments availableCustom rate feeds hourlyTranslate and Adapt scaleTranslation agency APIStart native; add apps only for proven gaps
Decision guide for native Shopify Markets versus third-party international apps

What SEO and technical issues break Shopify international stores?

Currency without hreflang is a common gap. Google must see each language URL as an alternate, not duplicate content. Shopify emits hreflang for translated storefronts when languages are published correctly—verify in View Source on /ne/products/example and the English equivalent.

SEO checklist

  • Translate meta titles and descriptions per language in Translate & Adapt.
  • Keep one canonical URL per locale; avoid query-string language hacks.
  • Submit the language sitemap from Settings → Domains or Search Console.
  • Align Shopify SEO best practices for 2026 with your market domains.
  • Track organic performance per country in Google Analytics 4 with filtered views.

Page speed drops when themes load unused locale fonts or duplicate tracking scripts per market. Run speed optimisation after enabling Arabic or Devanagari webfonts. Lazy-load non-Latin fonts only when that locale is active if your theme allows conditional loading.

Operational gotchas I've seen on client projects

Email notifications stay in the store default language unless you customise notification templates per locale. Shipping profiles do not always map cleanly to new markets—re-test flat-rate and weight rules. Gift cards and discount codes may ignore market context. App embeds from legacy currency switchers conflict with Markets; remove them before go-live.

If you also run a Laravel sibling site for the same brand, keep currency display rules consistent with your Laravel multi-currency setup so customers are not confused between storefronts.

How do you test and launch Shopify Multi-Currency and Multi-Language Setup?

Testing is where most launches fail quietly. A wrong market rule shows USD to a Doha visitor until someone complains.

Pre-launch test matrix

  1. Use Shopify's preview or a VPN to hit each market country.
  2. Confirm product, cart, and checkout currencies match the market.
  3. Switch language on mobile—selectors often break in drawer menus.
  4. Place a real test order in each primary market; refund after verification.
  5. Validate transactional emails, packing slips, and tax lines.
  6. Run QA across browsers with Nepali and Arabic script if published.

Document market rules in a shared sheet: country, currency, language, pricing mode, domain, and owner. Future staff will not infer this from the admin alone.

For domain or platform moves, pair this work with website migration services so DNS, SSL, and redirects stay aligned with new locale paths. Technical SEO review after launch catches hreflang gaps before Search Console fills with warnings.

Key Takeaways

  • Configure Shopify Markets first, then enable local currencies through Shopify Payments—not the other way around.
  • Publish languages only after products, policies, and theme strings reach usable coverage; half-translated stores erode trust.
  • Use automatic conversion for speed and manual prices for hero markets where Rs 999 or QAR 49 matters psychologically.
  • Remove legacy currency and translation apps that fight native Markets selectors.
  • Verify hreflang, sitemaps, and GA4 country filters before you announce international shipping.
  • Test checkout with real orders per market; admin previews lie about tax and payment methods.

People Also Ask

Does Shopify support Nepali language and NPR currency?

Yes. Add Nepali under Settings → Languages and include Nepal in a Market with NPR enabled. Confirm your theme font supports Devanagari. Shopify Payments availability for Nepal-based merchants depends on payout country—many Nepal businesses use USD as store currency and manual NPR display until local payout options apply.

Can customers pay in their local currency on Shopify?

When Shopify Payments multi-currency is enabled and the buyer's country belongs to an active market, checkout can present local currency. The store currency still drives accounting. Exchange rates update automatically unless you override with fixed local prices.

Is Translate & Adapt enough for professional translation?

It is enough for SMB stores with manageable catalogues. Export CSV for agency translation when volume grows. Machine translation inside the app is a starting point, not a finish line, for legal or medical copy.

How does Shopify Multi-Currency and Multi-Language Setup affect SEO?

Published languages generate locale-specific URLs and hreflang alternates. Untranslated strings, duplicate titles across locales, and blocking the wrong country in robots.txt hurt rankings. Treat each locale as a first-class SEO surface with unique metadata.

Ship a global storefront that converts

Shopify Multi-Currency and Multi-Language Setup is achievable in a focused sprint when you sequence Markets, Payments, translations, and SEO correctly. Start native, test with real orders, and expand markets as data proves demand. Need hands-on help for Qatar, Nepal, or multi-region rollouts? Contact us for Shopify theme work, migration, and international launch support—or browse the international eCommerce portfolio for shipped examples. Read more on the blog or explore ongoing Shopify maintenance if your store is already live.

Frequently Asked Questions

Shopify Markets for country rules, Shopify Payments for checkout currency, and Translate and Adapt with theme strings for languages—three layers configured together before launch.

Multi-currency is not a single toggle. Confirm your store currency under Settings → Store details, then enable Shopify Payments under Settings → Payments. Open Settings → Markets, add a market per region such as Nepal, GCC, or Australia, enable Products and pricing, choose automatic conversion or fixed local prices, and turn on Local currencies so checkout shows NPR, QAR, or AUD instead of only your base currency. Assign web presence per market if needed. Confirm your Online Store 2.0 theme exposes a country or currency selector via Shopify's localization form, and use cart currency objects and money filters rather than hard-coded symbols so amounts stay correct after market switches.

Language setup is separate from currency—a buyer may want NPR prices with English copy, or QAR with Arabic. Go to Settings → Languages, add your target locale, install Translate and Adapt if prompted, and translate products, collections, pages, policies, and theme strings before publishing. Shopify generates locale-prefixed URLs such as /ne or /ar. Theme JSON locale files under locales/ control button labels and cart messages—export them when you customise strings. For Nepali, type Unicode directly or convert romanized text first, and verify Devanagari fonts on mobile. Standard plans support up to twenty published languages; Shopify Plus raises limits for very large catalogues.

Yes, when Shopify Payments multi-currency is enabled and the buyer's country belongs to an active Market with local currencies turned on. Your store currency still drives accounting and reports.

Native Markets covers most stores in 2026. It suits B2C sellers targeting fewer than twenty countries where Shopify Payments is available and Translate and Adapt handles your content volume—you get one admin, one theme, and minimal monthly app fees. Reach for third-party apps when you need complex B2B price lists per country, ERP-driven exchange rates, translation memory across ten thousand SKUs, or markets Shopify does not natively support. Wholesale international pricing often pairs Markets with a B2B app. Headless Hydrogen storefronts pull locale and currency via the Shopify Admin API version 2026-07 or later instead of theme selectors.

Currency without hreflang is a common gap—Google must see each language URL as an alternate, not duplicate content. Verify hreflang in View Source on translated product pages and their English equivalents. Translate meta titles and descriptions per language in Translate and Adapt, keep one canonical URL per locale, avoid query-string language hacks, and submit language sitemaps from Settings → Domains or Search Console. Page speed drops when themes load unused locale fonts or duplicate tracking scripts per market—test after enabling Arabic or Devanagari webfonts. Untranslated strings, duplicate titles across locales, and blocking the wrong country in robots.txt all hurt rankings.

Testing is where most launches fail quietly—a wrong market rule can show USD to a Doha visitor until someone complains. Use Shopify preview or a VPN to hit each market country and confirm product, cart, and checkout currencies match. Switch language on mobile because selectors often break in drawer menus. Place a real test order in each primary market, then refund after verifying tax lines, payment methods, transactional emails, and packing slips. Run QA across browsers with Nepali and Arabic script if published. Document market rules in a shared sheet covering country, currency, language, pricing mode, domain, and owner—admin previews alone misrepresent tax and payment behaviour.

Yes. Add Nepali under Settings → Languages and include Nepal in a Market with NPR enabled. Confirm Devanagari theme fonts on mobile. Payout-country rules may require USD as store currency until local Shopify Payments payout applies.

Automatic conversion suits fast launches across many countries because exchange rates update daily, but psychological price points like Rs 999 or QAR 49 are harder to control. Manual local prices fit hero markets where fixed NPR, QAR, or USD amounts matter for trust and conversion—I use this on florist stores like Petals Qatar and Petals Nepal where local currency with sensible round numbers reads trustworthy. A mixed approach—manual for primary markets and automatic elsewhere—works when you document rules clearly. Compare rates against your base currency before fixing prices, especially when USD is the reporting currency. Revisit manual prices when forex moves significantly.

For SMB stores with manageable catalogues, Translate and Adapt is usually enough—it covers products, collections, pages, policies, and theme content inline. Export CSV for agency translation when volume grows. Machine translation inside the app is a starting point, not a finish line for legal or medical copy. Publish languages only after products, policies, and theme strings reach usable coverage; half-translated stores erode trust. Deeper custom content may need metafields per language when the app does not cover a specific field. Treat professional translation as a review workflow, not a one-click publish.

Email notifications stay in the store default language unless you customise notification templates per locale. Shipping profiles do not always map cleanly to new markets—re-test flat-rate and weight rules after adding regions. Gift cards and discount codes may ignore market context. Legacy currency switcher app embeds conflict with native Markets selectors and should be removed before go-live. If you also run a Laravel sibling site for the same brand, keep currency display rules consistent with your Laravel multi-currency setup so customers are not confused between storefronts. These issues rarely surface in admin preview—they appear only in live checkout and post-order communications.

Shopify Payments is the primary path to local-currency checkout when your store currency differs from the buyer's market currency. Enable it under Settings → Payments after confirming store currency under Store details. Without Shopify Payments in supported payout regions, local-currency options are limited and you may need a third-party gateway plus an app. Your store currency remains the accounting base—all reports roll up to it regardless of what the customer pays in at checkout. Configure Markets and enable local currencies only after Payments is set up correctly, not the other way around—a sequence I have seen reversed on client projects with checkout surprises on day one.

Most Online Store 2.0 themes include country and language pickers via Shopify's localization form in the header or footer—both use the same form pattern with a country_code or locale_code select and submit button. Do not hard-code currency symbols in theme snippets; use cart currency objects and money filters so amounts stay consistent after a market switch. Language options should display endonym names from available languages. Theme JSON locale files such as en.default.json and ne.json control UI strings like cart labels—export and version-control them when you customise copy. Broken selectors in mobile drawer menus are a common failure point worth testing on real devices, not only desktop.

Configure Shopify Markets first, then enable local currencies through Shopify Payments—not the reverse. Confirm store currency and Payments before creating regional Markets with pricing rules and local currency checkout. Add languages under Settings → Languages and translate content, but publish only after products, policies, and theme strings reach usable coverage. Wire hreflang and language sitemaps after locales go live. Remove legacy currency and translation apps that fight native Markets selectors before go-live. Test checkout with real orders per market last—admin previews lie about tax and payment methods until the full stack is connected end to end.

Yes. Create separate Markets under Settings → Markets—for example a primary market for Nepal with NPR and Nepali plus English, a secondary for Qatar with QAR and English plus Arabic, and another for Australia with AUD and English. Enable automatic or manual pricing per market, turn on local currencies, and assign web presence via subdomain, subfolder, or dedicated domain as needed. Shopify's built-in geolocation can redirect visitors by IP to the appropriate country and currency. The same catalog powers all regions when market rules and translations are documented clearly. On multi-region stores I have shipped, local price and language choices directly affect buyer trust and conversion abroad.

Share this article

0 Comments

Leave a comment

Your email is not published. Comments appear once they have been read. Sign in to have your details filled in.

Quick Contact Options
Choose how you want to connect me: