{% for variant in product.variants %} sync -> 8 storefronts cart.attributes.tier GID://shopify/Product/ git commit -m "fix: oos quick-add" metaobject.reference -> handle
Currently taking on new Shopify Plus projects

I build the Shopify
systems that hold up
once you're at scale.

Shopify Plus developer specialising in B2B, multi-storefront, and high-traffic theme architecture. Currently building and maintaining the systems behind 8 live storefronts for an Australian apparel brand - AU, US, EU and CA, retail and wholesale.

End-to-end builds: Liquid, Shopify Flow, GraphQL/Storefront API, and the theme architecture decisions that keep a store maintainable long after it's outgrown its first build.

8
Live storefronts managed
B2B + DTC
Retail and wholesale builds
End‑to‑end
Theme, Liquid, Flow, APIs
01 / SHOPIFY
02 / EXTENDED
03 / APPROACH

What I actually do.

I build front-end systems for Shopify - theme architecture, modular Liquid components, conversion flows, and the logic that connects everything together.

Rather than working on isolated screens, I think in terms of how a system behaves across products, regions, and customer types. The goal is a store that's clear for shoppers and genuinely maintainable for the team running it.

How I scope a build.

Before touching code I want the edge cases: what happens with sold-out variants, stacked discounts, a market switching mid-checkout. Most of the real work in a Shopify build is in those cases, not the happy path.

Backed by experience across marketing, content, and commerce - I design and build with an understanding of how people actually arrive, decide, and convert.

Behind a build.

My process is shaped by real-world constraints - timelines, technical limitations, business goals, and whatever's already live and can't break.

I focus on practical execution: mapping flows, defining components, implementing logic, and refining based on how things actually perform once live. I've led development teams and work best in close, direct collaboration.

Things I care about.

Clarity over cleverness. Systems that don't fight the user, and interfaces that stay calm even as the complexity underneath grows.

Work that holds up over time - design that survives real use, real traffic, and real business needs. If it looks good but breaks down in practice, it isn't finished.

AI & search readiness.

Search is changing - AI assistants and shopping tools now read product data directly, not just the page a person sees. I build for both: structured data (JSON-LD), crawlable product content, and metadata that holds up whether it's read by Google or an AI agent.

That includes auditing where content is technically present but not actually crawlable - dropdown-rendered features, JS-only descriptions - and fixing it with structured, visually-hidden markup instead of a redesign.

Internal tooling & operations.

Not everything client-facing needs solving with a theme change. I build internal tools - dashboards, sync scripts, custom apps - that remove the manual, error-prone parts of running multiple stores.

Recent example: a Next.js dashboard that syncs product and metafield data across 8 live Shopify Plus stores from a single source of truth, with bulk CSV tools and a real-time sync log so nothing runs silently in the background.

04 / STACK
ShopifyShopify
LiquidLiquid
JavaScriptJavaScript
HTMLHTML
CSSCSS
GitGit
UI/UXUI/UX
FigmaFigma
PhotoshopPhotoshop
IllustratorIllustrator
After EffectsAfter Effects
UnityUnity
05 / CONTACT

Get a quote

Tell me a bit about the project and I'll get back to you with next steps - usually within a day or two. Prefer to just email? That works too.

dev@jessitilbrook.com
Opens in your email app - nothing is sent from here directly.