Wir verwenden Cookies, damit CarphaCom funktioniert, Ihre Einstellungen gespeichert werden und wir die Leistung messen können. Sie können alle akzeptieren, nicht notwendige ablehnen oder Ihre Auswahl anpassen.
Bald verfügbar1-Klick-Bereitstellung auf Vultr MarketplaceBenachrichtigen

Languages, Currencies & Localization

Multi-language storefront

Each language has a URL prefix (/en, /ro, /de). Visitors can switch from the header language picker. Their choice is remembered via cookie.

Enable a language

  1. Go to Settings → Languages.
  2. Click Add language, pick from the list (RO, EN, DE, FR, ES, IT, PL, …).
  3. The language becomes available immediately.

Translate strings

The storefront UI uses translation keys (e.g. nav.account, product.add_to_cart). When you add a new language, missing keys fall back to English.

  1. Go to Settings → Languages → [language] → Edit translations.
  2. You see a table: key, source (English), translation. Edit inline.
  3. Click Save. The storefront picks up changes within a minute.

Auto-translate

Click Auto-translate missing keys. The system uses your configured translation backend (DeepL or Gemini) to fill in missing translations. You can review and edit any of them afterwards.

Currencies

Currencies are tied to regions, not to languages. A French visitor browsing your Romania region still sees RON. Some shops set up a separate region per currency (e.g. Eurozone with EUR, USA with USD).

To add a currency:

  1. Create a new region in Settings → Regions.
  2. Pick the currency.
  3. Add the countries that belong to this region.
  4. Set per-region prices on each product (or use auto-conversion).

Auto-conversion

Toggle Auto-convert prices in a region. Prices in other regions are converted to this region's currency at the daily exchange rate (refreshed every 24 hours).

Locale-aware checkout

The checkout flow is fully translated. Address forms also adapt: postal-code regex, required fields, and state/county dropdowns change based on country.

SEO per language

Each language gets its own sitemap (/en/sitemap.xml, /ro/sitemap.xml) and hreflang tags linking equivalent pages. Search engines correctly index each language version.