Same manufacturer. Completely different documents depending on the country.
Brazil: a few pages. Japan: a 20+ page booklet — parts, accessories, control panel, usage, tips, maintenance, troubleshooting, after-sales service.
The sequence isn't random
That structure follows the user's actual journey. Opening the box → using it → something goes wrong → contacting support.
You couldn't get there by translating the Brazilian manual. The volume, the sequence, the granularity — all rebuilt around what Japanese users expect, where they feel uncertain, what makes them trust.
That's not translation. That's experience redesign.
The same applies to SaaS
Translating your English UI doesn't reproduce the experience of a Japanese user feeling confident enough to adopt, pay, and stay.
The volume of information, the sequence in which it's presented, the granularity of explanation — these aren't stylistic choices. They're structural decisions that determine whether users trust the product enough to keep using it.
Localization isn't a language problem. It's a UX problem.