Checkout Extensibility Build
Checkout UI extensions for trust content, delivery choice, gifting and post-purchase upsell. Native, upgrade-safe, and no longer dependent on checkout.liquid.
Plus builds for Swiss brands running several currencies, a European wholesale book and a checkout that has to explain a customs border.
Delivered remotely for brands across Zurich and Switzerland.
What makes the Plus case in Zurich is almost never traffic volume. It is complexity. A watch or precision-homeware brand here typically sells direct in Switzerland, direct into the EU and UK, and wholesale to stockists in four countries, with different prices, different tax treatment and different delivery promises in each. That is three businesses sharing one catalogue, and it is exactly the shape Markets, B2B and Functions were built for.
Checkout is where the border becomes a design problem. A Swiss store shipping to Munich has to make a decision visible: are duties and import VAT settled now, or does a courier collect them at the door. Checkout UI extensions let you say that in the customer's own language at the moment it matters, alongside delivery choice, gift options and the deposit or part-payment flows that high-order-value categories need. Functions carry the logic underneath — market-specific shipping rules, wholesale volume tiers, payment methods hidden or shown by market — server-side, instead of stacked apps arguing with each other.
Headless comes up often and deserves an honest answer. For most Zurich brands the constraint is not storefront rendering speed, it is catalogue depth in three languages and a wholesale portal that still runs on email. Hydrogen is worth building when the content model is genuinely large or when a configurator sits at the centre of the buying experience. When it is not, we say so, and we spend the same budget on Markets, B2B and checkout, where it will actually move revenue.
Running Switzerland and the EU from one store means holding two commercial realities at once. Domestic orders settle in Swiss francs with TWINT and invoice payment normal, and delivery judged against Swiss Post standards. EU orders settle in euros at prices you set rather than convert, carry the fourteen-day withdrawal right that Swiss law does not impose domestically, and need IOSS handling for low-value consignments so VAT is collected at your checkout rather than by a courier. Markets is what stops that becoming two stores; Functions and checkout extensions are what stop it becoming twelve apps. On the wholesale side, a stockist in Vienna or Lyon reordering by PDF is not a small inefficiency for a Zurich brand — it is where the margin is, and B2B on Shopify gives them company-level price lists, payment terms and self-serve reordering against the same inventory your direct customers are buying from.
The same standard of work we run for every client — applied to a Zurich brand’s realities.
Full service detailCheckout UI extensions for trust content, delivery choice, gifting and post-purchase upsell. Native, upgrade-safe, and no longer dependent on checkout.liquid.
Custom discount, delivery and payment-method logic written as Functions. Volume tiers, bundle pricing and B2B rules run server-side instead of via three stacked apps.
Company profiles, price lists, payment terms, quantity rules and a self-serve reorder portal. Wholesale and DTC on one catalogue, one inventory, one admin.
Multi-currency, multi-language, market-specific catalogues, domain routing and correct hreflang. Expansion without a store-per-country sprawl.
Hydrogen on Oxygen with the Storefront API, edge caching and streaming SSR. We build this only when the performance or content case is real, and we say so when it isn't.
NetSuite, Business Central, Akeneo or a 3PL wired in through a documented middleware layer with retry logic, error alerting and a reconciliation report.
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 scopedWe map your systems, order flows and edge cases end to end, then document where data breaks today. Output is an architecture diagram you can hand to any engineer.
Native-versus-custom decision for every requirement, with cost and maintenance load attached. Plenty of requests get answered with a $0 native setting.
Two-week sprints in a dev store with a staged demo at the end of each. You see working software every fortnight, not a status deck.
Peak-traffic simulation, payment-failure paths, partial-sync recovery and a rollback plan. We break it in staging so BFCM doesn't break it live.
Phased rollout, monitoring dashboards and training for ops and finance. Every custom component ships with a README and a named owner.
Anonymised under NDA. Figures pulled from the client’s own analytics.
~$4.2M/yr, 60% subscription revenue, 22 SKUs, US · Shopify Plus (Recharge, Klaviyo)
Monthly subscription churn hit 9.4% and the cancel flow was a single button on a hosted page nobody had touched in three years. Support processed 340 subscription changes a month by hand because customers could not do it themselves. The named constraint: no forced logins. The brand refused to gate account access behind a password reset, which ruled out every off-the-shelf portal.
~$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.
“We sell wholesale into about 400 accounts and were still taking reorders by email like it was 2009. They built the B2B catalog on Shopify with net-30 terms and per-account price lists, and moved our whole rep team onto it in one week. Average reorder went from roughly 20 minutes of back-and-forth to under three.”
“A Hydrogen build plus a NetSuite sync that our own team had failed at twice. Inventory finally matches between the warehouse and the storefront, which sounds boring and is the most valuable thing anyone has done for us this year. LCP went from 4.1s to 1.3s. The honest part: the first six weeks felt slow and I genuinely wasn't sure we'd picked right — it only clicked once we moved to a standing Thursday call with the engineers instead of account-manager summaries.”
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.
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.