What's new
Chat on WhatsApp
Toggle Nav
My Cart
Adobe Certified · Switzerland

Magento developer in Switzerland

I’m Kishan Savaliya, an Adobe Certified freelance Magento developer working with shops in Switzerland from Ahmedabad, India. Swiss stores are small markets with big expectations: prices in CHF, TWINT in the checkout, and a site in German, French and often Italian. Because Switzerland is outside the EU, I also plan for customs on every parcel that crosses the border, in either direction.

  • TWINT next to cards and PostFinance, through Datatrans, Wallee or Stripe
  • Privacy notice and consent set up for the revised FADP
  • German, French, Italian and English store views with CHF pricing
Reserve my slot See pricing
Free 30-minute call in your morning Quotes in USD, CHF figure on request
  • TWINT On most Swiss phones

    More than five million people in Switzerland use TWINT, so a shop without it looks foreign. I add it through Datatrans, Wallee or Stripe, next to cards and PostFinance Pay.

  • revFADP Swiss privacy law

    The revised Federal Act on Data Protection has applied since September 2023. It is close to the GDPR but not identical, so I check your privacy notice, consent and data-export flow against the Swiss text, not only the EU one.

  • 4 languages One store view each

    German for Zürich and Bern, French for Geneva and Lausanne, Italian for Ticino, English for visitors and expats. Each gets its own URL and hreflang.

  • 6 hrs Overlap with your morning

    My 12:00 to 18:00 IST is 7:30 to 13:30 in Zürich in winter and 8:30 to 14:30 in summer. Your whole morning, every working day.

What you get

What I set up on a Swiss Magento store

Switzerland looks like one small market and behaves like three or four. Language, currency and customs decide more of the build than the theme does, so I plan these six first.

  • TWINT, PostFinance and cards

    TWINT goes near the top, PostFinance Pay for its loyal account holders, then Visa, Mastercard and Apple Pay. I connect them through a Swiss provider such as Datatrans or Wallee, or through Stripe or Adyen if you also sell in the EU.

  • revFADP privacy setup

    Under the revised FADP your privacy notice must say which data you collect and which countries it goes to, and that includes your hosting and email tools. I list those properly, set up consent, and give your team a simple way to export or delete a customer’s data.

  • German, French, Italian, English

    Swiss German shoppers expect Standard German with no ß, Romandie expects real French, not a quick translation. I build one store view per language with hreflang, and keep product data in one place so a price change lands everywhere at once.

  • MWST, CHF and the QR-bill

    Products mapped to 8.1% standard or 2.6% reduced MWST, prices in CHF rounded to five Rappen, and for invoice customers a Swiss QR-bill on the PDF, which replaced the old orange payment slips.

  • Swiss Post and customs

    Swiss Post handles most domestic parcels. For orders into the EU, or from an EU warehouse into Switzerland, I set up delivered duty paid shipping so the customer is not surprised by a customs bill at the door.

  • Built around what you sell

    Watches and luxury goods in Zürich and Geneva, specialty suppliers in Basel, outdoor and lifestyle brands around Bern. On the first call I ask what you sell and to whom, and the language and payment plan follows from that.

How it works

Five steps from booking to live

Staging is ready from day three. A 9:00 call in Zürich or Geneva is 13:30 in Ahmedabad in winter and 12:30 in summer, so we speak in your morning and I act on it the same day. Nothing reaches production until you say so.

  1. 01

    Audit

    Free 30-min call. I map your CH payment stack (TWINT / PostFinance / Stripe CH), revFADP posture, language plan (DE/FR/IT/EN) and Swiss Post / DHL CH carrier rules. Written scope follows.

    Day 1
  2. 02

    Quote & reserve

    Fixed-price quote in USD with CHF equivalent. Pay by IBAN, card, or PayPal. Slot reserved on signature, written project plan with risk register included.

    Day 2
  3. 03

    Build

    Staging up by day 3. Daily commits, daily Loom recap, status calls in CET. Multi-language store-view rollout coordinated with your translator.

    Days 3-18
  4. 04

    Deploy

    Blue-green cutover at off-peak, typically 23:00 CET when Swiss traffic dips. Old build stays warm 72 hrs for instant rollback. TWINT live-key swap last.

    Launch night
  5. 05

    Stabilise

    14-day post-launch coverage during CET business hours. Bug-fix, Lighthouse-score guarantee, MWST verification, revFADP DSAR-flow smoke tests across DE / FR / IT views.

    Days 18-32
Pricing

Fixed prices. No per-hour surprises.

Pick the tier closest to your store. If the audit turns up extra work, I quote it before I start, never after.

  • Express

    $ 1,499 USD

    5-7 days · ~CHF 1,360 · single-version upgrade

    Best for: Single-version Magento upgrades, TWINT integration, single-language CH storefront, MWST 8.1% rate refresh.

    • Free 30-min CH-scope audit
    • Fixed-price written quote (USD with CHF equivalent)
    • TWINT integration (live + sandbox keys)
    • Single-version M2 upgrade or single-payment add-on
    • MWST 8.1% / 2.6% tax rates verified
    • Staging environment + daily commits
    • Blue-green deploy + 7 days post-launch coverage
    Book Express slot
  • Most popular

    Standard

    $ 3,499 USD

    10-14 days · ~CHF 3,180 · most popular

    Best for: Hyvä migration, multi-language DE/FR/IT storefront, TWINT + PostFinance + Stripe CH multi-rail, revFADP cookie + DSAR flows.

    • Everything in Express, plus:
    • Hyvä theme migration (or Hyvä Checkout install)
    • Multi-language store views: DE + FR + IT (EN optional)
    • Multi-rail payments: TWINT + PostFinance + Stripe CH + Apple Pay
    • revFADP cookie consent + DSAR / DPO automation
    • Swiss Post + DHL CH carrier rules wired into ShipperHQ
    • Locale-aware schema + hreflang per language
    • 14 days post-launch coverage (CET business hours)
    Reserve Standard slot

  • Enterprise

    Custom

    4-8 weeks · luxury / B2B / 4-language / cross-border

    Best for: Luxury watch/jewellery DTC, B2B + DTC dual flows, full 4-language (DE/FR/IT/EN), cross-border CH↔EU DDP, FINMA-touching finance flows.

    • Everything in Standard, plus:
    • Full 4-language storefront with regional hreflang (DE-CH / FR-CH / IT-CH / EN)
    • Cross-border CH↔EU DDP shipping engine + customs codes
    • B2B + DTC dual-checkout (IBAN-preferred for high-value B2B)
    • Datatrans + Wallee enterprise gateways (luxury / watches)
    • Adobe Commerce Cloud (Frankfurt) or AWS Zürich migration
    • FINMA-aware data flows (for finance-touching catalogs)
    • Dedicated CET-time-zone PM + 30 days post-launch coverage
    Get Enterprise quote

Prices in USD. CHF equivalent at current rate available on request, ask in the booking form. TWINT / Datatrans / Wallee licence fees are paid directly to those vendors.

Book your slot

Reserve your Swiss Magento project slot

The form takes about two minutes. I reply with a written quote within 24 business hours, with the CHF figure if you ask for it.

Message me on WhatsApp

No form to fill. Send me a quick message and I reply within 4 hours on IST working days, often sooner.

Helpful to mention

  • Company
  • Store URL
  • Magento version
  • Canton
  • Languages needed
  • Payment methods used / wanted

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

What clients say

What clients say about working with me

Reviews from clients on Upwork, Clutch and LinkedIn, from several countries. Ask me on the call if you want to speak to one of them.

Consistently accessible with strong Magento expertise.

“Consistently accessible with strong Magento expertise. I intend to collaborate with him on another

GY

Gina Yan

Excellent developer.

“Excellent developer. Helped us get to where we needed to be and fixed the problems i a fast period of time. Very

D

Darren

CEO, Ocean Telecom

Kishan was a huge help on my Magento project.

“Kishan was a huge help on my Magento project. Five stars all the

LO

Lauren Osterstock

great professional with enthusiasm, knowledge, skill and exceptional patience in solving problems.

“great professional with enthusiasm, knowledge, skill and exceptional patience in solving

D

Dennis

Bay Tech

Perfect and professional help on my Magento project.

“Perfect and professional help on my Magento project. Will hire him again once needed. Thanks for your work

ND

Neal De Vreede

Great experience working with Kishan Savaliya.

“Great experience working with Kishan Savaliya. completed job very fast and provided me accurate results. I highly recommend him for Magento 2 and development work. Thank

AS

Ajay Singh

Other markets I build Magento stores for

  • United States
  • United Kingdom
  • Switzerland
  • Germany
  • France
  • Italy
  • Netherlands
  • India
FAQ

Questions Swiss store owners ask me

How do I integrate TWINT with my Magento 2 store?

TWINT is the dominant Swiss mobile-payment rail, 5M+ Swiss users, near-mandatory for any Swiss DTC checkout. Two integration paths:

  • Direct TWINT acquirer, via Datatrans or Wallee, which both have certified Magento 2 modules. Best for stores doing >CHF 500k/yr in Swiss volume; fees ~1.3-1.8%.
  • Stripe CH or Adyen as TWINT enabler, both now offer TWINT as a payment method on top of their existing Magento connectors. Best for multi-region stores that already run Stripe / Adyen elsewhere; fees slightly higher (~2.0-2.5%) but one contract.

We wire TWINT QR-on-PDP, TWINT in checkout, and the QR-on-paper-receipt flow for omnichannel B2B. Sandbox tested before live-key swap on cutover night.

Multi-language Swiss site, DE/FR/IT/EN, how should I structure it?

Switzerland has 4 official languages, and Swiss shoppers strongly prefer their regional language. The right Magento structure:

  • One website (single product catalog, single inventory).
  • One store for Swiss commerce (CHF, MWST 8.1%, Swiss Post rules).
  • 4 store views: de_CH, fr_CH, it_CH, en_CH.
  • URL structure: /de/, /fr/, /it/, /en/ with hreflang per view (de-CH, fr-CH, it-CH, en-CH).

Translations live in Magento’s native i18n + catalog_product_entity_*_store tables, we manage the translation pipeline (typically via Crowdin or Phrase) so the DE source-of-truth syncs cleanly to FR / IT / EN. Locale-aware schema.org emitted per store-view.

What is revFADP and how does it differ from EU GDPR?

revFADP (revised Federal Act on Data Protection) is Switzerland’s data-protection law, in force since 1 September 2023. It replaced the 1992 FADP and is broadly “GDPR-equivalent”, the EU recognises it under an adequacy decision, so EU↔CH data flows continue freely.

Key Swiss specifics vs EU GDPR:

  • Only natural persons are protected (EU GDPR also covers some legal-entity edge cases).
  • Profiling has stricter explicit-consent rules.
  • DPO appointment is voluntary (not mandatory like under EU GDPR Art. 37).
  • Sector regulators on top, FINMA for finance, BAG for health.
  • Penalties are applied to individuals (executives), not just companies.

We wire revFADP-compliant cookie consent, DSAR automation, retention rules in customer + sales_order, and a privacy notice in DE / FR / IT / EN.

How do I handle CH↔EU cross-border shipping (DDP) in Magento?

Switzerland is not in the EU customs union, so every CH↔EU parcel crosses a customs border. For premium DTC (luxury, watches, fashion), DDP (Delivered Duty Paid) is the expected default, the seller pre-pays VAT + customs so the customer never sees a surprise bill at the door. Two-part Magento setup:

  1. Pricing engine, we add an EU-VAT calculation layer (per destination country: DE 19%, FR 20%, IT 22%, NL 21%, etc.) on top of CHF list prices, and quote “CHF X (DDP, all duties included)” in checkout.
  2. Carrier rules, Swiss Post + DHL CH both offer DDP-bonded labels with the right HS commodity codes per SKU. We populate product_attribute with HS codes (8-digit), country-of-origin, and net weight, and the carrier module emits the right CN23 / commercial-invoice docs.

For low-value parcels (< EUR 150), IOSS to EU is optional; for >EUR 150 it’s mandatory full customs clearance.

How does Swiss MWST 8.1% work for an online store?

Swiss MWST (Mehrwertsteuer / TVA / IVA) has three rates from 2024+:

  • 8.1% standard, raised from 7.7% on 1 January 2024. Most goods + services.
  • 3.8% special, hotel accommodation.
  • 2.6% reduced, food, books, medicines, newspapers.

Registration threshold is CHF 100k worldwide turnover, foreign sellers shipping into CH must register if they cross it. Magento setup:

  1. Configure 3 tax rates in tax_rate table per canton (rates are federal so it’s really one set, but we keep the canton column for future-proofing).
  2. Map MWST tax classes to product attribute sets (e.g. food vs general).
  3. Show price inclusive of MWST on PDP / cart / checkout (Swiss B2C convention) but exclusive for B2B store views.
  4. Quarterly MWST return: export from Magento, file via the federal eMWST portal.
What’s the best hosting for Swiss Magento, Hostpoint, Infomaniak, AWS Zurich, or Adobe Commerce Cloud Frankfurt?

Pick by stage + budget:

  • Hostpoint (CH-based, St. Gallen), managed hosting, good for <CHF 1M stores. Data stays in CH (good for some FINMA-touching catalogs). CHF 50-200 / mo.
  • Infomaniak (CH-based, Geneva), eco-friendly, ISO 27001, popular for French-speaking CH. Similar price band to Hostpoint.
  • Cyon / Metanet, smaller CH-based options for SMBs.
  • AWS Zürich (eu-central-2), opened 2022, ideal for >CHF 5M stores wanting auto-scale + Swiss data residency. CHF 500-3,000+ / mo.
  • Adobe Commerce Cloud (Frankfurt), if you’re already on Adobe Commerce. ~30ms latency to most Swiss postcodes. Data leaves CH (DE-hosted), worth checking against your revFADP risk register. CHF 25k+ /yr.
  • Hyvä Cloud, great middle-ground for Hyvä-based Swiss stores.

We benchmark + migrate, the right answer depends on data-residency requirements (FINMA / health) and traffic profile.

How do I integrate PostFinance and Stripe Switzerland together?

Many Swiss stores want both: PostFinance (the Swiss Post-owned bank, hugely trusted by older Swiss shoppers) and Stripe CH (best dev experience + global cards). They live happily side-by-side as separate Magento payment methods:

  • PostFinance e-Payment, via the official Magento 2 module; handles PostFinance Card, PostFinance e-finance, and a few common credit-card rails as a redirect flow.
  • Stripe CH, via the official Stripe Magento 2 module; handles Visa/MC/AMEX, Apple Pay, Google Pay, Klarna, and now TWINT as a payment-method.

We wire both, set Stripe as default for <CHF 200 orders (lower fees on cards) and PostFinance as default for >CHF 500 (higher trust on big-ticket items). Refund + chargeback flows tested for both. PostFinance settles to your Swiss IBAN; Stripe settles to whatever bank you nominate.

Should I migrate to Hyvä for my Swiss luxury / watches store?

Almost certainly yes if you’re on Luma. Swiss luxury / watch shoppers expect the speed + polish of brand sites like Rolex, Omega, IWC, and they shop on iPhone in DE / FR / IT:

  • Lighthouse 95+ on Hyvä vs typically 40-60 on Luma luxury themes, Google ranks fast pages higher for “rolex submariner switzerland”-style queries.
  • Hyvä Checkout loads in < 1s, halves bounce on CHF 5,000+ checkouts where any latency creates doubt.
  • TWINT QR + Apple Pay render natively on PDP without the React/jQuery double-render Luma has.
  • Multi-language store-view switching (DE↔FR↔IT) is instant on Hyvä, vs full-page reflow on Luma.
  • Datatrans / Wallee enterprise checkout integrate cleanly via Hyvä payment-method bridge.

Typical migration timeline: 4-6 weeks. Conversion lift in the first 90 days post-launch is usually 8-25% from speed alone. See our Hyvä service page for fixed-price tiers.

How do I configure regional store views for Zurich vs Geneva vs Ticino?

Pure-language store-views work for most Swiss stores, but for stores with strong regional brands (e.g. luxury watches with Zürich vs Geneva flagship boutiques) we sometimes layer a region dimension on top:

  • Default Swiss store: 4 store-views (DE / FR / IT / EN), one CHF price-list, MWST 8.1%.
  • Region overlays via customer_segment or store_group: Zürich-default sees the Zürich boutique address + DE; Geneva-default sees the Geneva boutique address + FR; Ticino-default sees the Lugano boutique address + IT.
  • Click-and-collect: per-region pickup-point modules so a Geneva shopper sees Geneva pickup options first.
  • Hreflang: de-CH, fr-CH, it-CH, en-CH at minimum, we don’t fragment further by canton (Google treats CH-DE as one regional target regardless of which canton).
What time-zone overlap can I expect from India?

Real, daily, 4-6 hours of working overlap:

  • India Standard Time = UTC+5:30
  • Switzerland = UTC+1 (CET, winter) or UTC+2 (CEST, summer)
  • Overlap window: 12 PM, 6 PM IST = 7:30 AM, 1:30 PM CET (winter) or 8:30 AM, 2:30 PM CEST (summer).

That covers your morning standup, mid-morning review, and lunchtime hand-off. Daily 14:00 CET review on staging is the typical cadence. If you need late-day overlap (post-15:00 CET) we can flex 2-3 days/week. Slack / WhatsApp async covers the rest. We’ve worked this way with Zürich, Geneva, Basel, and Bern clients for years.

Can I run a single Magento for CH + EU customers?

Yes, and for most Swiss DTC stores it’s the right default. Three patterns by volume:

  • Single store, geo-priced, one storefront, MWST + EU-VAT calculated by destination, DDP shipping for EU. Cheapest. Good for <CHF 2M stores.
  • Two store-views per language pair, e.g. de-CH + de-DE, fr-CH + fr-FR, etc. One Magento backend, separate prices/tax per region. Most popular for >CHF 2M.
  • Two websites, two backends, legally separate CH AG + EU GmbH/BV. Best for >CHF 10M with EU fulfilment hub. Magento website-level split.

Customs is the wrinkle, CH is outside the EU customs union, so even the “single store” pattern needs DDP labels + HS codes wired into Swiss Post / DHL. We architect, build, and migrate live data including 301 redirects.

What’s the right setup for a luxury Swiss watch store with B2B + DTC?

Luxury watches are the canonical Swiss e-commerce vertical, high AOV (CHF 2k, 500k), strict authorised-dealer rules, B2B (boutiques / retailers) + DTC (collectors) on the same catalog. Setup:

  • Adobe Commerce (or Open Source + B2B-features extension) for the company entity, authorised dealers as company records with credit limits and customer-specific pricing.
  • Catalog gating: limited-edition / haute-horlogerie SKUs hidden from DTC, visible to verified B2B accounts only.
  • Payments: Datatrans or Wallee for high-AOV cards (3DS2 strong-auth), IBAN bank-transfer for B2B, TWINT only on <CHF 1k accessories.
  • Authentication: serial-number + warranty registration on PDP, with optional NFC chip-tap (we’ve built this).
  • FINMA / AML: for >CHF 100k orders the “Geldwäschereigesetz” (anti-money-laundering act) requires identity verification, we wire Onfido or Veriff into checkout.
  • Multi-language: DE / FR / IT / EN baseline, optional ZH-Hant + Arabic for international collectors.

Typical timeline: 8-12 weeks. Enterprise tier above is sized for this.