Product Manual Translation for Device Brands

Quick answer — A consumer device manual now exists in four places at once — the in-box card, the downloadable PDF, the support site and in-app help. They are usually translated separately, which is why they disagree. Translate them from one source and one glossary instead.

Vitra.ai Universe keeps one product vocabulary across box, app, page and video.

The manual stopped being a document

Ten years ago a device shipped with a booklet and that was the manual. Now the same instructions appear on a folded card in the box, as a PDF on the support site, as a set of help articles, and as an in-app help panel that the companion app renders. Four artefacts, four owners, four content systems. Packaging is owned by industrial design, the PDF by technical writing, the help articles by support, the in-app strings by engineering.

Each of those teams commissions its own translation, on its own schedule.

Which is why they disagree

A customer who reads "press and hold the mode button for five seconds" on the card and "hold Function until the light flashes amber" in the app is not reading a translation problem. They are reading an organisational one that translation then multiplies by the number of languages shipped.

The button has one physical label. It should have one name everywhere, in every language, and that name is a terminology decision rather than a writing one.

What to fix first

Lock the vocabulary before any of it is translated. Button names, port names, LED states, mode names, accessory names, the product name itself.

Pin those so no general match can overwrite them, and they resolve identically whether the string arrives from a print file, a help article or an app resource bundle. Translation memory is what makes that hold across four pipelines rather than inside one.

Then translate each artefact in its own format — documents keep the PDF layout, the knowledge base keeps the article structure, and figures with baked-in callouts need image translation rather than a text pass.

The rest of the set

Each of these has its own failure mode, and they are covered separately:

• Setup guides and the quick start card - Safety warnings and regulatory markings - Spec sheets and product pages - Companion apps and firmware notes - Support articles and troubleshooting - Demo video, unboxing content and retail campaigns - Warranty terms, product naming and voice assistants

More on the whole launch set at Vitra for consumer electronics.

FAQ

Why do device manuals contradict the app? Because the card, the PDF, the support articles and the in-app help are owned by four different teams and translated on four different schedules. The fix is shared terminology, not better writing in each silo.

What should be locked before translation starts? Button names, port names, LED states, mode names, accessory names and the product name. These are terminology decisions, and pinning them stops a general match from renaming a physical button.

Does each manual artefact need a different process? Different formats, yes — print files, PDFs, help articles and app strings all behave differently. What they share is one glossary and one memory, so the same phrase resolves the same way in each.

What about callouts inside figures? Those are pixels, not text, so a document pass leaves them in English. They need image translation, and they are the most common reason a translated manual still looks half-finished.