# Headless Shopify modernisation: upgrade, rebuild or return to a theme.

> We modernise older headless Shopify storefronts built on early Hydrogen, Gatsby, custom React or early Next.js. We keep the routes and design where they work and replace the commerce layer, or move the store back to a Shopify theme when headless no longer pays. It starts with a fixed-fee Readiness Assessment.

Headless commerce · Headless modernisation

- **Starts with:** A fixed-fee Readiness Assessment
- **Typical build:** Upgrade, rebuild or theme, phased and priced first
- **You own:** The code, the redirects and the documentation

## When does a headless storefront need modernising?
- Dependencies can’t be upgraded without breaking the build.
- The storefront still calls Storefront API features Shopify has deprecated.
- Builds are slow enough that catalog changes wait to go live.
- The engineers who built it have left, and nobody wants to touch it.
- The storefront costs more to run than the experience earns.

## How does a headless modernisation run?
1. **Assess** — Code, dependencies, API versions and apps reviewed; each path costed.
2. **Map the URLs** — Every route, redirect and canonical recorded before anything changes.
3. **Rebuild what must change** — Commerce on current Shopify APIs, or a theme, with checkout native.
4. **Launch in steps** — Templates moved in slices where possible, with a pre-launch crawl and rollback plan.
5. **Keep it current** — Shopify API and dependency upgrades scheduled, by your team or ours.

## A storefront on current foundations.
- A recommendation: upgrade, rebuild or return to a theme
- A dependency and API version audit
- A URL map with every redirect tested
- The commerce layer on current Shopify APIs
- Or a Shopify theme carrying the existing design
- Crawl and Search Console checks before and after launch
- Upgrade notes your next team can follow

## What usually goes wrong
- **Rebuilding when an upgrade would do.** — We cost the upgrade before recommending a rebuild.
- **Changing URLs without a redirect map.** — Every route is mapped and tested before launch.
- **Staying headless out of sunk cost.** — A theme is costed as a real option.
- **Redesigning and replatforming in one move.** — A stable design makes any ranking change traceable.

## Questions
### Should we upgrade or rebuild?

Upgrade when the structure is sound and the gap is mostly dependencies and API versions. Rebuild when upgrading would touch most of the code anyway. The assessment costs both over two years before you choose.

### Can we move from headless back to a Shopify theme?

Yes. When the experience no longer needs headless, a custom theme can carry the design, return the theme editor to marketers and bring theme apps back. Every URL is mapped and redirected to protect search rankings.

### How do we keep search rankings during the change?

Every URL is recorded and mapped before work starts, redirects are tested, and structured data and canonicals are rebuilt. We crawl before and after launch and watch Search Console. Keeping the design stable makes any movement easier to trace.

### We’re on Gatsby. What are our options?

Usually a rebuild on Next.js with Shopify’s Hydrogen library, or on Hydrogen itself, keeping your routes and design. If the experience no longer needs headless, a Shopify theme. The assessment compares each path with a two-year cost.

### Can we upgrade an older Hydrogen storefront in place?

Often, if it already follows a recent Hydrogen structure. The earliest Hydrogen releases worked differently from today’s, so those storefronts usually need a rebuild. The assessment tells you which you have before anything is priced.

[Request a Readiness Assessment](https://www.studioantipodes.com/start-a-project)