What changed in Shopify’s app sunset flow?
Shopify’s November 12, 2026 release note introduces self-service permanent removal from the Shopify App Store through Partner Dashboard > Apps > app > Distribution > Remove from App Store. For public-app developers, the key change is operational: you can initiate the removal yourself, choose a sunset date at least 30 days out, and the listing comes down right away. Existing installs do not stop working immediately, but the removal cannot be undone. If you want the app listed again later, you would need to go through review and resubmission.
This is a storefront and distribution change, not an automatic merchant-offboarding event. Shopify does not cancel charges, uninstall the app for you, or send merchant notice on your behalf. That means the merchant transition still belongs to the app team.
Shopify release note: Remove your app from the Shopify App Store yourself
Shopify docs: Sunsetting your app
What changes when the listing comes down
- Does: remove the public App Store listing immediately after you submit the removal.
- Does: let you choose a sunset date at least 30 days in the future.
- Does not: automatically uninstall the app from existing stores.
- Does not: automatically cancel recurring billing or notify merchants for you.
- Removal cannot be undone. To list the app again, you must resubmit it for review.
Limited visibility is a separate option. It keeps your app out of App Store search and category pages, but a merchant with the direct listing link can still install it. Use limited visibility if you want less discovery. For a permanent retirement, use Shopify’s sunset process.
Before you schedule removal: confirm one merchant and the billing path
Before you click Remove from App Store, pick one active installation and verify the basics: Is the merchant still using the app? Is billing Shopify-managed or handled outside Shopify? Do you have any backend work that must remain available until cancellation and uninstall are complete? That one-merchant check helps you avoid scheduling a sunset date that creates a gap in support, access, or billing reconciliation.
Rehearse the handoff with a fictional store and a mock subscription record. Have someone on the team walk through the notice, the export instructions and the order of the final checks before you touch a live installation.
Fictional handoff example
Example: a public app team decides to sunset a reporting app. First, they send a notice to the merchant that explains the replacement path, what to export, and when support will end. Next, they verify one active installation and confirm whether the subscription is Shopify-managed before they schedule removal. They leave backend services active long enough to finish any required API work, then reconcile the remaining install count and any outstanding charges at the end. The rehearsal stays separate from production work, so the team can confirm the handoff without affecting a live merchant.
Before / after checklist
- Before: identify the active merchant(s) and confirm billing ownership.
- Before: send notice, replacement guidance, and any export instructions.
- Before: identify which tasks still need access to the app or its API, and assign someone to finish them before uninstalling.
- Before: schedule removal with a sunset date at least 30 days away.
- After: monitor remaining installs and merchant responses.
- After: cancel applicable recurring subscriptions and complete the documented uninstall steps while your app and API access still work.
- After: reconcile charges, access, and support obligations once the offboarding is complete.
Practical takeaway for public-app developers
Before you remove the listing, make sure one merchant could follow your notice, export what they need and move to an alternative. Then use that check to plan the handoff for the rest of your installs.
