A custom Shopify theme is storefront code written for one store, not a stock theme with a new logo and a color change. We design it around how your products are actually shopped, write it in Liquid on Online Store 2.0, and build it so everyday page changes stay with you in the theme editor.
Book a free consultation →Plenty of Shopify stores open on a theme from Shopify's Theme Store, and many of them should. A good stock theme is written to suit as many kinds of shops as possible, so it arrives with a sensible homepage, a product page with room for photos and a description, a collection grid, and a settings panel for colors, type and spacing. Swap the logo, choose a palette, reorder a few blocks, and a store can start selling without anyone writing code.
The catch is in how a stock theme is put together. Its sections are general-purpose by design: an image with text, a featured collection, a slideshow, a block of rich text. Its product page offers every shop the same set of blocks, a title, a price, a variant picker, a description and a few general-purpose extras, and the catalog has to fit those shapes. For a lot of stores that fit is fine. For a catalog whose products carry details a shopper compares before buying, those details end up pasted into description fields or general-purpose blocks, and the page stops matching the way the products are really chosen.
A theme written from scratch starts at the other end. Before any design, we read the product data: which fields exist, what differs from one product to the next, what a shopper has to see before adding to cart, and which page types the store really uses. The theme is built around those answers. The general case for custom work over templates on any kind of website is made in custom website versus template.
Whether your store needs a coded theme at all is its own question, answered in whether to hire a Shopify developer or use a theme. A custom theme is not the default recommendation here, and if a stock theme fits your catalog, you will hear that on the consult.
Online Store 2.0 is the theme architecture that lets sections appear on most pages of a Shopify store, not only the homepage. A theme built from scratch on it is a set of files we write rather than inherit. These are the parts an owner should know about.
None of this is exotic. Current stock themes use the same architecture. The difference is who decided what each section is for: an author writing for every store at once, or someone writing for your catalog.
The same approach is behind a theme we built from scratch with 50 custom sections, and a second theme built from scratch with 36 custom sections. The stores are not named on this page, and no results are attached to them. The counts are here for a narrower reason: they show that the work is section-level code, written file by file, rather than a stock theme with its settings changed.
A section count is not a target. A store needs as many sections as its pages have distinct jobs, and a smaller catalog with simple products may need far fewer than either number. The count a theme ends up with comes out of reading the product data, never out of a wish to look big on a proposal. It is also why the section plan is written down before design starts: at any size, a section nobody can explain in a sentence is a section nobody will use.
For anyone comparing Shopify theme developers or Liquid developers, the useful question follows from that: ask how a candidate splits a page into sections and what settings each one exposes. The split decides how much of the store you can run yourself.
A theme built this way is meant to be run by the store, not by whoever wrote it. In the theme editor and the Shopify admin, without touching code, you or anyone you give access to the store can:
Some changes still need someone who writes Liquid:
One tradeoff belongs on the table before you commit. A custom theme receives no version updates from a theme vendor, so its upkeep comes from whoever maintains it, through website maintenance or by the job.
The build runs in an order that keeps unfinished work away from shoppers.
If the store is already selling and the new theme replaces one shoppers use every day, the rollout is its own job, covered on Shopify store redesign. If there is no store yet, the account, the catalog structure and the launch belong to Shopify store setup. How long either takes depends on scope, and how long a Shopify build takes explains what moves the calendar.
A theme build changes how the store looks and behaves, not which platform it runs on. It helps to know where that line sits before scoping anything.
That line also marks where theme work ends. When a store needs something no theme can reach, that is a different build: a site coded outside Shopify altogether is custom web design work, and the way theme work fits with the rest of what we do on the platform is laid out in Shopify web design and development.
A custom theme is scoped per store, quoted after the free consult. The cost of a Shopify website answer explains the pieces that sit around the build. There is no package price here, because the variables below change the work more than a label could.
Shopify's own plan and theme prices change on Shopify's schedule, so they are kept with their dates on Shopify pricing explained. For anything else, send the details or call (407) 694-2055.
Yes. A finished design is coded the same way as one drawn here: it is broken into sections first, and each section gets the settings you will need in the editor. That split tends to surface gaps early, such as a product page drawn around one tidy example that has to hold products with far more detail, or none. Those gaps are settled with you before the code is written.
Most do. Apps built with theme app extensions add their features in the theme editor, either as app embeds, which work on any theme, or as app blocks, which go into sections written to accept them, so a theme built from scratch plans where they can go. Older apps that ask for code pasted into theme files need that code placed deliberately in the new theme, and some turn out to be doing a job a custom section can handle on its own.
No. Products, collections, customers and orders live in the store's admin, and a theme displays them rather than storing them, so the catalog stays exactly where it is. What can change is where details are stored. Specs typed into description fields may need to move into metafields so the new sections can show them the same way on every product, and that move is part of the scope.
Whoever you choose. Nothing arrives from a theme vendor, so fixes and new sections come from a developer, whether that is us on a maintenance arrangement, us by the job, or someone else. The theme is ordinary Liquid, JSON, CSS and JavaScript sitting in your store's theme library, so another developer can open the same files and pick it up. Shopify keeps running the platform and the checkout either way.
It can be lighter, but no one can promise a speed score from a theme alone. Speed depends on more than theme code, and a custom theme controls only part of it. Writing only the sections a store uses and self-hosting its assets can remove weight. If a store is slow today, the diagnosis comes before any rebuild, so the causes are checked before anyone pays for a new theme.
As many as its pages have distinct jobs, and no more. One well-planned section can often serve more than one template with its own settings on each, so a small catalog with simple products may need a short list, while a large catalog with detailed product data needs more. Every section should earn its place in the editor, because each one is something the store has to keep working.
Shopify services · Store Setup · Store Redesign · Shopify SEO · Free website report card · All services
Schedule a free 30-minute consult with the owner, and if a stock theme would serve your store better, that is the first thing you will hear. You can also text (407) 694-2055 or describe the catalog in the quote form.
Book a free consultation → Or call/text directly: (407) 694-2055Tell us a little about the business and we will come back with an honest read: what we would fix first, what it costs, and whether you need us at all. Prefer to see work before you talk numbers? Get a free homepage mockup, built for your business, yours to keep either way.
Brandon reads every one of these himself. You will hear back shortly with an honest read on what we would do first, what it costs, and whether it is worth it for you.