Direct answer: On November 17, 2026, Shopify said legacy custom apps created in the Shopify admin now appear in the Dev Dashboard. Existing installations, access tokens, scopes and webhooks continue to work. The change gives teams access to IP restrictions and API and webhook logs. For a consumer brand with several agency, fulfillment or reporting integrations, the immediate job is to identify who owns each custom app and what would break if its credentials or network access changed. Shopify does not say that this move itself rotates tokens or turns on an IP allowlist.
What moved and what did not
Shopify’s announcement is specifically about custom apps that were created in the admin. They now appear in the Dev Dashboard, where these apps are managed. New custom apps are created through the Dev Dashboard or Shopify CLI. Shopify says the existing apps remain installed and their access tokens, access scopes and webhooks continue working. A brand should therefore treat this as a change in management and visibility, not as evidence that every integration needs to be reinstalled.
The new visibility matters because many established stores have custom connections for ERP, warehouse operations, feeds or internal reporting. A credential may be shared across more than one job even when only one app name is visible. Map the business owner, technical owner, data touched and recovery contact for each app before tightening its access.
Use the logs to build an inventory
Shopify says the Dev Dashboard offers API request and webhook activity logs for these apps. Review recent traffic to understand which endpoints, webhooks and processes are active. Compare that activity with the integrations your team believes it runs. Unexpected calls deserve investigation; inactivity alone does not prove an app can be removed, because some processes run only at month end or during a promotion. This audit sequence is Etail Rocket’s operating recommendation, not a Shopify mandate.
Test IP restrictions before enforcing them
The dashboard also exposes IP allowlisting. Shopify’s developer documentation says that, when enforcement is on, GraphQL and REST Admin API calls using an app’s tokens from outside the allowed sources fail with a 403 response. Its setup guide includes a test against recent traffic before enforcement. Have the integration owner identify every production source, including fulfillment and reporting partners, then run the test and a controlled request check. A rushed allowlist can interrupt order and inventory flows.
Shopify’s separate developer documentation sets requirements for some public apps and custom apps installed outside the developer’s organization. Those deadlines depend on the app’s distribution and installation context; the November 17 announcement does not by itself make every merchant-owned custom app subject to the same deadline. Ask the app owner to verify its category before applying a blanket deadline to your store.
Operator checklist
- List admin-created custom apps now shown in the Dev Dashboard and assign a business and technical owner.
- Confirm the jobs, data access and webhook dependencies for each app.
- Review API and webhook logs, including periodic jobs that may not appear in a short window.
- Test an IP allowlist against real traffic and coordinate any enforcement with the integration owner.
Etail Rocket can include marketplace feeds and store integration ownership in a focused Shopify operations audit.