July 21, 2025
Article
International Stores Without the Chaos
How to design fashion & jewelry stores that work across countries—without breaking UX or SEO. Currency, sizing, languages, legal pages, shipping notes, regional content, and clean locale routing. (Shopify-first, site redesign only.)
The goal
Sell in multiple countries without turning your site into a maze. For fashion & jewelry, that means clear currency, correct sizes, readable languages, market-specific info, and SEO that doesn’t duplicate everything.
Currency switcher (that shoppers actually trust)
Design patterns
Location hint + manual control: auto-detect to a sensible default, but always show a visible switcher in the header or mini-cart. Never trap users.
One label, one meaning: show currency code and symbol (e.g., EUR €), not symbols alone.
Sticky choice: once a user selects a currency, persist it through PLP → PDP → cart → checkout.
Rounding rules: avoid weird decimals (e.g., €49.90 → €50). Choose market-specific rounding.
Microcopy examples
Cart note: “Prices shown in EUR. Taxes/duties calculated at checkout if applicable.”
PDP bar (international shoppers): “Ships from EU warehouse. Typical delivery 4–6 business days.”
Do / Don’t
✅ Do show free-shipping thresholds in the selected currency.
❌ Don’t switch currency without the shopper’s consent mid-journey.
Sizing localization (EU / US / UK)
Fashion
Dynamic size labels: map variant labels to the shopper’s region (e.g., EU 38 shows as US 6 with an info tooltip).
Compact converter: “View size in: EU / US / UK” right above the size grid. Keep it one tap.
Size guide per locale: fabric notes and model measurements should change with the language/region.
Jewelry
Ring sizer flow: quick picker (US/UK/EU) + link to printable guide.
Specs near price: metal, stone, carat—never in a collapsed tab.
Do / Don’t
✅ Do remember the last size system a user chose.
❌ Don’t bury the size chart; keep it within one tap of the size grid.
Language toggles (clarity over flags)
Patterns
Text labels over flags: languages aren’t countries—use EN / DE / ES (with full name on hover).
Header placement: near currency; keep both controls predictable and reachable on mobile.
Copy length elasticity: allow headings and buttons to expand in DE/ES without breaking layout.
Fallbacks: if a translation is missing, fall back gracefully (don’t show mixed-language screens).
Legal clarity
Translate Terms, Privacy, Returns/Warranty, and imprint/company info per language. Link them in the footer per locale.
Shipping notes & legal pages (market-specific)
What to localize
Shipping speeds & carriers by region (EU vs US vs UK).
Taxes/duties: state whether you collect them or if they’re due on delivery.
Returns language: fashion emphasizes size/fit; jewelry highlights care, warranty, and engraving policy.
Contact details: local phone formats, business registry/VAT where required.
Placement
PDP: short delivery & returns summary above the fold (expandable).
Cart/mini-cart: threshold bar + returns teaser line.
Footer: full legal pages per locale.
Region-specific content blocks
Where it helps
Home hero & promo bar: region-specific shipping offers or seasonal campaigns.
PLP banners: country-specific size guidance or “UK Next-Day available.”
PDP badges: “Made in Italy,” “Hallmarked in the UK,” “2-Year Warranty”—toggle per market.
Payments row: show the logos shoppers recognize (Shop Pay/Apple Pay/Google Pay/Amex) based on region.
Implementation tip (Shopify-first)
Use Markets and locales to conditionally render blocks in the theme (no heavy app stack). Keep it simple and editorial-friendly.
Avoiding the SEO mess (clean locale routing)
Use subfolders, not parameters
Prefer
/en/,/de/,/es/(and optionally/en-us/,/en-gb/,/en-eu/) over?lang=en. Subfolders are clearer for users and search engines.
Hreflang done right
On each localized page, include
hreflangpointing to its siblings (and an x-default). This tells search engines which version to serve per user.
Canonicals
Canonical each page to itself in its locale. Don’t canonical EN to DE or to a generic root.
Consistent slugs
Keep product/collection slugs aligned across locales where possible (translate only when necessary) to simplify maintenance.
Redirects & UX
Soft prompt on first visit (“Looks like you’re in Germany — switch to DE?”). Don’t hard-redirect without a visible choice, and always keep the manual language/currency controls.
Sitemaps
Generate a sitemap that includes all locales. Submit in Search Console for primary domains.
QA checklist (5-minute sanity test on mobile)
Currency switcher visible, persists through checkout.
Free-shipping threshold updates in the selected currency.
Size system toggle works; size guide opens fast.
Language toggle visible; no mixed-language UI.
PDP shows localized delivery/returns summary.
Footer links to locale-specific legal pages.
URLs use the correct
/locale/path; hreflang present.
How we ship this (Siteon approach)
We redesign the entire site—navigation, PLP, PDP, cart/mini-cart, and global components—then layer in locale controls that are simple to maintain:
Header controls: language + currency (compact, consistent).
Locale-aware size modules (fashion & jewelry).
Market-specific blocks for shipping, payments, and trust badges.
SEO-safe routing using subfolders and hreflang.
No tracking, no ads—site only. 7–14-day delivery.

