Shopify Development

Theme done well. Performance done right.

Shopify development inside the Online Store 2.0 architecture — sectioned themes, Liquid, metaobjects, and the disciplined app strategy that keeps a fast platform fast. We build storefronts the merchandising team can ship without breaking and the search engine can read without guessing.

Sub-techniques covered · Theme Customisation · Liquid · Shopify Apps · Performance · Headless Storefronts · Migrations · Multi-Channel · Schema
01 — What’s Included

Eight sub-techniques.
One considered build.

Shopify development is not template installation. It is a deliberate set of choices — theme architecture, Liquid logic, app boundaries, performance budgets, and structured data — that together decide whether the store loads quickly, ranks honestly, and survives the next theme update.

Every engagement begins with a Lighthouse and architecture audit, every customisation lives inside Online Store 2.0 conventions, and every change is reviewed on staging before a single byte reaches the live storefront.

N° 01

Theme Customisation

Online Store 2.0

We customise themes through Online Store 2.0 architecture — sectioned templates, JSON page configuration, theme blocks, and section settings that the merchandising team can edit without involving a developer for every change. Custom hero sections, product galleries with proper variant handling, lookbook layouts, store locators, comparison blocks, and bespoke product templates for hero SKUs all sit inside the theme’s design tokens rather than fighting them. The result is a storefront that looks like the brand rather than the demo, survives Shopify’s own theme updates, and stays editable in the Theme Editor by people who do not write code.

N° 02

Liquid & Custom Logic

Native templating

Liquid is Shopify’s templating language and the cleanest way to extend a storefront without bolting on another app. We write Liquid that is readable, performant, and scoped to the theme rather than scattered through file globs. Custom collection logic, conditional product badging, dynamic merchandising rules, structured FAQ blocks, customer-segment messaging, and the small pieces of business logic that would otherwise need an app — handled in twenty lines of Liquid, deployed alongside the theme, and reviewed in version control. We use metafields and metaobjects for structured content so the data model survives long after the current campaign ends.

N° 03

Shopify App Strategy

Stack discipline

Every app earns its keep on three measures — real business value, performance cost, and operational cost — or it is replaced with native theme code, a metafield, or a lighter alternative. We audit the current app stack ruthlessly, measure each app’s actual JavaScript and request weight on the storefront, and recommend cuts where the same job can be done with twenty lines of Liquid. For new installs we vet candidates by code quality, pricing transparency, and merchant reputation — not by app-store ranking. Bespoke apps are built only when the requirement is genuinely beyond what the platform and its ecosystem already provide.

N° 04

Performance & Core Web Vitals

Lighthouse 90+

Shopify’s CDN and infrastructure are fast on their own. Most slow Shopify stores are slow because the theme and apps undid that work. We tune image delivery through Shopify’s built-in image_url filters and responsive variants, defer non-critical JavaScript, lazy-load below-the-fold sections, eliminate render-blocking app scripts where the app permits, and trim the cumulative-layout-shift causes that hide in carousels and late-loading product reviews. Core Web Vitals are measured on field data via the Chrome User Experience Report, not just synthetic Lighthouse scores — because field is what Google ranks.

N° 05

Headless & Hydrogen Storefronts

Custom front-end

When a brand outgrows what the standard storefront can deliver — usually for performance reasons, deep editorial content needs, or a custom design language that Liquid templates cannot reach — we build headless storefronts using Shopify’s Storefront API, Hydrogen, or a Next.js front-end against the same backend. The Shopify admin and checkout stay where they are; the customer-facing layer becomes a fully bespoke React or Remix application with proper server-side rendering, edge delivery, and full creative control. Headless is the considered exception, not the default — we use it when the trade-offs genuinely earn the added complexity.

N° 06

Platform Migrations

Onto or off

Migrating onto Shopify from WooCommerce, Magento, BigCommerce, or a custom platform requires careful product-data restructuring (Shopify caps at three options per product), URL redirects from every old product and collection URL, customer-account and order-history transfer where preservation matters, and theme rebuilding in Liquid because PHP templates do not port. We have also done the reverse — Shopify off-ramps to WooCommerce or to a headless build when a brand has outgrown what the hosted platform can do. Both directions run on staging end-to-end before a single redirect goes live, with full SEO preservation through the cutover.

N° 07

Multi-Channel & B2B

Beyond the storefront

Shopify is a commerce backend long before it is a website. We configure multi-channel selling across Shopify POS for retail, the Shopify mobile app for buy-online-pickup-in-store, marketplace integrations through approved channels, wholesale and B2B catalogues with customer-segment-specific pricing, and the bespoke order workflows that B2B brands need. Markets is configured for international stores with proper currency, language, and domain handling. The storefront is one surface among several, and we set up the data model so all of them stay in sync without manual reconciliation.

N° 08

Structured Data & Schema

Machine-readable

Shopify auto-generates a baseline of Product schema, but the baseline is not enough — and on most stores it is incomplete or duplicated against app-injected schema, which Google then ignores. We audit existing structured data, eliminate the duplicates, and implement the schema types that actually drive rich-result eligibility and AI-search citation: Product with proper aggregateRating and offers, BreadcrumbList on every collection and product, Organization with the merchant’s brand, FAQPage on collection and product pages, Article on the blog, and LocalBusiness for stores with physical retail. JSON-LD, validated against Google’s tests, monitored after deploy.

02 — Our Approach

Use the platform.
Add what it misses.

Shopify is a deliberate trade-off — managed infrastructure and frictionless checkout in exchange for control over the substrate. We respect that trade. The work happens inside the platform’s architecture, not around it.

i

Inside the architecture

Sectioned themes, JSON templates, metafields, metaobjects, theme blocks. Every customisation lives in Online Store 2.0 conventions so it survives theme updates, the Theme Editor remains useful for the marketing team, and Shopify’s own performance work continues to benefit your store. Fighting the platform is a slow way to lose; using it well is faster than building from scratch.

ii

Performance budget first

Every build starts with a Lighthouse target and a JavaScript-weight budget — usually 90+ on mobile and under 250KB of third-party script before render. Apps and theme features are evaluated against that budget. If a feature breaks the budget, it gets reworked, replaced with a lighter alternative, or cut. The budget is set before the design decisions, not negotiated after launch when the score has already collapsed.

iii

Less app, more Liquid

Most Shopify problems are better solved with native theme code, metafields, or twenty lines of Liquid than with another app subscription. We default to those options and add an app only when the function genuinely needs the third-party expertise. The cumulative effect across a year is a faster storefront, a smaller monthly app bill, and a simpler stack the in-house team can actually understand and maintain.

iv

Honest about platform limits

Some things Shopify simply cannot do on standard plans — checkout extensibility beyond colour and logo, fully editable URL prefixes, certain technical SEO levers. We say so directly. Sometimes the right answer is to acknowledge the constraint, sometimes it is to upgrade to Plus, sometimes it is to migrate to WooCommerce or headless. We help you tell which is which before quoting work the platform cannot deliver.

03 — Who It’s For

Brands that want managed infra
without losing the craft.

Shopify is the right substrate for a wide range of commerce businesses, but the right kind of Shopify build depends on where the brand sits in its lifecycle and what it needs the storefront to do. We scope each engagement to the actual job.

Shopify development clients usually arrive in one of four moments — and the work looks different in each one.

  • i Launching a new Shopify storeYou are starting a brand or moving online for the first time and want to be on managed infrastructure rather than self-hosting. Full build — theme architecture, product setup, payment and shipping configuration, schema, performance budget, launch checklist — so day one looks like the brand and not like the demo.
  • ii Replatforming a custom Shopify buildYou inherited a theme that was customised by three previous agencies, half the changes are duplicated across sections, and every Theme Editor change risks breaking something. We rebuild on Online Store 2.0 architecture, consolidate the customisations, and document what each Liquid file actually does.
  • iii Migrating onto or off ShopifyComing from WooCommerce, Magento, BigCommerce, or a custom platform — or, less often, going the other way. Product-data restructuring, URL redirect strategy, customer and order migration, theme rebuild in Liquid. Run end-to-end on staging before any redirect goes live.
  • iv Going headless or considering itYou want the Shopify backend and checkout but a fully custom front-end — Hydrogen, Next.js, or Remix against the Storefront API. We help you tell whether headless is the right answer for your specific needs, and if so we build it; if not, we say so and keep you on the standard storefront with a custom theme instead.

If you are not sure which of these describes you, the free Performance Report below is the fastest way to find out. We send back a written assessment within 48 hours covering Core Web Vitals, app-stack health, and the prioritised fixes worth chasing first — no sales call, no obligation.

04 — A complimentary report

Wondering why your Shopify store feels slow?

Send us your URL. We’ll send back a Premium Performance Report within 48 hours — page speed, Core Web Vitals, accessibility, app-stack weight, and a prioritised fix list ranked by impact on rankings and conversion. Shopify-specific patterns get called out by name.

No sales call required.

Shopify ships fast by default. The real work is keeping it that way after the apps, the campaigns, and the third agency have all left their fingerprints.
— The Aureole Practice —
05 — Frequently Asked

Questions Shopify
merchants ask.

If a question is missing here, the contact link at the foot of the page goes straight to the person who would answer it. No ticket queues, no funnels.

i Do you build on Online Store 2.0 themes or older sectioned themes?
All new builds use Online Store 2.0 architecture — sectioned templates, JSON page configuration, theme blocks, metafields, and metaobjects. The older Sections-on-the-homepage-only model is no longer worth starting from in 2026: it locks editorial control to a single page, makes the merchandising team dependent on developers for every change, and adds friction to every theme update. For brands inheriting an older theme, the first conversation is usually whether to migrate to a 2.0 base — most of the time the answer is yes, and it is faster than continuing to extend a structure the platform itself has moved on from.
ii How is this different from the platform-buyer view at /shopify?
The Shopify technology page is for someone deciding whether Shopify is the right substrate for their commerce business and what an engagement on the platform looks like end-to-end — store setup, SEO, app stack, content depth, AI-search visibility. This page is the development-side detail under Web Design & Development: theme architecture, Liquid, performance, headless, migrations, schema. Different audiences, same underlying team — and the engagement is usually scoped from one of these two doors depending on whether the conversation starts with “should we be on Shopify” or “we are on Shopify, build the storefront properly”.
iii How long does a typical Shopify build take?
A standard Shopify storefront with a custom theme on Online Store 2.0 architecture typically runs four to six weeks from kickoff to launch — design, theme build, product import, payment and shipping configuration, schema, Lighthouse tuning, and a staging review pass. Larger catalogues with B2B logic, multi-currency Markets configuration, or custom Liquid sections push the timeline to six to ten weeks. Headless builds on Hydrogen or Next.js typically run ten to sixteen weeks because the front-end is built from scratch. We provide a written timeline with milestones in the proposal before any work begins, and we keep to it.
iv Should we go headless on Hydrogen, or stay on a standard storefront?
For most brands, the answer is to stay on a well-built standard storefront. Headless adds genuine complexity — a separate front-end deployment, edge-rendering configuration, an API layer that needs maintenance, and a learning curve for the marketing team. Headless is justified when there are specific frontend performance, design, content-modelling, or composability needs that the standard storefront cannot meet — for example, very heavy editorial content alongside commerce, a fully bespoke design language that Liquid templates cannot deliver, or a multi-brand setup running off a single Shopify backend. We help you tell which case is yours before recommending the work, and we are honest about the operational cost of headless after launch.
v Can you reduce the number of apps on our store?
Yes — and most stores we audit have at least three apps that fail one of our three tests (real business value, performance cost, operational cost). The audit is concrete: we measure each app’s JavaScript footprint on the storefront, identify where two apps are doing overlapping work, and recommend cuts or replacements. Some functions can be replaced with twenty lines of Liquid, some by a metafield, some by a lighter alternative app from a more disciplined vendor. The cumulative effect is usually faster Core Web Vitals, a lower monthly app bill, and a stack the in-house team can reason about. We never just rip apps out without a replacement plan; everything happens on staging first.
vi Will the build work with the SEO and content work on the same engagement?
Yes — and that is one of the main reasons brands engage with us rather than a Shopify-only agency. Our SEO practice, content team, and Shopify development sit under the same accountable team, so the schema we deploy matches the keyword strategy, the collection-page copy is written by people who understand search, and the AI-search visibility work plugs directly into the same content layer. The build, the SEO, and the content move together rather than waiting for handoffs between three agencies that do not talk to each other.
The Invitation

Ready to build a Shopify store
that earns its load?

Tell us about your store, your catalogue, and what you are trying to fix or grow. We’ll come back with a clear scope, timeline, and quote — written by the person who would actually run the build, not a sales department.

Mon–Fri · 9–6 PT support@aureoleintelligence.com Reply within 1 business day