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 engineering in the city where headless was invented — including the part where we tell you not to go headless.
Delivered remotely for brands across San Francisco and California.
This is a strange market to sell Shopify Plus into, because half the founders here have friends who build headless commerce for a living and have already been told, socially and confidently, that Liquid is legacy. So the conversation starts further along than it does elsewhere. Our position is unpopular and consistent: for a brand between one and ten million a year with no in-house front-end team, a well-built theme on Plus outperforms a decoupled stack on every measure that matters, including speed, because the decoupled stack degrades the moment nobody is paid to maintain it.
What Plus is genuinely for here is logic that a stack of apps handles badly. Wine club tiers with allocation releases, volume and case pricing, member-only pricing, bundle discounts that survive a promotion, delivery method rules that hide options a licensed shipper cannot legally offer to a given state — all of that belongs in Shopify Functions, running server-side, instead of in three overlapping subscriptions that fight each other at checkout. Age verification, deposit collection and staged payments for a hardware pre-order belong in checkout UI extensions.
B2B is the quieter half. A specialty food brand that started at a Ferry Building stall and now supplies grocery and cafés across Northern California is running two businesses out of one catalogue: consumer units online and case packs on terms. B2B on Shopify gives those accounts their own price lists, quantity rules, payment terms and self-serve reordering without a second platform, a second inventory truth or a rep re-keying purchase orders from email into the admin.
In most cities the question is whether a custom feature is affordable. Here it is whether the team should just write it themselves over a sprint, and often they genuinely could. That makes the honest scoping conversation different: we are not defending a budget, we are arguing about maintenance cost over three years and about who owns the thing after the engineer who wrote it leaves for a Series B. We will happily hand a Function or a checkout extension to your own developer and review the pull request instead of building it, and we will tell you when a Shopify app you already pay for does the job well enough that writing code for it is a hobby. What we will not do is quote a Hydrogen build because it makes for a better statement of work. If your content layer, product configurator or multi-locale front end genuinely justifies Hydrogen on Oxygen, we will say so and scope it properly — that case exists, it is just rarer than it is talked about at meetups in SoMa.
The same standard of work we run for every client — applied to a San Francisco 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 San Francisco 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.