# Product Naming Across Markets: What to Translate | Vitra.ai

> Product names, model codes, feature names and taglines follow different rules. Getting the split wrong is the terminology mistake that is hardest to reverse.

**Canonical URL**: https://www.vitra.ai/consumer-electronics/product-naming-across-markets
**Source**: This is the Markdown rendering of https://www.vitra.ai/consumer-electronics/product-naming-across-markets, generated at build time from that page.

---

4 min read

# Product Naming Across Markets: What to Translate

Product names, model codes, feature names and taglines follow different rules. Getting the split wrong is the terminology mistake that is hardest to reverse.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Senior Product Manager , Vitra.ai
Updated Aug 18, 2026

![Product Naming Across Markets: What to Translate](https://www.vitra.ai/static/images/blog/product-naming-across-markets.jpg)

Table of contents

[Four categories, four rules](#four-categories-four-rules)

[Screening comes before tooling](#screening-comes-before-tooling)

[Feature names are frozen once decided](#feature-names-are-frozen-once-decided)

[Keep, translate, or transliterate](#keep-translate-or-transliterate)

[Making it stick](#making-it-stick)

[FAQ](#faq)

Contributors

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Senior Product Manager

Subscribe to our newsletter

Subscribe

> **Quick answer —** Product names and model codes normally stay fixed, feature names are decided once per language and then frozen, and taglines are rewritten rather than translated. Screening has to happen before tooling and packaging, not after.[Vitra.ai Universe](https://www.vitra.ai/platform) keeps one product vocabulary across box, app, page and video.

## Four categories, four rules

Naming is treated as one decision and behaves as four.

Type

Default

Why

Product name

Keep, unless screening objects

Recognition, packaging, search

Model code

Never change

Support, parts, compatibility

Feature name

Decide per language, then freeze

Appears in every asset

Tagline

Rewrite

Wordplay does not survive

Accessory names

Usually keep, sometimes describe

Sold separately, searched separately

The expensive mistakes come from applying one rule to all five rows.

## Screening comes before tooling

A name that carries an unfortunate meaning, sounds like something else, or collides with an existing mark in a target market has to be caught before packaging is printed, moulds are cut and listings are created.

Screening after launch is not screening, it is a recall decision. That check belongs at the same point as the [wake word](https://www.vitra.ai/consumer-electronics/voice-assistant-localization) review, since both are phonetic questions and both are effectively irreversible.

## Feature names are frozen once decided

A feature name appears on the box, the [product page](https://www.vitra.ai/consumer-electronics/electronics-product-page-localization), in the [app](https://www.vitra.ai/consumer-electronics/companion-app-localization), in the [manual](https://www.vitra.ai/consumer-electronics/electronics-manual-translation), in [support articles](https://www.vitra.ai/consumer-electronics/device-support-article-translation) and in every campaign. Renaming one after launch means updating all of it, in every language, including printed material that cannot be updated at all. That is why the decision deserves more scrutiny than its size suggests, and why it should be recorded in the glossary rather than left to whoever translates the next asset. The same reasoning applies in software, covered in [naming features across languages](https://www.vitra.ai/saas/saas-feature-naming).

## Keep, translate, or transliterate

Three genuine options, and the choice is per market rather than global. Keeping the English name preserves recognition and search volume, and works where the audience is comfortable with English product terms. Translating helps comprehension where the name is descriptive rather than coined. Transliterating into a different script keeps the sound while making the name readable and typeable — the distinction is set out in [transliteration versus translation](https://www.vitra.ai/general/transliteration-vs-translation). Search behaviour in the market is the deciding evidence, not preference.

## Making it stick

Put every naming decision on a [do-not-translate list](https://www.vitra.ai/general/do-not-translate-lists) with the per-market variants recorded, and pin them in [translation memory](https://www.vitra.ai/features/translation-memory) so no fuzzy match can rename a product mid-campaign.

Then [quality control](https://www.vitra.ai/features/quality-control) checks names on every output, which is the only way to catch the one asset in two hundred where a name slipped back to English.

Ranges with many variants make this harder again, which is the subject of [automotive terminology across model ranges](https://www.vitra.ai/automotive/automotive-terminology). Holding one name everywhere is [brand consistency across languages](https://www.vitra.ai/solutions/brand-consistency-across-languages).

## FAQ

**Should product names be translated?** Usually not, since the name carries recognition and search volume. The exceptions come from screening — a name that carries an unfortunate meaning or collides with an existing mark has to change in that market.

**What about model codes?** Model codes never change. Support, spare parts and compatibility all depend on them being identical everywhere, and a translated code makes a device unsearchable in its own support site.

**How should feature names be decided?** Once per language, then frozen in the glossary. A feature name appears on packaging, the product page, the app, the manual and every campaign, so renaming it later means updating material that cannot be updated.

**When should a name be transliterated rather than translated?** When the market uses a different script and the name is coined rather than descriptive. Transliteration keeps the sound while making the name readable and typeable, which supports local search.

Our blog

## Lastest blog posts

Tool and strategies modern teams need to help their companies grow.

Automotive

[Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization)
A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

Automotive

[Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization)
Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

Automotive

[Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation)
A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

[View all posts](https://www.vitra.ai/blog/page/1)

---

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://www.vitra.ai/consumer-electronics/product-naming-across-markets"
  },
  "headline": "Product Naming Across Markets: What to Translate",
  "image": [
    {
      "@type": "ImageObject",
      "url": "https://www.vitra.ai/static/images/blog/product-naming-across-markets.jpg"
    }
  ],
  "datePublished": "2026-08-18T00:00:00.000Z",
  "dateModified": "2026-08-18T00:00:00.000Z",
  "author": [
    {
      "@type": "Person",
      "name": "Samhitha J Bhatt"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "Vitra.ai",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.vitra.ai/static/images/vitra-v-logo.png"
    }
  },
  "description": "Product names, model codes, feature names and taglines follow different rules. Getting the split wrong is the terminology mistake that is hardest to reverse."
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.vitra.ai"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Consumer-electronics",
      "item": "https://www.vitra.ai/consumer-electronics"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Product Naming Across Markets: What to Translate",
      "item": "https://www.vitra.ai/consumer-electronics/product-naming-across-markets"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Should product names be translated?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Usually not, since the name carries recognition and search volume. The exceptions come from screening — a name that carries an unfortunate meaning or collides with an existing mark has to change in that market."
      }
    },
    {
      "@type": "Question",
      "name": "What about model codes?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Model codes never change. Support, spare parts and compatibility all depend on them being identical everywhere, and a translated code makes a device unsearchable in its own support site."
      }
    },
    {
      "@type": "Question",
      "name": "How should feature names be decided?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Once per language, then frozen in the glossary. A feature name appears on packaging, the product page, the app, the manual and every campaign, so renaming it later means updating material that cannot be updated."
      }
    },
    {
      "@type": "Question",
      "name": "When should a name be transliterated rather than translated?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "When the market uses a different script and the name is coined rather than descriptive. Transliteration keeps the sound while making the name readable and typeable, which supports local search."
      }
    }
  ]
}
```