A translation can be fluent and still change what a shop promises. Consider this source sentence:
Orders are dispatched within two business days. Delivery time depends on the destination.
If the translated page simply says that orders arrive within two days, the customer has been given a different service commitment. This is a hypothetical example, but it is a useful test case for a multilingual storefront.
Disclosure: I work on LumoWP. We make the Lumo WPML AI Translation Addon. The process below is an editorial workflow you can use alongside the addon; it is not a benchmark or a promise that a model will always translate correctly.
Start with a small set of facts
Before translating, write down what the page actually says about shipping. Separate dispatch time from transit time, business days from calendar days, and an estimate from a guarantee. Include cut-off times, excluded regions and any dependency on stock availability.
This is also a good moment to ask whether the policy applies to the target market. A translation model cannot decide whether your courier serves a region or whether your business should offer the same return terms there.
Give the translator boundaries
A useful instruction might look like this:
Translate this product page naturally into French for customers in France. Preserve delivery estimates, units, quantities, conditions and exceptions. Distinguish dispatch from delivery. Do not add a guarantee or strengthen a product claim. Keep product identifiers unchanged.
Adapt the language and market to your project. If a term has an approved translation, include it. Keep the instructions specific enough that a reviewer can tell whether they were followed.
Avoid treating a prompt as a test result. It expresses what you want; the output still needs checking.
Compare meaning in a review table
For one representative page, create a short table:
| Source fact | What the target page must preserve | Reviewer result |
|---|---|---|
| Dispatch within two business days | Time before handing the parcel to the courier | To check |
| Destination affects transit time | No fixed arrival date is implied | To check |
| Excluded destinations listed | Exceptions remain visible | To check |
| Return shipping paid by customer, where applicable | Responsibility is not reversed | To check |
The rows are examples, not policies to copy into your shop. Populate them from the business's real terms.
Have someone fluent in the target language compare those facts side by side. Back-translation can highlight suspicious wording, but it should not be your only acceptance check: the same model may repeat the same misunderstanding.
Open the storefront on mobile
Now look at the information where a customer sees it. Check the product description, delivery tab, variation messages, buttons and links. Make sure an important exception has not disappeared behind a broken layout or an untranslated label.
A correct translation in an editor does not prove that every customer-facing field is correct. Read the buying journey and confirm the actual shipping methods available at checkout separately.
Where the addon fits
Lumo WPML AI Translation Addon connects supported AI providers to WPML using your own API key. It supports translation workflows for posts, products, taxonomies, custom fields, WPML strings and Elementor templates. WPML is required and provider usage is billed separately.
It handles translation work within that workflow. Your business and reviewer remain responsible for approving the meaning and deciding whether the terms fit each market.
Explore the addon and its supported workflows.
When the original shipping information changes, record which translated pages need another review. That maintenance step is easy to overlook after the initial launch.
Top comments (0)