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.
Markets, B2B and checkout engineering for Danish brands running several countries and a wholesale book out of one admin.
Delivered remotely for brands across Copenhagen and Denmark.
Danish brands reach the limits of a standard Shopify setup earlier than their revenue suggests, because they are multi-country and multi-channel from the beginning. A studio doing a few million kroner direct can easily be selling in DKK, EUR and SEK, invoicing wholesale accounts in three countries, and shipping goods that need freight rather than a parcel rate. That is a Plus-shaped problem long before it is a Plus-shaped turnover.
Markets is the centre of the work. Per-country price lists let you fix clean euro price points and leave them alone — the krone's peg to the euro means you are not chasing a moving rate — while Sweden and Norway get their own currencies, their own payment methods and their own delivery promises. One admin, one inventory, one catalogue, with the differences expressed as configuration instead of as three copies of your store drifting apart.
Then the parts most Plus accounts never switch on. Shopify Functions can express the rules a Danish goods business actually runs on: freight bands by dimensional weight, surcharges for island and non-mainland delivery, a different shipping method above a certain volume, wholesale tiers, and delivery options that only appear for products in stock. Checkout extensions add the things buyers here look for at the last step — parcel shop choice, stated delivery week for made-to-order items, gift options. Headless is a separate conversation, and in most Copenhagen cases we will argue against it.
The Copenhagen pattern is a brand built through stockists, fairs and press, with a direct channel added later. That inverts the usual Plus scope: B2B on Shopify is often the higher-value half of the build, not the extension. What it has to handle is specific — company profiles for dealers across Denmark, Germany, Sweden and the Netherlands; price lists per account and per currency; minimum order values and case quantities; net payment terms; and a self-serve reorder portal so a shop in Hamburg can place a repeat order at nine in the evening without emailing a PDF to someone in Nordhavn. Getting that onto the same catalogue and inventory as the DTC store is what stops the classic Danish situation where the webshop shows stock the wholesale team has already committed. We scope which side of your business carries the weight in the first workshop, because a wholesale-first Plus build and a DTC-first one share very little beyond the platform name.
The same standard of work we run for every client — applied to a Copenhagen 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 Copenhagen 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.