Translate from an approved source, preserve protected fields, and use a qualified language reviewer for the target audience. Check specifications, commercial conditions, terminology, and readability before mapping the copy back to each product.
In this guide
How can a translation change what is included?
These authored sentences illustrate a meaning difference; they are not a translation-service benchmark. Keep the source sentence, target sentence, and product row together so a target-language editor can make the final wording decision. Repeat the bundle check in the headline and image caption. A back-translation may expose a question, but it cannot certify that the final Spanish suits every market.
| Stage | English / Spanish practice wording | Review result |
|---|---|---|
| Source | Divider sold separately. | Separate-purchase condition |
| Draft | Bandeja con separador incluido. | Implies the divider is included |
| Revision | El separador se vende por separado. | Restores the separate-purchase condition |
Review all places a condition can be lost
Check titles, bullets, captions, tables, and calls to action as well as paragraphs. A carefully translated body does not neutralize an overbroad headline. Ensure each language's internal links lead to relevant, usable material rather than an unrelated page with a similar name.
When the source product changes, identify all affected language versions by the same product and claim IDs. Keep the update status visible so a current source page does not conceal an outdated translation. A version map makes that maintenance task much easier to scope.
Fix the source version before multiplying languages
Start with approved source copy and identified product records. Record the target language, market, reader, and permitted localization rules. A translated page cannot repair an unverified source claim, and different language versions should not quietly inherit different specifications.
Create a glossary for product names, materials, accessories, and technical terms. Mark protected values such as model IDs and dimensions. Define whether a unit conversion is permitted and who checks it; otherwise retain the approved values and units rather than allowing the model to choose.
- Provide the source version, target market, glossary, protected fields, and approved commercial conditions.
- Request translated text keyed to the original product/section IDs, with uncertain terminology flagged.
- Compare specifications, negations, quantities, inclusions, compatibility, and conditions against the source table.
- Ask a capable target-language reviewer to check meaning, tone, terminology, and natural reading in context.
- Resolve discrepancies and review any changes that affect the approved source meaning.
- Keep the final language version, reviewer decision, and product mapping together before updating the store.
Preserve protected fields in the translation request
Translate this APPROVED SOURCE COPY: [text + section IDs]. TARGET LANGUAGE, MARKET, AND READER: [state] GLOSSARY: [approved terms] PROTECTED PRODUCT FIELDS: [IDs, quantities, units, inclusions, compatibility] COMMERCIAL CONDITIONS: [scope and exceptions] Return translated sections with the same IDs, a glossary-use report, and uncertainty questions. Preserve protected values and optional-versus-included distinctions. Flag any localization requiring a new fact or policy decision. Do not invent a local warranty, availability, or unit conversion. The output goes to a language reviewer.
Save the glossary and corrected examples
Keep recurring terminology decisions and examples of misleading wording with the next translation brief. Update the reusable instructions from observed corrections rather than adding more generic demands to sound native.