Marketplace and ecommerce listing translation

A catalog that has to read right in twelve markets

You run a marketplace with sellers in twelve countries and you're preparing for a new weekend campaign. An existing German seller updates several listing while another French seller loads 57 new products. Meanwhile, a shopper in Milan reads a review written in Italian that contains an English product name.

Marketplace translation is rarely uniform. Listings, reviews, product metadata, and buyer-seller messages all behave differently. Some need strict format preservation. Others need higher throughput. Some can run in the background, while others are user-facing. The translate routes cover each of these cases, so the work is picking the right route per traffic type, not forcing one path for everything.

Match the traffic to the route

Lexel Translate supports a variety of routes to ensure that your diverse needs are met, including:

• Synchronous translation for live support messages, where the reply has to come back as soon as possible. See the translate docs.
• Synchronous batch translation for mixed-language listing payloads, where each item keeps its own language pair, glossary, and protection settings (batch docs).
• Shared synchronous batch for bulk catalog refreshes that share one common language pair and one glossary selection (shared batch docs).
• Asynchronous jobs for large content migrations and export workflows, where nothing blocks on the result (async docs).

If a user is waiting on the result or the update needs to happen as soon as possible, use a synchronous route. If the work can happen in the background, use asynchronous translation.

Why consistency matters

Marketplaces lose trust when catalog terms, product names, or brand phrases drift across languages. The listing, the product metadata, and the review all need to describe the same product. Glossary control and structured payload handling matter as much as raw output quality, because drift is what shoppers notice.

Glossaries hold mapping entries and do-not-translate items, and each change creates an immutable version you can pin for reproducible output (glossary docs). Structured content modes such as json and csv are preprocessed before translation, so catalog payloads come back with their shape intact, and do_not_translate and preserve_placeholders keep product names and format tokens as written (translate docs).

What changes

Catalog refreshes stop being a copy-and-paste exercise across a dozen spreadsheets. Reviews land in the buyer's language without a second human pass. Product names and brand phrases stay as written because the glossary and protected terms enforce it. And before a sale event, the refresh runs in the background while your team handles the listings that need a human eye.