If You Build in Hydrogen, Do You Own Checkout Too?
Hydrogen storefronts do not own checkout, so the verdict is CUSTOMIZE: Shopify's migration docs route checkout to a subdomain, assigning checkout.example.com to checkout while the Hydrogen storefront serves example.com. Extend that checkout with checkout UI extensions and branding configuration, both Plus-gated on the core steps. Budget zero for building a checkout, and note the Checkout Blocks branding editor is removed on December 31, 2026.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's own Hydrogen migration documentation, re-read on 2026-09-05, states the routing directly: the primary domain receives traffic on the Hydrogen storefront while the checkout subdomain receives traffic at checkout, and the migration guide instructs you to assign checkout.example.com to checkout. Checkout is therefore hosted infrastructure on every plan, and a Hydrogen rebuild changes the storefront rather than the checkout. The customization surface is Plus-shaped and documented: checkout UI extensions that render on the information, shipping and payment steps are available only to stores on a Shopify Plus plan, thank-you and order-status extensions reach every plan except Shopify Starter, and Shopify's May 13, 2026 changelog states that Plus merchants can access more advanced surface-specific overrides through the Checkout and Accounts Configuration API. One dated item belongs in any plan starting now: the Checkout Blocks branding editor is Plus-only and is documented as deprecated, with removal on December 31, 2026. No App Store search applies here, because no app sells a merchant ownership of Shopify's checkout, and none was searched for beyond confirming the platform architecture.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · Liquid storefront moving to Hydrogen · agency or in-house React bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Non-Plus store going headless | CUSTOMIZE | Thank-you and order-status extensions serve every plan except Starter, and branding settings apply from the editor. The information, shipping and payment steps stay closed until Plus. |
| Plus store, presentation and content needs | CUSTOMIZE | Branding configuration and a handful of extensions cover the requirement. Writing code for something the checkout and accounts editor already sets is money spent on a settings screen. |
| Plus store with real checkout logic | BUILD | B2B rules, eligibility gating and payment or delivery conditions belong in checkout UI extensions and functions, versioned with the storefront rather than configured in a vendor dashboard. |
| A requirement to host checkout yourself | WAIT | Shopify sells no plan that hands over checkout, so there is nothing to buy and nothing to build. Re-examine the requirement before the architecture, because the answer is not a budget question. |
What Hydrogen Checkout Ownership Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Checkout conversion is the last and highest-leverage step, and Shopify's hosted checkout carries Shop Pay and accelerated wallets a self-hosted checkout would forfeit. |
| Customer experience | High | Checkout on a subdomain is a visible handoff, so type, wording and account pages have to match the Hydrogen storefront or shoppers register the seam. |
| Operational efficiency | High | Not building checkout removes the largest workstream a headless project could contain, along with PCI scope and payment-integration maintenance forever. |
| Data & insight | Medium | Checkout records stay in Shopify's model through the migration, so storefront analytics change and checkout reporting keeps its shape. |
| Retention & LTV | Low | Customer accounts and sign-in pages inherit the same branding configuration, which holds the returning-customer experience together at no extra cost. |
Spend ceiling: Checkout is not a line item in a Hydrogen budget, because it is not yours to build. Size the spend to extensions, branding configuration and the functions that carry real rules. Any proposal that prices a custom checkout on Shopify is pricing something the platform does not sell, on any plan.
What buying enables (top apps)
- + Checkout content and presentation changed without a release: custom fields, trust messaging, upsells and rule builders assembled in an editor
- + Branding applied through Shopify's own editor across checkout, customer accounts and sign-in pages at once
- + A shorter path for teams whose checkout requirement is copy and layout rather than business logic
What building additionally unlocks
- + Checkout UI extensions on the information, shipping and payment steps, which only Shopify Plus stores can render at all
- + Rules as code through validation, delivery customization and payment customization functions, versioned and tested rather than clicked into a dashboard
- + Surface-specific branding overrides through the Checkout and Accounts Configuration API, which Shopify limits to Plus merchants
- + One release process covering the Hydrogen storefront and its checkout extensions, so brand changes ship on both sides of the handoff together
Find Your Verdict in 3 Questions
Does the requirement call for a checkout you host and control end to end?
Yes: Your verdict: WAIT — Shopify sells no such option on any plan, so revisit the requirement before the architecture.
No: Go to question 2.
Do the changes you need sit on the information, shipping or payment steps?
Yes: Go to question 3.
No: Your verdict: CUSTOMIZE — thank-you and order-status extensions plus branding settings serve every plan except Shopify Starter.
Is the store on Shopify Plus?
Yes: Your verdict: CUSTOMIZE — build checkout UI extensions on the core steps and configure branding through the Plus-only overrides.
No: Your verdict: WAIT — those steps are Plus-only, so the plan decision comes before the build decision.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A checkout customization app configures in an afternoon; extensions and functions are code, review and a release tied to the storefront. | ||
| Recurring fees | Checkout apps bill monthly for as long as checkout looks that way; extensions you write carry no subscription line at all. | ||
| Maintenance & upgrades | Checkout extensibility versions on a published cadence, and Shopify dates its removals: the Checkout Blocks branding editor goes on December 31, 2026. | ||
| Switching & exit | App-configured checkout changes leave with the vendor; extensions are your code and branding configuration stays inside Shopify. | ||
| Risk | |||
| Vendor risk | A checkout app sits on the highest-stakes surface in the store, which makes vendor stability a conversion issue rather than an inconvenience. | ||
| Security & compliance surface | Neither lane touches card data, because checkout stays Shopify's; the platform carries Level 1 PCI DSS and SOC2 certification. | ||
| Platform-deprecation exposure | Checkout extensibility moves and moves with dates, so the maintenance calendar is published rather than a surprise. | ||
| Value | |||
| Fit to requirement | Apps deliver the changes their editor anticipated; extensions and functions express rules that come from your business, not from a settings list. | ||
| Time to market | Configuration ships this week; extensions ship with the storefront release train, which is the right cadence but a slower one. | ||
| Performance & scale | Checkout runs on Shopify's infrastructure in both lanes, under a 99.99% uptime SLA on the Plus plan. | ||
| Data ownership & AI-readiness | Checkout records stay in Shopify either way; what differs is whether custom field definitions live in your code or in a vendor's dashboard. | ||
| Focus & opportunity cost | Checkout work is small beside a Hydrogen storefront rebuild, so the risk is over-investing here while the storefront slips. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify's hosted checkout on a Hydrogen storefront | Native — First-party Shopify, and mandatory. Shopify's migration documentation states that the primary domain receives traffic on the Hydrogen storefront while the checkout subdomain receives traffic at checkout, and instructs merchants to assign checkout.example.com to checkout. Shared carts require the same products published to both the Online Store channel and the Hydrogen storefront. Checkout inherits Shopify's Level 1 PCI DSS and SOC2 posture and, on Plus, a 99.99% uptime SLA (verified Sep 2026). | Included on every Shopify plan (verified Sep 2026) | Every storefront on Shopify, headless or not, because there is no alternative |
| Checkout UI extensions and branding configuration | Native — First-party customization surface, and the same surface whether the storefront is Liquid or Hydrogen. Checkout UI extensions on the information, shipping and payment steps are available only to Shopify Plus stores; thank-you and order-status extensions reach every plan except Shopify Starter. Branding settings apply across checkout, customer accounts and sign-in pages from one editor, with Plus-only surface-specific overrides through the Checkout and Accounts Configuration API. The Checkout Blocks branding editor is Plus-only and is removed on December 31, 2026, so plan a destination for anything configured there (verified Sep 2026). | Included with your plan; the Plus-only surfaces require Shopify Plus (verified Sep 2026) | Plus merchants who need the core checkout steps, which nothing else reaches |
| Checkout customization apps | Category — The Checkout category's 24 listings sell terms checkboxes, checkout rules, upsells, cart-drawer upsells and payment-method hide or sort tools. None does pixel-level visual or branding customization, checked 2026-09-05. Buying here buys rules, not styling. | Varies by listing (illustrative); none of it buys branding control | Merchandisers who need checkout content changed without a release |
| Custom checkout extensions and functions (custom app) | Build lane — Your own checkout UI extensions on the core steps, plus validation, delivery customization and payment customization functions for the rules behind them. Custom apps containing Shopify Function APIs are Plus-only, and the core-step extensions are Plus-only as well, so this lane is Plus twice over. It buys you checkout behavior, never checkout hosting. | $10,000–$30,000 one-time plus upkeep (Deploi estimate, illustrative) | Plus merchants whose checkout carries business rules rather than copy changes |
The Build Path
- Route checkout to the subdomain and prove it before launch: Shopify's migration guide is specific: if your Hydrogen store is example.com, assign checkout.example.com to checkout. Publish the same products to both the Online Store channel and the Hydrogen storefront so shared carts work, set redirects for every customized route, and update feed rules to the Hydrogen domain. Test the handoff on a real device before anyone sees it.
- Close the seam between storefront and checkout: Branding settings now apply consistently across checkout, customer accounts and sign-in pages from the checkout and accounts editor, and Plus merchants reach more advanced surface-specific overrides through the Checkout and Accounts Configuration API. Match type, spacing and wording, not just color. Shoppers notice the domain change less than they notice a different voice.
- Put rules in functions, not in the storefront: Cart and checkout validation, delivery customization and payment customization functions run inside checkout, where your Hydrogen code cannot reach. Custom apps containing Shopify Function APIs are Plus-only. A rule enforced in React and not in a function is a rule a determined shopper can skip.
- Plan the Checkout Blocks branding editor migration: The Checkout Blocks branding editor is available only to Shopify Plus merchants and is documented as deprecated, with removal on December 31, 2026. Anything configured there needs a destination inside the checkout and accounts editor or the Configuration API, and that date sits inside the planning horizon of a Hydrogen project starting now.
- Effort band
- $10,000–$30,000 for checkout extensions, branding configuration and one function — Deploi estimate (illustrative); lands in the $25–75K contact-form band
- Typical timeline
- 3–7 weeks running alongside the storefront build (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,500–$6,000/yr (Deploi estimate, illustrative) for checkout API version bumps, extension upkeep and the removals Shopify dates in advance.
- What you own — and what you take on
- You own: the extensions, the branding configuration, the checkout functions and the release process that ships them with the storefront. You take on: a Plus dependency for the core checkout steps, and a deprecation calendar somebody has to read every quarter.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$2,500 | $10,000–$30,000 |
| Years 1–3 (recurring) | $1,800–$10,800 (app subscriptions) | $4,500–$18,000 (maintenance) |
| 3-year total | ≈$1,800–$13,300 | ≈$14,500–$48,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Left column is one or two checkout customization apps at typical tiers, held flat; neither column buys checkout hosting, because no plan offers it.
- † Right column is custom checkout UI extensions, branding configuration and one checkout function, built alongside the storefront; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Checkout customization apps configure Shopify's checkout and none of them sells ownership of it, whatever a comparison page implies
- — The Checkout Blocks branding editor is Plus-only and is removed on December 31, 2026, so anything configured there needs a destination first
- — Extensions on the information, shipping and payment steps are Plus-only, so a non-Plus store can buy an app that cannot reach the step it needs
- — Checkout configuration held in a vendor dashboard leaves with the vendor, on the one surface nobody wants to rebuild in a hurry
On the build path
- — Checkout extensibility is versioned and its removals are dated, so this maintenance is scheduled work rather than an occasional surprise
- — Custom apps containing Shopify Function APIs are Plus-only, so checkout rules as code quietly assume a plan you keep paying for
- — The storefront hands off to a checkout subdomain, so brand seams appear in wording and account pages, not only in colors
- — ~$1,500–$6,000/yr upkeep (Deploi estimate, illustrative)
What Merchants Say
Teams describe the headless pitch and the checkout reality arriving in the same week: full control of the storefront, and a checkout that still runs on Shopify's own subdomain.
The recurring complaint after a headless launch is the seam rather than the checkout itself: type, wording and account pages that stop matching the storefront the moment a shopper clicks buy.
If You Change Your Mind Later
If you bought and outgrow it
Removing a checkout customization app reverts checkout to its configured defaults, and the settings that lived in the vendor's dashboard go with it. Record custom field definitions and screenshots before you uninstall, because checkout is the surface nobody wants to reconstruct under time pressure.
If you built and want out
Checkout extensions are your code and branding configuration is stored inside Shopify, so a storefront change strands nothing. Moving from Hydrogen back to a Liquid theme keeps every extension and every branding setting, because the checkout surface never depended on which framework rendered the storefront.
When This Answer Changes
We're watching for:
- ▸ December 31, 2026, when the Checkout Blocks branding editor is removed, a date inside the planning horizon of any Hydrogen project starting now
- ▸ Shopify opening checkout UI extensions on the information, shipping and payment steps below Plus, which would change the plan calculus for headless merchants
- ▸ Any change to the checkout subdomain routing model, which is what makes checkout a handoff rather than a route in your own application
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Does a Hydrogen storefront include its own checkout?
No. Shopify's migration documentation routes checkout to a subdomain: the primary domain serves the Hydrogen storefront while checkout.example.com receives traffic at checkout. Checkout stays Shopify's hosted checkout on every plan, Shopify Plus included. Shopify's platform carries Level 1 PCI DSS and SOC2 certification and a 99.99% uptime SLA on Plus, which the hosted checkout inherits.
What can we actually customize in checkout on Plus?
Checkout UI extensions that render on the information, shipping and payment steps are available only to stores on a Shopify Plus plan. Thank-you and order-status extensions reach every plan except Shopify Starter. Branding settings apply across checkout, customer accounts and sign-in pages from one editor, and Plus adds surface-specific overrides through the Checkout and Accounts Configuration API, per Shopify's May 13, 2026 changelog.
How much should a Hydrogen project budget for checkout?
Budget $10,000–$30,000 for checkout extensions, branding configuration and one function, plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative). Budget nothing for building a checkout, because no Shopify plan sells one. Add a line for migrating anything configured in the Checkout Blocks branding editor, which is Plus-only and is removed on December 31, 2026.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Delete any checkout-build line from the Hydrogen estimate, because checkout is not available to build on Shopify
- Assign the checkout subdomain early and test the handoff on a real device, not only in a preview environment
- Publish products to both the Online Store channel and the Hydrogen storefront so shared carts behave
- Match branding across checkout, customer accounts and sign-in pages from the checkout and accounts editor
- Audit anything configured in the Checkout Blocks branding editor and schedule its migration before December 31, 2026
If you're going with BUILD
- List the checkout rules that must be enforced, then assign each to a validation, delivery or payment customization function
- Confirm Plus, since core-step extensions and custom function apps both require it
- Ship checkout extensions on the storefront release train so brand changes land together
- Test every extension against the thank-you and order-status surfaces, which behave differently from the core steps
- Diary the checkout API version bump each quarter rather than discovering it during a peak week
Official Docs & Sources
- Redirect traffic to a Hydrogen storefront — shopify.dev
- Migrate to Hydrogen — shopify.dev
- Checkout UI extensions — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy Observability for Checkout Functions on Shopify?
Shopify documents 12 function error types and stores each run in the Dev Dashboard, but no default alert tells you a checkout function has started failing.
Do Customer Accounts Follow Shoppers Across Plus Stores?
Each Plus store keeps its own customer records, so accounts don't follow shoppers between stores. Multipass rides legacy accounts Shopify deprecated.
Should You Build or Buy Cross-Store Staff Access on Plus?
Custom organization-level roles give one staff login reach across a Plus organization. No app grants staff access across stores; below Plus, every store is separate.
Customer Account API vs. a Custom Login System on Headless?
Shopify's Customer Account API authenticates buyers on headless. A custom login build costs six figures, and legacy accounts are deprecated since February 2026.
Build or Buy Performance Monitoring & App Audits on Shopify?
Measurement is free on Shopify; storefront speed comes from an audit-and-remediation program, not a speed app.
Scoping a Hydrogen build with checkout in the estimate?
We take checkout hosting out of the budget where it never belonged, then scope the part that is real: extensions on the core steps, branding that closes the seam, and the rules that have to live in functions.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.