ConversionEX
Services
WorkReviewsAboutContact
Zurich

Shopify Store Design & Development in Zurich

Shopify storefronts for Zurich brands whose customers read in three languages and whose parcels cross a customs border on the way out.

Delivered remotely for brands across Zurich and Switzerland.

Build · Zurich

Why Zurich brands come to us for this

  • German, French and English storefronts on one Shopify catalogue through Markets, not three drifting sites
  • TWINT, buy-on-invoice and card decided before design, because the payment set changes the checkout layout
  • Landed cost for EU buyers built into the product page and cart rather than buried in a shipping policy
  • Product templates built for the categories Zurich actually exports: movements, cocoa origin, fit and technical spec
  • Swiss Post delivery options and pickup points presented the way domestic buyers expect to see them

A Zurich merchant usually arrives with a better product than website. The company is profitable, family-held, forty years old in some cases, and the store was built once by an agency that treated it as a brochure with a cart attached. Nothing is broken. It simply never had to work hard, because the reputation and the wholesale channel carried the numbers. The moment direct sales matter, every soft spot shows at once: a product page that describes a movement or a cocoa origin in one paragraph, a size and fit story that stops at a PDF, a checkout that offers card only.

The build here is shaped by a small home market. Nine million people split across German, French and Italian commercial regions means the storefront has to serve several languages on one catalogue from day one, not as a phase two. We build it through Shopify Markets with translation held in the theme layer, so navigation, filters, metafield labels, cart copy and transactional email all switch together. A half-translated store reads as unfinished, and a Swiss buyer is unusually intolerant of unfinished.

Then the border. Every parcel leaving Switzerland for the EU is an export, so the product page and cart have to answer a question a domestic-only theme never asks: what will this actually cost me when it arrives. We design landed cost into the page rather than hiding it in a shipping FAQ, wire duties and import VAT into the checkout where DDP makes commercial sense, and make sure the commercial invoice and HS codes come out of the system rather than out of someone in Altstetten typing them into a courier portal.

3 storefrontsGerman, French and English on one catalogue and one inventory
Theme-level i18nfilters, cart and transactional email translate with the product, not after it
DDP-ready cartduties and import VAT resolved at checkout for EU destinations
Local context

One catalogue, three storefronts, and a border in the shipping logic

Most Swiss stores we inherit have solved multi-language by duplicating themselves: a .ch site in German, a French site someone built later, and two inventories that stopped agreeing about eighteen months ago. Rebuilding that as one catalogue with market-level storefronts is the single highest-value structural decision in a Zurich build, and it has to be made before design starts because it changes URL structure, hreflang, price presentation and how your merchandiser works every day. Prices get set per market rather than converted live, so a German customer sees a clean euro figure instead of CHF times whatever the day's rate produced. Payment gets built around what people here actually use — TWINT, buy-on-invoice through a third-party provider, cards — which changes cart and checkout layout, not just a settings page. And delivery options are presented against Swiss Post's service levels for domestic orders and a separate, honest international promise for everything crossing out.

Scope

What Design & Build includes

The same standard of work we run for every client — applied to a Zurich brand’s realities.

Full service detail
01

Conversion-Led UX & Wireframes

Wireframes for home, collection, product, cart and checkout drawn from your own session recordings, site-search logs and support tickets. Not a template library.

02

Custom Online Store 2.0 Theme

A bespoke theme in clean, commented Liquid with modular sections your team can rearrange themselves. Zero dependency on page-builder apps.

03

Merchandising & Navigation System

Collection architecture, filtering, badging and cross-sell rules mapped to how your catalogue actually sells. Bestsellers surface; dead stock stops eating grid space.

04

Speed Budget & Core Web Vitals

Image pipeline, third-party script audit and app cleanup enforced against a hard budget: LCP under 2.5s on 4G mobile, CLS under 0.1, INP under 200ms.

05

Catalogue & Content Load

Products, variants, metafields, collection copy and redirects loaded and QA'd in a dev store before cutover. You review a real store, not a Figma file.

06

Launch, Handover & Documentation

Loom walkthroughs, a written theme guide and 30 days of post-launch fixes included. Your team owns the store from day one.

Scoped and quoted for your Zurich store

We do not work off a rate card. Every Zurich engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.

Get this scoped
How it runs

From kickoff to results

01

Discovery & Data Pull

Two weeks inside your analytics, heatmaps, site search and support inbox. We leave with a ranked list of what is currently costing you revenue.

02

Architecture & Wireframes

Sitemap, template inventory and grey-box wireframes for every page type. Signed off before a single pixel gets designed.

03

Design System

Figma component library, type scale and every awkward state: empty cart, sold out, pre-order, bundle, back-in-stock, subscription upsell.

04

Build & QA

Liquid development in a dev store, tested on real devices and against your live app stack. Accessibility checked to WCAG 2.1 AA.

05

Launch & Measure

Redirect map, tracking validation, DNS cutover on a low-traffic window. Then 30 days of monitoring against the pre-launch baseline.

Proof

Design & Build results

Anonymised under NDA. Figures pulled from the client’s own analytics.

Performance Apparel (DTC)

~$6M/yr DTC, 900+ SKUs across size and colour variants, US · Shopify Plus

Returns ran at 31% and refund cost consumed the entire paid media margin. One size chart image served 40 different fits, and 62% of add-to-carts started on a collection page that never showed variant availability. The named constraint: no new product photography budget, so every fix had to come out of the existing asset library and the review corpus.

+29%sitewide conversion rate1.71% to 2.21%, five-month average
+14%average order value$84 to $96 once the threshold bar and cross-sell shipped
31% → 22%return ratenine-point drop, roughly $310k/yr in recovered margin
1.9x → 2.4xblended MERwith paid spend held flat throughout
Engagement Conversion-led rebuild + paid mediaTimeframe 5 months

Home Goods & Furniture

~$11M/yr, 2,300 SKUs, configurable upholstery, US · Shopify Plus + Hydrogen storefront (Oxygen)

Fabric, leg and size options turned 2,300 SKUs into more than 40,000 variant permutations, and the Liquid theme rendered a configurable PDP in 6.9 seconds on mobile. Collection filtering ran client-side, so 40% of shoppers left before the first product painted. The named constraint: the ERP stayed. It was the single source of truth for stock and lead times and was not up for replacement.

6.9s → 1.4smobile LCP75th-percentile field data on configurable PDPs
+64%CVR on configurable products0.44% to 0.72%. Sitewide conversion rate rose 23%
+52%organic sessionsserver-rendered facets made 1,900 filter combinations indexable for the first time
+$2.4Mincremental annualized revenuemonth-8 run rate vs. the pre-build baseline
Engagement Paid growth audit → headless buildTimeframe 8 months (6-week audit, 6-month build)
In their words

Clients on this work

AOV $58 → $79

“Full rebuild in 11 weeks, launched two days before Black Friday, which was an aggressive ask and probably a stupid one on my part. They pushed back hard on three homepage ideas I was attached to and were right about all three. AOV went from $58 to $79, mostly off the bundle builder they put on the product page.”

CEOHome fragrance brand, ~$6M/yr · Phoenix, AZ
Verified via Shopify Partner referral
FAQ

Design & Build in Zurich — your questions

No. ConversionEX operates from a single office in Albuquerque, New Mexico. We work with Swiss clients remotely and say so plainly rather than renting a Kreis 1 address to look local. What we do commit to is a fixed meeting window in your late afternoon and written updates waiting when you start your day.

Structurally, all at once. The expensive part is not the words, it is the theme architecture — translation keys, market routing, hreflang, per-market pricing. Retrofitting that into a live store means hunting hard-coded strings a previous developer left in section files across every template. Publishing the French storefront later is fine; building the store as if French will never exist is not.

It is a real concern for a Zurich brand sitting in Bahnhofstrasse windows or in specialist retail across Europe. The usual answer is separation rather than avoidance: your direct store carries configurations, engraving, limited runs, servicing and the full brand story, while stocked lines stay priced to protect the channel. Shopify handles this with market-level price lists and a B2B layer, so one admin serves both without a second store.

As a content and compliance question, not a badge. Swissness rules set real criteria for what may carry the claim, and they differ by product category, so the page has to describe what is actually made where instead of implying more. We build that into the product template as structured content in every language you publish, which also happens to convert better than a flag icon.

Eight to twelve weeks for most brands, from kickoff to live. A single-catalogue store with clean product data lands closer to eight. Add subscriptions, B2B, or a multi-market rollout and you are looking at fourteen to eighteen. We give you a dated Gantt in week one and update it weekly.

We build on Shopify's Dawn reference theme and replace the sections we need. That gives you Shopify's own performance and accessibility baseline plus a codebase that survives platform updates. Premium themes carry code you will never use and cannot safely delete.

That is the point. Every content block is a native theme section with a schema your merchandiser can configure in the theme editor. You get a written guide and recorded walkthroughs. If you still need us for a homepage change, we built it wrong.
Next step

Design & Build for your Zurich brand.

Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.

Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead

Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.