Custom Shopify theme development

Feel Reformed's store had been built in rounds, and every round left something behind. I rebuilt it from scratch on Horizon, Shopify's own theme. Mobile load time went from 8 seconds to 2, the app count from 54 to 12, and a new campaign page now takes the team 2 hours where it used to take 2 days.

A bespoke build isn't always the right answer. For a brand launching with a straightforward catalogue and no unusual requirements, a good bought theme is a sensible choice. It stops being sensible when the design is genuinely bespoke, when speed matters commercially, or when your team needs to build pages without asking a developer every time.

What a bespoke theme gets you

Only the code you use. A bought theme carries every feature every customer might want, and loads most of it. A theme built for one brand carries what that brand needs. That's where most of the speed difference comes from, and why it lasts as features get added.

Sections your team can actually use. The real value of a custom build shows six months after launch, when a marketer builds a campaign page from existing sections, without a developer, and it still looks right. That means designing the section library around what your team will really do, which is a different job from recreating the design.

Logic in the right place. Custom pricing, bundles and cart rules built as Shopify Functions, so they hold up when a campaign trebles traffic.

Accessible from the start. Proper markup, keyboard support and focus handling built into every section. Adding accessibility to a finished theme costs several times what building it in does.

Horizon and what it changes

Shopify's newer theme architecture is built around theme blocks, which can nest and be reordered inside sections. Building on it, or on a Horizon-based foundation, keeps the section library small: one hero section that accepts blocks does the job of six near-identical variants.

For an editor, that means building exactly the thing they had in mind from a short list of sections. For a developer, it's far less code to maintain.

It isn't the right base for every project. A brand with heavily art-directed pages and only a few templates may be better served by a leaner bespoke build, so I decide it per project.

Speed

Speed decided at the start is architecture. Speed added at the end is decoration.

What actually moves it: what loads before the page appears and what waits, how many third-party scripts the marketing stack has collected and which of them block the page, whether the theme sizes and formats images properly, and how much JavaScript ships for things that could work without it.

On most Plus stores the biggest wins sit in the apps. A well-built theme loaded with eleven scripts, each adding a third of a second, is a fast theme having a bad time. Part of building a custom theme is telling you plainly which apps are worth their weight.

How long it takes

A bespoke build from a finished design, with a normal catalogue and a standard checkout, takes 4 to 6 weeks. One with a product configurator, B2B pricing or a complex integration takes 8 to 10. The biggest factor is the design being finished before development starts, and it's the one most often optimistic.

If you're not sure whether to rebuild or fix what you have, the Shopify Plus audit will tell you, or book a call.