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 London brands running one admin across the UK, the EU and a wholesale book that predates the website.
Delivered remotely for brands across London and United Kingdom.
Most London brands arrive at Plus for one of two reasons, and they are rarely the reason on the sales deck. Either the EU has become complicated enough that running markets, currencies and duty rules through apps has stopped scaling, or a wholesale business that has existed since a stand at Pure London or Top Drawer is still being run on emailed order forms and a spreadsheet of trade prices. Both are Plus problems. Neither is a theme problem.
Markets is the first lever. Per-country catalogues so a product you cannot legally sell in one EU state simply is not there, price lists set locally rather than converted, domain or subfolder routing with hreflang that agrees with itself, and duty collection configured so a Milan customer is never handed a bill by a courier. Checkout extensibility is the second: delivery-choice content, a clear duty-paid statement, gifting and post-purchase upsells built as native extensions rather than the checkout.liquid edits that used to hold this together.
B2B on Shopify is where the London wholesale story gets interesting. Company profiles with multiple buyers, price lists per account, payment terms, minimum quantities and a self-serve reorder portal — running on the same catalogue and the same stock pool as your DTC store, which is the whole point. And Hydrogen: we build it when there is a genuine content or performance case, and we tell you plainly when your problem is a 900KB hero image and four apps rather than an architecture.
For a London brand the Plus features that pay for themselves are almost never the ones demoed. They are Markets configured per EU country with correct VAT treatment and duty collection, Functions writing your own delivery and discount logic instead of stacking three apps that each want a subscription, and B2B replacing a wholesale portal that was bolted on when the trade side outgrew email. We also design for the post-Brexit reality that your commercial data has to support the claim you make at the border: commodity codes and origin held as structured metafields, flowing into the customs paperwork rather than being retyped by whoever is packing that day. The delivery rhythm accounts for the seven-hour gap — technical decisions get written down as a documented native-versus-custom call you can read at 9am UK, and the live discussion happens in the late-afternoon overlap.
The same standard of work we run for every client — applied to a London 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 London 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.