Executive summary
- What: Custom apps created inside the Shopify admin now appear in the Dev Dashboard, with IP allowlisting and request-level logs for API calls and webhook deliveries.
- Why: These apps hold the Admin API tokens behind ERP, OMS, and warehouse integrations, and until now had no credential controls and no audit trail.
- Who: Store admins and integration owners on Shopify Plus, plus any agency or integrator that installed a custom app on a client store.
What changed
Legacy custom apps created in the Shopify admin are now visible and manageable in the Dev Dashboard, alongside public and CLI-built apps. Functionally nothing was disturbed: apps stay installed, existing Admin API tokens keep working, scopes are unchanged, and webhook subscriptions keep delivering. What changed is the management surface.
Two capabilities arrive with the move: restricting which IP addresses or networks may use an app's credentials, and inspecting logs of the requests it makes and the webhooks it receives. The migration does not rotate tokens and does not switch on IP restrictions for you.
Why it matters
Admin-created custom apps are the quiet risk in most enterprise Shopify estates. They were fast to create, so they multiplied, and a typical one carries write access to orders, inventory, and products. The token is a bearer credential, so anyone holding the string can act as that app from anywhere. An IP allowlist closes that gap: Shopify rejects any Admin API request from outside your list with a 403, so a leaked token is useless off your network.
The logs matter just as much day to day. When an ERP sync double-writes an order or stops receiving fulfillment webhooks, you were left correlating timestamps across two systems with no view of what Shopify sent. Delivery-level visibility turns that into a five-minute check, and it fits alongside the monitoring practices you should already have around a Plus store.
There is also a deadline. Allowlists are already required for custom apps installed on stores outside your own organization: November 20, 2026 for new installs, and January 1, 2027 for apps already installed there. If you run multiple orgs, or an integrator installed an app on your store, treat this as a dated compliance item, not optional hardening.
Role-specific impact
- Marketers: Little changes in your tooling, but the apps feeding order and customer data into your ESP or CDP are often admin-created custom apps. You can now ask for proof that a webhook fired before escalating.
- Developers: Credentials, scopes, allowlists, and logs for every app type now live in one dashboard. Create new custom apps with the CLI or Dev Dashboard, and make request logs your first stop when debugging an integration.
- Store admins: You finally have an inventory of what holds a token on your store. Removing stale apps with write scopes is the cheapest security improvement available this quarter.
Use-case example
Real-world scenario
A home goods brand on Shopify Plus runs ERP order sync through an admin-created custom app, with a second for its 3PL and a third left from a loyalty vendor dropped 18 months ago. The Dev Dashboard review shows the loyalty app still holds write access to customers and orders with no request in 11 months, so it is uninstalled that afternoon. The ERP app is pinned to the middleware host's two static egress addresses. A fortnight later the webhook logs surface roughly 4 percent of fulfillment webhooks succeeding only on retry, a drift corrected before month-end reconciliation rather than during it.
Implementation checklist
- Open the Dev Dashboard and list every custom app now showing against your store or organization.
- Record each app's access scopes and the internal system or vendor that holds its token.
- Uninstall any app that no longer backs a live integration, starting with those holding write scopes.
- Collect static egress IP addresses or ASNs for each remaining integration from your hosting provider.
- Enable IP restrictions one app at a time, beginning with your lowest-traffic integration.
- Watch request and webhook logs through a full business cycle after each change, batch jobs included.
- Prioritise apps installed on stores outside your organization, where the allowlist requirement has a fixed date.
FAQ
Q: Will this break our ERP or 3PL integration?
A: Not on its own. Tokens, scopes, and webhook subscriptions are untouched, and no allowlist applies until you create one. The real risk is enabling IP restrictions with an incomplete address list, so stage the rollout and review logs after each step.
Q: Do we still create custom apps in the Shopify admin?
A: No. New custom apps are created in the Dev Dashboard or with Shopify CLI. Apps you created previously keep running and are now managed there with everything else.
Resources
Shopify IP allowlist documentation
Need guidance? Talk to Makro.