A translated product page can sound fluent and still make the product harder to identify. If a model name is treated as an ordinary word and translated, the buyer may no longer be able to match it to a quotation, manual or equipment label. Keeping every technical paragraph in the source language creates the opposite problem: the identity survives, but the explanation becomes inaccessible.

The useful starting point is the job each piece of text performs. Some text identifies an item. Some explains its use. Some helps a person locate a control on a real screen. Those jobs call for different translation decisions.

Amazon Translate documents a way to preserve selected text in HTML using a do-not-translate attribute. Its API reference, published September 10, 2026, continues to describe text and document translation capabilities. This is a practical use of documented functionality, not a claim that the preservation feature has just launched.

Preserve identity without freezing the explanation

For an international buyer, a model identifier is a matching key. The same string should make sense across the supplier's page, the equipment label and the commercial discussion. A changed letter, separator or sequence can create uncertainty about whether two documents concern the same version.

That does not mean the surrounding product description should remain untouched. A stable identifier can sit beside a localized category name, explanation of use and relevant limitations. The reader should be able to understand what the item does while retaining the exact string needed to ask about it.

Technical terminology requires judgment rather than a blanket rule. Where a well-established target-language term exists, use it appropriately. Where a term is ambiguous, confirm the concept with someone who understands the product before polishing the sentence. A smooth translation of the wrong concept is still wrong.

Numbers also need classification. A number embedded in a model name is not a measurement to convert. A dimensional value may require an explicit unit treatment, with attention to precision and conditions. The translation process should not be left to infer which commercial or technical role a number plays.

Match interface labels to the interface people actually see

A manual or product explanation may refer to a control whose label is displayed in another language. Translating the label alone can make the sentence easier to read but the control harder to find.

A concise combination often works better: keep the actual label and explain its meaning in the reader's language. That lets a person match the text to the screen without requiring them to understand every word of the original interface. It is particularly useful where the supplier's equipment language and the buyer's preferred reading language differ.

Use this selectively. Repeating every phrase in two languages makes a page slower to read and can bury the few identifiers that truly matter. Preserve what needs a direct visual match; explain what needs understanding. The two layers should help each other rather than compete.

This is a writing distinction, not permission to invent operating instructions. A correctly named control does not establish that a reader is qualified to use it. Safety-related and maintenance material should continue to follow the verified instructions appropriate to the equipment and user.

Keep exclusions narrow enough to review

A local preservation tag is most useful when it surrounds the smallest piece of text that genuinely needs to remain unchanged. Applying it to an entire paragraph because the paragraph contains one model name can leave ordinary explanatory copy untranslated as well.

That failure can be easy to miss in an automated pipeline. The process returns an output, the identifier is intact, and a simple comparison looks satisfactory. But the buyer receives a passage that switches languages halfway through without a reason.

Review the result in two ways. First, compare the identifiers and necessary labels against the source material. Second, read the surrounding sentences as target-language prose. The first check catches a tiny but consequential identity change; the second catches awkward grammar, missing context and excessive untranslated text.

Neither check substitutes for the other. A perfect character match cannot prove that the description is understandable. A fluent reading cannot prove that a model number survived. Keeping those questions separate makes the review more precise without turning it into a large administrative exercise.

For China-based manufacturers, this is also a useful brief for external language providers. Specify which strings must remain stable and why, rather than asking them vaguely to “keep technical terms.” The reason helps distinguish a product identifier from a term that should in fact be localized.

Our discussion of independent language pages and instant translation addresses how multilingual content is maintained over time. Selective preservation works at a smaller scale, inside the sentence. Both matter when a buyer needs to read the page and then use it to identify the actual product.

Sources

AWS, Using do-not-translate in Amazon Translate, maintained feature documentation without a separate publication date; Amazon Translate API Reference, document publication date September 10, 2026. That date is not presented as the feature's original release date.