E-Commerce Translation Services
E-commerce translation services put an online store’s product content into the language of each market it sells to — the listing fields, the structured data behind them and the contract copy around the basket, rather than the pages surrounding the catalogue. Espresso Translations is a translation services provider certified to ISO 17100:2015: e-commerce translation starts at £0.10 per word over 2 to 3 working days, a certified document is £30 per page of up to 250 words in 24 to 48 hours, and a free quote reaches you within 1 hour.
ISO 17100:2015 Certified
Native-Speaker Translators
Priced Per Word
Second-Linguist Check
150+ Languages Covered
Quote Free in 1 Hour


Get an E-Commerce Translation Quote
We reply within 1 hour
What are e-commerce translation services? E-commerce translation services translate the product content of an online store — titles, descriptions, variant and attribute data, size fields, category trees, feed and marketplace fields, delivery and returns terms, checkout copy and customer reviews — into the language of each market it sells to. Espresso Translations covers 150+ languages with native linguists and a second-linguist check under ISO 17100:2015; e-commerce translation starts at £0.10 per word over 2 to 3 working days and a certified document is £30 per page of up to 250 words in 24 to 48 hours. The point a UK retailer usually needs clearing up is that the two halves of the business answer to different rules. The General Product Safety Regulations 2005 impose no English-language requirement on a domestic listing. Sell the same item into the EU and Article 19(d) of Regulation (EU) 2023/988 wants the warning text inside the offer in a language easily understood by consumers in the destination state, while Article 8(2) of Directive 2011/83/EU dictates the wording of the order button.
What Do E-Commerce Translation Services Actually Translate?
The listing, and everything around it that decides the sale. That means product titles and product descriptions, the variant and attribute data behind them, size and measurement fields, the category tree the item is filed under, the feed and marketplace fields that carry it to a channel, delivery and returns terms, payment and checkout copy, the frequently asked questions block on a product page, and customer reviews. Espresso Translations handles all of it with native speakers of the target language and a second-linguist check, and the same team translates the support materials that travel with the goods.
What belongs somewhere else is the site around the catalogue. Website localization — navigation, website content, editorial pages, hreflang tags and URL structure — is a different job, and our website translation page covers it. Multilingual SEO is a separate discipline again: keyword research in a new market, relevant keywords for local search and the ranking of a translated site are not things a translated product title delivers by itself. Keeping the two apart matters commercially, because a translated site sitting on an untouched product feed fails in a way nobody notices until a channel stops showing the products.
Two different things are sold under the name ecommerce translation and they are priced differently. One is human translation of product content by a linguist who knows the category. The other is machine translation with post-editing, MTPE, which many translation agencies now offer as the default. The difference is not a matter of taste: ISO 17100:2015 excludes raw machine translation with post-editing from its own scope, so an MTPE file is not a file produced to that standard, whatever the invoice says. CSA Research’s 2020 survey of 8,709 consumers in 29 countries found that 66% of online shoppers use machine translation themselves, which is an argument for controlling your own terminology rather than leaving it to theirs.
On a live store this is continuous work rather than a single project. Translation memories hold the repeated copy so a catalogue update is quoted as a diff, a glossary fixes product names, attribute values and brand voice in each language version, and a project manager keeps both between releases. Translated content that is written once and then updated in English only drifts back into the half-translated state within a season, and e-commerce websites change faster than any other kind.
Does UK Law Require an Online Store To Be in Any Particular Language?
Not expressly, and the answer surprises most retailers. The General Product Safety Regulations 2005, SI 2005/1803, remain the GB product-safety regime and they carry no English-language mandate. Regulation 7(1) requires a producer to provide consumers “with the relevant information to enable them— (a) to assess the risks inherent in a product throughout the normal or reasonably foreseeable period of its use, where such risks are not immediately obvious without adequate warnings, and (b) to take precautions against those risks.” The duty is that the information enable risk assessment; no language is named. The word English occurs once in the whole instrument, inside a citation to an Official Journal reference rather than inside a requirement. The table sets out where the duties that do name a language come from, and almost every one of them arrives with an EU sale. This is a description of the instruments and not advice: a retailer selling into a new market should put its own range in front of its own solicitor.
| What you are selling, and to whom | Language duty as drafted | Instrument |
|---|---|---|
| Any product listed to a GB buyer | None named; the information must enable the buyer to assess the risk | General Product Safety Regulations 2005 (SI 2005/1803), regulation 7(1) |
| Clothing listed to a GB buyer | English | Regulation (EU) No 1007/2011 as retained in Great Britain, Article 16(3) as replaced |
| The same product listed to an EU buyer | Warning and safety text inside the offer, in a language easily understood by consumers as determined by the destination Member State | Regulation (EU) 2023/988 (GPSR), Article 19(d) |
| The basket and the order button, selling to an EU consumer | Only the words “order with obligation to pay” or a corresponding unambiguous formulation | Directive 2011/83/EU (CRD), Article 8(2) |
| Clothing listed to an EU buyer | The official language or languages of the destination Member State | Regulation (EU) No 1007/2011, Article 16(3), with Annex I |




What Changes the Moment You Sell Into the EU?
Three duties arrive at once, and all three land on the listing rather than in the warehouse. The product becomes made available on the market in a Member State under Article 4 of Regulation (EU) 2023/988 where the offer is targeted at consumers there; the offer itself has to carry translated warning and safety text; and the basket copy has to satisfy the destination’s own contract-language rule as well as the prescribed wording of the order button. The platform does not change that analysis — Shopify, Magento, now Adobe Commerce, WooCommerce and BigCommerce all export the same field types — but a channel can stop showing the products.
How Does Translating the Offer Decide Which Regime Applies?
Article 4 of Regulation (EU) 2023/988 turns on targeting. A product offered online counts as made available on the market where the offer is aimed at consumers in the Union, and an offer is aimed there where the operator directs its activities, by any means, to one or more Member States. Recital 21 then lists what to weigh, and language sits in the middle of the list: dispatch areas, “the languages available, used for the offer or for ordering”, the means of payment, use of that Member State’s currency, a domain name registered there. The recital also closes off the easy escape — an interface simply being reachable in a Member State is, in its word, “insufficient”.
For a GB retailer that cuts both ways, and it is worth modelling before a market launch rather than after it. Accepting an order from a Dutch shopper who found your English store is not, by itself, directing activity at the Netherlands. Publishing a Dutch language version, pricing in euro, offering local payment methods and dispatching there is evidence that you are. So translation belongs in a market-entry decision and not only in a conversion plan, and the e-commerce sales you win across borders arrive with the destination regime attached to them.
What Exactly Has To Be Translated Inside the Offer?
Article 19 of Regulation (EU) 2023/988, applicable since 13 December 2024, lists what an online offer has to show clearly and visibly: the product’s identification, the manufacturer’s details, the EU responsible person’s details where the manufacturer sits outside the Union, and, in point (d), any warning or safety information “in a language which can be easily understood by consumers, as determined by the Member State” where the product is made available. Instructions and safety information carry the identical standard under Articles 9(7) and 11(4). Article 21 pulls digital delivery inside it, so a QR code pointing at an English-only page settles nothing. And Article 36(2) raises the bar for a recall notice, which is owed in the language or languages of the Member States where the item was sold.
Note what that standard is not. It is a comprehension test set by the destination Member State, not a requirement to use the official language, and the Regulation leaves the determination to that state rather than to the seller. Whether machine translation satisfies it is unresolved: no Commission guidance on the point was found, so this page does not claim it fails the test and does not claim it passes. Article 16(1) matters too for a seller outside the Union — a product may not be placed on the market unless an economic operator established in the Union is responsible for the tasks in Article 4(3) of Regulation (EU) 2019/1020, and Article 19(b) requires that operator’s details in the online offer.
What Must the Order Button Say?
Article 8(2) of Directive 2011/83/EU requires that where placing an order entails activating a button, the button be labelled in an easily legible manner “only with the words ‘order with obligation to pay’ or a corresponding unambiguous formulation”. The sanction is the reason to care about it: “the consumer shall not be bound by the contract or order”. Because the Directive is enacted in every official language the correct string is a lookup rather than a decision — «commande avec obligation de paiement», «ordine con obbligo di pagare», «pedido con obligación de pago», «encomenda com obrigação de pagar», „zahlungspflichtig bestellen“ — and Buy now, translated for fluency, is the wrong answer.
Two savings sit beside that. The model instructions on withdrawal in Annex I(A) and the model withdrawal form in Annex I(B) are part of the Directive, so an official version of each already exists in every EU language; the job is filling in the brackets of the target-language original, and Article 6(4) treats points (h), (i) and (j) as discharged once the trader has handed those over “correctly filled in”. Article 8(3) is the other cheap one: before the ordering process starts, a trading website has to say legibly which delivery restrictions apply and which means of payment it takes.
Where Do Reviews and Review Disclosures Fit?
Reviews are what shoppers ask for in their own language more than anything else on a product page. The figure behind that claim is traceable, unlike most of the numbers in this market: CSA Research put out a press release on 7 July 2020 about a Kantar-run survey of 8,709 consumers across 29 countries, in which 73% wanted product reviews in their language if nothing else, 76% preferred buying where the information was in their native language, and 40% said they would never buy from a site in another language. Read those with three qualifications attached: the publisher sells into the localization industry and is not a neutral observer, 2020 is five years back, and the public document is a summary of a report nobody here has read. Strip the body, the year or the sample out of the sentence and the number stops being usable — which is why none of the familiar unattributed variants appears on this page.
The legal position is narrower than most pages on the subject suggest. Article 7(6) of Directive 2005/29/EC, as the Omnibus Directive amended it, treats information about how a trader checks that published reviews come from people who really bought or used the product as material — so that statement has to sit beside the reviews in every language version, and it is part of what lets a shopper build trust in them. Annex I point 23c puts “misrepresenting consumer reviews” among the practices that are unfair whatever the circumstances, and point 23b catches a trader who claims purchaser-verified reviews “without taking reasonable and proportionate steps to check”. Does translating a review misrepresent it? No authority we could reach has ruled either way, so the honest answer is that it is unsettled, and legal content of this kind is worth a solicitor’s hour before a translator’s.
What Happens to Pricing, Units and Measurement?
Where a unit price has to appear, the reference unit belongs to the destination market. Article 2(b) of Directive 98/6/EC sets it at a kilogramme, a litre, a metre, a square metre or a cubic metre, or else at whatever “single unit of quantity” is “widely and customarily used in the Member State concerned” for that kind of product. Article 3(4) carries the unit price into any advertisement that quotes a selling price; Article 4(1) wants both figures unambiguous, easily identifiable and clearly legible; Article 4(2) ties the quantity to national and Community provisions. So this field is localised by rule, not by taste.
Sizes run the opposite way, and this is the instruction most often got wrong: declare the system, do not convert the number. Google’s product data specification gives size_system a closed value list — US, UK, EU, DE, FR, JP, CN, IT, BR, MEX, AU — as “the country of the size system used by your product”, and size_type a closed English list: regular, petite, maternity, big, tall, plus. Rewriting a UK 12 as a German 40 inside a free-text field destroys the one comparison a shopper can actually make, against a garment already owned. Currency and payment are a separate decision from language, and Google treats them as separate fields too.
Which Fields Does a Translator Touch, and Which Must Be Left Alone?
Free text is translated, controlled vocabularies are not, and identifiers never move at all. Google’s product data specification states the rule plainly: attribute names and the values of attributes that take supported values go in English, and its worked example is condition — new, refurbished, used — whose values “must be submitted in English in order for the system to read them”. Where an attribute is free form, such as the title or the description, the instruction is one language throughout a single data source. And an identifier is deliberately language-blind: the same product keeps the same ID whichever country or language it is listed in.
Category trees are two fields and not one. google_product_category is mapped to Google’s own taxonomy, and the numeric ID is the recommended form precisely because it carries no language; your own product_type tree is free text to 750 characters and is the part that gets localized. Listing metadata moves with the title, so a half-translated catalogue leaves it in the source language, and alt text on a product image is listing copy as well. Those are the fields a prose pass misses and a channel notices.
A multilingual e-commerce catalogue is therefore a mapping exercise before it is a writing exercise. We build the attribute map and the glossary first, with native linguists working in the category, and the second-linguist check under ISO 17100:2015 runs against the source rather than against a style guide. Espresso Translations is ISO 17100:2015 certified and is ATC certified and an ATC member, and every linguist on a retail account has at least five years of experience.
Alongside listing copy we translate the legal content around it — terms and conditions, delivery and returns policies, warranty text — the marketing copy built around a launch, the technical documentation and safety instructions that ship with the goods, and the product and brand video our transcription team turns into text first. We cover 150+ languages with 2,000+ linguists, which is what makes several local audiences possible at once, and localization services and translation are quoted on the same brief.
£0.10 per word is where e-commerce translation starts, over 2 to 3 working days. Certification of a document attached to a catalogue is charged by the page — £30 covers up to 250 words, back in 24 to 48 hours — and a sworn translation, which some receiving countries ask for under that name, is £55 a page and takes 7 to 14 working days. Sworn translator is not a legal status in the United Kingdom, so that route exists for the destination country and never for a British requirement. Video and audio work begins at £5 a minute, counted per video minute for subtitling and per audio minute for transcription. Urgent jobs can go on the 24-hour express tier where the project allows, and the quote itself costs nothing and lands within 1 hour.
| E-commerce service | Price | Delivery |
|---|---|---|
| Product listings, descriptions, feeds and checkout copy | From £0.10 per word | 2–3 working days |
| Certified translation of an attached document | From £30 per page (up to 250 words) | 24–48 hours |
| Express catalogue update | Quoted per project | 24 hours for selected projects |
| Quote | Free | Within 1 hour |
Additional E-Commerce Language Services
We also provide transcription through our transcription services, subtitling for product and brand video, technical translation for manuals and data sheets, and certified translation where a document attached to a catalogue needs a signed statement of accuracy. Subtitling and transcription start from £5 per minute, per video minute and per audio minute respectively.
How Does an E-Commerce Translation Project Run at Espresso?
In four steps, beginning with the fields rather than the word count, because a catalogue quoted as prose is quoted wrong. Each step below is one you sign off before the next begins.
Step 1: Send an Export, a Feed or a List of URLs
Upload a catalogue export, a feed file, a spreadsheet of listing fields or a list of product URLs. Tell us the target markets, the channels involved and the data source language of each feed, and flag any attribute wired to a filter. If a document attached to the catalogue has to be certified, send every page of it.
Step 2: Field Scoping and a Free Quote in 1 Hour
A project manager splits free text from controlled values, counts only the words that will actually be translated, and marks every string that is a lookup instead — button wording, warning text, permitted fibre names, the Annex I withdrawal documents. Within 1 hour you have a free, itemised quote that names the fields we intend to leave untouched as plainly as the ones we intend to translate.
Step 3: Human Translation, Glossary and Review
A native linguist working in your category translates the free-text fields against the glossary, and a second linguist reads the result against the source under ISO 17100:2015. Prescribed strings are not translated at all: they are copied out of the enacted instrument — the permitted fibre name from Annex I, the button wording from the Consumer Rights Directive, the withdrawal documents from the Directive’s own annexes.
Step 4: Return in the Same Structure
The catalogue comes back with the same columns, the same product IDs and the same controlled values, so it loads without a reconciliation pass. The glossary and the attribute map come with it, and the next release is quoted as a diff rather than as a new job.
Why Is a Partly Translated Catalogue the Worst State To Be In?
Because it is the one configuration a channel’s own published rules are aimed at, and because the legal duties do not fade gradually. Google says that where the key elements of a listing — it names title, description and variant information — do not match the data source language, performance suffers because the information will not meet what a user searched for in that language; and where most of the product data does not match, “your products may be disapproved”. May, and the channel is the one deciding. Search engine visibility follows from that rule rather than motivating it, which is why search engines are not the argument this page rests on.
The legal half is blunter. A warning line left in English in an offer aimed at Italian consumers does not partly satisfy Article 19(d). A button reading Compra ora rather than the prescribed formulation does not partly bind the buyer. And a recall notice carries a constraint a translator’s instinct will break. Article 36(2)(c) of Regulation (EU) 2023/988 requires the hazard set out without anything that might dull a consumer’s sense of the risk, and it names the offending words itself: “voluntary”, “precautionary”, “discretionary”, “in rare situations”, “in specific situations”. Reaching for a gentler word in the target language is the single move that provision rules out.
What Does Translating Well Actually Buy a Retailer?
Local expectations met in the fields a shopper reads, and a submission a channel can process. That is a smaller claim than this market usually makes, and deliberately so: no body publishing a conversion or basket-abandonment figure for translated product content with a disclosed method was found, so no percentage uplift appears anywhere on this page. What is documented is the CSA Research preference data above, Google’s published consistency rule, and the language duties the instruments themselves set out. Those are enough to decide a budget on, and none of them depends on a number nobody can source. Adapt the copy to the market by all means; just do not buy the statistic.
Which Related Translation Services Does Espresso Offer to Retailers?
Very few retail accounts sit inside a single service. Start from whichever line below describes the file on your desk; the questions at the foot of the page deal with fields, prices and prescribed strings one at a time.
Certified Translation Services
Conformity paperwork, a supplier declaration or a contract riding along with a catalogue, where the receiving party wants a signed statement of accuracy — that is our Certified Translation Services page.
Legal Translation Services
Distribution and supply agreements, your terms and conditions, or a dispute that has started over what a listing said — start at Legal Translation Services.
Website Translation Services
Everything outside the catalogue — menus, editorial pages, the body copy of the site itself — is handled on the Website Translation Services page, which owns website localization. This page owns the commerce layer sitting inside it.
Technical Translation Services
Installation guides, data sheets and the safety instructions boxed with the goods belong with Technical Translation Services.
Digital Marketing Translation
Launch campaigns, email sequences and advertising copy are covered on the Digital Marketing Translation page.
Transcription Services
Footage, a brand film or a recorded supplier briefing that has to exist as text first: Transcription Services.
2,000+
Linguists
ISO 17100
Certified quality standard
1 hour
Free quote
150+
Languages Supported
What Else Do Retailers Ask About E-Commerce Translation Services?
How much do e-commerce translation services cost?
£0.10 per word is the starting point for e-commerce translation, delivered in 2 to 3 working days, and the quote is broken down by field type, since free text, controlled values and prescribed strings cost different amounts to handle. Certification works by the page: £30 buys a page of up to 250 words back within 24 to 48 hours, and that single figure already contains the translation, the second-linguist check and the signed statement of accuracy. Where a destination country insists on a sworn translation by that name, it is £55 a page across 7 to 14 working days. Video and audio begin at £5 a minute. Books and literary work sit higher, at £0.15 to £0.20 per word. Send the export; the quote costs nothing and arrives inside the hour.
Do I have to translate my online store for the UK market?
No instrument requires it. The General Product Safety Regulations 2005 place the duty on content rather than on language: regulation 7(1) requires a producer to give consumers the relevant information to enable them to assess the risks inherent in a product and to take precautions against those risks, and no language is named anywhere in the instrument. One GB exception runs the other way, and it is the textile rule: in the retained Great Britain version of Regulation (EU) No 1007/2011, Article 16(3) was replaced in full and requires English, so the fibre composition on a clothing listing to a GB buyer is English copy by law. Everything else is a commercial decision until you start selling into the EU, where the duties become express.
What does a GB clothing listing have to say in English?
Its fibre composition. Article 16(1) of Regulation (EU) No 1007/2011 requires the fibre composition descriptions to be indicated in catalogues and trade literature, on packaging, labels and markings, legibly and in uniform print, and to be clearly visible to the consumer “before the purchase, including in cases where the purchase is made by electronic means” — so it is listing copy, not only label copy. In the retained Great Britain version Article 16(3) was replaced in full and requires English. Annex I fixes the permitted fibre names, and the obvious cognate is often wrong when the same garment is listed into the EU: entry 43 is elastane in English, elastano in Spanish and Portuguese, elastan in Italian and élasthanne in French. That is a lookup rather than a translation.
What changes when I start shipping to the EU?
Three things, and every one of them lands on the listing rather than in the warehouse. Regulation (EU) 2023/988 has applied since 13 December 2024, and its Article 19(d) wants any warning or safety information inside the offer, in a language consumers in the destination state can easily understand, with that state deciding what qualifies. Article 8(2) of Directive 2011/83/EU then dictates the order button, and a button carrying the wrong words leaves the consumer unbound by the contract or order. Third, the contract copy around the basket answers to the destination’s own language statute, because the Directive hands that subject to the Member States in recital 15 and Article 6(7). Clothing adds a fourth duty: in its EU form, Article 16(3) of the textile Regulation wants the destination’s official language.
Which fields in a product feed must stay in English?
Anything taking a controlled value, plus the identifiers. Google’s product data specification puts attribute names and supported values in English, and uses condition — new, refurbished, used — to make the point, because the system has to be able to read the value. size_system is a closed list of country codes; size_type is a closed English list. google_product_category is a mapping job against Google’s own tree, with the numeric ID preferred exactly because a number has no language. One product keeps one ID across every country and every language it appears in. What is left — the title, the description, your own product_type tree — is genuine free text, gets translated, and has to be in a single language within one data source.
Is machine translation with post-editing good enough for product content?
That depends on what the output has to satisfy, and one point should be stated plainly rather than sold. ISO 17100:2015 excludes raw machine translation with post-editing from its own scope in its own words, so an MTPE file is not a file produced to that standard even when the supplier holds the certificate. Whether machine translation meets the GPSR standard of a language easily understood by consumers is unresolved — no Commission guidance on the point was found, so this page does not claim it fails and does not claim it passes. For a prescribed string the question does not arise at all: the order button wording, a fibre name and the withdrawal texts come from the enacted instrument, and no engine and no translator gets to improve on them.
Do I need to translate my terms and conditions and returns policy?
That is a question for each destination country rather than for the EU. Recital 15 of Directive 2011/83/EU records that the Directive “should not harmonise language requirements applicable to consumer contracts”, and Article 6(7) lets Member States maintain or introduce their own requirements about the language of contractual information. What the Directive does require is plainness: Article 8(1) asks for the Article 6(1) information “in plain and intelligible language”, which is not the same as the consumer’s language however often it is read that way. Article 6(1) is also the list of what the copy has to cover — total price inclusive of taxes and all delivery charges, payment and delivery arrangements, the withdrawal right and the model form in Annex I(B), who bears return costs, after-sales assistance and commercial guarantees.
How is a translated catalogue kept up to date?
As a diff rather than a rerun. Translation memories hold the repeated copy, so an update is quoted on the new and changed rows only and the same sentence is never charged twice; the glossary holds product names, attribute values and brand voice in each language version; and the attribute map records which columns were deliberately left in English. Without those three the second release is as expensive as the first and drifts away from it in wording. This is the part that decides whether multilingual e-commerce is sustainable: a store that publishes in English and translates quarterly spends most of the year in the half-translated state that Google’s own disapproval rule describes.
Can you work with Shopify, Adobe Commerce, WooCommerce or BigCommerce exports?
Yes. Whatever the platform exports — a CSV or XML feed, a catalogue dump, a spreadsheet of listing fields, or just a list of product URLs — comes back in the same shape, with the controlled-value columns and the product IDs exactly as they left. What this page will not do is describe any platform’s or marketplace’s own language policy. Google’s specification and its supported-languages documentation could be read in full, so they are quoted; the corresponding Amazon, eBay, Shopify and Etsy pages could not, so this page says nothing about what they require or how they review, in either direction. No partnership, integration or approved-supplier relationship with any of them is claimed anywhere on this site.
Does translating my store into a language change which law applies?
It is one of the facts that settle the question, which is why it belongs in the market-entry plan rather than in the marketing plan. Under Article 4 of Regulation (EU) 2023/988 an online offer aimed at consumers in the Union makes the product available on that market, and recital 21 weighs the evidence of aim: where you will dispatch to, the languages the offer and the ordering flow are available in, the payment methods, the currency, the domain. Mere reachability of an interface, it says, is not enough. Pointing the other way, Article 4(3) of Regulation (EU) 2018/302 makes clear that obeying the geo-blocking rules does not of itself drag in the buyer’s own national non-contractual requirements. Two different questions with two different answers; put your own catalogue in front of your own adviser.
Do customer reviews have to be translated?
Nothing in the instruments requires it, and it is the thing shoppers ask for most: in CSA Research’s 2020 survey of 8,709 consumers across 29 countries, 73% wanted reviews in their own language even if nothing else was. What the law does demand is the disclosure sitting next to them. Under Article 7(6) of Directive 2005/29/EC as amended, how a trader verifies that published reviews come from real purchasers counts as material information, so it has to appear in each language version. Annex I point 23c treats misrepresenting consumer reviews as unfair in every circumstance. Whether a translated review has been misrepresented is a question no authority we could reach has answered, so get advice before you start.
What does ISO 17100:2015 actually cover?
It is a standard a translation service provider is certified to, not a qualification an individual holds — so the accurate phrasing is certified to ISO 17100:2015, and Espresso Translations is. Its practical content for a catalogue job is the review requirement: the target text is checked against the source by a second person before delivery, which is why every listing we translate goes through a second linguist. The standard also excludes raw machine translation with post-editing from its own scope, so MTPE output is outside it. Alongside it we hold ATC certification and ATC membership. No other professional body is claimed on this site, and a supplier that lists several is worth asking which of them actually audits translation.
How long does an e-commerce translation take?
Listing and catalogue work takes 2 to 3 working days; a certified document comes back inside 24 to 48 hours; a sworn translation needs 7 to 14 working days, since a third-party office rather than Espresso controls that clock. Where the project allows it, there is a 24-hour express tier for urgent work. On a catalogue, though, translation is seldom the slow part. The slow parts are extracting a clean export, settling which attribute columns feed a filter, and pinning down the strings that are lookups — button wording, permitted fibre names, the withdrawal documents. Say what the deadline is and which channel the content is for when you send the file, and we will tell you which leg to worry about.
Can you translate product video and marketing copy as well as listings?
Yes, and most retail accounts need both. Our transcription team turns product video, brand film and recorded supplier material into text that can then be translated or subtitled, and subtitling and transcription start from £5 per minute, per video minute and per audio minute respectively. Marketing copy around a launch, email and campaign content sit on our digital marketing translation page; the technical documentation, data sheets and safety instructions that ship with the goods sit on the technical page; and website content, navigation and editorial pages sit on the website translation page. One brief can cover all of them, with one glossary across the account so the product name reads the same in an ad, a listing and a manual.











