SAP Commerce Cloud in Switzerland and the DACH Region: Implementation Guide

Selling to Swiss customers through SAP Commerce Cloud means dealing with a market that operates differently from the rest of Europe. Four official languages. Two currencies in active daily use. A data protection law (nDSG) that runs parallel to GDPR but isn’t GDPR. Payment methods that don’t exist anywhere else. And cross-border logistics that need to handle customs declarations for a country that isn’t in the EU.

Most Commerce Cloud implementation guides treat this as an edge case. For us, it’s the default. Spadoom is headquartered in Zurich. We’ve delivered Commerce Cloud projects for Franke and Distrelec in this market. The DACH requirements aren’t optional extras we bolt on at the end. They’re the starting point.

TL;DR: DACH e-commerce on SAP Commerce Cloud requires multi-currency (CHF/EUR with automatic VAT per destination), four languages with locale-specific content management, Swiss payment integration (TWINT, PostFinance, Datatrans/Saferpay), nDSG and GDPR dual compliance, and cross-border logistics handling customs for a non-EU country. Standard Commerce Cloud deployments don’t cover this out of the box. You need a partner who builds these requirements into the architecture from day one.

Why DACH E-Commerce Is Different

Switzerland ranks among the top e-commerce markets in Europe by per-capita spending. Swiss consumers spent CHF 15.7 billion online in 2024 (VSV/GfK, 2024). But the technical requirements for operating here are significantly more complex than a single-currency, single-language EU market.

Five things make DACH e-commerce different from a standard deployment:

Multilingual as a baseline, not an add-on. Switzerland has four official languages: German, French, Italian, and Romansh. In practice, most storefronts serve DE, FR, IT, and EN. This isn’t just translation. Product names, category structures, legal texts, and CMS pages need per-locale management. A product description that works in German Zurich may need different terminology for French-speaking Geneva.

Two currencies in daily operation. Swiss domestic commerce runs in CHF. Cross-border trade with Germany and Austria runs in EUR. B2B customers often expect pricing in both. This means real-time currency-specific pricing, not just display conversion.

A regulatory environment that sits between EU and Swiss law. Switzerland isn’t in the EU. The nDSG (New Federal Act on Data Protection) applies alongside GDPR for any business serving EU customers. Cookie consent requirements differ. Data transfer rules are separate. You can’t just deploy a standard EU compliance template.

Payment methods unique to the market. TWINT processes over 100 million transactions per year in Switzerland. PostFinance is the payment arm of the national postal system. Neither exists in Germany or Austria. A storefront without TWINT in Switzerland is like a storefront without iDEAL in the Netherlands. Possible, but you’ll lose sales.

Cross-border logistics with customs. Shipping from Switzerland to Germany means customs declarations, tariff classifications, and VAT handling at the border. Shipping from Germany to Switzerland is the reverse. EU-based fulfilment doesn’t automatically work for Swiss delivery. The logistics setup needs to handle both directions.

Multilingual Commerce: Four Languages, One Platform

SAP Commerce Cloud supports multilingual content natively. But supporting a feature and implementing it well for the DACH region are different things. Here’s what a proper four-language deployment actually involves.

Content Management per Locale

Every product in Commerce Cloud carries locale-specific attributes. For a DACH deployment, this means:

• Product names and descriptions in DE, FR, IT, and EN. Machine translation gets you 60% of the way. The remaining 40% — technical specifications, legal claims, sizing — needs human review per locale.
• Category structures that may differ by market. Swiss German consumers expect different navigation hierarchies than French Swiss consumers. “Haushalt” and “Maison” aren’t always a direct mapping.
• CMS pages per locale. Terms and conditions, return policies, shipping information — each needs a legally accurate version per language. Switzerland requires separate legal texts from Germany, even when both are in German.

URL Strategy and SEO

Multi-language SEO in Commerce Cloud requires deliberate URL architecture. We use locale-prefixed paths:

/de-ch/produkte/kaffeemaschinen/
/fr-ch/produits/machines-a-cafe/
/it-ch/prodotti/macchine-da-caffe/
/en-ch/products/coffee-machines/
/de-de/produkte/kaffeemaschinen/
/de-at/produkte/kaffeemaschinen/

Each locale gets its own hreflang tags, sitemap entries, and canonical URLs. Search engines treat de-ch and de-de as separate targets. If you serve both from the same URL, you lose ranking in both markets.

Commerce Cloud’s CMS cockpit manages all of this, but the architecture needs to be correct from the start. Retrofitting locale-specific URLs after launch means redirecting established search rankings.

Content Workflow

For Franke’s global platform, content moves through a structured pipeline: German is the master locale (authored first), followed by translation to FR, IT, and EN with market-specific review. Commerce Cloud’s staging and approval workflow handles this natively once configured correctly.

The key decision: centralised content management (one team manages all locales) versus distributed (each market manages their own). Both work. For Swiss businesses operating primarily in DACH, centralised with market review is typically more efficient.

Multi-Currency and Tax: CHF, EUR, and VAT Complexity

Currency Zones

Commerce Cloud handles multi-currency through currency-specific price rows on products. For DACH, the standard setup is:

• CHF price list for the Swiss storefront (de-ch, fr-ch, it-ch, en-ch)
• EUR price list for Germany (de-de) and Austria (de-at)
• Optional: dual pricing for B2B customers who want EUR prices displayed on the Swiss storefront

Price rows are maintained independently. This isn’t a display conversion — it’s actual pricing per currency zone, pulled from SAP ERP in real-time when connected to S/4HANA. Currency-specific promotions, volume discounts, and customer-specific pricing all work within each zone.

VAT Handling

This is where DACH gets properly complicated:

• Swiss VAT: 8.1% standard rate, 2.6% reduced rate (food, medicine, books), 3.8% accommodation rate. As of 2025.
• German VAT: 19% standard, 7% reduced.
• Austrian VAT: 20% standard, 10% and 13% reduced rates.

Cross-border B2C sales from Switzerland to Germany trigger German VAT obligations once you exceed the EU-wide distance selling threshold. Commerce Cloud calculates this per destination, but the tax determination logic needs to be configured for each corridor.

For B2B, reverse charge mechanisms apply on cross-border sales. Commerce Cloud supports this through tax condition records, but the configuration requires knowledge of both Swiss and EU VAT rules.

EU VAT One Stop Shop (OSS)

If your Commerce Cloud storefront sells B2C from Switzerland to multiple EU countries, the EU’s One Stop Shop simplifies VAT registration. Instead of registering in every EU country where you sell, you register once and report all EU sales. Commerce Cloud’s tax engine supports OSS, but your SAP ERP configuration needs to handle the reporting correctly.

Swiss Payment Systems: TWINT, PostFinance, and Beyond

Payment processing in Switzerland looks nothing like Germany or Austria. A DACH Commerce Cloud deployment needs to handle three distinct payment landscapes.

TWINT

TWINT is Switzerland’s mobile payment system. Over 5 million active users (TWINT, 2025) in a country of 9 million people. For e-commerce, TWINT works via QR code or app-to-app redirect. It’s not a card payment. It connects directly to the customer’s bank account.

Integration with Commerce Cloud goes through a payment service provider (PSP) — typically Datatrans, Saferpay (Worldline), or Adyen. The PSP handles the TWINT protocol; Commerce Cloud receives a standard payment confirmation. The checkout UX needs to support the TWINT flow: display QR code, wait for confirmation, handle timeout.

PostFinance

PostFinance Card and PostFinance E-Finance cover a significant share of Swiss online payments. PostFinance Card works like a debit card. E-Finance is a direct bank transfer from the customer’s PostFinance account.

Both integrate through the same PSP layer as TWINT. The key difference: PostFinance E-Finance redirects the customer to the PostFinance login portal, which adds a step to the checkout flow. Your Commerce Cloud checkout needs to handle this redirect gracefully without losing the cart.

Payment Service Provider Architecture

For DACH, we recommend a single PSP that covers all three markets:

Commerce Cloud’s payment extension framework connects to the PSP via a standardised API. One integration covers all payment methods across all markets. The PSP handles method-specific flows (QR codes, redirects, 3DS authentication) behind a unified interface.

Data Privacy and Compliance: nDSG Meets GDPR

Operating a Commerce Cloud storefront in the DACH region means dual compliance: Swiss nDSG and EU GDPR. They’re similar in spirit but different in implementation.

Where nDSG and GDPR Differ

The practical impact for Commerce Cloud: your consent management, privacy policy, and data processing records need to cover both frameworks. A GDPR-only implementation doesn’t satisfy nDSG requirements for Swiss customers, and vice versa.

Cookie Consent Implementation

Commerce Cloud’s storefront needs a consent banner that handles both regimes:

• Swiss visitors: Consent framework based on nDSG. Less prescriptive than GDPR on cookies specifically, but requires transparency about data processing purposes.
• EU visitors: Full GDPR cookie consent. Opt-in before any non-essential cookies or tracking.

Geolocation-based consent is the cleanest approach: detect the visitor’s country and apply the appropriate consent framework. Commerce Cloud’s tag management integration supports this through consent mode configuration.

Data Residency

Swiss companies increasingly require data residency guarantees. SAP Commerce Cloud runs on SAP BTP infrastructure. For DACH deployments, SAP offers data centres in Germany (EU10 Frankfurt) and Switzerland (CH20 Zurich for SAP BTP). Data residency configuration is part of the Commerce Cloud provisioning process.

Logistics and Shipping: Swiss Post, DHL, and Cross-Border

Domestic Delivery

Swiss domestic shipping is dominated by Swiss Post (Post CH). Standard options:

• PostPac Priority: next-business-day delivery across Switzerland
• PostPac Economy: 2-3 business days
• PickPost / My Post 24: locker and pickup point delivery

Commerce Cloud’s shipping extension integrates with Swiss Post’s web services API for label generation, tracking, and delivery status updates. The API handles German, French, and Italian addresses natively.

Cross-Border CH to EU

Shipping from Switzerland to EU countries requires:

• Customs declaration (CN22/CN23) for commercial shipments
• HS tariff classification per product
• Country of origin on commercial invoices
• DAP/DDP Incoterms decision: does the customer or seller pay import duties?

For DDP (Delivered Duty Paid) — where the seller handles customs — Commerce Cloud needs to calculate import duties at checkout. This requires integration with a customs duty calculation service. For DAP (Delivered At Place) — where the customer pays — the duty is collected at delivery.

We recommend DDP for B2C (customers hate surprise customs charges) and DAP for B2B (they handle import duties as part of their standard procurement).

Cross-Border EU to CH

German or Austrian fulfilment centres shipping to Switzerland face the same customs process in reverse. Swiss customs limits, duty-free thresholds (CHF 300 for most goods), and the prohibition on certain product categories all apply.

Commerce Cloud needs to validate Swiss import eligibility at cart level. Blocking restricted items before checkout prevents failed shipments and customer complaints.

Multi-Warehouse Fulfilment

For DACH operations with both Swiss and EU warehouses, Commerce Cloud’s sourcing strategy determines which warehouse fulfils each order. The logic typically follows:

1. Ship from the closest warehouse
2. Ship from the warehouse with the item in stock
3. Prefer same-country fulfilment to avoid customs (CH orders from CH warehouse, DE/AT orders from EU warehouse)

This sourcing logic is configured in Commerce Cloud’s order management module and integrates with SAP ERP’s ATP (Available to Promise) for real-time inventory.

Spadoom’s DACH Commerce Track Record

We’re not a consultancy that lists “DACH” as a capability because we once did a project in Munich. Spadoom is headquartered in Zurich. Our team works in German, French, Italian, and English daily. The DACH market is where we live.

Franke: Global B2B Commerce Platform

Franke’s Commerce Cloud platform is a global headless B2B/B2C deployment that we rescued from a stalled implementation and rebuilt into an award-winning platform. Key DACH-relevant elements:

• Multi-country deployment serving 10+ global channels from one Commerce Cloud instance
• Multi-language content management with centralised authoring and market-specific review
• B2B pricing with customer-specific price lists per currency zone
• 75% reduction in manual orders through automated self-service

Franke won an SAP Quality Award for this implementation. The platform went from legacy to production in 90 days.

Distrelec: B2B Electronics Distribution

Distrelec’s Commerce Cloud deployment handles high-volume B2B electronics distribution across Europe, with Switzerland as the home market:

• Complex product catalogue with hundreds of thousands of SKUs, technical specifications, and datasheets per product
• Multi-language product content managed through SAP PCM
• B2B features: punchout catalogues, approval workflows, organisation hierarchies, contract pricing
• Cross-border logistics between Switzerland and EU markets

What Sets Us Apart

The only other SAP partner in Switzerland with comparable Commerce Cloud depth is Advanis. Here’s the difference: we don’t just implement Commerce Cloud. We integrate it into the full SAP CX stack — Sales Cloud, Service Cloud, Emarsys, CDP. Commerce doesn’t exist in isolation. The customer who browses your storefront is the same customer your sales team quotes and your service team supports.

Our SAP Gold Partner certifications cover the full CX portfolio, not just Commerce.

Implementation Approach for DACH: Phased Rollout

We’ve learned from experience: trying to launch all DACH markets simultaneously is the fastest way to delay everything. The phased approach works better.

Phase 1: Home Market (8-12 weeks)

Start with your primary market. For most Swiss companies, that’s Switzerland with DE, FR, and IT storefronts.

Deliverables:

• Commerce Cloud provisioned and configured
• Product data model and catalogue structure
• Three-language storefront (DE, FR, IT)
• Swiss payment integration (TWINT, PostFinance, cards via Datatrans or Saferpay)
• Swiss Post shipping integration
• nDSG-compliant consent and privacy setup
• SAP ERP integration for pricing and inventory

This gives you a production-ready Swiss storefront. Real customers, real orders, real data. Everything learned in Phase 1 feeds into Phase 2.

Phase 2: DACH Expansion (6-10 weeks)

Extend to Germany and Austria:

• EUR currency zone with DE/AT-specific pricing
• German and Austrian payment methods (SEPA, Klarna, PayPal)
• DHL and Austrian Post shipping integration
• GDPR compliance layer alongside existing nDSG setup
• Cross-border logistics (customs, duty calculation, sourcing rules)
• EN storefront (if not already live)

Phase 3: Optimisation (Ongoing)

Post-launch refinement:

• A/B testing per market
• Performance tuning based on real traffic patterns
• Content personalisation per locale
• Additional payment methods based on market demand
• Marketplace integrations (Galaxus for Switzerland, Amazon for DE/AT)

Why Switzerland First?

Starting with Switzerland forces you to solve the hardest problems first. Multi-language, multi-payment, nDSG compliance, customs handling — these are all Switzerland-specific requirements. Once your Commerce Cloud instance handles Swiss complexity, extending to Germany and Austria is straightforward. The reverse is not true. If you start with a single-language, single-currency German storefront, adding Swiss requirements later means significant rearchitecting.

Ready to Talk Commerce Cloud in DACH?

If you’re evaluating SAP Commerce Cloud for the Swiss or DACH market, we should talk. Not a sales pitch — a technical conversation about your specific requirements, integration landscape, and timeline.

Get in touch or explore our E-Commerce solution page for more detail on what Commerce Cloud can do.

Frequently Asked Questions

Does SAP Commerce Cloud support Swiss Francs and Euros?

Yes. Commerce Cloud natively supports multi-currency with real-time pricing per currency zone. Swiss storefronts typically run CHF for domestic and EUR for cross-border, with automatic tax calculation per destination.

Can Commerce Cloud handle four Swiss languages?

Yes. Commerce Cloud supports unlimited languages with per-locale product content, category structures, and CMS pages. DACH deployments typically run DE, FR, IT, and EN with locale-specific content management.

What Swiss payment providers integrate with Commerce Cloud?

TWINT, PostFinance, and all major card processors integrate via payment service providers like Datatrans, Saferpay (Worldline), or Adyen. SAP Commerce Cloud’s payment extension framework makes integration straightforward.

Is Spadoom an official SAP Commerce Cloud partner?

Yes. Spadoom AG is a certified SAP Gold Partner headquartered in Zurich, with specific Commerce Cloud implementation expertise. We’ve delivered Commerce Cloud projects for Franke, Distrelec, and others in the DACH region.

How long does a DACH Commerce Cloud implementation take?

8-16 weeks for a single-country B2B storefront, 4-6 months for a multi-country deployment with full multilingual content and localised payment/logistics integration. Our phased approach starts with Switzerland and expands to Germany/Austria in a second phase.