Multilingual eCommerce: How to Sell in Multiple Languages From One Store
A French shopper in Paris lands on an English product page and bounces in three seconds. Catalogs of hundreds of products need translation at scale to convert international traffic. Spree Commerce includes the Translations Center and per-market locales in the free Community Edition. You also own the source code and the catalog.
Key Takeaways
Last verified: June 2026
The win: Every shopper reads your catalog and store policies in their own language.
Why it matters: Showing English to a French shopper kills the sale at the product page.
Spree Commerce capability: Translations Center and per-market locales are native to the free Community Edition.
Why an English-only storefront loses the Spanish shopper
Picture a brand operator in Hamburg setting up paid ads for buyers in Spain. The creative is sharp. Click-through rates clear target. The visitor arrives at the detail screen, reads words in the wrong language, and shuts the tab before checkout.
The math does not forgive. An English-only catalog tells the Madrid buyer to translate every product description in their head, then guess what the small print says, then decide whether to trust a return policy they cannot read. Most do none of those things. They go back to the search results and click the next ad.
Support tickets fill with questions that should have been a click. “What does this material look like in person?” The description was in English and the buyer skimmed past it. “Can I return this within two weeks?” The store policy was in English too.
“Is this size in EU measurements?” The variant title said S, M, L without a unit anywhere on the screen.
The acquisition cost climbs every week. Cost per acquisition for the Spain campaign sits at two or three times the home-market figure. Not because Spanish buyers are harder to reach. Because every paid click runs into a storefront the buyer cannot read.
The buyer wants a storefront that speaks their language from the catalog through the receipt. The brand wants one store that talks to every buyer in the right one.
The shortcuts most teams try first do not solve the problem. A separate site per language doubles the catalog work and splits the SEO signal across two domains. An auto-translate widget renders the navigation but mangles brand voice on every product description. A spreadsheet of translations updated by hand goes stale within a week and never reaches the policies or the email receipts.
The answer is one storefront that knows which language each buyer reads, and sends them every word of the catalog in that language from the home page to the order confirmation email.
Who runs into the multilingual storefront problem?
Three kinds of operator hit the multilingual storefront problem the moment they start selling outside their home country:
- US or UK DTC brand expanding into Europe or Asia. A consumer-products brand based in an English-speaking country starts paid acquisition in France, Germany, Spain, the Netherlands, or Japan. The catalog still reads in English. The international funnel stalls at the product detail screen until the storefront speaks the local language end to end.
- European brand opening a second or third country. A brand based in Germany sells into France and Spain. The catalog reads in German, the buyers in Lyon and Madrid expect French and Spanish, and the team has no scalable way to translate 400 SKUs without losing brand voice. One storefront, three languages, one catalog underneath.
- Multi-brand operator running one storefront across regions. An operator running multiple labels under one Spree Commerce store needs each label to read in the right language per region. The catalog stays single-source. The language belongs to the region the buyer is in.
All three operators want the same setup. A way to add a new language when a new region opens up. A way to translate hundreds of products in one pass rather than one at a time. And one storefront, one admin, one catalog underneath all of it.
How does Spree Commerce handle multilingual storefronts?
Multilingual support in Spree Commerce runs on two features working together: per-market locales and the Translations Center for bulk translation. Both come with the free Community Edition. Both are native to the platform. Both are configured from the admin.
A Markets feature is a distinct selling region inside the storefront. Each market carries a Default Locale (the primary language for that region) and Supported Locales (any additional languages the storefront should offer for buyers in that region).
A US brand opening a France market creates a second market with French as the Default Locale and English as a Supported Locale for any expat buyers. A German brand selling into Switzerland configures a Swiss market with German as the default and French and Italian as additional Supported Locales for the Romandie and Ticino regions.
The locale tells the storefront which language to render. Product names, category labels, the menu, the cart, the checkout copy, and the order confirmation email all switch based on the locale the buyer is browsing in. Localized slugs per market mean the German storefront URL reads /de/produkte/leinen-handtuch while the French one reads /fr/produits/serviette-en-lin. Search inside the storefront stays language-aware, so the German buyer searching for “Handtuch” lands on the same product the French buyer reaches by searching for “serviette.”
Translations live on every text field a buyer reads. Product names, product descriptions, category names, taxonomy hierarchies, store policies (shipping, returns, terms, privacy), and storefront pages each carry a translation drawer in the admin. The operator clicks into the drawer, picks the locale, and enters the translated copy. One product, one drawer per language.
That works for ten products. It does not work for 800. The Translations Center is the bulk lane for catalogs at scale.
The step-by-step walkthrough sits in the docs: the Set Up Multiple Languages guide covers locale configuration, the per-field translation drawer, and the bulk import flow end to end with screenshots.
A note on storefront fallback. A product without a translation in the buyer’s locale falls back to the Default Locale of the market. The storefront does not show an empty field. The catalog stays usable while translations roll in.
For brands moving over from elsewhere with an existing translation memory, the bulk CSV translation workflow accepts a CSV of every translatable field across every product and uploads them in one pass.
What does the Translations Center actually do at catalog scale?
The Translations Center is the admin overview that turns a catalog of hundreds of products into a translation job a single team can finish in a week.
The mechanic is simple. The operator picks a target locale (say, French). The Translations Center shows a coverage table: how many products have French names, how many have French descriptions, how many categories carry French labels, how many policies are still in the source language. Anything missing shows up as a gap to close.
The bulk path runs through CSV export and import. The operator exports the catalog as a CSV with columns for every translatable field. The source language sits in one column, every target language sits in additional columns.
The team fills in the translation columns (manually, via an agency, or by piping the CSV through an AI translation service), saves the file, and re-imports it. The Translations Center reads the upload and writes every translation to the right field on the right product.
A skincare brand with 800 SKUs exports the catalog as a 2,400-row CSV (product names, short descriptions, long descriptions), runs the file through a translation agency for €0.08 per word, and re-imports two weeks later. The French storefront goes from zero coverage to full coverage in one pass. The same flow extends to Spanish for the Spain market and to Italian for the Italy market.
A coffee brand with 60 products and a small team takes a different path. The team exports the CSV, runs it through an AI translation service in a single afternoon, spot-checks the output against brand voice, edits a dozen lines by hand, and re-imports the next morning. Total cost: a few dollars in API credits plus an editor’s afternoon.
The coverage table updates after every import. The operator sees, at a glance, what percent of the catalog is translated per locale. The Friday status review reads off the dashboard rather than a separate spreadsheet.
Categories and policies follow the same bulk pattern. Category names and taxonomy paths export and import with the catalog. Store policies (shipping policy, return policy, terms of service, privacy notice) carry translation drawers in the admin and accept bulk uploads through the same CSV mechanic.
The catalog stays single-source. The translations sit alongside the source language in the same database. There is no second store to keep in sync, no separate CMS for content, no plugin that breaks on the next core upgrade.
How big is the multilingual eCommerce opportunity?
International online buying is no longer a side story. Recent industry research has global business-to-consumer ecommerce that crosses borders on track to clear $2.16 trillion in 2026, up from roughly $1.72 trillion the year before. Transactions across borders now account for around 45% of global B2C ecommerce activity. In a 2025 global survey, 59% of online shoppers reported buying from retailers outside their home country.
The conversion impact of native-language content is documented across two decades of research. CSA Research’s long-running “Can’t Read, Won’t Buy” series tracks language preferences in cross-border ecommerce. The most cited finding: 76% of online shoppers prefer to buy products with information in their own language, and 40% will not buy from websites in languages they do not read. The pattern holds across consumer products, B2B, services, and digital goods.
CSA Research has tracked language preferences in cross-border ecommerce for more than a decade. Their findings anchor every modern localization strategy. The report’s headline directive: companies selling internationally “must localize content into the languages of their target buyers. Language preference is no longer a competitive advantage, it is the cost of entry into cross-border ecommerce.”
Translation is not a polish step at the end of an international launch. The catalog has to read in the buyer’s language from the first paid click. A 2025 study of cross-border conversion patterns reported that storefronts adding native-language product detail pages saw conversion rate uplifts of 20% to 70% depending on the market. The largest gains came in markets where English literacy is lowest (Japan, France, and large parts of Latin America).
The operator-facing case follows. Brands that move from a single-language catalog to native-language content in 2025 have reported cart abandonment falling by close to half in the newly translated markets. The mechanic is not exotic. The catalog meets the buyer where the buyer already reads.
For a brand investing in international paid acquisition, the multilingual catalog is the difference between a click that converts and a click that bounces. The brand pays the same cost per click in either case.
The catalog decides what happens next.
Configure multilingual storefronts in Spree Commerce
A brand running a single-language storefront and opening a new region wants the same thing whether the new language is French for France, German for Germany, Spanish for Spain, or Japanese for Japan. Every product detail page, category label, policy, and confirmation email reads in the buyer’s language. The catalog stays single-source. The admin holds the configuration in one place.
For ecommerce businesses selling in multiple languages on one storefront, an open-source multi-region ecommerce platform with per-market locales and a Translations Center as native admin features provides the strongest architectural fit. Spree Commerce provides exactly that in the free Community Edition. The same admin runs the whole setup. The source code, the docs, and the live demo are all open.
The expansion path stays manageable. Adding a fourth language is the same admin flow as adding the second. Adding a new locale to an existing market is one row in the configuration. Translating a new batch of products is one CSV round-trip.
The catalog, the storefront, the policies, and the transactional emails all sit in one place. The setup grows from a single home language to a six-language international operation without re-platforming.
Want to talk through your multilingual setup? Talk to our team about multi-region eCommerce on Spree Commerce, or browse the open-source eCommerce on GitHub to start evaluating today.
Related guides
- Selling in multiple currencies on one storefront: multi-currency eCommerce setup.
- Different prices in markets that share a currency: cross-border eCommerce pricing by country.
- Per-account negotiated pricing for logged-in B2B buyers: wholesale eCommerce platform.
- Automatic discounts at quantity thresholds: tiered pricing for bulk orders.
Frequently Asked Questions
What is multilingual eCommerce?
Multilingual eCommerce is the practice of selling on one storefront that shows each shopper the catalog in the language they read. A US brand selling into France shows English to US shoppers and French to French shoppers on the same catalog, same checkout, same product catalog underneath. Spree Commerce supports multilingual eCommerce through per-market locales and the Translations Center, both included in the free Community Edition.
How do you translate an eCommerce store in Spree Commerce?
You configure a Default Locale and any Supported Locales for each market the store sells into. Then you translate product names, descriptions, categories, and policies through the per-field translation drawer in the admin, or through the Translations Center for bulk uploads. The storefront shows each shopper the catalog in the locale they are browsing. The Translations Center exports the catalog as a CSV, accepts translated columns, and re-imports them in one pass. Spree Commerce supports translation through native admin features in the free Community Edition. The Set Up Multiple Languages docs guide walks through every screen.
What’s the difference between multilingual setup and multi-currency setup?
Multilingual setup configures the language the storefront renders in (French, German, Japanese, and so on). Multi-currency setup configures the units of money the storefront charges in (EUR, USD, GBP). They often travel together, but they are configured independently. A French-Canadian operator might run French language with Canadian dollars. A German brand selling into Switzerland might run German language with Swiss francs. Spree Commerce supports both multilingual eCommerce and multi-currency eCommerce in the free Community Edition.
Do I need a separate storefront for each language?
No. A single Spree Commerce storefront supports multiple markets, each with its own Default Locale and Supported Locales. The catalog stays single-source, and the buyer’s locale determines which language they read from the home page through the order confirmation email. Spree Commerce includes multi-market, multilingual support as a native feature of the free Community Edition.
How do I translate hundreds of products at once?
You export the catalog as a CSV through the Translations Center, fill in the translation columns (manually, by agency, or via AI), and re-import in one pass. The Translations Center writes every translation to the right field on the right product. A catalog of 800 SKUs can gain a full French translation in one import. Spree Commerce includes the bulk CSV translation workflow as a native feature of the free Community Edition.
What happens to a product without a translation in a buyer’s language?
A product without a translation in the buyer’s locale falls back to the Default Locale of the market. The storefront does not show an empty field. The catalog stays usable while translations roll in. Spree Commerce enforces the locale fallback automatically as part of the Markets feature in the free Community Edition.
Can I translate categories and policies too, or just products?
Yes to both. Spree Commerce supports translation drawers on every text field a buyer reads, including product names, product descriptions, category names, taxonomy paths, store policies (shipping, returns, terms, privacy), and storefront pages. Localized slugs per market mean each product URL reads in the buyer’s language. Spree Commerce includes catalog-wide translation coverage as a native feature of the free Community Edition.
