Every week a merchant tells us some version of the same story: they turned on Shopify Markets, added two or three target countries, watched the currency switcher appear on the storefront, and then waited for the international orders that never came. The dashboard says the markets are live. The traffic reports even show visitors from those countries. But the sales line for anything outside the home market stays flat, and it is not obvious why.
If that is you, the good news is that the cause is rarely mysterious and rarely the product. Shopify Markets is very good at making multi-market expansion look finished, and that is exactly the trap. Setup is not the same as being localized, and international buyers can feel the difference within a few seconds of landing on the page. This guide walks through why an international Shopify store stops short of selling, in the order the problems actually bite, and what to fix first.
Why is my international Shopify store not selling?
The short answer: your international store is not selling because it is set up for other markets but not localized for them. Shopify Markets gives you the scaffolding, the languages you can enable, the currencies, the domain or subfolder routing, but it does not translate your content, adapt your pricing presentation, or build local trust. When a buyer in Germany or Japan lands on a storefront that is 70% translated, priced in a way that feels foreign, and missing the reassurance signals they expect, they leave. They rarely complain. They just do not buy.
Flat international sales almost always trace to one of five gaps, and most struggling stores have more than one at once:
- The storefront is only half-translated.
- Pricing, currency, or tax display looks foreign or wrong.
- There are no local trust signals at the moment of decision.
- The translated pages were never found by search engines.
- Checkout introduces friction from missing local payment or address norms.
The rest of this guide takes each one in turn. If you only do one thing first, shop your own store as a local buyer would (the diagnostic below walks you through it), because that single exercise surfaces most of these gaps in ten minutes.
The setup-is-done illusion
Shopify Markets is a routing and configuration layer. When you add a market, Shopify sets up currency conversion, tax rules, and the URL structure that sends buyers in that region to the right version of your store. Shopify’s own Markets documentation is clear that enabling a language makes it available, not translated. That distinction is where most flat-sales stories begin.
The illusion is convincing because the admin gives you green checkmarks. The market is active. The language is enabled. The currency shows the right symbol. Everything reads as complete. But a green checkmark next to “German” only means German is switched on as an option, not that a single word of your catalog has been rendered into German. A buyer who switches to that locale and sees English product descriptions has just learned that the store is not really built for them, and that impression is very hard to recover from.
Treat Markets as the frame and the content as the painting. Markets gets the frame on the wall. Everything a buyer actually reads, the products, collections, pages, navigation, policies, and metafields, is content you still have to localize.
Reason 1: The storefront is only half-translated
This is the single most common cause of flat international sales, and it is worth being precise about what “half-translated” means. It almost never looks like a store that is 50% English. It looks like a store that is 90% translated with the last 10% left in the default language, and that last 10% is disproportionately the trust-critical surface.
The pattern we see over and over: homepage and top product titles translated, but product descriptions truncated back to English partway down, size guides in English, shipping and returns policies in English, cart and error messages in English, and image alt text still in English. Each untranslated element is a small signal that the store was not really made for this buyer, and they compound. A shopper forgives one. By the third English string on the path to checkout, they have quietly concluded this is a foreign store that might not ship to them, might not support them, and might not honor returns.
The reason this happens is structural. Manual translation covers the pages people remember to translate and skips the ones buried in settings. App-based translation that only covers product titles and descriptions leaves metafields, theme strings, and policy pages behind. This is exactly the failure mode we wrote about in 5 Shopify translation mistakes hurting your sales: set-and-forget partial coverage that looks done from the admin and reads as broken from the storefront.
The fix is to translate the whole surface, not the memorable pages. With LocaleFlow, the full resource set, products, collections, pages, blogs, menus, metafields, and image alt texts, is one configuration step rather than a checklist you can half-complete; you can see the field-level controls for exactly which resource types are in scope. Whatever tool you use, the standard to hold is simple: a buyer should be able to travel from homepage to order confirmation without meeting a single word of your home language.
Reason 2: Pricing and currency look foreign
Even a fully translated store can feel foreign at the moment that matters most, when the buyer looks at the price. Localization of money is not just currency conversion, and Shopify Markets does the conversion but leaves the presentation to you.
Three things go wrong here:
- Unrounded converted prices. A product that is a clean 49 in your home currency converts to 53.87 in the target currency. Native competitors show 49.90 or 55. An algorithmically converted price signals “this store is not really local, it is a foreign store guessing at my currency.” Shopify Markets supports price rounding rules per market; use them.
- Tax-display expectations. Some markets expect tax-included consumer pricing by law and by habit. A German or Japanese buyer who sees a price that jumps at checkout because tax was added on top reads it as a bait-and-switch, even when it is legal in your home market. Configure tax-inclusive display for markets that expect it.
- Shipping and duty surprises. A price that looks fine until an import duty or unexpected shipping fee appears at the door is the most expensive kind of foreign-feeling. Where you can, ship Delivered Duty Paid so the checkout total is the final total.
The through-line: a price that reads as locally native converts; a price that reads as converted-from-abroad hesitates. This is a presentation problem, not a translation problem, and it is why fully translated stores can still stall.
Reason 3: No local trust signals
Buyers in a new market do not yet know your brand, so they read the storefront for proxies of trustworthiness, and those proxies are local. A store that is linguistically translated but culturally generic still fails the trust test.
The signals buyers look for are specific and vary by market: a returns policy stated clearly in their language and reachable from the product page, local payment methods they recognize, a delivery estimate that sounds realistic for their country, an address form that matches how addresses actually work where they live, and contact or support options that imply someone will answer in their language. Missing any of these does not produce a complaint. It produces a closed tab.
This is the layer that separates a technically correct localization from a commercially effective one, and it is the theme of our Shopify localization for Japan playbook: the language layer is necessary but not sufficient, because market conventions, address formats, and payment norms carry as much conversion weight as the words. The remedy is not more translation; it is auditing each target market for the two or three trust signals that market specifically expects, and making sure they are visible before the buyer has to decide.
Reason 4: Search engines never found your translated pages
Sometimes the store is beautifully localized and still not selling, for the simplest possible reason: nobody is arriving. If your international traffic is near zero rather than converting poorly, the problem is discovery, not conversion, and it usually lives in your hreflang and sitemap setup.
Translated pages need three things to earn organic traffic: correct hreflang annotations so search engines understand which language version serves which region, a locale-aware sitemap so those pages get crawled, and internal links between language versions so discovery does not depend on the sitemap alone. Miss these and your translated content technically exists but never surfaces in local search results. The pages are there. Google just never shows them.
This is common enough that we dedicated a whole guide to it. If your international traffic is thin, work through the complete multilingual SEO guide for Shopify before touching anything else, because no amount of conversion tuning helps a page that gets no visitors. A good translation tool handles the SEO fields, meta titles, descriptions, URL handles, and alt text, as part of translating the page, so the translated version is search-ready rather than search-invisible.
Reason 5: Checkout friction from local norms
The last gap sits at the highest-stakes moment, the checkout, where a small mismatch loses a buyer who was otherwise ready. Shopify’s checkout is strong, but a few local conventions still trip up international carts.
| Friction point | What buyers expect | Quick fix |
|---|---|---|
| Payment methods | Local wallets and card networks, not only Visa/Mastercard | Add the dominant local method per market (for example iDEAL, Konbini, or SEPA) |
| Address format | Fields ordered the way addresses work locally | Verify Shopify’s country-specific address layout renders in the target locale |
| Currency at checkout | The same currency shown while browsing | Confirm the market currency carries through to the payment step |
| Untranslated checkout strings | Their language all the way to confirmation | Translate checkout-adjacent content and error states, not just product pages |
None of these is exotic, but each converts a “ready to buy” into an “I will come back later” that never happens. The pattern that ties Reason 5 to Reason 1 is the same: the further a buyer travels toward payment, the more expensive an untranslated or foreign-feeling element becomes.
The fastest diagnostic: shop your own store
Before you invest in any fix, run the ten-minute diagnostic that surfaces most of these gaps at once. Switch your storefront to the target locale and complete a purchase as a local buyer would:
- Land on the homepage in the target locale. Is every visible string translated?
- Open a product page. Read the full description, the size guide, and the metafields. Any English?
- Check the price. Is it rounded like a local price, and is tax displayed the way this market expects?
- Add to cart and open the cart. Are the cart and any promo or error messages translated?
- Begin checkout. Does the address form match the local format? Are local payment methods present?
- Look for trust signals: returns policy in-language, delivery estimate, support contact.
- Search Google for one of your products in the target language. Does your translated page appear at all?
Write down every friction point. That list, in order, is your fix backlog. Most merchants are surprised how far the storefront falls short of “done” the moment they stop looking at the admin and start looking at the store the way a buyer does.
How to fix a store that is not selling internationally
Work the fixes in the order the problems bite, not the order that is easiest:
- Complete the translation of the whole surface first. A half-translated store leaks trust on every page, so full coverage is the highest-leverage fix. Products, collections, pages, blogs, menus, metafields, alt text, and policies, all of it, in every enabled locale.
- Fix pricing and currency presentation. Add rounding rules, set tax-inclusive display where markets expect it, and remove door-step duty surprises with DDP where you can.
- Add the local trust signals. Returns policy in-language, local payment methods, realistic delivery estimates, and correct address forms per market.
- Fix discovery. Verify hreflang, submit locale-aware sitemaps, and internally link language versions so search engines rank your translated pages.
- Remove checkout friction. Local payment methods, local address layouts, and translated checkout strings all the way to confirmation.
The first step is both the largest and the one that unblocks the rest, which is why it comes first. It is also the step where the right tooling changes the math. Doing full-surface translation by hand across several locales is a project; doing it with LocaleFlow is about five minutes of setup, after which every enabled locale auto-syncs when your content changes, on clear tiers — $49/month for 2 languages (Local) or $150/month for unlimited (Global) — with no word counts or per-word overages.
Conclusion
An international Shopify store that is not selling is almost never a store with a bad product. It is a store that Shopify Markets made look finished before it was localized. The buyers arrive, meet a half-translated page or a foreign-feeling price or a checkout that does not fit their country, and quietly leave. Close those five gaps, starting with full-surface translation, and the market you already turned on starts behaving like a market you actually built for.
If the language layer is where you are stuck, that is the part LocaleFlow makes easy: install it, enable your locales, and the full resource set is translated and kept in sync automatically. Start translating and give the international traffic you are already getting a store worth buying from.