Build with us
Ready to sell in Dutch, German and French?
Tell us about your shop and your markets. One free call, one honest quote in euros, zero pressure.
Get a fixed-price quote →Separate URLs per language, translated slugs, hreflang that validates, checkout and emails in the customer's language, and VAT that follows the destination.
€200 per additional language on a Scorpyns build · from €600 per language on an existing shop.
Weglot, GTranslate. A script swaps text in the browser. Fast to install, but the translated pages barely exist for Google, the monthly fee scales with words, and checkout errors show up untranslated.
WPML, TranslatePress. Real translated pages with their own URLs. Works, but adds database weight, a yearly licence, and a layer of complexity in every template. WooCommerce Multilingual on top of WPML is where a lot of "why is my shop slow" tickets come from.
Each language is a first-class version of the site with its own URL structure (/nl/, /de/, /fr/), its own translated content, and shared products, stock and orders underneath. This is what we build. Where a plugin is genuinely the better fit — very large catalogues with frequent content changes — we use Polylang or WPML and say so upfront.
Language is a preference; country is a fact. A Belgian customer might read in Dutch or French and still needs Belgian VAT, Belgian shipping rates and Bancontact. We keep these separate: the visitor picks language; billing address sets tax, shipping and payment methods.
EU One-Stop-Shop rates applied by destination, B2B reverse charge with live VIES validation, and OSS-ready reports so your accountant can file quarterly without spreadsheets.
A single admin where each product has language tabs. Untranslated fields fall back to the default language rather than showing blank. Bulk export/import for sending content to a translator and pulling it back.
We translate the store — everything that isn't your content. Your product texts, category descriptions and blog posts are translated either by you, by a translator you choose, or by us at €0.10–0.13 per word with a native review. Machine translation with human post-editing is available for large catalogues where speed matters more than nuance.
Fixed, per-language pricing, quoted in euros. See the full pricing overview.
| Scenario | Price |
|---|---|
| Additional language on a Scorpyns-built shop | €200 per language |
| Full multilingual store, new build (NL + DE, ready for FR) | from €3,650 |
| Adding proper multilingual to an existing WooCommerce shop | from €600 per language, after a short audit |
| Migrating from Weglot/GTranslate to native pages | quoted after audit |
| Content translation | from €0.10 per word |
Not for SEO. Subfolders (/de/) on one domain consolidate authority and are easier to run. Separate ccTLDs make sense only if you have a distinct business entity and marketing budget per country.
Yes, if they exist as real pages with hreflang and content in German. Overlay translations generally don't.
That's the usual path. We build the architecture multilingual-ready from the start so adding a language later is content work, not a rebuild.
One French version is enough for the shop UI; we tag it fr-BE and fr-FR via hreflang as needed. Product copy can differ by market if you want it to.
Native pages don't. Overlay scripts and heavy plugins can. This is one of the reasons we avoid them.
Tell us about your shop and your markets. One free call, one honest quote in euros, zero pressure.
Get a fixed-price quote →