How to Translate Shopify Variant Options and Product Attributes for International Markets

A French shopper who sees "Size: Small / Medium / Large" instead of "Taille: Petite / Moyenne / Grande" isn't just reading English — they're being told this store wasn't built for them. Variant options and product attributes are some of the most-touched elements in any buying journey, and they're also the most commonly skipped when merchants set up multilingual Shopify stores.

This guide covers exactly how to translate Shopify product variants — the mechanics, the edge cases, and the decisions that most tutorials gloss over.

---

Why Variant Options Are a Localization Blind Spot

Most merchants focus on product titles and descriptions when they first go multilingual. That makes sense — those are the obvious fields. But variant options sit in a different layer of Shopify's data model, and translation apps handle them inconsistently.

The consequence is a store that looks translated on the surface but breaks the illusion the moment a shopper opens a dropdown. A German customer selecting "Color: Navy Blue" or a Brazilian customer choosing "Material: Cotton Blend" encounters untranslated strings that signal the store is either automated slop or simply not made for them.

There's also a subtler problem: attribute labels like "Fit," "Finish," or "Weight" can carry meaning that doesn't transfer word-for-word. "Slim Fit" in German fashion contexts is often left untranslated deliberately because it's become an industry term — but "Regular Fit" absolutely needs localization. These are judgment calls that require understanding both your category and your market.

For a broader picture of how product content fits into multilingual strategy, see How to Translate Shopify Product Descriptions Without Losing Conversions.

---

What Shopify Actually Translates (and What It Doesn't)

Shopify's native translation layer, accessed via the Translations API, lets you store locale-specific strings for most content types. For products specifically, the translatable fields include:

• Product title
• Product description (body HTML)
• Option names (e.g., "Color," "Size," "Material")
• Option values (e.g., "Red," "Large," "Cotton")
• Variant-level metafields (if you've added them)
• SEO meta title and description

The critical distinction: option names and option values are separate resources in the API. A common mistake is translating only the option name ("Color" → "Couleur") while leaving all the values ("Red," "Blue," "Green") in English. Both need to be addressed.

What the Translations API Looks Like in Practice

If you're building a custom integration or troubleshooting a translation app's output, it helps to see the actual API call. Here's a minimal POST request to translate an option value using the Shopify Translations API:

POST /admin/api/2024-01/translations.json
Content-Type: application/json
X-Shopify-Access-Token: {your_token}

{
  "translation": {
    "locale": "fr",
    "key": "option1.values.Red",
    "value": "Rouge",
    "market_id": null,
    "resource_id": 123456789,
    "resource_type": "Product"
  }
}

Two things worth noting from this structure. First, option values are keyed by their English source string, so if you rename "Red" to "Crimson" in your source store, any existing French translation for "Red" becomes an orphan — it won't appear. Second, the locale field maps to an ISO 639-1 code, so you need a published locale in your Shopify Markets setup before translations will render. If Markets isn't configured yet, How to Set Up Shopify Markets for Multiple Languages and Currencies Together walks through that prerequisite.

---

The Three Categories of Variant Content and How to Handle Each

1. Standard Dimensional Options (Size, Color, Quantity)

These are the most straightforward to translate but still require care. Size in particular has a localization layer beyond language: the US "Medium" may correspond to a different numerical size in Japan or Germany. A German customer expects to see "Größe: S / M / L" not "Size: S / M / L" — but they may also expect a size chart with EU sizing, which is a separate localization problem covered in How to Translate Shopify Size Charts and Units of Measurement for International Markets.

For color names, be conservative with creative naming. "Midnight Storm" as a color option is hard to translate meaningfully — if it renders as "Tormenta de Medianoche" in Spanish it may read as awkward. Either localize the creative name properly or simplify to a standard color term in each locale.

2. Technical Product Attributes (Material, Finish, Weight Class)

These are often populated via metafields rather than Shopify's native variant options, which puts them in a slightly different translation workflow. The Translations API handles metafields, but only if they're marked as translatable in your schema. If you're using product metafields to surface technical specs, check that your app or integration is including them in the translation payload — they're easy to miss. For details on that workflow, see How to Translate Shopify Metafields, Metaobjects and Custom Data.

For material names specifically: textile terms like "Modal," "Tencel," and "Merino" are internationally recognized brand terms and should usually stay untranslated. Generic terms like "Cotton," "Polyester," or "Leather" should be translated.

3. Brand-Specific Option Names

If your store uses custom option names ("Collection Tier," "Drop," "Edition") as part of your brand vocabulary, decide upfront whether these translate or stay in English. Luxury and streetwear brands often keep proprietary option labels in English globally. If you do translate them, use a translation glossary to lock down the approved translations so they stay consistent across every product that uses the same term.

---

A Practical Translation Workflow for Variant Options

Here's a process that works whether you're handling this manually or through an app:

1. Audit your option names and values across your catalog. Export them and identify which are: (a) generic terms that need translation, (b) brand/industry terms that should stay in English, and (c) creative names that need localization judgment calls.

2. Set up your glossary before you run any translation. If "Size" maps to "Größe" in German and "Taille" in French, lock that in first. Any translation — AI or human — will then apply it consistently. This prevents the scenario where "Size" becomes "Größe" on 200 products and "Maß" on 30 others.

3. Translate option names and option values as separate passes. Don't assume your tool handles both in one step. Verify in a live locale that both the label ("Color") and its values ("Red," "Blue") are rendering in the target language.

4. Spot-check dropdowns in your published storefront, not just in the app dashboard. The Translations API and Shopify's storefront rendering can occasionally be out of sync after bulk operations — a browser test in the target locale confirms what shoppers actually see.

5. Re-translate only what changes. If you update "Blue" to "Navy Blue" in your source, the old translation for "Blue" is now orphaned. A good translation workflow — or an app with change detection — should flag this automatically rather than silently leaving the old string in place.

For stores with large catalogs, How to Bulk-Translate Hundreds of Shopify Products in Minutes covers how to make this process efficient at scale.

---

Where StoreLingo Fits In

StoreLingo translates Shopify products — including option names and option values — using Claude AI across 47 languages. Merchants can review translations before publishing, which matters for variant content where a wrong color name or size label causes real confusion at checkout.

The glossary feature lets you pin specific translations for terms that appear across hundreds of products, so "Cotton" is always "Coton" in French regardless of which product it's on. You can start on the free plan (1,000 words/month) to validate the workflow on a subset of your catalog before scaling.

Add StoreLingo on the Shopify App Store →

---

SEO Considerations for Translated Variant Content

One clarification worth making explicitly: Shopify does not generate separate URLs per variant or per option value. A translated option value like "Rouge" does not create a new indexable URL. The SEO value of translating variant options is indirect — it improves on-page experience and reduces bounce rate for non-English shoppers, which can affect rankings, but you won't see variant translations appearing as separate indexed pages.

What does matter for SEO is that your product titles, descriptions, and meta fields are translated for each locale, with correct hreflang implementation pointing search engines to the right language version. If that infrastructure isn't in place, even perfectly translated variant options won't contribute meaningfully to multilingual organic traffic. See Shopify Multilingual SEO: How to Rank in Every Language for the full picture.

---

FAQ

Do I need to translate variant option values separately from option names in Shopify? Yes — in Shopify's Translations API, option names (like "Color") and option values (like "Red," "Blue") are distinct translatable strings and must be translated independently. Translating only the option name while leaving values in English is one of the most common gaps in multilingual product setups.

Will translating my variant options improve my store's SEO in other languages? Not directly — Shopify doesn't create separate URLs for variant values, so translated option strings aren't indexed as standalone pages. The benefit is improved user experience for non-English shoppers, which can reduce bounce rates and support conversions; the SEO lift comes from translating your product titles, descriptions, and meta fields correctly.

What should I do when a variant option value is a brand term or industry standard that doesn't have a clean translation? Leave it in its source form and document the decision in your translation glossary so it's applied consistently. Terms like "Merino," "Modal," or proprietary color names often read more credibly in their original form than in a forced translation — the key is making that a deliberate, consistent choice rather than an oversight.