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-tier work for Baltimore suppliers whose biggest orders still arrive as a phone call, an email attachment or a fax.
Delivered remotely for brands across Baltimore and Maryland.
The Plus conversation in this city almost never starts with headless. It starts with a supplier around the port — riggings, safety gear, fittings, packaging, lab consumables — realising that the two people who spend their week keying in phone and email orders are the most expensive part of the operation. Everything those two people do is a Shopify B2B feature: company profiles with multiple named buyers, a price list per account, net payment terms, quantity rules that reflect case packs rather than consumer units, and a reorder history the customer works from themselves.
Baltimore adds a second layer that most B2B builds elsewhere skip. Johns Hopkins, the bioparks and the hospital systems buy the way institutions buy: a formal quotation, then a purchase order raised against it, then tax-exempt treatment applied correctly, then an invoice their finance system will accept. A store that cannot produce a quote a procurement officer can attach to a requisition is not competing for that business at all. We build quote-to-order on top of native B2B so the institutional path is first-class rather than a contact form with a promise attached.
Then there is the physical reality of what moves through here. Ro-ro cargo, machinery and equipment mean parts that ship by pallet and freight, not by parcel, and a checkout that quotes a flat rate on a 400-pound item is losing money on every order. Shopify Functions handle it natively: shipping methods that switch to freight above a weight or dimension threshold, delivery logic tied to packing days for perishables, volume tiers computed server-side instead of stacked across three subscription apps. Headless comes up occasionally and we usually argue against it — a Liquid theme with clean Functions beats a Hydrogen build nobody on your team can maintain.
Baltimore's advantage is inland reach — the port sits further west than any other major East Coast harbour, which is why so much machinery, vehicle and equipment trade routes through here and why the local supply base of forwarders, brokers, riggers and dealers is unusually deep. Those businesses share a profile: high order values, repeat accounts, freight logistics, and almost no consumer-style browsing behaviour. That makes the Plus scope predictable. Company accounts and contract pricing come first, then Functions for freight and quantity logic, then checkout extensions for PO reference fields, delivery instructions and dock or liftgate requirements that currently arrive as a note someone has to read. Shopify Markets rarely leads the scope here the way it does in a border city, though the DC corridor forty miles south often justifies a separate delivery and pickup market. We decide all of that in technical discovery, because paying the Plus fee for capability you never switch on is the most common waste we find in this region.
The same standard of work we run for every client — applied to a Baltimore 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 Baltimore 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.