To uninstall a Shopify app, open Settings > Apps, use the app's menu, and choose Uninstall. First review its removal instructions and save any data you need. Theme cleanup, external subscriptions, and verification need separate attention; removing the app alone does not finish every task.
Before uninstalling: record what depends on the app
Shopify's uninstall guidance warns that dependent features stop working, some data may be unrecoverable, and inventory at an app-managed location needs attention. Reinstallation might not restore settings or data. Follow the vendor's cleanup sequence while the app is still installed.
Create a removal record with these fields:
- Owner and replacement: who approves removal, and which feature takes over?
- Data export: file location, export date, and a sample record checked for completeness.
- Dependencies: product templates, cart behavior, fulfillment routing, automations, and other apps that use its output.
- Billing location: Shopify invoice, provider account, or both.
- Baseline: affected page URLs, screenshots, and expected behavior before removal.
For example, replacing a reviews app requires more than hiding its widget. Check that exported reviews retain product identifiers and that the replacement displays the intended records. This is a planning example, not a report of testing a particular app.
Use the app cost register and permissions checklist to document the decision.
Review theme code without guessing ownership
Keep a dated backup and a separate working copy using Shopify's theme duplication instructions. Preview edits in the unpublished working copy. A theme backup is not a backup of the app's external data, and uninstalling an app affects the store, even when you are viewing a theme preview.
Shopify documents three ways apps can extend a theme: app blocks, app embeds, and direct code changes. Embeds can load invisible functionality and have market-specific settings. Record the relevant settings before changing them.
A duplicate theme is not a clean baseline. It copies modifications already present. A fresh theme can have different settings and templates. Therefore, seeing a script on one preview but not another does not establish where it comes from or whether uninstalling will remove it.
Use this diagnostic matrix to decide what evidence to collect:
| Observation | Possible explanation | Next check |
|---|---|---|
| An app-branded snippet remains | Direct theme modification, possibly still referenced | Match it to vendor removal instructions and search for every reference |
| A script loads only on one theme | Different template, embed, or custom code | Compare the same page, market, consent state, and embed settings |
| A missing-file error appears | A reference points to an absent file | Trace the reference and confirm whether the feature should be restored or removed |
| Tags or metafields remain | Another workflow may still read them | Identify their owner and consumers before considering deletion |
Search filenames, snippet references, and script domains as clues. A generic name such as reviews.js is not sufficient evidence to delete a file. Ask the app or theme developer to identify ambiguous code.
Once ownership is established, follow the vendor's removal instructions in the working copy. Review references and their target files together; deleting a snippet while leaving calls to it can introduce errors. Change one integration at a time and retain the diff.
Separate Shopify charges from external subscriptions
According to Shopify's app billing documentation, uninstalling ends future recurring billing cycles through Shopify. An already-generated charge can still appear on the next invoice. Externally billed subscriptions need separate cancellation with the provider; uninstalling does not cancel them.
Review Settings > Billing > View current charges and past bills. Save the provider's cancellation confirmation separately. If a later charge appears, compare its service period and billing source with your removal record before treating it as a new subscription charge. Request any refund from the app developer; do not assume uninstalling creates one.
For metered fees, the app usage charges guide explains what to record before removing an integration.
Verify the storefront and replacement workflow
Use this acceptance checklist before publishing theme edits, then repeat the relevant checks on the live storefront after removal:
| Area | Pass condition to record |
|---|---|
| Product pages | Variants, media, pricing, and the replacement widget behave as intended |
| Cart | Add, update, and remove actions work; totals and discounts match the chosen scenario |
| Navigation and search | Menus and search results remain usable on mobile and desktop |
| Checkout handoff | The cart reaches the expected checkout; required replacement integrations are checked separately |
| Errors and requests | No new visible Liquid errors or unexplained failed requests on the affected pages |
| Operations | The owner confirms the replacement automation or fulfillment workflow works |
A theme preview cannot validate every store-level workflow. Schedule the uninstall accordingly, and do not assume publishing the backup theme will restore an uninstalled app or deleted data.
If speed is the reason for removal, compare repeated measurements of the same pages under the same conditions. Record the change without promising a particular gain. Use the page-speed diagnostic when the bottleneck remains unclear.
Close the data and maintenance record
Shopify's privacy webhook documentation describes a store-redaction notification that developers handle after uninstall. That notification is not evidence that a particular provider has completed deletion. Check the provider's retention policy and deletion process when confirming what remains in its systems.
Keep the export, theme backup, changed-file list, verification results, uninstall date, and billing cancellation record together. For the next app you install, record its cleanup instructions at the start so a future removal does not begin with unidentified code.