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.
Berlin
Shopify Plus & Headless Commerce in Berlin
Plus-tier engineering for Berlin brands running dealers, distributors and three DACH markets out of one catalogue.
Delivered remotely for brands across Berlin and Germany.
Scale · Berlin
Why Berlin brands come to us for this
- Native B2B company profiles and price lists so dealer pricing lives behind the same catalogue your consumers see
- VAT ID validated at the B2B checkout and stored on the company record, so reverse-charge invoicing is defensible rather than assumed
- Net payment terms for German and Austrian trade accounts, replacing the invoice-by-email workflow that eats your ops week
- Checkout UI extensions for delivery choice and invoice-payment context, built to survive Shopify upgrades instead of blocking them
- Shopify Functions for volume tiers, fleet pricing and bundle logic that a flat price list cannot express
Berlin's export categories reach a wall that has nothing to do with the storefront. A synth manufacturer with two hundred dealers across Europe, a cargo-bike builder selling to fleet operators and shops, a hobby publisher allocating a print run across distributors — all of them end up running wholesale on a price list PDF, an email inbox and a spreadsheet of net terms. Shopify's native B2B handles most of that on the same catalogue and the same inventory, which removes an entire parallel system rather than digitising it.
The German-specific part is what happens at the B2B checkout. Intra-EU business buyers expect to give a VAT identification number and be invoiced without VAT under reverse charge, which means the number has to be validated rather than trusted, stored against the company record, and reflected correctly on the invoice. Domestic dealers expect net payment terms, not a card form. Both are solvable natively with company profiles, price lists and payment terms, with Functions covering the pricing rules that lists alone cannot express.
Checkout extensibility earns its keep here too. The German consumer checkout has content obligations and a payment mix that a stock checkout does not present well, and checkout UI extensions let you place delivery choice, invoice-payment context and withdrawal information natively — upgrade-safe, rather than in the checkout.liquid that Shopify has already retired. Headless is a smaller conversation than the vendors suggest: worth it when you are running a heavy editorial layer or a genuine product configurator, and not worth it because a competitor announced Hydrogen on LinkedIn.
Local context
Markets, not stores, for Germany, Austria and Switzerland
The default instinct when a Berlin brand expands is another store — a .at domain, a .ch domain, three themes and three sets of redirects to maintain. Shopify Markets makes that unnecessary and, in a DACH context, actively harmful, because the three markets differ in tax treatment rather than in catalogue. Germany and Austria both sit inside EU VAT, so once cross-border consumer sales pass the EU-wide threshold you are charging destination rates and filing through the One Stop Shop, which is a tax-configuration problem, not a storefront problem. Switzerland is an export market with customs at the border, Swiss VAT once you cross the local registration threshold, francs on the price tag and a decision about delivering duty-paid. We build all three as markets against one admin, one inventory pool and one theme: per-market pricing and rounding, market-specific payment methods, duties handling for the Swiss lane, and hreflang that keeps de-AT and de-CH from cannibalising de-DE in search. The filing itself stays with your Steuerberater — we make sure the store produces data they can actually work from.
Scope
What Plus & Headless includes
The same standard of work we run for every client — applied to a Berlin brand’s realities.
Full service detailShopify Functions
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.
B2B on Shopify
Company profiles, price lists, payment terms, quantity rules and a self-serve reorder portal. Wholesale and DTC on one catalogue, one inventory, one admin.
Shopify Markets & Localisation
Multi-currency, multi-language, market-specific catalogues, domain routing and correct hreflang. Expansion without a store-per-country sprawl.
Headless Hydrogen Storefront
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.
ERP, PIM & 3PL Integration
NetSuite, Business Central, Akeneo or a 3PL wired in through a documented middleware layer with retry logic, error alerting and a reconciliation report.
Scoped and quoted for your Berlin store
We do not work off a rate card. Every Berlin 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 scopedHow it runs
From kickoff to results
Technical Discovery
We 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.
Solution Design
Native-versus-custom decision for every requirement, with cost and maintenance load attached. Plenty of requests get answered with a $0 native setting.
Build in Sprints
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.
Load & Failure Testing
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.
Launch & Enablement
Phased rollout, monitoring dashboards and training for ops and finance. Every custom component ships with a README and a named owner.
Proof
Plus & Headless results
Anonymised under NDA. Figures pulled from the client’s own analytics.
Supplements (Subscription DTC)
~$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.
9.4% → 6.1%monthly subscription churnheld for five consecutive months, not a single-month dip
+34%12-month customer LTV$187 to $251 on the subscriber cohort
19% → 38%of revenue from email + SMScategory benchmark for a healthy program is 25-40%
-71%subscription support tickets340/mo to 98/mo after the self-serve portal launched
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
In their words
Clients on this work
Reorder time 20 min → 3 min
“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.”
Director of WholesaleFood & beverage brand, ~$22M/yr · Dallas, TX
Verified client, 2025LCP 4.1s → 1.3s
“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.”
CTOJewelry brand, ~$18M/yr · New York, NY
Verified client, 2026FAQ
Plus & Headless in Berlin — your questions
For most Berlin brands, yes. Company accounts with per-company price lists, quantity rules, net terms and a self-serve reorder portal covers the majority of what a dealer relationship actually needs. Where it strains is bespoke contract pricing and formal quoting workflows, which we cover with Functions or a light custom app rather than a second platform. The bigger win is usually killing the parallel wholesale system entirely.
The VAT identification number gets collected against the company profile and validated rather than accepted at face value, and tax treatment follows from the validated record rather than a checkbox the buyer ticked. That gives your accountant a record they can defend if the number is ever questioned. Getting this wrong is expensive in a way that only surfaces at audit, which is why we treat it as a data problem rather than a checkout convenience.
No — a Swiss market, configured deliberately. Switzerland needs Swiss francs with sensible price rounding, customs documentation, its own shipping rules and a decision on delivered-duty-paid, but none of that requires a second catalogue or a second theme. Splitting it into its own store doubles your maintenance and your redirect surface for a difference that Markets already models properly.
Usually not, and we would rather say so early. A well-built Liquid theme reaches the performance ceiling that matters, and headless adds a front-end you now have to staff. The cases where it genuinely earns its cost in this city are a real product configurator — cargo-bike builds, modular studio setups — or a content operation heavy enough that the CMS should own the front end. If your reason is speed alone, we will show you the cheaper path first.
Usually not. A well-built Liquid theme hits sub-2s LCP and costs a fraction to run. Headless earns its keep when you need a custom front-end framework, a heavy CMS-driven content layer, or interactive product configuration Liquid cannot serve. We will talk you out of it if the numbers don't hold.
No. Shopify has retired it in favour of checkout extensibility, and anything still running on it is on borrowed time. We migrate custom checkout logic into checkout UI extensions and Functions, which survive platform upgrades instead of blocking them.
For most mid-market brands, yes. Company accounts, per-company price lists, net payment terms and quantity rules cover the majority of wholesale workflows natively. Where it falls short is complex quoting and contract pricing, which we handle with Functions or a light custom app.
Next step
Plus & Headless for your Berlin 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.