Sell from complete content
Localise the catalogue for each market , not word for word
Titles, descriptions, attributes and categories move into the locales you configure, with local units, your own vocabulary and every untranslated field flagged.
The situation today
What goes wrong today
The catalogue has to launch in several countries, and translation is slow, uneven or too literal. Content written for Germany, France or Italy is not the same content in another language: usage, units and conventions differ, and a specification translated correctly with the wrong unit still reads as an error to the shopper. Meanwhile nobody can say which share of the catalogue is actually complete in Dutch.
The mechanism
How it runs in Fuse
Translator moves titles, descriptions, attributes and category labels into the locales you define. Metric units and market conventions stay local. Brand vocabulary comes from the glossary you approved, so the same term is used everywhere. Fields that are still untranslated are reported rather than shipped empty, and anything that needs a commercial judgement goes to a person in the Inbox. Wording that gets approved is reused through the glossary and translation memory.
The e-commerce model ships with EN, FR and NL. Further locales need schema and Translator configuration. Reusing approved wording through the glossary and translation memory improves consistency; it is not model retraining.
What changes
What you get
-
Faster market launch
Opening a country becomes a configuration and a review queue, not a translation project.
-
One tone across markets
Brand vocabulary is applied from a list you own, so local pages do not drift apart.
-
No unit or terminology slips
Units and technical terms follow the market's convention rather than the source language's.
-
Language coverage you can see
Untranslated fields are a number you can report on, per locale and per range.
Indicators to track
How to measure it
- Products localised per language
-
records complete per locale
- Time to publish per market
-
days from decision to live catalogue
- Untranslated field rate
-
percentage of fields missing per locale
- Linguistic corrections after publication
-
corrections per month, per market
The number to watch: it says whether the glossary is doing its job.
Next
Related use cases
-
Attribute normalisation
Fuse converts source values into the reference lists your business uses for units, colours, sizes, materials, dimensions and technical characteristics.
-
Commercial content
From validated fields, Fuse drafts descriptions, bullet points, structured attributes and channel titles, with people reviewing the claims that matter.
-
Marketplace feeds
From one golden record, Fuse builds the feed each channel expects and reports the non-conformities, product by product, before publication.
Choose the market you cannot yet call complete
We localise one range into the locales you configure, keep the local units and your approved wording, and report every field still waiting for a translation.