Before / after
7 Dutch localization mistakes that quietly kill trust — and the biggest one is having no Dutch at all
These are real patterns pulled from live foreign Shopify stores selling into the Netherlands and Belgium — not invented examples. Brand names are removed; the mistakes are exactly as found. Dutch shoppers don't file complaints when copy reads wrong (or is missing) — they just quietly lose confidence and leave. Mistake #2 below — zero Dutch content — is the single most common one we see, which is exactly what the Nederlandse Storefront Starter is built to fix.
1. Gender errors on basic nouns
Dutch nouns are either "de" or "het" words, and getting it wrong on a store-credit or account page reads as instantly non-native to any Dutch speaker — including the relative pronoun that has to agree with it.
2. Whole pages — often the whole store — left untranslated
Not a sentence: entire product descriptions, About pages, Terms clauses, or the entire homepage left 100% in English while the store otherwise clearly serves NL/BE (EUR pricing, Dutch/Belgian shipping zones, sometimes a locale switcher that just isn't used). This is the most common finding we make, by far — more common than any grammar slip on this page. It's not a "fix the errors" job at that point; there's nothing local to fix, only content to write. That's the gap the Nederlandse Storefront Starter exists for: ready-to-paste native copy for the homepage, best-selling products, and policy pages, generated fresh rather than patched.
3. Machine-translation calques
Literal, word-for-word carryovers from English that no Dutch speaker would actually write. Individually small, but they add up fast across a whole storefront and are one of the clearest tells of unedited machine translation.
| Before (literal) | After (natural) |
|---|---|
| gebruikmaakt van | maakt gebruik van |
| vooraleer / voorafgaandelijk (used on a nl-NL site) | voordat / vooraf |
| geef ze een cadeaukaart (singular "someone" treated as plural) | geef diegene een cadeaukaart |
4. Legal pages that quietly switch tone mid-document
Privacy policies and terms should stay in the formal register ("u/uw") throughout. We regularly find isolated sentences — often around payment or checkout clauses — that slip into the informal "je/jouw" register mid-document, which reads as sloppy on exactly the pages meant to build legal trust.
5. A real mistranslation that changes meaning, not just tone
The one that matters most: a mistake that actually reverses or confuses meaning rather than just sounding awkward.
6. Missing local payment methods in the copy
iDEAL gets mentioned on most stores that bother to localize at all — Bancontact, the Belgian equivalent, is missing far more often, even on stores that explicitly serve Belgian customers elsewhere on the site (currency, shipping zones, locale switcher).
7. Untranslated urgency and CTA copy
"Limited time only," "Explore," "Shop now" — small phrases that get missed because they live in template snippets or banner components rather than the main product copy, so a page-by-page translation pass skips right past them.
Does your own store have zero Dutch content, like mistake #2?
Send us your Shopify URL and we'll rewrite one section of your own homepage in natural Dutch — free, no obligation. If it's a full "no Dutch at all" situation, what you want is the Nederlandse Storefront Starter: ready-to-paste native copy for your homepage, best-selling products, and policy pages, flat €300, delivered within a day. (Already have Dutch copy with mistakes like #1, #3, or #4 above? That's the Localization Audit instead — same price.)
Get your Storefront Starter — €300, instant checkoutPrefer to see an example first? Request a free example rewrite instead.