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.
The Plus features that matter in Washington are the unglamorous ones: company accounts, purchase orders, net terms and tax exemption that survive procurement.
Delivered remotely for brands across Washington and District of Columbia.
In most cities the argument for Shopify Plus is checkout upsells and international expansion. In Washington it is usually procurement. A hospital system, a federal contractor's training department or a university library cannot buy from a normal checkout — they need a company account, a purchase order field, thirty-day terms and an exemption certificate applied at the account level rather than typed into a notes box and hoped for.
B2B on Plus does that natively. Company profiles with assigned buyers, price lists mapped to dues tiers or contract categories, quantity rules for bulk publication orders, and payment terms that a finance office recognises. The work that actually takes the time is not the configuration; it is agreeing who may open an account, who approves terms, and what happens when a department orders outside them. We write that workflow down before we build it.
Shopify Functions cover the logic that used to require three stacked apps: member versus non-member pricing computed server-side, bundled conference registrations plus merchandise, free shipping for a specific dues tier, order minimums for institutional accounts. Headless is a separate question and we will usually talk you out of it — for an association or museum shop, Hydrogen rarely repays its maintenance cost, and we say so before anyone signs anything.
Selling to Washington institutions means designing for their finance calendar, not yours. Budget authority concentrates before the federal fiscal year closes on 30 September, and a surprising amount of institutional purchasing across the region clusters against that date and against university and association year-ends. So the B2B build has to be ready before the window, not during it: company accounts provisioned, exemption certificates collected and attached, PO fields validated, credit terms agreed. There is also a tri-jurisdiction wrinkle unique to this metro — the same organisation may ship to DC, Maryland and Virginia addresses in a single order cycle, each with its own tax treatment and exemption handling, and getting that wrong produces invoices that a finance office bounces back weeks later.
The same standard of work we run for every client — applied to a Washington 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 Washington 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.