Product pages & catalogue data
Titles, descriptions, features, materials, specifications, variants and structured product fields.
Localize the store as a connected buying journey. Product data, category content, search and filters, cart and checkout text, customer emails and post-purchase support are reviewed together so terminology and instructions stay consistent from discovery to delivery.
A product name or attribute may appear in the catalogue, filters, product page, cart, order email and support content. Ecommerce localisation works better when those repeated terms are reviewed across the complete journey.
Titles, descriptions, features, materials, specifications, variants and structured product fields.
Category headings, introductions, attributes, filter labels, sorting options and collection content used for product discovery.
Menus, breadcrumbs, search prompts, zero-result messages and recurring navigation labels across the storefront.
Buttons, fields, delivery choices, payment guidance, validation messages, order review and account-creation content.
Marketplace titles, bullet points, descriptions and structured seller content prepared for the target audience and channel.
Order confirmations, delivery updates, returns guidance, support articles and other post-purchase communication.
Approved product names, features and collection terminology are reviewed across catalogue data, pages, marketplaces and customer communications.
Sizes, colours, materials, units and variant labels are handled in relation to the product field they belong to rather than as disconnected words.
Buttons, forms and validation text are localised according to the stage of the purchase journey so instructions remain clear.
Order emails, delivery messages and returns guidance are reviewed against the storefront terminology customers have already seen.
Product volume alone does not define the project. Store fields, repeated content, marketplace variants, checkout strings and post-purchase content all affect how the localisation should be scoped.
Provide catalogue data, store pages, checkout text, customer emails, target languages and the required return format.
Product families, repeated fields, marketplaces, store journeys and recurring terminology are identified before localisation starts.
Discovery, product evaluation, checkout and post-purchase content are handled with the customer action in mind.
Terminology, variants, fields, placeholders and agreed file structure are checked before the content is returned.
Send the most editable source available. Product IDs, field names and channel references help preserve relationships between the source content and the returned localisation.
CSV / XLSXCatalogue exports, product fields, attributes, source and target columns, IDs and review notes.
XML / JSONStructured product or storefront data where customer-facing values sit alongside technical fields.
CMS EXPORTSuitable store exports that retain enough context to identify products, categories and customer-facing fields.
URL / PAGE LISTUseful for smaller stores, landing pages, marketplace references and live customer-journey review.
The final quote is confirmed after reviewing the language pair, source-word volume, product structure, file format, SEO requirements, review level and deadline.
For suitable higher-volume ecommerce content where an AI-supported workflow with human review fits the catalogue and brief.
For customer-facing store content requiring natural wording, product consistency and journey-specific human localisation.
For content requiring additional SEO-aware handling, complex product terminology or a more specialist review workflow.
Use this page for product catalogues, store discovery, checkout and customer lifecycle content. Use Website Localization for broader website pages and Marketing Translation for standalone campaign assets.
Ecommerce localization adapts an online store for another language and market. It can include products, categories, navigation, checkout, marketplace content, customer emails and post-purchase support.
Yes. Large catalogues can be reviewed from structured exports such as spreadsheets or suitable CMS data, with product IDs and fields used to keep source and target content aligned.
Yes. Buttons, forms, delivery choices, payment guidance, validation messages, order summaries and confirmation text can be handled as part of the buying journey.
Yes. Marketplace titles, bullet points, descriptions and related seller content can be included when they form part of the ecommerce project.
Yes. Product, category and landing-page titles, metadata, headings and supplied search context can be considered where SEO-aware localisation is part of the brief. This does not guarantee rankings.
Suitable AI-supported content with human review starts from £0.08 per word, human ecommerce localisation from £0.12 per word, and SEO or specialist work from £0.16 per word. Final pricing depends on language, volume, files, complexity and deadline.
Include target languages, sales channels, product terminology, deadline and the return format your team needs. We can then confirm the ecommerce-localisation workflow and price.