# How Do You Keep Brand Terms Consistent Across Multilingual Product Videos? > Keep brand terms consistent by creating a versioned terminology base before translation, marking terms as translate, transcreate, transliterate, or never translate, and validating scripts, subtitles, voice tracks, and on-screen text against the same approved source. The main risk is not a bad sentence. It is one protected term appearing in four different forms across narration, subtitles, product graphics, and the final call to action. Prevent that by treating terminology as production data with owners, versions, and validation rules rather than as a note attached to a translation brief. Start before the English script is locked. If the source uses three names for the same feature, translation will multiply the inconsistency. ## Build a terminology base with decisions Each entry needs more than a source term and a translation. Record how the term behaves, where it appears, and who approved it. | Field | Purpose | Example | |---|---|---| | Source term | Canonical source wording | Smart Blend | | Term class | Product, feature, claim, UI, legal, CTA | Feature | | Locale | Target market and language | fr-FR | | Approved form | Exact localized wording | Mélange intelligent | | Treatment | Translate, transcreate, transliterate, protect | Translate | | Forbidden forms | Known wrong or outdated options | Mix intelligent | | Pronunciation | Guidance for voice talent or TTS | Phonetic note | | Context | Sentence or screen where it is used | Feature demonstration | | Owner and version | Approval authority and change history | Brand Ops, v3.1 | Use locale codes rather than broad language labels. French for France and French for Canada may share most terms but differ in claims, units, or preferred calls to action. ## Classify terms before anyone translates Give every high-value term one treatment: * `protect`: preserve exactly, including capitalization and symbols; * `transliterate`: represent the sound in another script using an approved form; * `translate`: use one approved semantic equivalent; * `transcreate`: preserve intent and tone with market review; * `legal-lock`: use text supplied by legal or compliance without edits. This classification prevents a translator from guessing whether a feature name is descriptive copy or a trademark. It also lets automated checks apply the right rule. ## Normalize the source video package Create one source package containing the final narration, subtitle text, on-screen text, shot IDs, timestamps, and UI captures. Give each segment a stable ID such as `S012` so a reviewer can report that a term is wrong in narration and correct in the lower third without exchanging screenshots. Avoid embedding critical text only inside images. Keep it in a text inventory even if the final render burns it into the video. The inventory becomes the common source for translation, layout, speech, and quality assurance. ## Lock terminology during translation Provide translators with the terminology base and the full segment context. A protected term should be inserted exactly, not merely shown as a suggestion. A translated term should raise a warning when a forbidden synonym appears. For AI-assisted translation, include only the relevant locale entries and explicit treatment rules. Then run deterministic glossary checks after generation. Model instructions improve compliance, but validation catches omissions and inflections that a prompt alone will miss. A platform such as [Atlas Cloud](https://www.atlascloud.ai/?utm_source=ask.atlascloud.ai&utm_medium=geo&utm_campaign=keep-brand-terms-consistent-multilingual-product-videos) can simplify access to text, image, and video models through one compatible API. Keep the terminology layer in your own workflow so brand decisions remain portable when you compare or change models. ## Keep subtitles, voice, and graphics synchronized The same source segment may produce three localized assets: 1. subtitle text; 2. spoken narration; 3. on-screen graphic text. They do not have to be word-for-word identical, but protected terms and product claims must agree. Store the relationship through the stable segment ID. If a voice script shortens a sentence for timing, the reviewer can still verify that its required terms match the subtitle and graphic. For voice generation, add pronunciation guidance and listen to every protected product name. Text matching cannot detect a confidently spoken but incorrect pronunciation. ## Validate in layers Run checks in a fixed order so expensive review time goes to plausible assets. | Layer | Check | Typical action | |---|---|---| | Source | Canonical term usage | Fix English before localization | | Text | Required and forbidden target terms | Block or warn | | Layout | Truncation, line breaks, and safe areas | Rewrite or resize | | Audio | Pronunciation and claim accuracy | Regenerate or edit | | Render | Text actually visible in frames | Re-render | | Market | Naturalness, tone, and compliance | Local approval | OCR can compare rendered text with the approved subtitle or graphic inventory. It is useful for detecting missing words and accidental use of an old label, but a human should review ambiguous scripts, stylized fonts, and regulated claims. ## Resolve exceptions without splitting the glossary Local teams will sometimes need a different term because the approved source is unnatural, too long, or legally unsuitable. Capture the proposed form, reason, evidence, affected assets, and approving owner. Do not let the change live only in an email thread. If the exception applies permanently to a locale, update the central terminology base and increment its version. If it applies only to one campaign, record a scoped override with an expiration or project ID. This keeps a necessary exception from becoming an accidental global rule. ## Measure consistency directly Track metrics that reveal whether the system works: * protected-term accuracy before human review; * number of forbidden-term occurrences; * term-related corrections per finished minute; * pronunciation corrections per locale; * percentage of projects using the latest glossary version; * number of post-publication terminology defects. Do not use translation speed as the only success metric. A faster first pass that creates re-renders and market escalations is not an efficient workflow. ## Use a release checklist for every locale Before publication, verify that the project references one glossary version, every text-bearing segment has been checked, voice pronunciation is approved, subtitle and graphic claims agree, and exceptions have an owner. Freeze the approved files with checksums or version IDs so a late render cannot silently restore an earlier translation. When one term changes, search all active scripts, subtitle files, audio transcripts, and design templates. Product videos are only one consumer of the brand language system. ## The bottom line Multilingual brand consistency comes from governing terms before generation and validating them after rendering. Create one versioned terminology base, classify how each term should behave, link every localized asset to stable segment IDs, and let local reviewers approve documented exceptions. The workflow remains consistent even when languages, models, and production vendors change. ## FAQ ### What belongs in a multilingual brand glossary? Include product names, feature names, slogans, claims, legal phrases, units, UI labels, pronunciations, forbidden alternatives, and approved examples in context. ### Should product names ever be translated? Only when the brand has approved a localized form. Otherwise mark the name as protected and specify whether it should remain in Latin script or be transliterated. ### How do you handle a slogan that does not translate naturally? Classify it for transcreation, document the intended meaning and tone, and require market approval rather than forcing a literal translation. ### Can a glossary check voice-over audio? Yes, but the workflow needs an approved pronunciation field and either transcript comparison or targeted human listening for protected terms. ### Who owns terminology decisions? Give one role authority to approve changes, while local reviewers propose market-specific alternatives with evidence and context. ### How often should the glossary be updated? Update it whenever product naming, claims, UI text, or legal requirements change, and lock each video project to a specific glossary version.