When a translation changes what you sell

A bilingual catalogue can look consistent while offering two different products. The photographs match, the product code matches and both pages sound fluent. Yet one reader expects a box of components and another expects somebody to arrive and install them.

That difference deserves more attention than whether the English sentence sounds polished. For an Argentine business presenting its products to Spanish- and English-speaking buyers, language review needs access to the offer itself: what is supplied, what requires a separate agreement and what the sales team can actually discuss.

This guide follows a fictional mounting-kit catalogue. Its Spanish description says “incluye herrajes de fijación.” The English page says “installation included.” The approved product sheet lists brackets, screws and anchors; it includes no installation service. The English wording has turned supplied hardware into a promise of labour.

Find the commercial difference before rewriting the sentence

The first useful question is what a buyer would reasonably expect to receive. A translator can improve grammar without knowing whether the manufacturer supplies fixings, fits the product at a customer's premises or helps the customer's own installer. The product owner must settle that distinction.

For this example, the catalogue manager checks the kit's approved component list and confirms three facts: the listed mounting hardware is supplied in the box; installation is outside the offer; and the enquiry team can answer product questions under an agreed language arrangement. None of those facts establishes that the kit is suitable for every wall, building or installation method. Technical suitability remains subject to the product's approved instructions and the responsible specialists.

The team records the approved meaning before editing either language. That gives the language reviewer something definite to preserve. If the business later adds an installation service, it will need its own scope and commercial approval rather than an unrecorded change to a catalogue adjective.

Write for the reader's decision

A defensible English description for this fictional kit is: “The kit includes the brackets, screws and anchors listed in the component sheet. Installation is not included.” The Spanish description can make the same boundary explicit: “El kit incluye los soportes, tornillos y tarugos detallados en la ficha de componentes. No incluye instalación.”

Those sentences are an example of a resolved offer, not wording to apply automatically to other products. The actual components, terms and document reference need approval for each catalogue. If a particular fastener is optional, it must not become standard merely because a neighbouring product uses the same layout.

The surrounding explanation can differ by audience. A domestic buyer may already know the product range and need to find the correct component sheet. An overseas distributor may need to ask which documentation is available before discussing a purchase. The two pages can serve those different questions while keeping the supply boundary consistent. Neither needs to invent export approvals, worldwide delivery or local installation partners.

Trace the mistaken promise through the catalogue

Correcting the long description leaves a problem if the product card still advertises installation. In this case the catalogue manager locates the English statement in four places: the product page, a collection card, a downloadable overview and the email enquiry prompt generated from that product.

Each occurrence has a different job. The page explains the kit; the card invites a closer look; the overview may circulate without the website around it; and the enquiry prompt carries the buyer's context to staff. The correction must preserve those jobs. A concise card might say “Mounting kit with listed fixings” while the detail page carries the full exclusion. A download needs its own identifiable revision so staff can distinguish the corrected overview from an earlier attachment.

Review the page title and search description as well. They should describe the product without bringing back an unsupported benefit. Search snippets are not entirely under a publisher's control, so editing metadata is a correction to the source presentation, not a promise that every old search result disappears immediately.

Test equivalence without forcing identical pages

Give a reviewer the English page on its own and ask what arrives in the box, who performs installation and how the reviewer would ask a product question. Repeat with the Spanish page and compare the answers with the approved offer. A reader who correctly repeats the headline but still expects an installer has exposed an unresolved communication problem.

Then inspect the route between languages. From the kit's English detail page, the Spanish option should reach its actual counterpart where one exists. Sending the visitor to a general homepage loses the product context and can hide the corrected boundary. Where a counterpart is unavailable, the link should describe the destination honestly instead of presenting an unrelated page as a translation.

Technical declarations support this structure. W3C's language guidance explains how HTML identifies the language of a page and passages within it. Google's guidance on localized versions explains the separate annotations used to associate genuine language or regional counterparts. Neither mechanism checks that a commercial translation is accurate.

Keep the repair bounded and maintainable

For this fictional correction, the product code, component list and underlying kit remain unchanged. The team replaces the misleading English promise, clarifies the Spanish boundary, updates the four affected surfaces and verifies that both language routes still lead to the same product. A different kit with an explicitly separate installation option remains unchanged. That comparison helps catch an overly broad replacement across the entire catalogue.

The closing record should identify the approved source document, the corrected locations, the product and language reviewers, and any old download still needing removal from a controlled distribution channel. A fresh preview of both language paths confirms the correction; it does not prove what every buyer has already read. Existing enquiries that repeat the installation expectation need a human response based on the business's actual commitments.

For future changes, assign responsibility by fact as well as by language. The product owner approves what is supplied. The language reviewer makes that meaning clear to the intended reader. The site maintainer updates the correct routes and shared components. When the source offer changes, both language versions need a decision, even if one requires only a brief confirmation that its wording remains accurate.

Bring the disagreement to the project brief

The most useful starting material is often two conflicting descriptions and the document that resolves them. It shows where editorial judgement, product knowledge and website structure meet. Faith Forge Labs can help organise that review and implement the approved catalogue presentation; the working language and any specialist translation or review are agreed for the project.

Explore content and search work or describe the catalogue problem. Include public examples or a suitably anonymised excerpt, with a short explanation of what the buyer should understand differently.