Executive summary
- What: Shopify published an action-required notice asking every app developer to complete a security checklist this week, including a new vulnerability scan and a migration to expiring offline access tokens.
- Why: Attack volume across the app ecosystem is rising as AI lowers the cost of finding vulnerabilities, and public apps that still present non-expiring offline tokens lose Admin API access on January 1, 2027.
- Who: Partners and in-house teams who maintain public apps must act. Merchants should treat it as a prompt to audit which third parties hold API access to their stores.
What changed
Shopify asked app developers to do seven things, framed as this week's work rather than a roadmap item: scan the app with the new security check in Shopify AI Toolkit, which looks for unauthenticated routes, cross-shop data access and unverified webhooks; move to expiring access tokens, soon required for all public apps; run vulnerability scanners across every endpoint; treat all rendered data as untrusted, including content pulled from metafields; review Dev Dashboard API logs filtered by client IP; turn on two-step authentication across Partner accounts, hosting, CDN, repositories and email; and keep the emergency developer contact current.
Shopify also set out what it is changing on its own side: tighter boundaries for storefront app code, IP address restrictions so API keys only work from a developer's own servers, and higher App Store security requirements. Timelines will be shared before any change takes effect.
Why it matters
For a Plus merchant, the installed app list is the real attack surface. A typical enterprise store runs twenty or more apps holding scopes across orders, customers, inventory and fulfilment. If one vendor's token store is compromised, an attacker gets read and write access to that data without ever touching your own credentials. Non-expiring offline tokens make that worse, because a token leaked today still works indefinitely.
The enforcement date carries a second, more mundane risk. Shopify will reject Admin API requests presenting a non-expiring offline token, and merchants lose access to the app until someone re-authenticates. For an app sitting in the middle of order sync or fulfilment routing, that is an operational outage, not a security incident. Vendor readiness is worth asking about directly, alongside your own security and compliance posture on Shopify Plus.
Role-specific impact
- Marketers: Check which marketing and personalisation apps hold customer and email scopes. A vendor breach involving those scopes is a notification obligation, not just a service interruption.
- Developers: Run the security check against every custom and private app you own. Enable the expiring token flag in app templates, or add the expiring parameter to token exchange, and store refresh tokens properly. Audit webhook verification and output escaping on metafield-sourced content.
- Store admins: Inventory installed apps across every store in the organisation, uninstall anything dormant, enforce two-step authentication on all staff and Partner accounts, and confirm emergency contacts reach someone who can act.
Use-case example
Real-world scenario
A Plus merchant running four regional stores had twenty-two apps installed across the organisation. A two-hour audit found six apps with no activity in over ninety days, each still holding order and customer read scopes. Uninstalling them cut the number of third parties able to read order data from fourteen to eight, a 43 percent reduction, with no change to any live workflow.
Implementation checklist
- List every app installed across every store in the organisation, with its scopes and last activity date.
- Uninstall apps that are dormant or duplicated across stores.
- Ask each business-critical vendor in writing whether they have migrated to expiring offline access tokens, and request a date.
- Run the security check command against every custom or private app your team owns.
- Enable the expiring offline access token flag in app templates, or add the expiring parameter to your token exchange requests.
- Enforce two-step authentication on Partner accounts, hosting, CDN, repositories and email.
- Review Dev Dashboard logs filtered by client IP and investigate unfamiliar sources.
- Update the emergency developer contact in the Partner Dashboard.
- Put the January 1, 2027 token deadline on your integration roadmap with a vendor-by-vendor owner.
FAQ
Q: Does the expiring token requirement affect custom apps we built in house?
A: No. Shopify enforces it on Admin API requests from public apps. Custom apps and apps created by merchants are out of scope, although short-lived tokens remain the safer pattern and the security scan still applies.
Q: What happens if one of our vendors misses the deadline?
A: After January 1, 2027, Shopify rejects Admin API requests presenting a non-expiring offline token. The app stops working against your store until a merchant user re-authenticates it, so plan for a potential outage.
Resources
Shopify security best practices for apps
Need guidance? Talk to Makro.