When a Türkiye-based Shopify brand expands internationally, one of the first requirements is usually straightforward: European customers should see euros, US customers should see dollars, and each customer should ideally pay in the currency they expect.
The important distinction is that display currency and checkout currency are not automatically the same thing.
Shopify Markets is one layer of the solution
Markets can help organize countries and regions, languages, domains, catalogs and market-specific storefront experiences. Currency settings can also be part of that configuration.
However, the payment provider and the merchant's eligibility for specific Shopify payment capabilities still influence what can happen at checkout.
Currency display is not the same as settlement
A storefront can display a converted price without guaranteeing that the payment will be processed in that same currency.
This distinction matters when a store uses third-party payment providers. Before designing the currency selector, teams should clarify which currencies the payment provider accepts through the Shopify flow, which currency reaches checkout and how funds are settled to the merchant.
Why currency-converter apps are not the complete answer
A converter can improve the browsing experience by showing an approximate local price. But it does not necessarily change the currency used by the actual payment transaction.
For conversion and trust, merchants should avoid creating a large surprise between the currency shown on the product page and the currency presented during payment.
What about Turkish payment providers?
Some local payment providers support transactions in multiple currencies within their own product offerings. That capability should not automatically be assumed to map one-to-one to Shopify Markets or checkout behavior.
The correct test is end to end: market selection, displayed price, checkout currency, gateway request, customer charge and merchant settlement.
Architecture options for Türkiye-based brands
1. One Shopify store with a primary checkout currency
This is operationally the simplest model. International visitors can receive localized content and possibly reference currency display, while checkout follows the supported payment configuration.
The trade-off is that the payment experience may not be fully localized for every market.
2. A separate global Shopify store
As international volume grows, a separate storefront can be considered. This allows pricing, payment providers, applications and market operations to be separated.
It also creates additional work: subscription costs, inventory synchronization, ERP integration, content, SEO and operational ownership all need to be managed across stores.
3. Regional company and store architecture
Larger organizations may operate Türkiye and other regions through different legal entities and payment setups. At that point the decision includes tax, fulfillment, inventory ownership, invoicing and banking as well as Shopify.
A subdomain does not solve payments by itself
Using tr.brand.com and brand.com can help route customers to different stores or experiences. The domain itself does not determine which currencies a gateway can charge.
Company structure, store currency, gateway support, settlement and integrations still need to be designed.
Pricing strategy is also separate from FX conversion
An international price does not always need to be the domestic price divided by the current exchange rate. Shipping, returns, taxes, marketing cost and target margin can vary by market.
For that reason, multi-currency planning should include commercial pricing strategy as well as technical currency support.
Questions to answer before implementation
- Which countries will the brand sell to?
- Which currency should customers see?
- Which currency should customers actually pay in?
- Which payment provider will process the transaction?
- How will funds be settled to the business?
- Should Türkiye and global operations share one store or use separate stores?
A useful planning order is:
Market → Company structure → Currency → Payment provider → Checkout → Pricing → Store/domain architecture.
At Digimaps, we treat multi-currency as a payment and operating-model decision first, and a storefront setting second.