A product in German is more than a translation

"We translated the product" almost always means in practice: the interface strings now exist in German. That is the part a translation agency can deliver, and it is the smaller part. The larger one sits underneath, in fields and formats nobody perceives as language until they are wrong.

Formats are language, even when made of digits

A date shown as 08/24/2026 does not read as wrong to a German user so much as foreign, and when in doubt, backwards. The same goes for decimal separators, thousands separators, calendar weeks, which day a date picker starts on, and whether time appears on a twelve or twenty-four hour clock.

None of this is hard. It is simply rarely part of a translation brief, because it does not look like text. And it surfaces at exactly the moment a user enters a number that is then interpreted differently from how they meant it.

Address and tax fields are a data model, not a form

A form that expects a five-digit postcode, demands a state as a required field, or has no concept of a VAT identification number is not a translation problem. It is a modelling problem that only becomes visible in the form.

For companies with business customers there is more: billing address and delivery address are not the same thing, the company name belongs in its own field, and the VAT ID has to appear on the invoice. Retrofitting that rarely changes only one input.

Forms of address and tone are product decisions

German forces a decision many products from other languages never face: formal or informal address. The choice is not merely taste; it has to run consistently through the entire product, including system emails, error messages and push notifications. A product that is informal during onboarding and formal in an error message does not read as relaxed, it reads as unfinished.

Error messages deserve particular attention. They are almost always translated last, often by machine, and they arrive at the moment a user has the least patience.

And then the mandatory pages

Imprint, privacy notice and consent are not texts you translate once and file away. They name a specific legal person and have to change when that person does. Technically this needs one place where those details live, rather than copies inside three language versions of a page.

What a multilingual structure that carries this looks like is in building a multilingual platform. Why the legal person also determines the invoice is in GmbH or branch office.

The honest effort

Translating the text usually takes days. Formats, fields, forms of address and mandatory pages are a matter of weeks, but only if they are treated as one task. Spread across individual tickets over half a year they never finish, because each one on its own looks too small to prioritise.

Where this sits within the wider move is on German market entry.