Create a single reference brief
Store the verified name, material, dimensions, sizes and pack contents in one brief. Mark brand names, model numbers and SKUs as identifiers to preserve. Separate store policies from item attributes so a translation does not move a return promise into a marketplace title. Resolve missing facts before creating multiple versions.
Check meaning, not word matching
“Pack of 2” must stay two items; “not included” must keep its negation. For example, a kurta set that excludes a dupatta must not become a complete three-piece set in another language. Read the translated sentence as a buyer would and ask what they would expect to receive. Use familiar terms rather than a literal English word order.
Review quantities and promises separately
Compare each version side by side. Pay particular attention to units, decimal values, delivery conditions, price validity and warranty wording. “May be available” is not the same as “available”; “estimated delivery” is not a guarantee. For high-impact promises or unfamiliar terminology, obtain a fluent reviewer’s check before publishing.
Separate app language from copy language
In Likhao, interface language and the language requested for generated content are separate choices. Changing the interface is not a review of your saved copy. After drafting a new language version, check its facts and confirm the channel’s current language requirements. Keep the reviewed versions together so a later product change can be applied consistently.
Common questions
Does translated copy guarantee a marketplace accepts that language?
No. Check the current language and category requirements for the destination. Use a supported format even when you prefer another language.
