Product Localisation

A product ready for other languages, a translation pipeline with glossary, style guides and quality reviews, and the formats, payment methods and launch plans that make each new market feel local.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Localisation, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

🧩 Product Management

Product Localisation

Adapting a product for new languages and regions, including translation workflows, local formats, regulations and market-specific features.

  1. Internationalisation readiness audit of one user flow
  2. Scorecard for choosing the next three locales
  3. Locale codes and fallback chain policy
  4. Localisation roles and decision rights
  5. Translation management system selection
  6. String resource file conventions
  7. Product glossary and do-not-translate list
  8. Voice and style guide for each locale
  9. Localisation cost model per locale
  10. Continuous localisation pipeline
  11. Pre-release string freeze and handoff
  12. Monthly linguistic quality sampling
  13. Pseudo-localisation in every build
  14. Translation memory and glossary upkeep
  15. Weekly localisation bug triage
  16. Locale coverage and quality dashboard
  17. In-market feedback loop from regional teams
  18. Quarterly locale health review
  19. Translation vendor performance review
  20. Unicode and text handling basics for product managers
  21. Plurals, gender and message formats
  22. Right-to-left layouts and bidirectional text
  23. Local formats for dates, numbers, currencies and addresses
  24. Writing source copy that translates well
  25. Machine translation and post-editing levels
  26. Cultural adaptation beyond translation
  27. Translation method by content tier
  28. Text expansion and truncation fixes
  29. Local payment methods and currency display
  30. Language detection and switcher design
  31. International name, address and phone forms
  32. Help centre translation priority list
  33. Fonts and typography for non-Latin scripts
  34. Screenshots and context for translators
  35. First new locale launch
  36. Country requirements inventory before market entry
  37. Localised website and search presence for a launch market
  38. Regional holiday and release calendar
  39. Pausing or retiring an underperforming locale
  40. Enterprise contract that requires a language
  41. Localisation without a dedicated localisation manager
  42. Shared localisation platform across product teams
  43. Internationalisation retrofit of a legacy product
  44. In-country reviewer programme
  45. Community translation programme
  46. Market-specific feature adaptation
  47. Measuring the return on a new locale
  48. AI-assisted translation with human review gates
  49. Locale-level product analytics
  50. Accessibility across languages

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Internationalisation readiness audit of one user flow

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before a single string goes to a translator, the code has to be able to hold another language: strings outside the source code, no sentences glued together from fragments, dates and numbers formatted by locale, and layouts that survive longer words.

First tasks

  • Pick one user flow that touches the most screens and emails
  • Screenshot every screen, email and error message in that flow
  • Tag each hard-coded string, concatenation and fixed date or number format
  • Ask an engineer to size each issue as small, medium or large

Scorecard for choosing the next three locales

Teams often pick their next language because a senior person speaks it or one large prospect asked. Scoring candidate markets on the same criteria, such as existing sign-ups from the region, sales pipeline, competitor coverage, regulatory effort and translation cost, turns that into a decision you can explain to the board and revisit next year.

First tasks

  • Pull sign-ups and traffic by country for the last twelve months
  • Ask sales for open pipeline and lost deals by region
  • Agree five weighted criteria with sales, finance and engineering
  • Score each candidate locale and write the decision note
  • Rescore the candidate locales with fresh data @recurring(yearly)

Locale codes and fallback chain policy

Products that mix 'es', 'es-ES' and 'spa' across services end up showing English to Mexican users or Spain's Spanish to Argentines. Agreeing one standard for locale tags, usually BCP 47, and a written fallback order for each locale stops this at the source and gives engineering a rule to test against.

First tasks

  • List every place the product stores or reads a language or region setting
  • Choose BCP 47 tags as the standard unless there is a strong reason not to
  • Write the fallback chain for each planned locale
  • Ask engineering which services still use other codes

Make it yours.

Install Product Localisation, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.