If you’ve spent any time in the Shopify theme editor, you’ve probably had two conflicting reactions: surprise at how much you can build without touching a line of code, and frustration the moment you hit something it just won’t do.
That gap is the whole question behind this post. Since Online Store 2.0 rolled out, Shopify’s native customisation tools got genuinely powerful, sections, blocks, and app blocks can now do things that used to require a developer. But there’s still a real ceiling, and knowing exactly where it sits saves you from two expensive mistakes: paying for custom Shopify theme development you didn’t need, or limping along on drag-and-drop tools when your store has genuinely outgrown them.
This post walks through what the theme editor and Online Store 2.0 architecture can actually achieve, where Liquid customisation or a fully custom build becomes the sensible option, and how to work out which side of that line your store is on.
What Online Store 2.0 changed
Before Online Store 2.0 (launched in 2021), Shopify themes were largely rigid. Sections, the modular content blocks you see in the theme editor, only existed on the homepage. Everything else (product pages, collection pages, the cart) was fixed layout defined in the theme’s Liquid templates, and moving anything meant editing code.
Online Store 2.0 introduced sections everywhere, JSON templates, and app blocks. In practical terms:
- Every page type, product, collection, blog post, even the 404 page, can now be built from sections and blocks, not just the homepage.
- Merchants (and staff without dev access) can add, remove, and reorder sections through the theme editor, on any template.
- Apps can inject their own functionality directly into a section as an app block, without a developer manually pasting a code snippet into theme.liquid.
- Themes store layout as JSON templates, which makes it possible to duplicate a template, test changes on a copy, and publish without downtime.
This is the reason a well-built modern theme (Dawn and its many commercial derivatives) can support a surprising range of layouts without custom code. If your theme still uses the old .liquid-only template structure, a lot of what follows won’t apply to you until you’re on an Online Store 2.0-compatible theme.
What you can genuinely achieve in the theme editor
Assuming a decent OS 2.0 theme, here’s what’s realistically achievable through the editor alone:
Layout and content changes
– Reordering, adding, or removing sections on any page (hero banners, featured collections, testimonials, image-with-text blocks, FAQs)
– Building out entirely custom landing pages from existing section types
– Adjusting column counts, spacing, and section-level padding in themes that expose those settings
– Swapping between layout variants a theme ships with (e.g. grid vs carousel product listings)
Branding and visual design
– Colour schemes, typography pairings, and logo placement, usually via global theme settings
– Custom CSS in themes that expose a “custom CSS” field in section or theme settings (a genuinely useful middle ground, technically code, but contained and low-risk)
– Image and video content swaps across every section type
Functionality via apps
– Product reviews, upsells, countdown timers, size charts, trust badges, subscription widgets, and loyalty programs, most well-built Shopify apps now ship as app blocks you drag into a section
– Multi-currency and multi-language display (Shopify’s native Markets feature, largely settings-driven)
– Basic personalisation like “recently viewed” or “you may also like” blocks, when the theme or an app provides them
Content structure
– Metafields let you attach structured custom data (a “care instructions” field, a “fit guide,” a set of specs) to products or collections, and modern themes can display metafield content in sections without custom Liquid, this alone covers a lot of what merchants used to need a developer for
For a genuinely large share of Shopify stores, particularly ones in their first one to three years, or with a fairly standard product-collection-cart structure, this native toolkit is enough to build a professional, on-brand, conversion-ready store.
Where the theme editor and app blocks stop being enough
The limits tend to show up in four areas.
1. Custom functionality that doesn’t exist as a section or app
The theme editor and app blocks give you access to what’s already been built, either by your theme developer or an app developer. If you need behaviour nobody has built yet (a bespoke product configurator, a non-standard bundling logic, a checkout customisation beyond what Shopify Functions or Checkout Extensibility expose, a unique quiz-to-product-recommendation flow), no amount of dragging blocks around will produce it. Someone has to write it.
2. Complex, non-standard layouts
Sections are powerful, but they’re still built around a fairly predictable content model: heading, some blocks, maybe an image. Genuinely unusual layouts, asymmetric grids that change behaviour at different breakpoints, interactive storytelling pages, complex data visualisations, heavily animated experiences, usually exceed what section schema settings can express. You can fake some of this with custom CSS/JS snippets, but past a certain complexity you’re better off with purpose-built sections.
3. Performance, when apps and sections pile up
This is the one merchants underestimate most. Every app block and every extra section adds JavaScript, CSS, and often additional API calls. A store that’s added a dozen apps over two years, each injecting its own scripts, can end up with a noticeably slower storefront even though no individual change looks like a big deal. The theme editor doesn’t warn you about this, it’ll happily let you add a fifteenth app block. Cleaning this up (auditing what’s actually loading, consolidating overlapping app functionality, lazy-loading below-the-fold sections) usually does need someone comfortable reading theme code and browser performance reports, even if the fix isn’t a full rebuild.
4. Genuine brand differentiation
There’s a ceiling on how distinctive a store can look when it’s built entirely from a commercial theme’s section library, even a good one. Competitors on the same theme, using the same sections, tend to converge on similar layouts. If visual differentiation is a real priority for the brand, not just “make it look nice” but “look like nobody else in this category”, that generally means custom-designed sections and often custom Liquid, even if the underlying theme stays OS 2.0-based rather than fully bespoke.
Theme editor vs Liquid customisation vs full custom build
It helps to think of this as three tiers rather than a binary choice.
Tier 1, Theme editor and app blocks only. No developer needed day-to-day. Right for stores with standard product types, a straightforward catalogue, and branding needs a good commercial theme can express. Fastest and cheapest to maintain.
Tier 2, Liquid customisation on top of an OS 2.0 theme. A developer builds custom sections, modifies existing ones, or writes targeted Liquid/JS for specific functionality (a custom filtering UI, a bespoke product page layout, tailored metafield display), while keeping the theme’s core architecture and update path intact. This is where most growing stores land, it’s targeted, controlled spend, not a ground-up rebuild.
Tier 3, Fully custom theme development. Built from scratch (or from a minimal starter) around the brand’s specific requirements, rather than adapted from a commercial theme. Makes sense when the store’s needs are structurally different from what off-the-shelf themes assume, complex B2B catalogue logic, a highly bespoke UX, heavy performance requirements at scale, or a Shopify Plus store where the storefront is a genuine competitive asset. This is real custom shopify theme development, not a customised template, and it comes with a proportionate cost and timeline.
A practical framework for deciding
Run through this sequence before committing to a build approach:
- List the specific things you need that you can’t currently do. Be concrete, not “it needs to look more premium” but “I need a product page that shows different content blocks depending on product type.”
- Check whether an app already solves it. The Shopify App Store is large; a huge share of “custom” requests turn out to be a well-reviewed app away from solved.
- Check whether your current theme’s section settings solve it, even awkwardly. Sometimes two existing sections combined get you 90% there.
- If neither, scope it as a Liquid customisation, not a rebuild. Ask whether the change is isolated (a section, a template, a specific interaction) or systemic (affects layout logic across the whole store).
- Only consider a full custom theme build if the gap is structural, your catalogue, business model, or brand requirements genuinely don’t fit the assumptions a commercial theme is built around, or performance/technical debt from years of app stacking has made the existing theme unworkable.
- Weigh maintenance, not just build cost. Fully custom themes need a developer for future changes; theme-editor-friendly builds keep more control in-house. Factor in who maintains the site after launch, not just who builds it.
Getting this sequencing wrong is common, merchants either over-invest in a full rebuild for problems an app would have solved, or under-invest in Liquid work and end up with a theme editor Frankenstein that’s slow and hard to maintain. If you’re not sure which tier your requirements actually sit in, this is exactly the kind of assessment a Shopify web design and development engagement should start with, a proper audit of what’s achievable natively versus what genuinely needs custom work, before any code gets written.
Signs you’ve outgrown the theme editor
- You’re paying for multiple apps that each solve 60% of a problem, none of them well
- Page speed has crept down every time you’ve added a new feature, and nobody’s looked at why
- Your team keeps saying “we can’t do that in Shopify” about things that are actually possible, just not through the section library
- The store looks visibly similar to two or three direct competitors on the same theme
- You’re using custom CSS/JS snippets pasted into multiple sections as a workaround, and nobody remembers what half of them do
None of these mean you need a full custom theme. Most point to Tier 2, targeted Liquid work, rather than starting over.
Frequently asked questions
Can I switch themes without losing my theme editor customisations?
Not automatically. Section and block content is generally tied to the theme it was built in, so switching to a different theme means rebuilding your section layout, even if the content (products, pages, metafields) carries over. Duplicating your current theme before making major changes is good practice regardless.
Do app blocks slow down my store?
They can, particularly when several apps each load their own scripts on every page rather than only where needed. A single well-coded app block is rarely the problem; a dozen loosely audited ones over time usually is. Periodically reviewing installed apps and removing ones you’re not actively using is worth doing every few months.
Is Liquid customisation the same as building a custom theme?
No. Liquid customisation typically means a developer adjusting or extending an existing OS 2.0 theme, new sections, modified templates, targeted functionality, while keeping the theme’s core structure, update path, and much of its cost efficiency. A fully custom theme is built from the ground up around the brand’s specific requirements, which is a larger investment with different trade-offs.
How do I know if my current theme is Online Store 2.0 compatible?
Check the theme’s details in your Shopify admin under Online Store > Themes, or ask the developer who built it. Most themes released or meaningfully updated since 2021 support OS 2.0’s sections-everywhere architecture; older, unmaintained themes may not, which limits what you can achieve without code regardless of how good the theme editor looks on paper.
What does custom Shopify theme development typically involve, timeline-wise?
It varies significantly with scope, but a genuinely custom build (not a themed template) generally runs longer than a theme customisation project, often several weeks to a few months depending on catalogue complexity, integrations, and design scope. Liquid customisation on an existing theme is usually faster, often measured in days to a few weeks per feature.
Ready to find out where your store sits?
If you’re weighing up a theme editor tweak against a proper development project, don’t guess. A Shopify audit will tell you exactly what your current theme can and can’t do natively, or you can book a call to talk through your specific requirements with someone who builds Shopify themes for a living.
