We customise Shopify themes in Liquid: new sections your team can edit, landing pages built from your designs, product page improvements, and fixes for speed and broken pages. Changes are made on a copy of your theme and published when you approve them.
Tell us what you needSee typical projectsYou describe it. We build it.
What we hear from businesses before a project like this starts.
The requests that come up most often for this kind of work, and what each one takes to work properly.
Built as theme sections, so the copy and images can be changed in the theme editor without code.
Size guides, bundles, variant images, trust blocks and tabbed details, added as sections and blocks.
Figma or reference pages built into your current theme rather than a full rebuild.
Unused app code removed, images and scripts loaded properly, and Core Web Vitals measured before and after.
Broken carts, layout bugs and errors after an app was removed, found and repaired.
Translations and RTL layout for languages such as Arabic, using Shopify Markets and theme settings.
Tools that come up most: Shopify Liquid, Online Store 2.0 sections and blocks, Dawn and premium themes, Figma, Shopify Markets, Meta pixel, GA4.
Concrete pieces, each one something you can open and check when it's done.
New sections your team can add, move and edit in the theme editor, with settings for text, images and colours.
Liquid, JSON templates, section schemaCampaign and product landing pages built as reusable templates.
Page templates, metafieldsVariant logic, bundles, size guides, tabs and badges driven by metafields, not hard-coded per product.
Metafields, metaobjects, LiquidLeftover app code removed, images sized and lazy-loaded, render-blocking scripts deferred.
Lighthouse, Core Web Vitals, theme inspectorCart, layout and JavaScript bugs found and repaired, with the cause written down.
Theme code, browser dev toolsPixel, GA4 and Conversions API events checked and corrected so ads and reports see real orders.
Meta pixel, Conversions API, GA4, customer eventsExample packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
One landing page built from a Figma file or a reference page, as editable sections.
You get
Example package
The product template rebuilt with the blocks you need: size guide, bundles, tabs, trust badges.
You get
Example package
A measured speed pass on your home, collection and product pages.
You get
Example package
A list of broken things on the store repaired in one pass.
You get
Kestrel Coffee wanted a store that sells subscriptions first and single bags second. We built a custom Shopify 2.0 theme around the weekly roast: a homepage that leads with the subscription, product pages with size and grind options, a subscribe-and-save choice next to one-time purchase, and roast facts pulled from metafields. Every section can be edited in the theme editor, and the layout is mobile-first.
Shopify Liquid, Online Store 2.0, metafields, Shopify Subscriptions, JavaScript, CSS
A working example we built to show this kind of work. It is a demonstration, not a client project.
Sample build
Online Store 2.0 section where merchants pick up to three products, add feature rows as blocks and highlight one column with a badge. On phones the table scrolls sideways.
Liquid, Shopify section schema, CSS, liquidjs (static preview), Docker
About the screenshot: The section rendered in a static preview, outside a Shopify store.
The habits that keep this kind of project from going wrong.
All changes are made on a duplicate of your live theme and shown on a preview link. Nothing changes for customers until you approve.
New content is built as sections and blocks with settings, so your team can change it without us.
Speed work starts and ends with measurements on the same pages, so you can see what changed.
Custom code is kept in its own files where possible, so a future theme update is easier.
You know what you're getting before work begins, and you see it working at every milestone.
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
No. We send a collaborator request from our Shopify Partner account, and you choose the permissions. You can remove it at any time.
No. We work on a duplicate theme with a preview link, and publish only when you approve.
Our focus is changing and fixing existing themes. For a new store we can build on a theme you have chosen; we will tell you in the scope if a full build is better done another way.
You do. It lives in your theme, and we can also put it in a repository you own.
Most theme jobs take a few days to two weeks from the signed scope, depending on the number of pages.
In the 30 days after handover we fix anything we built at no charge. After that, we scope any further work with you first, so there are no surprises.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com