Skip to main content
| 7 min read | By Eyal Gantz, senior developer and fractional CTO, New York

Custom Shopify Theme Development: When a Stock Theme Is Not Enough

Shopify Theme Development Liquid

Custom Shopify theme development means writing the storefront's Liquid, CSS and JavaScript for one store, instead of installing a theme and adjusting its settings. It comes in three sizes: a stock theme that you configure, a stock theme with custom sections added, and a theme built for the business from a minimal base. Most stores need the first or the second. A fully custom theme is worth building when the storefront has to do something a stock theme was never designed for: sell by inquiry instead of a cart, show data that lives in another system, or carry rules about how products can be bought. If you cannot name the specific thing your current theme cannot do, you do not need a custom theme yet.

What counts as a custom Shopify theme?

People say "custom theme" about three different amounts of work, and the difference decides who maintains the storefront later.

Stock theme, configured Stock theme plus custom sections Custom theme
What changes Settings, fonts, colors, content New sections and blocks, written in code The whole storefront codebase
Who does the work The store team, in the theme editor A developer, for the custom parts A developer, start to finish
Theme updates Automatic while the code is untouched Added by hand as a copy that someone reviews None, your developer maintains it
Best fit Standard catalog and standard checkout One or two things the theme lacks A buying flow the theme was not built for
Main risk Looking like other stores Edits that make later updates painful Depending on the person who wrote it

The update row is the one people miss. Shopify updates a theme automatically only while its code files are in their original state. Once anyone edits the code, updates stop applying on their own. Shopify shows a notice, and someone has to add the new version as an unpublished copy. Somebody then checks that the edits survived and publishes it.

Is a stock theme enough for most stores?

Yes. For most stores, the better spend is on the theme they already have.

Shopify's free themes are built to be fast and accessible, and a store team can edit them without code. Horizon is the current family. Dawn, the older one, is still maintained. Horizon is built from blocks that nest inside other blocks, so layouts that once needed a developer can be assembled in the theme editor. Apps add reviews, subscriptions or bundles through app blocks, and nobody has to touch theme code.

The two reasons I hear most often rarely hold up.

"I want it to look different." Typography, photography, color and a handful of custom sections do most of that work. That is the middle column of the table.

"The store is slow." In my experience the cause is usually a stack of apps and oversized images. A new theme inherits both.

When is a custom theme worth building?

When the storefront has to behave differently and you can say how. Here are three cases from my own work. There are more in my portfolio.

The buying flow is not a cart. Moses NYC is a New York watch and fine-jewelry dealer. Its watches are an inquiry-only catalog. A visitor goes through a guided sourcing consultation instead of a checkout, and the inquiry goes to the sales team. Stock themes assume the cart is the point, so I built that storefront from a bare base theme.

The storefront shows data that lives somewhere else. Tres Colori sells personalized jewelry. Customers check where their piece is in production, and file a claim for a lost or damaged package, on the storefront itself. I wrote those pages to call the operations platform I built for the brand. A page like that is half theme and half order system, and the two have to be designed together.

The products come with buying rules. Goodbye Inventory is a beauty overstock and wholesale store that sells by the case. I built its storefront around browsing by brand and case-pack pricing. The rule itself runs inside Shopify checkout, in a Shopify Function, because a theme can only display a rule. It cannot stop an order that never passes through the theme.

Brand alone is a weaker reason than it sounds. A distinct look usually fits in the middle column.

What does custom theme development involve?

These are the parts that matter to the person paying for it.

  1. Start from a minimal base. Shopify publishes a starter theme called Skeleton for this purpose. Starting there is cleaner than stripping down a full theme, because nothing is in the codebase by accident.
  2. Build it as sections and blocks. The store team should still be able to rearrange a page, swap an image or add a landing page in the theme editor. If a banner swap needs a developer, the theme was built wrong.
  3. Keep the code in Git and preview before publishing. Work goes to an unpublished theme first. Someone checks it on a phone and on a desktop. Then it goes live.
  4. Protect the team's edits. Content the team changes in the editor is saved in the theme's own files, and a careless deploy overwrites it. On Goodbye Inventory, theme deploys preserve the edits the store team makes in the customizer.
  5. Support app blocks. When sections accept app blocks, most apps install the way they would on a stock theme.

This is the work I do as Shopify development.

Who maintains a custom Shopify theme after launch?

You do, which in practice means a developer you pay. The build is the smaller commitment.

Nobody ships updates for it. When Shopify adds a storefront feature, your developer adds support for it by hand.

Speed and accessibility stop being inherited. Someone has to test them on each release.

You depend on the person who wrote it. Reduce that before the build starts. Keep the repository in an account you control. Ask for a written description of how the theme is structured and deployed. Give the developer collaborator access that you can revoke.

Should it be an app or a Shopify Function instead of a theme?

Before you commission a theme, check whether the thing you want belongs somewhere else.

  • An app. Reviews, subscriptions, loyalty and search are maintained by teams whose whole product is that one feature.
  • Checkout. Rules about what can be bought, discounts and shipping options belong in Shopify Functions. They run inside Shopify checkout itself, so a rule still holds for a buyer who goes straight to checkout and never sees the theme's cart. Orders created outside checkout, by staff or by another system, are a separate case.
  • The back office. If the storefront shows the wrong stock or the wrong price, the fix is in the system that holds the numbers. A new theme will show the same wrong numbers in a nicer font.

How do you know if you need a custom Shopify theme?

Answer four questions in writing.

  1. What exactly can the current theme not do? Write one sentence about something a customer would notice.
  2. Could an app, a Function or a custom section on the current theme do it?
  3. Who maintains the result two years from now?
  4. What happens to the business if it never gets built?

If the first answer is vague, stay on a stock theme and put the budget into photography and product pages.

If it is specific and the second answer is no, you have a real case for a custom theme. Ask for a free 15-minute call and bring that sentence. I will tell you which of the three sizes it needs, including when the answer is to keep the theme you have.

For more, see my Shopify development service and the Moses NYC case study, the inquiry-only storefront I built from a bare base theme.

Share this article

Have a project like this?

Tell me what you run. The first step is a free 15-minute call.

Start with a free 15-minute call