Your theme is throwing a Liquid error

A single, well-defined Liquid bug — a Liquid error: undefined method, an Unknown tag syntax error, or a broken {% for %} loop — is typically reproduced, fixed and verified within 24–48 hours. If your theme is white-screening or a section has vanished from the live store, emergency triage starts in under 4 hours and we can roll the theme back immediately. Every fix is built on a duplicate theme and goes live only after you approve a preview.

Fixed prices at our canonical $25/hr rate, no hourly surprises:

• Quick Fix — $99 (~4h): one well-defined Liquid bug, 24–48h.
• Bug-Fix Sprint — $499 (~20h): a batch of bugs or one deep root-cause plus regression tests.
• Emergency / Retainer — custom: 24/7 on-call, immediate rollback, plus an optional $2,499 stabilization sprint (~100h) for themes in a bad state.

You get the scope and the price before any work starts.

It means a template is calling a property or filter on an object that is nil — for example undefined method ‘price’ for nil when a product, variant, or metafield no longer exists. The usual causes are a removed object, a renamed metafield, or a {{ ... }} that runs before the data is loaded. We trace the exact line, then guard the value with a default filter or an {% if %} check so the page renders cleanly instead of throwing.

That error — e.g. Liquid syntax error: Unknown tag ‘endif’ — almost always means the block tags do not match up. A common cause is a stray {% endif %} with no opening {% if %}, an {% endfor %} closing the wrong loop, or a typo in the tag name. We walk the template, fix the nesting so every open tag has a matching close, and re-validate the whole file so the parser stops complaining.

Yes. The {% schema %} block at the bottom of a section must be strict JSON. A trailing comma, a duplicate setting id, a smart quote pasted from a doc, or a missing bracket all trigger Invalid JSON in tag ‘schema’ and the theme editor refuses to save. We repair the JSON, de-duplicate setting IDs, and validate the whole block so the section saves and the editor controls work again.

Yes. Online Store 2.0 templates such as templates/product.json are JSON files that list which sections and blocks render. A hand edit can leave a bad section key, an orphaned block reference, or invalid JSON, and the page then fails to render. We rebuild the template tree — valid JSON, every section key matching a real section file, blocks in the right order — so the page loads as expected again.

Usually the {% for %} loop is iterating the wrong object, the {% paginate %} block is missing its {% endpaginate %}, or a limit conflicts with the paginate count so items are dropped or repeated. We fix the loop target, the paginate by value, and the pagination markup so the grid shows the right products with working next/previous links.

That error — e.g. Liquid error (sections/main-product line 42): Could not find asset snippets/price.liquid — means a {% render %} or {% include %} points at a snippet file that was renamed, deleted, or never uploaded. We either restore the missing snippet or repoint the include to the correct file name, then check the rest of the theme for other references to the same asset.

Yes. A connected metafield can render blank, throw Liquid error: undefined, or refuse to bind as a dynamic source in the editor when the namespace.key is wrong, the metafield type does not match how it is used, or the reference {{ product.metafields.namespace.key %}} is malformed. We fix the namespace/key, correct the type handling, and repair the dynamic-source binding so the value shows on the storefront.

Yes — this is the core of how we work. We never edit your published theme. We duplicate it, reproduce and fix the Liquid bug on the copy, regression-test it, and send you a preview link. The duplicate is only published as the live theme after you approve it. Because the old theme stays in your Online Store theme library, rollback is a single click if you ever need it.

The cleanest option is a Collaborator request (or a staff account) with Themes permission, so we can duplicate your theme and work on the copy. If you would rather not grant access, you can duplicate the theme yourself and share it, or download the theme files and send them over. We confirm exactly what we need when we reply to your bug report — we ask for the minimum scope required.

Yes. If the same Liquid bug comes back within 14 days of going live, we fix it again at no charge. Because we root-cause the real issue — the nil object, the malformed {% schema %}, the renamed snippet — rather than patching the symptom, recurrences are rare. For deeper themes, the part of our Shopify bug-fixing service that covers ongoing work is the retainer tier. This page is a spoke of our emergency e-commerce bug fixing service.