Shopify app sunsetting: what developers must still do
Shopify adds self-service app removal, but developers still handle notices, billing and uninstalling. Here is what merchants should check.
15 November: check what removal leaves behind
Before removing an app, map the discounts, stored data and storefront features that depend on it. Shopify’s uninstall guidance warns that dependent workflows stop, some data cannot be recovered, and reinstalling may not restore the old settings. Export what you need while the app is still accessible.
Uninstallation can also leave code in the theme. Shopify’s script-audit guide recommends checking for unused third-party code. Our recommendation is to have the developer identify the app’s additions and test the affected storefront journeys after cleanup, rather than delete unfamiliar code indiscriminately.
Separate Shopify billing from any external subscription. Shopify says uninstalling cancels future recurring app charges through its system, although the current billing cycle can still be billed; charges arranged outside Shopify require separate cancellation. Keep that merchant-side check alongside the developer’s sunset obligations below.
Shopify app developers can now begin a permanent shutdown from the Partner Dashboard without asking Support to remove the listing. The self-service button does not transfer responsibility for existing merchants to Shopify.
The 12 November release note separates two events: the App Store listing disappears immediately, while existing installations need a managed sunset. Developers choose a date at least 30 days ahead and remain responsible for notices, subscription cancellation and uninstalling their app.
Check the date before confirming
Shopify’s sunsetting guide says the process cannot be cancelled and the date cannot be changed once started. Relisting requires resubmission. This is not a temporary visibility switch.
The route is Apps, the selected app, then Distribution in the Partner Dashboard. The guide tells developers to email current merchants before starting, send a reminder, cancel recurring charges and complete the uninstall process before taking the app off their servers. Keeping the app’s Dev Dashboard record preserves historical information.
Plan the handover before removing the listing
Our recommendation is to build a closure checklist with an owner and evidence for each step. Record which stores depend on the app, what data they may need to export, how they can get support and how you will confirm billing has stopped. A notice being sent is not evidence that every merchant has completed a migration.
Test the replacement journey with the affected store team before the shutdown. A product feed, returns portal or checkout feature can have dependencies beyond the app’s main screen. Include those connections in the handover and record any work that needs to happen after the final export.
Keep the service available long enough to complete the required communications, billing and uninstall work. Switching off hosting first can remove the very access needed to finish an orderly closure.
If your store receives a sunset notice
Confirm the final date with the developer and identify the business function at risk. Ask for export instructions, support contacts and a clear explanation of any replacement. Check your own billing records after the transition rather than assuming that a missing App Store page means charges have ended.
The minimum scheduling window is not a guarantee that every merchant will personally receive 30 days of notice. Look for the developer’s actual communication and act on the date it gives.
A missing listing also does not identify the reason for removal. Voluntary retirement is different from enforcement. Our app-security checklist explains why delisting alone is not a breach verdict.
More from Shopify
See all →
Before Black Friday, test what a Shopify webhook retry sends twice

