Translation Memory

How it saves money

Every word you pay to translate once can be served from memory the next time it appears — on new pages, in footers, or in repeated UI patterns. Cached segments typically do not count toward usage the same way as fresh API calls.

That compounding effect is largest on ecommerce catalogs, documentation, and marketing sites with shared components — exactly where localization budgets usually balloon.

Consistency that visitors notice

Memory keeps terminology and phrasing aligned across your whole site. When “Add to cart,” warranty lines, or feature names change in one place, you can roll updates through memory instead of hunting every occurrence.

Approve once, reuse everywhere

High-quality human or AI-plus-review segments become the default for matching content later.

Update globally when messaging changes

Refresh a segment in memory when product naming or legal wording changes, then propagate with control.

Best practices

• Approve quality translations once; reuse everywhere
• Update a segment in memory to roll out changes globally
• Pair with glossaries for brand-critical terms
• Ideal for e-commerce, docs, and marketing sites with repetition
• Review key templates in the visual editor after large memory updates

How to get leverage from memory

1. Translate and approve core templatesFocus first on shared nav, footer, product cards, and checkout-adjacent copy.
2. Let memory fill matching segmentsAs you add pages or languages, identical and near-identical strings reuse approved output.
3. Combine with glossary rulesLock trademarks and product names so memory never “helps” by inventing variants.
4. Maintain as your product evolvesWhen messaging changes, update memory deliberately instead of letting old phrasing linger.