
Shopify is enforcing IP allowlists from 20 November 2026 and requiring expiring offline Admin API tokens across staged dates from 1 December 2026 to 1 April 2027. This practical playbook explains what marketing and commerce teams must do now.
These are not developer-only deadlines. Shopify security enforcement affects background jobs, order and inventory sync, and marketing automations. UK founders and marketing leaders should treat this as a platform stability and compliance priority, run a fast audit, prioritise integrations that perform background Admin API work, and coordinate developer fixes and customer communications now.
What Shopify is changing, and the enforcement dates
Shopify has published two linked app security measures that matter for merchants and agencies: IP allowlists for apps, and a migration to expiring offline Admin API access tokens. Shopify requires public apps that call the Admin API to have an IP allowlist enabled by 20 November 2026, and it will delist or block apps that do not comply from new installs. These checks also show up in merchant Settings > Apps, where apps without an allowlist are flagged. ([shopify.dev](https://shopify.dev/changelog/blog/app-security-updates-ip-allowlist-due-tomorrow?utm_source=openai))
Separately, Shopify requires apps to use expiring offline access tokens. Key dates to note are: 1 December 2026, from which new custom apps must use expiring offline tokens; 1 January 2027, when public apps using non-expiring offline tokens will be delisted or blocked from new installs; and 1 April 2027, when Admin API requests using non-expiring offline tokens will start returning HTTP 403 and thus cause background jobs and syncs to fail. These are official Shopify timelines, so plan by the exact dates. ([shopify.dev](https://shopify.dev/changelog/posts/expiring-offline-access-tokens-required-for-new-custom-apps-as-of-december-1-2026?utm_source=openai))
Why this is a cross functional risk, not a developer-only change
Many marketing and commerce functions rely on apps that perform regular Admin API tasks: order syncs to ERP or PIM, inventory updates, subscription billing reconciliation, abandoned basket recovery, and scheduled exports for analytics and advertising. If an app is delisted or its background calls start returning 403, those flows can stop silently, hurting revenue and customer experience. Marketing directors and commerce managers need to own the business impact assessment, not just leave it to engineering.
There are operational and compliance consequences as well. Apps that lose Admin API access may stop ingesting or exporting customer data, which can break consented marketing workflows or reporting SLAs. From a brand and commercial perspective, merchants should prioritise apps that perform high volume or high value background work, and treat remediation as a platform stability task that requires scheduling, testing and customer communications.
Low friction audit playbook for UK merchants and agencies
Step 1, inventory installed apps. Export a list from Shopify Admin or work with your agency to capture every installed app, noting whether it is public, private or a custom app. For each app, record whether it calls the Admin API, runs background jobs, uses bulk operations or has scheduled syncs. This short list is your priority universe for remediation.
Step 2, triage and flag. Use three buckets: high risk (apps that run order, inventory or billing background jobs), medium risk (analytics, reporting and marketing automations that poll the Admin API), low risk (pure storefront widgets that do not call Admin APIs). For high risk apps, check the developer or partner dashboard for an IP allowlist and confirm whether the app author has migrated to expiring offline tokens. If unsure, contact the vendor now and request confirmation in writing.
Developer remediation checklist: IP allowlists and expiring offline tokens
IP allowlists: enable an app IP allowlist in the Partner Dashboard or custom app settings, add the production static IPs or CIDR ranges used by your service, test connectivity from listed IPs, and update documentation. Shopify supports a combination of IP addresses and ASNs and up to 250 entries. For serverless or variable IP deployments, developers should document the architecture and arrange stable egress IPs through NAT gateways or a proxy so the allowlist remains feasible. ([shopify.dev](https://shopify.dev/changelog/posts/app-ip-allowlists-now-support-ip-addresses-and-asns-together?utm_source=openai))
Expiring offline tokens: migrate to the expiring offline access token flow described by Shopify, implement token rotation and refresh handling, log refresh outcomes, and exercise the refresh workflow in a dev store. Test how the app behaves when a refresh fails or when Shopify returns a 403. Ensure webhooks and background workers gracefully handle token expiry by retrying with reauthentication prompts, and log and alert when refresh attempts fail so failures are visible to ops and merchant teams. ([shopify.dev](https://shopify.dev/docs/apps/build/authentication-authorization/migrate-to-expiring-offline-access-tokens?utm_source=openai))
Commercial mitigation steps and communication templates
Backup integration plans: for critical flows (orders, inventory, subscriptions) build a fallback that reduces risk during reauthorisation. Options include temporary manual exports, switching to a vendor with a supported integration, or a short-lived middleware that retries and queues outbound requests until tokens are refreshed. Prioritise least friction approaches that keep revenue and fulfilment running while developers complete the migration.
Communications: schedule a reauthorisation window with your app vendors and create a short merchant-facing message that explains a planned brief service interruption if reauth is required. Example template points: what is changing (Shopify security enforcement dates), which customers are affected (those using X app), expected impact and timing, and who to contact for support. Make the message clear, factual and sent at least one week before any required reauthorisation.
Practical checks for your business
List all installed Shopify apps and mark those that call the Admin API or perform background syncs
Flag any app without an IP allowlist enabled in the Partner or Custom app settings
Identify apps using non-expiring offline tokens and prioritise those that run cron jobs, webhooks or bulk operations
Schedule reauthorisation windows and a rollback plan for critical integrations before the enforcement dates
Shopify agency creating premium e-commerce journeys
Shopify design and development for brands that need a distinctive, maintainable store with stronger product discovery, buying journeys, tracking and customer retention.
Explore Shopify agency →Rebuilding a distinctive Webflow store experience in Shopify
A detailed migration focused on preserving the established brand experience while introducing Shopify commerce and maintainable store operations.
See the delivery example →This guide is maintained by Clicky Clicks for practical business education and reviewed by Chris Waterhouse before publication. Automated research or drafting may assist the editorial process, but final responsibility for accuracy, relevance and recommendations remains with the named author.

