Skip to main content
A Shopify store runs the theme and every installed app in the same page. Apps that touch the cart, the product page, reviews, translations, or tracking can change behavior the theme is responsible for, and the result usually looks like a theme bug. This guide isolates the source without breaking your live store.

​
When to suspect an app

The strongest signal is timing.
  • The problem started after you installed, updated, or reconfigured an app
  • It only happens when a particular app feature is active
  • It affects one area an app is known to touch, such as the cart or reviews
  • A clean theme copy with no custom code still shows it
A clean copy that still fails does not prove the theme is at fault. Apps inject into every copy of the theme, so a clean copy rules out your custom code, not apps.

​
Isolate it safely

1

Record what changed

Note the app name, what it does, and the date of the last change. If several changed, list them in order.
2

Identify what it touches

Determine whether it modifies the cart, product page, theme code, checkout, reviews, translations, or tracking. That narrows which symptoms it could plausibly cause.
3

Duplicate the theme

Work in an unpublished copy. Never test on the published theme.
4

Disable the app block in the copy

Turn off the app’s block or embed in the duplicate rather than uninstalling the app. Uninstalling can remove data and affect the live store.
5

Retest the same scenario

Same product, same browser, same device. Changing two variables at once makes the result meaningless.
6

Restore and confirm

Re-enable the app. If the problem returns, you have proven the link.
Uninstalling an app can delete its data and its theme changes. Disable the app block or embed in an unpublished copy instead. Only uninstall when you have confirmed it is safe to lose what the app holds.

​
Apps that commonly collide

​
An app you removed is still breaking the theme

Uninstalling an app does not always remove the code it added. Shopify strips the app’s own blocks, but hand-added snippet includes and leftover asset references stay in your theme files and now point at something that no longer exists. The giveaway is a Liquid error naming a missing asset, on the storefront or in the theme editor:
The theme is not at fault. It is rendering an include the app left behind.
1

Note the exact filename

The error names it. Copy the part after snippets/, for example some-app-name.liquid.
2

Work on a duplicate

Duplicate the theme and edit the copy, so a mistake in the code editor cannot take the store down.
3

Find every reference

In Edit code, search your theme for that filename. Look first in theme.liquid, the cart templates, and the product templates, which is where app installers usually write.
4

Remove the include, not the file

Delete the {% render %} or {% include %} line that names the missing snippet. Leave the surrounding theme code alone.
5

Preview, then publish

Confirm the error is gone and the page still renders before publishing the duplicate.
Shopify support can see the error but generally cannot remove it for you, because the line lives in your theme’s code rather than in the app. If you are not comfortable editing Liquid, raise a ticket with the exact error text and it can be done for you.
Check app embeds too. Online Store → Themes → Customize → App embeds can still list a removed app’s embed. Turn it off there before hunting through code.

​
Once you know which app it is

Decide where the fix belongs.
  • The app changes something Elixir also controls. Turn the duplicate feature off on one side. Running the theme’s cart upsells and an upsell app at once is the most common version of this.
  • The app misbehaves on its own. Report it to the app vendor with your reproduction steps and the result with the app enabled and disabled.
  • The two genuinely need to coexist. Raise a ticket with the evidence below so it can be looked at properly.
Before installing a new app, check whether Elixir already does the job. The theme includes upsells, bundles, gifts, quantity breaks, countdown timers, and shipping protection. Running two systems for the same feature is the most reliable way to create a conflict.

​
If it is still not resolved

  • The app name and version
  • Exact reproduction steps
  • The result with the app enabled and with it disabled
  • Your theme version
  • Any console errors