Shopify app developers can now retire an app on 30 days' notice. Run the drill before that email arrives
One of the apps your store depends on could disappear on a date its developer picks, as little as thirty days out. As of this week they can set that date themselves, without asking Shopify, and the only warning you're guaranteed is whatever they send. It's worth knowing now which app would hurt most.

Since November 12, 2026, Shopify app developers can remove an app from the App Store themselves and set a sunset date at least 30 days out, after which the app is uninstalled from merchants' stores. Shopify doesn't email merchants; the developer is responsible for notice. Merchants should list the apps they depend on, note where each one's data and storefront pieces live, and plan a replacement for the few that would hurt most, before any notice arrives.
What changed on November 12
Shopify announced that app developers can now remove their apps from the Shopify App Store themselves, from their Partner Dashboard, without contacting Shopify Support.
The process is short. The developer clicks Remove from App Store and picks a sunset date at least 30 days away. The app vanishes from the App Store immediately, so nobody new can find or install it. Merchants who already have it keep using it until the sunset date. On that date, the app is sunset and removed from their stores.
Two details matter most to merchants. First, Shopify doesn't email you, cancel your charges or uninstall the app for you. The developer is responsible for all of that. Shopify's developer documentation tells them to email current users before starting, post a notice inside the app about two weeks out, and send a reminder a week before. That's guidance to developers, not a guarantee to you. Second, once started, the sunset can't be undone, cancelled or moved.
None of this means developers are about to retire apps in large numbers. Most will never use the button. It does mean the process is now quick and quiet, and the notice you get depends on the developer.
Sequence of work
What the developer's thirty days look like
- Day 0
Developer starts the sunset; the app disappears from the App Store. They're told to email current users first.
- Around two weeks out
Shopify's guidance: post a notice inside the app.
- One week out
Shopify's guidance: send a reminder email.
- Sunset date
Charges cancelled and the app uninstalled; Shopify cleans up its webhooks, script tags and admin links.
Why thirty days is shorter than it sounds
Picture a small skincare brand on Shopify with fourteen apps installed. One handles subscriptions. One collects and displays reviews. One runs the loyalty points. One adds a size-and-skin-type quiz to product pages. A couple were installed for a promotion two years ago and nobody's sure what they do anymore.
Now the review app's developer sends an email: the app sunsets in thirty days.
Thirty days is enough time to switch an app. It isn't enough time to find out what the app was quietly doing. Where do the reviews live: in Shopify, or only on the developer's servers? Can they be exported, and in a format the next app can import? Which product page templates have the review block in them? Do the post-purchase emails link to a review form that will stop working? Does the loyalty app award points for reviews through this app?
Every one of those questions takes a day to answer properly in the middle of a normal month. In the middle of peak season, it's worse.
Shopify's developer documentation also describes what uninstalling does: it triggers cleanup that deletes the app's registered webhooks, script tags and Shopify admin links. That's tidy, and it also means anything on your store that depended on those pieces stops working on the sunset date, not before.
Thirty days is enough time to switch an app. It isn't enough time to find out what the app was quietly doing.
Run the drill now
The cheapest time to answer those questions is before anyone sends an email.
List every app. Settings, Apps. Include the ones nobody remembers installing. Note what each one costs and who on your team uses it.
Mark the ones customers touch. Anything in checkout, subscriptions, reviews, loyalty, shipping rates, product page widgets, or customer emails. These are the ones where a sudden gap shows up as a lost order or a confused customer.
Find where each one's data lives. Some apps store data in Shopify itself, in metafields, customer tags or orders. Others keep it on the developer's own servers. Ask the developer if you're not sure, and check that an export exists and that you've actually opened one.
Find its pieces on your store. Theme app blocks, embedded scripts, links in notification emails, automations in Shopify Flow or elsewhere that call it. Write them down, because those are what break on the sunset date.
Note who installed it and who hears from it. Apps often outlive the person who installed them. Make sure the store's contact email goes to a mailbox someone actually reads, because that's the likeliest place for a developer's notice to land, and write down who on the team would own a migration for each app.
Name a replacement for the top three. For the three apps that would hurt most, write down what you'd move to, whether another app or a small custom build, and roughly how the data would move. You don't have to switch. You just don't want to be choosing under a deadline.
How the work moves
The drill, one app at a time
- List every installed app
Including the ones nobody remembers installing.
- Mark the ones that touch customers
Checkout, subscriptions, reviews, loyalty, shipping, the storefront.
- Find where its data lives
In Shopify, or only on the developer's servers.
- Find its pieces on your store
Theme blocks, scripts, emails, automations that call it.
- Name a replacement
For the top three, the next app or a custom build, and how you'd move.
What to ask a developer you rely on
You can also ask, politely, before there's a problem. Our earlier note on what to ask your Shopify app developer covers security questions; these are about continuity.
- If you ever retire the app, how much notice will you give, and how will you send it?
- Can I export my data today, in a format another app could import?
- What on my store depends on your app, beyond the app itself?
- Is there a person I can reach if something breaks during a migration?
A good developer will have answers. A developer who bristles at the question has told you something useful too.
The same questions apply when you're choosing a new app. A busy listing with good reviews tells you the app works today. It doesn't tell you how the developer would leave, and since the listing disappears the moment a sunset starts, you won't be able to go back and check later. Ask before you install, and keep the answers with the rest of your notes on the store. For the broader version of this, see when the vendor kills the feature and scoring exit readiness before you need to leave.
When the email does arrive
Start the day it arrives, not the week before the date. Write the sunset date on the team calendar with the name of the person who owns the switch. Export the data first, while the app still works. Pick the replacement. Move the data and test it on a copy of your theme. Remove the old app's blocks and scripts yourself, before the sunset date, so you see what breaks on your schedule rather than the developer's. Then uninstall.
If an app you depend on is doing something central to how orders, customers or inventory flow, the safer long-term answer may be to own that piece, or at least to make sure its data lives where you control it. That's our ecommerce work: following the order all the way through and connecting the systems behind it. Talk to us.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.