Shopify Liquid error / theme error on product or collection page after app or edit.

Several products can look like “my theme broke.” They do not share a settings panel. This page is only when the live product or collection URL prints Liquid error / theme error (often after an app install, Code Editor edit, or section save). Theme editor Save / Publish that refuses or never goes live is theme-editor-publish-failing. Theme customizer blank / JSON templates or section groups not loading is json-templates-section-groups-broken. App embed / theme app extension never appearing on the live URL is app-embed-not-loading. Cart drawer / AJAX cart not updating is cart-drawer-not-updating. Variant picker / swatches not updating price or image is variant-picker-not-updating. This page is only: Liquid / theme error text on product or collection pages after an app or edit.

Six ordinary reasons Liquid error lands on product / collection: a snippet / section file deleted or renamed while the template still renders it, an undefined object or nil drop after a schema change, a broken Liquid filter or tag typo, leftover app block / include after uninstall, editing a draft theme while Current still serves the broken code, or you are debugging Save / Publish, blank customizer, app embed chrome, cart drawer, or variant picker instead. Walk them in that order. You already pay for Online Store. You do not need another seat to clear a Liquid error string.

Open the broken product or collection in a private window on the live domain (not the theme editor preview alone). Screenshot the full red Liquid error / theme error line — file name, line number, “undefined variable”, “Could not find asset”, “Invalid filter”, or similar. Note which app was installed / uninstalled or which Code Editor / section edit landed immediately before it broke.

Honest proof: if the live PDP / collection prints Liquid error / theme error text, stay on this page. If Save / Publish in Themes → Customize fails or never publishes, leave for theme-editor-publish-failing. If Customize itself opens blank / white with no storefront error string, leave for json-templates-section-groups-broken. Do not mix those proofs.

The most common storefront Liquid error is a render / include / section call that points at a file that no longer exists — renamed snippet, deleted app snippet, or a merge that dropped sections/*.liquid while templates/*.json still reference them.

Fix: Online Store → Themes → … → Edit code. Open the file named in the error. Restore the missing snippet / section from a prior theme version or from the app’s docs, or remove the render / include / {% section %} call if the feature is gone. Save. Confirm you are editing the Current / Published theme. Hard-refresh the live product / collection. If the customizer will not open at all because JSON is invalid, that is json-templates-section-groups-broken — repair JSON first, then return if a Liquid error remains on the live URL.

Product and collection templates assume objects exist — product, collection, variant, metafield, section.settings. A typo, a metafield definition removed while the template still prints it, or a filter that no longer accepts the type will print Liquid error on only some SKUs or collections.

Fix: read the error’s object / filter name. Guard with if / else or default filters, reconnect the metafield dynamic source on the Current Online Store 2.0 template, or remove the dead print. Test both a product that has the metafield and one that does not. Pure “metafield never shows but no Liquid error” is product-metafields-not-showing. Variant UI that never updates price / image without a Liquid error string is variant-picker-not-updating.

Uninstalling an app does not always remove every app block, snippet, or scripttag reference from product.json / collection.json or from classic Liquid. The live page then calls assets or objects the app no longer serves — classic Liquid error after “I just removed the app.”

Fix: Themes → Customize → product / collection template on Current. Remove orphaned app blocks. Edit code and delete leftover snippets the error names. If the bug is only that an App embed toggle is off (no Liquid error text, widget simply missing), leave for app-embed-not-loading. Cart AJAX that fails without a Liquid error banner is still cart-drawer-not-updating.

Theme editor Save / Publish failing or changes never live is theme-editor-publish-failing. Blank customizer / JSON templates / section groups not loading is json-templates-section-groups-broken. App embed / theme app extension not loading (no Liquid error string) is app-embed-not-loading. Cart drawer / AJAX cart not updating is cart-drawer-not-updating. Variant picker / swatches not updating is variant-picker-not-updating.

The only honest test for this page: the live product or collection URL shows Liquid error / theme error text after an app or edit. Capture the string, repair or remove the broken include / object / leftover app code, publish Current, retest. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove the live URL error string, restore or remove missing snippets, guard undefined objects / filters, clear leftover app blocks, and stop confusing theme-editor-publish-failing / JSON templates / app-embed / cart-drawer / variant-picker with a Liquid error on product / collection. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: theme-editor-publish-failing, json-templates-section-groups-broken, app-embed-not-loading, cart-drawer-not-updating, variant-picker-not-updating.

Pay for help when the work is not the Liquid error row — it is connecting the stack you already have so lead capture is not dying in DMs, storefront and checkout-ready exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever Liquid / theme guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.