Executive summary
- What: Every custom app created on or after December 1, 2026 must request and use expiring offline access tokens for GraphQL and REST Admin API calls. Public apps have been held to this since April 1, 2026.
- Why: A non-expiring token stays valid until the app is uninstalled or the secret is rotated. An expiring token limits the blast radius of a leak to a fixed window.
- Who: Any merchant whose team or partner builds custom apps, which in practice means most Plus organizations running ERP, OMS, or middleware integrations through a private app.
What changed
For apps created on or after December 1, 2026, offline tokens obtained through the authorization code grant or token exchange must be expiring. You request one by including expiring=1 in the token request, then store the returned refresh token and use it to mint new access tokens as the current one lapses. The requirement now covers partner-created custom apps and apps merchants build themselves, not just App Store apps.
Two flows already satisfy the rule. Tokens from the client credentials grant expire after 24 hours by design, and application-only access tokens already qualify. If your app uses either, you are done.
Existing apps are untouched. Custom apps and merchant-created apps set up before December 1, 2026 can keep using their current offline tokens indefinitely. This is a forward-looking gate on new app creation, not a migration mandate.
Why it matters
This is not a developer-only concern. In most Plus organizations the highest-privilege credential in the business is the offline token belonging to a custom app syncing orders and inventory with the ERP. It holds broad write scopes, lives in a middleware config or CI secret, and has never been rotated. A non-expiring token in that position is a standing liability no amount of code review addresses.
Because the rule applies at creation time, the practical trigger is your next integration project. Any new custom app built after December 1 needs refresh-token handling designed in from the first sprint, not retrofitted when a sync fails at 2am. The cost of getting this right up front is a day of work. The cost of discovering it late is a silent integration outage.
Role-specific impact
- Marketers: Little direct impact, though any new custom app feeding campaign data, such as an audience export or loyalty sync, now depends on a refresh loop that can fail. Build alerting into the data pipeline, not just the app.
- Developers: Add expiring=1 to offline token requests, persist refresh tokens securely, and handle refresh failures with retry and alerting rather than a crash. If you use Shopify app templates or official libraries, upgrade to a recent version, since they already request expiring tokens by default.
- Store admins: When commissioning a new custom app after December 1, ask the builder how tokens refresh and where they are stored. Treat an app that cannot answer as unfinished.
Use-case example
Real-world scenario
A distributor with 1,400 daily orders was scoping middleware to push fulfilment status back from its WMS, planned for a January build. Reading the deadline, the team moved the token layer forward: the new app requests expiring offline tokens, stores refresh tokens in the existing secrets manager, and refreshes on a schedule with a failure alert to on-call. That added about six hours of engineering. The avoided scenario is one they had already lived through on an older app, when an invalidated token stopped fulfilment sync for 9 hours and left 212 orders showing as unshipped.
Implementation checklist
- Inventory every custom app in the organization and record which auth flow each one uses.
- Mark apps using the client credentials grant or application-only access as already compliant.
- For any app you plan to create after December 1, 2026, specify expiring offline tokens in the build requirements.
- Add expiring=1 to offline token requests, then store and use the returned refresh token.
- Upgrade Shopify app templates and libraries to current versions before starting new work.
- Instrument refresh failures with alerting, and confirm the app degrades gracefully rather than looping on a dead token.
- Consider migrating older high-privilege apps voluntarily, even though existing tokens stay valid.
FAQ
Q: Do we have to rebuild the custom app that runs our ERP sync today?
A: No. Apps created before December 1, 2026 keep working with their existing offline tokens, and no cutoff has been announced for them. Migrating is a security improvement you can schedule on your own timeline, not a compliance task.
Q: Does this affect apps we create directly in the Shopify admin?
A: Yes, if created on or after December 1, 2026. The requirement explicitly extends to merchant-created apps, which is the route many operations teams use for a quick integration. Plan for refresh handling even on apps that feel lightweight.
Resources
Shopify's reference on token types and the expiring offline token flow: Offline access tokens.
Need guidance? Talk to Makro.