Executive summary
- What: Custom apps created in the Shopify admin now surface in the Dev Dashboard, where they pick up IP restrictions and request-level logs for API calls and webhook deliveries.
- Why: It consolidates every app type behind one credential and observability model, on the same enforcement path as public apps.
- Who: Development teams, agencies, and integrators managing apps across one or many Shopify Plus stores.
What changed
Custom apps that a merchant or staff member created in the Shopify admin are now listed in the Dev Dashboard, with their credentials and logs managed there. Existing installs are not disrupted: apps keep their access scopes and webhook subscriptions, and existing Admin API access tokens continue to work. Public apps and other types you already managed in the dashboard are unaffected.
The useful additions are IP restrictions, which control which addresses may use an app's credentials, and API and webhook logs for investigating unexpected activity. Neither is applied automatically. The migration does not replace tokens and does not enable allowlisting on your behalf, so the before and after state of a working integration is identical until you act.
Why it matters
For anyone maintaining integrations across several stores, this removes a long-standing blind spot. These apps were previously opaque: no allowlist, no request history, and often no record of which system held the token. Credential policy is now something you can state and verify per app rather than per store convention.
The enforcement timeline is the part to plan around. An IP allowlist is required for custom apps installed on stores outside your own organization from November 20, 2026 for new installs, and from January 1, 2027 for apps already installed on such stores. Agencies and integrators are squarely in scope. Allowlists accept specific addresses and ranges as well as whole networks by ASN, which keeps dynamic egress workable.
Request logs also shorten the debugging loop in a measurable way. Webhook delivery failures are visible as events rather than inferred from missing records downstream, which is the difference between diagnosing a broken custom app integration in an hour and chasing it across two systems for a day.
Role-specific impact
- Marketers: No direct change, though data flowing into marketing platforms often depends on these apps. Webhook logs give you a defensible answer when a segment or flow appears to be missing orders.
- Developers: Build and manage all custom apps in the Dev Dashboard or through Shopify CLI. Expect to gather egress addresses or ASNs per environment, and note that allowlist rejections surface as 403 responses, so retry and alerting logic should treat them distinctly from rate limiting.
- Store admins: You can see which apps hold credentials on the store and confirm that each one maps to a system still in use. Coordinate before anyone enables restrictions, since a partial address list will break a working sync.
Use-case example
Real-world scenario
An agency maintains order and inventory sync for nine Shopify Plus clients, each through an admin-created custom app pointing at a shared middleware tier. Reviewing the apps in the Dev Dashboard, the team finds three with write scopes they no longer use and two installed on stores outside their organization, which puts them in scope for the January requirement. They allowlist the middleware ASN rather than enumerating addresses, since the hosting provider rotates egress IPs weekly. Rolling it out across nine stores takes two afternoons, and the logs confirm zero 403 responses across a full nightly batch window.
Implementation checklist
- List every custom app now appearing in the Dev Dashboard and confirm each shows the expected installation and scopes.
- Flag apps installed on stores outside your organization, since those carry dated allowlist requirements.
- Determine whether each integration has static egress addresses or needs ASN-based allowlisting.
- Enable IP restrictions per app in a staging or low-risk store before touching production.
- Update error handling so that a 403 from an allowlist rejection is logged and alerted separately from throttling.
- Review API and webhook logs for a full business cycle after each change, batch jobs included.
- Retire tokens and apps that no longer serve a live integration rather than allowlisting them.
FAQ
Q: Do we need to rotate tokens as part of this?
A: Not for the migration itself, which leaves tokens, scopes, and subscriptions in place. Rotation is still worth scheduling separately for any long-lived token whose storage location you cannot fully account for.
Q: Will IP allowlisting work if our integration runs on dynamic addresses?
A: Yes. Allowlists support autonomous system numbers in addition to addresses and ranges, so you can authorise the networks your integration runs on instead of chasing individual IPs through every provider change.
Resources
Managing apps in the Dev Dashboard
Need guidance? Talk to Makro.