Scope an ecommerce language enquiry beyond product descriptions

Create a content inventory for the enquiry

List product descriptions, attributes, category pages, interface text and supporting articles. Record the languages, audience and available export format. Ask which product identifiers, sizes or brand terms must stay unchanged and whether the client has an approved terminology list.

Mention recurring or near-identical content so the actual source can be assessed. Do not infer a final price from the number of products alone. If descriptions are still being revised, identify the version and expected update process.

Separate content delivery from store administration

Explain whether the client wants translated files, a language review after upload or another defined output. Platform configuration, payments, tax settings and legal compliance are not automatic parts of a translation referral.

With permission, introduce the client and a representative sample to Enuncia. The team reviews language availability, scope and timing. Web partners who encounter these requirements can apply to Enuncia Network and agree the relevant referral terms before making commercial promises.

Keep exploring

• Make a software-string enquiry understandable outside the codebase
• Do not leave navigation and form messages out of a website language brief
• Build a compact context pack for a localisation enquiry