Shopify now lets developers remove an app from the Shopify App Store directly from the Partner Dashboard. The November 12, 2026 change removes the need to contact Shopify Support to begin the process, but it does not transfer responsibility for merchant communication, billing, migration, or uninstall work.
An app sunset is a customer-transition project, not an administrative click. SMB software providers must protect merchants who rely on the app for orders, storefront behavior, reporting, customer communication, or internal operations. A good plan gives users time, explains alternatives honestly, cancels charges correctly, preserves required records, and leaves no silent dependency behind.
What Shopify’s self-service removal changes
In the Partner Dashboard, a developer can open the app’s Distribution settings and choose Remove from App Store. The sunset date must be at least 30 days away. Shopify removes the listing immediately, which stops new discovery and installs through the App Store.
The action cannot be undone. Listing the app again requires submitting it for review as a new app. Existing merchants can continue using the installed app until the scheduled sunset date. Read Shopify’s self-service removal announcement and current sunsetting documentation before acting.
What Shopify does not do for the developer
Shopify does not email merchants, cancel app subscriptions, or uninstall the app automatically on the developer’s behalf. The app provider must communicate the timeline, cancel recurring subscriptions through the appropriate API, and uninstall remaining instances when the transition is complete.
That division of responsibility matters. A listing can disappear while existing users continue to depend on scheduled jobs, theme extensions, webhooks, or data exports. Turning off servers too early can interrupt operations and remove the API access needed to complete cleanup.
Build a merchant transition inventory
List active installs, plan status, recent usage, critical workflows, stored data, configured integrations, and support history. Identify merchants whose operations depend heavily on the app and those who installed but no longer use it. Prioritize by business impact, not only account size.
Map what the app changes in each store: webhooks, script tags, theme app extensions, metafields, functions, discounts, customer-account components, or external automation. Record which items Shopify removes during uninstall and which data or configurations require separate handling.
Define the target outcome for each merchant
A merchant may migrate to another app, export data and continue manually, replace the workflow with custom development, or stop using the function. Do not imply that an alternative is equivalent unless it has been tested. Provide decision criteria and boundaries rather than a generic list of links.
Create a clear communication sequence
Initial notice
Explain what is ending, the sunset date, what will continue until then, billing treatment, data-export options, support contact, and the action the merchant should take. Use plain language and avoid burying the deadline.
In-app notice
Show a persistent message where active users will see it. Tailor the message to the merchant’s state: configured, inactive, export pending, or migration complete. Do not block access to data or required transition tools.
Reminder and confirmation
Send reminders with increasing specificity. Confirm when data has been exported, subscriptions have been canceled, and uninstall is scheduled. Provide a final completion notice with any retained-record policy and contact path.
Sequence the technical work safely
Preserve the app’s API access until subscription cancellation, export, migration, and cleanup are complete. Build an idempotent cancellation and uninstall process so retries do not create inconsistent states. Log outcomes with the minimum merchant data needed.
Test the full process in a development environment: notice delivery, export, subscription cancellation, uninstall, webhook cleanup, data deletion, and failure recovery. Confirm how frozen, pending, accepted, or other charge states are handled under current Shopify requirements.
Protect data during closure
Define which merchant and customer data will be deleted, exported, anonymized, or retained for a lawful purpose. Stop unnecessary collection as the product winds down. Restrict access, set deletion dates, and preserve only the audit evidence required to show completion.
Practical SMB example
Consider a hypothetical inventory-alert app used by 35 merchants. Ten merchants rely on daily alerts, eight use occasional reports, and the remainder are inactive. The provider chooses a date more than 30 days away and removes the listing so no new merchants enter the product.
Active users receive an initial email and in-app notice. The provider offers a structured export, identifies two tested alternatives, and schedules short migration calls for the ten dependent accounts. Billing is canceled only after the relevant final service period, and installs are removed after exports and confirmations. Failures enter a monitored exception queue with a named owner.
Measure the sunset
Track notices delivered, active merchants acknowledged, exports completed, migrations completed, subscriptions canceled, remaining installs, failed API actions, unresolved support cases, and data-deletion confirmations. Monitor daily as the deadline approaches.
Use a reconciliation report: Partner Dashboard installs, billing records, application database, and support cases should agree. A successful API response is not enough if a merchant still expects service or cannot access an export.
Where DIGIMAR can help
DIGIMAR helps businesses map and replace workflows through automation and integrations, web development, and ecommerce implementation. That can include data export, replacement workflow design, CRM or email handoff, monitoring, and customer communication automation.
The next step is a dependency inventory before pressing Remove from App Store. Confirm who is using the app, what each merchant depends on, how charges and data will be handled, and who owns every exception. Self-service removal makes the first click easier; responsible execution still requires a complete merchant transition.
Plan support capacity for the final weeks
Sunsets often create questions late in the timeline. Estimate support volume, publish a concise migration FAQ, and reserve staff for merchants with critical dependencies. Define which requests can be handled through documentation and which require account-level review. Track unanswered messages and response time so the team does not confuse a sent notice with a completed transition.
After the last uninstall, run a retrospective. Record why the product ended, which dependencies were hardest to remove, where communication failed, and what future product agreements should clarify about exports, portability, and closure.