A distributor with a good German-language site and a bad English-only one does not have a translation problem. They have a conversion problem that is being paid for in lost enquiries every week, and it shows up in analytics as a low conversion rate rather than as anything that looks like a language issue. The buyer arrives, finds a specification table in a second language, sees a price in a currency they do not invoice in, and leaves without telling anyone why.
The economics decide the order of work. Translating a whole catalogue into five languages is a six-figure project that most distributors start and never finish. Translating six page types into two languages, with a controlled glossary and a correctly configured hreflang set, captures most of the available gain within one quarter. This guide covers which pages to do first, how to present price, and the four technical mistakes that quietly suppress the traffic you just paid to translate. Our digital marketing strategy guide covers the acquisition side of the same funnel.
Why an English-Only Storefront Costs You EU Deals
The cost is measurable in three places, and none of them is the translation invoice.
The search result, first. A buyer in Bavaria searching for a German term for a 3D printer enclosure system does not find an English page, because the page does not contain the term. The loss happens before the click, which means it does not appear in your analytics at all. This is the largest single component of the cost and the one distributors consistently fail to estimate, because there is no report that shows it.
The second is the specification stage. Technical buyers in Germany, France, Spain and Italy read English competently in most cases. What they will not do is sign an internal justification document that cites English specifications when their own purchasing process requires a document in the local language. The machine is fine; the paperwork is not, and the paperwork decides.
The third is price. A quotation in US dollars forces the buyer's finance team to carry currency risk, and a page that shows a dollar price without VAT tells an EU trade buyer that the seller does not understand how they buy. Both effects push the enquiry toward whichever local competitor displays a euro figure with the tax stated.
The pattern worth noticing is that English comfort and commercial value are not correlated. The Netherlands and the Nordics read English best and need translation least; Germany reads English well and still requires local-language documents for its own procurement process. Sequencing by English comfort is the wrong sort. Sequence by where the revenue is and what the buyer's internal process demands.
The 80/20 Translation Order: Six Page Types Ranked
Rank the work by how close each page sits to a purchase, then by how many other pages depend on it staying consistent. Six page types carry almost all of the gain.
Product and specification pages first, always. A specification table is the page a technical buyer prints, forwards and compares. It is also the page with the highest density of terminology, which means it benefits most from a glossary and is the most expensive to translate badly. Translating the blog first is the classic misallocation: it produces traffic with nowhere to land.
The quotation page is second because it is short. Sixty to two hundred words, one form, and a price presentation decision. It is the cheapest high-value page on the list and should never be left until last on the grounds that it is "just a form".
Where the site also serves education buyers, the education and research guide covers how those pages differ in language and document expectations. As a budget reference, a distributor with 30 product pages, 25 support and shipping pages, and a blog archive will find that ranks 1 through 5 amount to roughly 60 to 90 pages. At professional rates of €0.10 to €0.18 per word with a technical translator, that is a four-figure to low-five-figure project per language, against a blog archive that would double it for a fraction of the return.
Terminology Control: Building a Two-Hundred-Term Glossary
Inconsistent terminology is the difference between a translated site and a professional one, and it is the cheapest quality control available. A glossary of 200 terms, built once per language pair, fixes the failure mode where the same component is called three different things on three pages.
Build the list from the specification pages, not from the site navigation. Extract every noun that names a component, a parameter or a unit: hotend, nozzle, build plate, layer height, tolerance, tensile strength, infill, raft, brim. Then record four columns per term: the English source, the approved target term, the terms that must not be used, and the page where the canonic form appears.
The units row is where technical translation fails most often and costs the most. German, French, Spanish and Italian all use a decimal comma and a space or a full stop as the thousands separator. A tolerance written as 0.35 mm that becomes 0,35 mm is correct in the target language; one written as 0,35 mm that a machine reads as 35 mm is a warranty claim. Specify the format in the glossary and check every numeric table on a rendered page, not in the source file.
The commercial and legal group needs a different treatment entirely. Terms such as warranty, guarantee, defect and reasonable time carry specific legal meanings in each jurisdiction, and the direct translation is frequently not the correct one. Have those forty to sixty terms reviewed by someone qualified in the target market's contract law, and expect that review to cost more than the translation of the surrounding text.
Currency and Tax Presentation: EUR With VAT, or Ex-VAT?
The short answer for B2B: show a euro figure excluding VAT as the primary price, state the VAT rate and treatment immediately beside it, and never present a bare number. The reason is that a professional buyer needs to compare your ex-VAT price against their own internal cost model, and a VAT-inclusive figure makes that comparison a calculation instead of a glance.
For consumers and for education buyers the convention reverses, because they cannot reclaim the tax and a bare ex-VAT figure is misleading to them. If the site serves both, the price block has to be explicit about which it is showing.
Two implementation details that avoid disputes. State the currency explicitly in the price block rather than relying on a symbol, because the same dollar sign serves several currencies. And fix a quotation validity window, 14 to 30 days, so that a euro price quoted before a currency movement is not held open indefinitely.
How the machine price is landed in the destination market is a separate question with its own guide: the Incoterms guide covers which trade term carries which cost, and the customs and tariff guide covers duty treatment. Selling a machine on a delivered basis means the price block has to reflect the term you quoted, not the price that left the factory.
hreflang and Canonical: Four Mistakes That Kill the Setup
The technical layer is where translated pages get suppressed, and the suppression is invisible: the pages exist, are indexed, and simply never rank in the market they were built for. Four mistakes account for most of it.
Self-referencing hreflang missing. Every page in the set must include a tag pointing to itself, including the English source. A cluster where the German page lists the French and English versions but not itself is an incomplete graph, and search engines may ignore the whole set. There is no penalty, just no effect.
Canonical pointing at the English page. This is the mistake that hurts most, because it is a deliberate decision that looks like good hygiene. Pointing the canonical of the German translation at the English original tells the engine the German page is a duplicate and should not be indexed. The correct configuration is: canonical to self, hreflang to the siblings.
Language and region codes used interchangeably. A German-language page for Germany, Austria and Switzerland has three targets: de-DE, de-AT and de-CH. Using a bare "de" for all three, or "de-DE" for all three, leaves the other two markets unserved. Conversely, treating en-GB and en-US as separate markets for a B2B machine catalogue is usually wasted effort, because the commercial difference is not in the content.
Reciprocity broken after a page edit. When a translation is retired or a URL changes, the cluster breaks and every page in it loses cohesion. Record the language map in one file, generate the tags from it rather than editing them by hand, and check the map whenever a page is retired.
Regulatory Text You Cannot Machine-Translate
Three blocks of text on an EU storefront carry legal weight, and machine translation of them is a compliance risk rather than a quality issue.
Product safety information. The EU General Product Safety Regulation imposes duties that include providing instructions and safety information in a language the consumer easily understands, with a stated manufacturer and an EU-based responsible person. A translated safety panel is not a marketing text, and an incorrect translation is a product placed on the market with defective information. Our GPSR and UKCA compliance guide covers what the panel must contain.
Extended producer responsibility and packaging labelling. Packaging EPR registration and national packaging labelling requirements are local-law obligations that vary by country, and they change more often than any other text on the site. The packaging EPR and PPWR guide covers the per-country requirements; the translated text must follow the current local wording, not a last year's translation held in the CMS.
Take-back, battery and WEEE statements. Registration obligations and the wording of take-back commitments are tied to the entity holding the registration, which may be the distributor or the importer depending on the structure. The WEEE and battery take-back guide covers the cost model; the point here is that the text must name the correct legal entity for each market, and a term rolled out across all markets with one entity name is wrong in most of them.
Measuring It: Four Metrics in Ninety Days
Translation projects are abandoned because their benefit is not measured, and the absence of a number thirty days in is read as an absence of value. Four metrics, read monthly, are enough.
Two interpretation notes. Impressions in the local language are the leading indicator and will move three to six weeks before anything else. Conversion rate on translated pages should be expected to exceed the English rate rather than merely match it, because the visitor arriving in their own language is further qualified. If it does not, the translation is present but the price and form presentation were left in the old format, which is the most common half-finished outcome.
Watch one signal that indicates a misconfiguration rather than a ranking problem. If indexed pages per language stall at a number far below the language map while the pages return 200 when fetched directly, the canonical or hreflang configuration is the cause, not content quality. Check those two before commissioning more translation.
Bottom Line
Translate product and specification pages, the quotation page, navigation, support and shipping into two languages before anything else, and build the 200-term glossary before the first word is translated. Show euro prices ex-VAT with the tax treatment adjacent, and treat the hreflang and canonical configuration as an engineering task with a test, not a settings panel someone clicked once. Price presentation is only half of the commercial layer: how the machine price is positioned against competing offers is covered in the pricing strategy and margin guide, and how published prices are protected across markets in the MAP and gray market guide. The distributors who do this see the gain in local-language search impressions within six weeks. Those who translate the blog first and leave the specification pages in English see nothing, and conclude, wrongly, that translation does not work in their market.
Reviewed by the Precise3D engineering & OEM team. Compliance files that accompany the catalog are auditable at the certification register.
Start Your Partnership
Selling Into Europe and Need Local-Language Technical Files?
Precise3D provides specification sheets, CE (LVD) and RoHS compliance documentation and print profiles in partner-ready form, so localisation starts from accurate source material rather than a translation of marketing copy.