Selling fashion internationally means more than translating product titles. Shopify translation for fashion stores requires handling size charts that differ between regions, fabric terminology that varies by language, and color names that carry different cultural associations. Getting any of these wrong can mean returns, confused customers, and lost sales.
The global fashion market is valued at roughly $1.7 trillion (source: Statista, 2024), and according to the International Post Corporation’s cross-border ecommerce report, around 26% of fashion purchases are cross-border. For Shopify fashion merchants, that cross-border demand represents real revenue, but only if the shopping experience feels native to each market.
Why fashion stores need translation beyond the basics
Most Shopify translation apps handle the obvious stuff: product titles, descriptions, navigation menus. Fashion stores, however, have a layer of complexity that generic translation misses entirely.
A clothing store’s product page typically contains structured data that matters just as much as the description. A customer in Tokyo looking at a linen blazer needs to see the size chart in Japanese sizing (which uses centimeters and a different numbering system), care instructions in Japanese, and fabric composition described with the correct textile terminology. If the description is in Japanese but the care label says “Dry clean only” in English, that inconsistency erodes trust.
Fashion also moves fast. Seasonal collections bring new terminology: “quiet luxury,” “mob wife aesthetic,” “coastal grandmother.” These trend-driven terms don’t have direct translations and need careful localization rather than literal word-for-word conversion.
For merchants targeting French, Italian, Japanese, and Korean markets, the stakes are particularly high. These are fashion-forward audiences who notice when product content feels off.
The size chart problem
Size charts are one of the biggest pain points in fashion translation. A US size 8 is a UK size 12, an EU size 40, and a Japanese size 11. The conversion itself isn’t a translation issue, but the labels, column headers, and fit descriptions that surround the chart absolutely are.
Consider what a typical size guide metafield contains:
- Column headers: “Chest,” “Waist,” “Hips,” “Length”
- Fit descriptions: “True to size,” “Relaxed fit,” “Runs small”
- Measurement units: Some markets expect centimeters, others inches
- Size range labels: “XS-XL” is relatively universal, but supplementary text varies
The challenge is that you need to translate the descriptive text (headers, fit notes) while leaving the numeric values and size codes alone. A blunt “translate everything” approach breaks the chart. A “translate nothing” approach leaves half your product page in the wrong language.
This is where field-level translation control becomes essential. You need to pick exactly which parts of your size guide to translate, down to individual metafields.
Material and fabric terminology
Fabric names are deceptively tricky to translate. “Cotton” is straightforward, but fashion stores rarely stop there. Product pages list specific fabrics: pima cotton, silk charmeuse, ponte knit, tencel lyocell, crepe de chine. Each has an established term in French, Italian, Japanese, and Korean. Using the wrong one, or a generic substitute, signals to a knowledgeable customer that the store isn’t serious about their market.
Common metafields that fashion stores need to translate include:
| Metafield | Example content | Translation approach |
|---|---|---|
material | ”70% Merino Wool, 30% Cashmere” | Translate fiber names, keep percentages |
care_instructions | ”Hand wash cold. Lay flat to dry.” | Full translation required |
size_guide | Headers and fit notes | Translate text, preserve numbers |
fabric_composition | ”GOTS-certified organic cotton” | Translate description, keep certification names |
Color naming adds another layer. “Burgundy” in English might be “bordeaux” in French and “enji” in Japanese. But fashion brands often use creative color names: “Dusty Rose,” “Slate,” “Cognac.” These need localization that respects the brand voice, not just dictionary translation. A custom term glossary prevents your carefully chosen color names from being rendered inconsistently across languages.
How LocaleFlow handles fashion content
LocaleFlow’s approach to Shopify translation for fashion stores centers on field-level control. Instead of translating everything or nothing, you configure translation rules at the metafield level.
Here is what that looks like in practice for a fashion store:
Translate these metafields:
material- Fiber and fabric namescare_instructions- Washing, drying, ironing guidancesize_guide- Header labels and fit descriptionsfabric_composition- Textile blend descriptions
Leave these untouched:
- SKU codes and internal identifiers
- Numeric measurements
- Certification codes (OEKO-TEX, GOTS numbers)
- Color hex values
Custom term rules let you lock in how specific fashion vocabulary translates. Once you define that “silk charmeuse” translates to “charmeuse de soie” in French and “crepe de chine” stays as “crepe de chine” (since it’s already French), those rules apply store-wide. Every product that uses those terms gets the same accurate translation.
This consistency matters when you have hundreds or thousands of SKUs sharing the same fabric types. One incorrect translation multiplied across your catalog creates a cleanup headache.
LocaleFlow also syncs translations automatically when you update source content. Change a care instruction on your English product page, and the translated versions update without manual intervention. For fashion stores that rotate inventory seasonally, this keeps translated content current without requiring a manual pass through every product after each collection drop.
Getting started with fashion store translation
If you’re running a Shopify fashion store and ready to translate for international markets, here’s a practical starting point:
-
Audit your metafields. List every metafield your theme displays on product pages. Identify which contain customer-facing text (translate) and which contain codes or numbers (skip). Our metafields translation guide walks through this step by step.
-
Build your term glossary. Compile a list of fabric names, color names, and fit terms your brand uses. Define the correct translation for each in your target languages. This prevents inconsistency across your catalog.
-
Start with your top market. Don’t translate into five languages at once. Pick the market with the most cross-border traffic (check Shopify Analytics > Sessions by location) and get that right first.
-
Test with real products. After configuring translations, view your product pages in each translated language. Pay special attention to size charts, material descriptions, and care labels. These are the fields where fashion-specific errors show up.
-
Measure the impact. Use the ROI calculator to estimate the revenue impact of translating your store. Fashion’s average order value of around $85 means that even modest conversion improvements from better localization add up quickly.
Translate your Fashion store - install LocaleFlow and start translating today.
Written by Kwadwo Adu, Co-founder of LocaleFlow.