Shopify Fall '26 Edition: what it changes for your automations and custom apps
The Shopify Fall 26 Edition for store owners with automations and custom apps: what needs action, what has a deadline and what you can safely ignore.
By Rokibul Hasan8 min read
- Shopify
- News

Shopify published its Fall '26 Edition, titled "Exponential", on 28 October 2026. The edition page runs to eleven sections, and most write-ups walk through all of them. This post is for people whose store depends on Flow workflows, custom apps, scripts and connected tools, and it asks a narrower question: what does the Shopify Fall 26 Edition change for you?
Most of it needs nothing from you, a handful of items need a check, and two carry hard dates. I am working from Shopify's developer post, its merchant post, the edition page and the developer changelog, as of 4 November 2026. Many features carry labels such as "Coming soon" or "Early access", so announced does not always mean available in your admin.
I build Shopify apps and automation, so this is a builder's reading. Nothing here is a reason to change anything before Cyber Week.
Shopify Fall '26 Edition triage
| Change | Who it touches | What to do | By when |
|---|---|---|---|
| Expiring offline tokens | Public apps, not custom apps | Ask your app vendors | 1 January 2027 |
| Script tag retirement | Any app still using them | Move to theme app extensions or web pixels | Storefront tags stop 1 March 2027 |
| Discounts in Rollouts | Tools that read discount dates | Read Discount.rollouts |
Before a discount goes in a rollout |
| Variant barcodes | Sync that reads barcode |
Read barcodes |
When you move to API 2026-10 |
| Flow through AI Toolkit | Your own store's workflows | Optional, with care | No date |
| IP allowlist, security check | App owners | Worth adopting | No date |
| WebMCP, Knowledge base | Every store | Review your published facts | Soon |
Custom apps: the token deadline that does not apply to you
Shopify's security update of 27 October says: "All public apps that call the Admin API must migrate to expiring offline access tokens by January 1, 2027." It also says custom apps, merchant-created apps and online access tokens are not affected.
If you own a custom app on your own store, you have nothing to do for this. If you rely on a public App Store app, the dates reach you through the vendor:
- 1 January 2027: apps that have not moved are delisted and blocked from new installs. Existing installs keep working.
- 15 January 2027: merchants using those apps see a warning in the admin.
- 1 April 2027: Admin API requests with non-expiring offline tokens return HTTP 403.
So ask each vendor whose app matters to your operations whether they have migrated. A store can run happily through January and lose an integration on 1 April. Custom apps have a different history, which I cover in Shopify legacy custom apps.
Two optional security features are worth a look. An IP allowlist in the Dev Dashboard makes Shopify reject Admin API calls from other addresses with a 403, even with a valid token. It suits apps on static IPs, and the changelog does not say whether it covers custom apps, so check your app's Settings page. The other is shopify app security check, a Shopify CLI command that scans for unauthenticated routes, cross-shop data access and unverified webhooks. Shopify says it supports public and custom apps, and also that "a clean report isn't a guarantee of security".
The two quiet breakers: script tags and barcodes
Script tags. Shopify's deprecation page says you cannot create or update a script tag after 1 October 2026. Tags on the order status page stopped working on 26 August 2026, and tags on storefront pages stop on 1 March 2027. The replacements are theme app extensions for storefront JavaScript, web pixels for analytics and customer account UI extensions for the order status page.
This one bites older tracking and review apps. A tracking script on the order status page may already have stopped, and the first sign would be a dip in reported conversions.
Barcodes. The edition allows up to 20 barcodes per variant. The 2026-10 API release notes deprecate ProductVariant.barcode in favour of barcodes, and the old field returns only the first entry. That is harmless until a variant gains a second barcode. A marketplace sync, warehouse scanner or label tool that matches on barcode then sees one value out of several. Check this before anyone starts adding them.
API 2026-01 stops being accessible on 16 January 2027, after which calls pinned to it fall forward to the oldest accessible version. Plan your move to 2026-10 for the weeks after Cyber Week.
Rollouts change what a discount date means
Rollouts bundle theme, checkout, catalogue and discount changes into one timed launch, event or experiment. For integrations, that changes an assumption: a discount's own start and end dates no longer tell the whole story once it is inside a rollout. The API now has rollout queries and webhooks, and apps need the read_rollouts scope, which can mean asking merchants to reauthorise.
Feeds, email tools, ERP exports and custom sale banners are all affected. The detail, and how to stay out of trouble this season, is in my Black Friday ecommerce checklist.
Flow and Sidekick: agents can now edit your automations
Shopify's changelog of 28 October says an agent using AI Toolkit can create, update, delete, activate and deactivate Flow workflows, and read them. Direct use of the API needs the write_automations scope, which Shopify must approve, and the entry says "third-party apps are prevented from using the underlying APIs directly".
So this is a tool for your own store, not an opening for a no-code vendor to run your Flow account.
The edition page also lists workflow version history, with preview, compare and restore, and role-based control over who can view, edit and activate workflows. Those two matter more than the agent feature. A workflow can tag orders, change inventory or call another system, so an active workflow is production code even if it never looked like code. If you let an agent build them, keep it simple: the agent drafts, a person reads and activates.
Shopify's merchant post describes a rebuilt Sidekick that can run calculations, write code and search the web while "ensuring that the merchant approves its changes". The admin activity log, which would attribute changes to a staff member, app or service, is marked "Coming soon". Until it arrives, keep your own notes on automation changes. My guide to Shopify Flow automation covers what to build in Flow in the first place.
What "agent-ready by default" leaves to you
The developer post says "Every Shopify store is agent-ready by default". Every Liquid and Hydrogen storefront and checkout now exposes WebMCP tools, so browser agents can search, change the cart and complete checkout after buyer approval. I explain the standard in WebMCP for online stores.
That is plumbing. It does not make your product data complete or your policies clear. Two admin features deal with that side:
- Catalog eligibility. A new admin view shows whether your store qualifies for Shopify Catalog and links to fixes.
- Knowledge base. Under Sales channels > Agentic, you review and publish facts agents receive, such as return windows and shipping destinations. The merchant post says "Agents that ask Shopify about a store only get facts the merchant has published".
Neither edition post mentions UCP, but the edition page lists two UCP items for developers:
/buy. A changelog entry of 28 October adds cart and checkout permalinks at/buyfrom UCP version 2026-08-25./cartlinks keep working as the legacy format./buydoes not yet support selling plans, line item properties, cart notes or cart attributes, so links for subscriptions or personalised products should stay on/cart./ask. The edition page describes an endpoint that "answers questions about a store, grounded in facts published by the business". Shopify's agent docs describe Ask as a UCP draft capability, outside dated UCP releases, so treat it as unsettled.
Hydrogen, Vercel Shop and the new theme architecture
Hydrogen is now generally available and, in Shopify's words, "works with any framework and any runtime". Vercel Shop, an open source Next.js template built on the Hydrogen SDK, is also generally available. If you were already considering a custom storefront, my post on headless Shopify with Next.js covers that decision. Neither is a reason to leave a theme that works.
The new theme architecture moves page structure into the Liquid template, with blocks, typed contracts, partial updates, built-in Tailwind and markdown files that guide agents. Merchants can edit these themes with Sidekick in Canvas, which is in early access. I found no migration deadline for existing themes, so watch this one for now.
A sensible order for the next few months
- Before Cyber Week: read-only checks. List your public apps, script tags and anything reading discounts or barcodes. Ship nothing.
- December to mid-January: move custom apps to API 2026-10 and fix what the checks found.
- By 1 March 2027: script tags gone from storefront pages.
- By 1 April 2027: every public app you depend on confirmed on expiring tokens.
If an app needs replacing, an App Store option that does the job is often the better answer. When none exists, my Shopify app plans start from $2,000 for an MVP with one focused feature. That is a starting price, with a fixed quote after a short brief.
FAQ
Does the Shopify Fall '26 Edition break my custom app?
Not by itself. The January 2027 token deadline applies to public apps, and Shopify says custom and merchant-created apps are not affected. Your custom app can still be caught by ordinary upkeep: script tags stop running on storefront pages on 1 March 2027, API 2026-01 stops being accessible on 16 January 2027, and API 2026-10 changes how discounts and variant barcodes should be read.
Do I need to do anything to make my Shopify store agent-ready?
Technically, no. Shopify says WebMCP tools are present on every Liquid and Hydrogen storefront and checkout, and the checkout tools need no merchant configuration. The useful work is in your content: check the Catalog eligibility view, review the facts in Knowledge base under Sales channels > Agentic, and fill in product attributes and policies. An agent can only repeat what you have published, so accuracy is where your time goes.
Can a third-party app manage my Shopify Flow workflows now?
Not through the new automation APIs. Shopify's changelog says third-party apps are prevented from using them directly, and direct use needs the write_automations scope, which Shopify must approve. What is open is your own agent working on your own store through AI Toolkit. Anyone offering to manage Flow for you still works inside your admin, so give them a role that fits and keep the version history in view.
If you want the Fall '26 changes checked against your own store, send me a short brief: the custom apps and public apps you depend on, what each one does, the API version if you know it, and what breaks if it stops. You can start from the Shopify app MVP plan, or read about my Shopify app development service.


