Vehicle Launch Content in Every Language

Quick answer — Vehicle launch content has to be ready in every market before the embargo lifts, which means translating specifications and claims that are still changing. Build from one approved master and hold volatile values as fields.

Vitra.ai Universe keeps one vehicle vocabulary across manual, showroom and screen.

The date is the constraint

Everything about a vehicle launch follows from one fact: the material goes live everywhere at the same moment, and nothing can be corrected quietly beforehand.

That inverts the usual order. Translation cannot wait for the source to settle, because the source settles days before the embargo lifts, and the markets need finished assets before that.

What ships at once

Six owners, one deadline, and each of them expects the others to be finished.

Hold the volatile values as fields

Prices, homologation figures, availability dates and comparative claims are the elements that change last and matter most. Baking them into translated text means every late change is a retranslation across every asset and every market. Holding them as fields, with the creative built around them, means the change is a value update at generation time — which is the difference between a controlled launch and a scramble. That also keeps a market from publishing a figure its regulator has not yet confirmed for that market.

Claims route locally

Performance and efficiency claims are governed differently in different markets, and the qualifying text that makes a claim defensible is local.

A workflow gate that parks claim-bearing segments for local approval while the rest of the asset continues is the practical shape of that. Agentic workflows hold those strings without holding the launch, and quality control checks the released files rather than the drafts.

One master, every market

The film cut for each market, the brochure, the configurator copy and the press kit should all draw on the same approved source and the same glossary, so the trim name in the price list matches the one in the film and the one on the configurator.

Video creation produces the market and format cuts from one master, and translation memory means the second market costs materially less than the first — which is what makes a simultaneous launch across many markets affordable at all. The publishing side of a simultaneous launch is global content publishing.

FAQ

What makes vehicle launch content different? Everything goes live in every market at the same moment, so nothing can be corrected quietly first. Translation has to run while the source is still settling, because the source settles days before the embargo lifts.

How do you handle prices and figures that change late? Hold them as fields rather than baking them into translated text. A late change then becomes a value update at generation time instead of a retranslation across every asset and market.

Who approves performance claims for each market? Local marketing or legal, since claims are governed differently and the qualifying text is market-specific. A workflow gate parks claim-bearing segments for approval while the rest of the asset continues.

How do you keep launch assets consistent with each other? By building everything from one approved master and one glossary, so the trim name in the price list matches the film, the configurator and the press kit without anyone reconciling them by hand.