← All articlesMultilingual

Email translation review: check the customer's decision

3 min read

An email translation review should ask whether the customer can make the intended decision. Correct grammar matters, but so do the product detail, discount condition, deadline, and destination. Read each version as a complete shopping experience, including its mobile layout, rather than checking sentences in isolation. A fluent translation can still send the reader to the wrong offer.

Give the reviewer context

Provide the campaign goal, audience, product facts, and commercial terms. Show the source message and the destination page, not just a spreadsheet of isolated sentences. Context helps the reviewer choose natural wording without changing the promise.

Mark the facts that must remain exact: measurements, compatibility, dates, prices, and eligibility. Ask the reviewer to flag unclear source copy rather than translating an ambiguity into several languages.

Ask the reviewer to explain the offer back to you

Instead of asking only whether the translation sounds good, ask what a customer would receive, who qualifies, what it costs, and what action to take. For a product guide, ask what question it answers and what the reader should do differently afterward. Their explanation exposes ambiguity more effectively than a general approval.

Imagine a translated offer that sounds like a free product when the source means free shipping. Both sentences may be grammatically fluent, but the commercial meaning has changed. Treat that as a release-blocking issue. A preference between two equally natural greetings is a lower-priority editorial choice.

Give the reviewer permission to challenge the source. If “available soon” has no confirmed date or a size description is ambiguous, translating it smoothly only spreads the uncertainty. Resolve the factual question with the responsible team member and update every affected version from the clarified brief.

Inspect the actual layout

Review the Sendvio version in its template. Check subject and preview together, then headings, buttons, captions, and personalized fields. A phrase that reads well in a document may wrap awkwardly inside a narrow control.

Look at mobile and, where relevant, right-to-left behavior. Keep readable type and spacing. If the text needs a shorter equivalent, have the reviewer approve it rather than deleting words solely to fit the design.

Make feedback specific enough to fix once

Record the location, current wording, proposed correction, and reason. A note such as “button unclear: this opens the size guide, not checkout” is actionable. A note such as “make it more local” leaves the writer guessing and can introduce a new inconsistency.

Separate factual corrections, usability problems, and tone preferences. Factual corrections include prices or eligibility; usability includes clipped text and unclear actions; tone includes overly formal or unnatural phrasing. This helps the team fix the highest-impact issues first while preserving useful editorial judgment.

Review the final rendered version after changes. A corrected phrase can become longer and expose a layout problem, or an editor may accidentally update the wrong language tab. Check the subject, main action, important terms, and destination again before recording approval. An approved document is not automatically an approved sent message.

Complete a customer-level test

Follow the link, inspect the destination language and offer, and test a missing personalization value. Confirm that fallback content remains understandable. Record approval for the version actually being sent, not an earlier draft.

After launch, collect recurring language questions and update the terminology guide. Consistent product terms save future review time, but leave room for natural sentence structure. The aim is a message that sounds like your store and helps the reader decide, not a mechanically identical copy of the source language.

After launch, add recurring terms and actual customer questions to a small language guide. Explain why a term was chosen and where it should be used. Keep this guide practical rather than turning it into a rigid dictionary: natural phrasing can vary while the product and offer meanings remain consistent.