If you work with Shopify stores as a developer or rely on a developer to keep yours running, 2026 is not a routine maintenance year. Three overlapping platform shifts landed at once: the mandatory sunset of Shopify Scripts, the release of Shopify CLI 4.0, and the opening of the Model Context Protocol (MCP) to any developer without prior approval. Each one changes how Shopify stores are built and maintained at a technical level.
Key takeaways
- Shopify Scripts were permanently shut down on June 30, 2026. Any store still using them for discounts, shipping, or payment logic lost that functionality on that date.
- Shopify Functions (compiled WebAssembly modules) are the mandatory replacement and deliver sub-5ms execution with no cold starts.
- Shopify CLI 4.0 (released May 21, 2026) introduced semantic versioning with automatic minor and patch upgrades.
- The Dev MCP server gives AI coding agents like Claude Code, Cursor, and Gemini CLI direct access to Shopify's GraphQL schemas and live store data.
- Agentic Storefronts went live by default on March 24, 2026, making eligible stores discoverable inside ChatGPT, Copilot, and Google AI Mode.
The definitive end of Shopify Scripts
Migrating from Scripts to Functions was the most urgent technical project in the Shopify ecosystem during the first half of 2026, and the deadline never moved.
Shopify officially retired all legacy Scripts on June 30, 2026. Before that, as of April 15, 2026, editing or publishing any Script became impossible. Stores that had custom discount logic, shipping rules, or payment gating through Scripts entered a frozen state: the code kept running but could not be touched. Any bug surfacing between mid-April and the end of June had no fix path inside the Script Editor.
What made this dangerous was invisibility. As one agency described it, Scripts tend to be set up once, often years ago by someone who has since left, and they run quietly in the background until they do not. The merchants most at risk were the ones who did not know they had active Scripts.
The migration is not a translation exercise. The migration requires rebuilding logic in a new programming model, not simply translating Ruby to another language, which means it takes real development time to do correctly. A focused migration of 5 to 15 scripts takes 8 to 14 weeks including scoping, development, QA on a dev store, and a production cutover with monitoring.
Why Shopify Functions is a real upgrade, not just a replacement
Functions run at the Shopify infrastructure level. Unlike Scripts, which ran in a sandboxed Ruby environment on Shopify's servers, Functions are compiled WebAssembly modules that execute inside Shopify's platform infrastructure. The good news is that Shopify Functions are a genuine upgrade: better performance, more extension points, testable input/output architecture, and configuration-driven business rules make the post-migration platform more capable than what Scripts ever offered.
For simple to moderate logic, many public apps expose Shopify Functions through a no-code or low-code interface, so you can often configure rules yourself in the Shopify admin. For complex or highly custom logic, you will likely need a developer or agency to build a custom app with Functions.
If your store is still on Scripts (or you are not sure), start with the Shopify Scripts Customizations Report inside your admin. It lists every active Script by type: Line Item, Shipping, or Payment. From there, prioritize by revenue impact before writing a single line of new code.
Shopify CLI 4.0 and the new development environment
Shopify CLI 4.0 (released May 21, 2026) introduced semantic versioning with automatic minor and patch upgrades, and removed deprecated flags and commands. For teams running CI/CD pipelines against Shopify's tooling, this matters: the old manual update cycle is gone, and version pinning now follows a standard SemVer contract.
The Developer Dashboard also received a significant overhaul alongside CLI 4.0. The Developer Dashboard was overhauled with time-series log visualisation, group-by filtering, app health gauges, and a unified view across dev stores, client transfer stores, and collaborator access. Web vitals monitoring for LCP, INP, and CLS was added on June 11, 2026, and app automation tokens enable CI/CD.
Other Spring '26 developer improvements worth noting:
- Admin API bulk queries are up to 4x faster with parallel reads.
- You can build lightweight apps with no backend using App Home directly in the admin.
- Webhooks can fire only on specific field changes, with custom GraphQL queries, and GraphQL and bulk operations run from the CLI with automatic auth.
- All new public apps are required to use GraphQL Product APIs, reinforcing Shopify's commitment to a faster and more efficient development framework.
One breaking change to plan for: Shopify is expanding expiring offline access tokens to all public apps using the Admin API. Starting January 1, 2027, public apps still using non-expiring tokens will get authentication errors, while custom apps and merchant-created apps are unaffected. If you maintain or commission a public app, this token migration is the next deadline on the calendar after Scripts.
Dev MCP: AI moves into the developer's environment
This is the shift most developers are still absorbing. The Shopify Dev MCP server connects AI coding agents directly to Shopify's platform data, not just its documentation.
One plugin gives a developer's editor (Cursor, Claude Code, Codex, Gemini CLI, Hermes, VS Code, and more) direct access to Shopify's reference guides, live store data, and admin tools, in a form Shopify describes as token-efficient.
The Shopify AI Toolkit, open-sourced on April 9, 2026, is the developer-side of the same MCP infrastructure. It is a free, MIT-licensed plugin that connects AI coding agents like Claude Code, Cursor, VS Code, Gemini CLI and OpenAI Codex directly to Shopify's documentation, GraphQL schemas, and live store operations through the Shopify CLI.
Practically, a developer working in Cursor can now validate GraphQL queries against live schema, run bulk product operations, and scaffold Hydrogen components without switching context to a browser tab. Shopify Dev MCP now supports all API versions and uses fewer tokens per response.
For merchants evaluating Shopify developers or agencies, this shift is relevant to hiring criteria. A developer who is not using MCP-integrated tooling in 2026 is working slower than one who is.
Agentic Storefronts: your store is already in ChatGPT
The developer platform changes above feed into a larger commercial shift. On March 24, 2026, Agentic Storefronts went live by default for eligible US merchants, making 5.6 million stores automatically discoverable inside ChatGPT, Microsoft Copilot, Google AI Mode and the Gemini app.
The Universal Commerce Protocol (UCP) is the standard Shopify co-developed with Google. It is the infrastructure for how AI agents transact with merchants, covering the full commerce journey from discovery to carts to checkout. UCP has broad industry support from Amazon, Meta, Microsoft, Salesforce, Stripe, Etsy, Target, and Wayfair.
For a developer building on Shopify today, UCP and the Catalog API are no longer gated behind an approval process. Developers don't apply for UCP access; they register their agent profile in the Developer Dashboard and call the public MCP endpoint. From there, they can build across the full flow, from product search to checkout.
Comparison: Shopify Scripts vs. Shopify Functions
| Dimension | Shopify Scripts (deprecated) | Shopify Functions (current) |
|---|---|---|
| Language | Ruby (sandboxed) | WebAssembly (Rust, JavaScript, AssemblyScript) |
| Execution speed | Variable, server-side Ruby | Sub-5ms, no cold starts |
| Status | Stopped June 30, 2026 | Active, actively expanded |
| Testability | Manual, limited | Input/output unit testing in dev store |
| Extension points | Line item, shipping, payment | Discounts, shipping, payment, cart transforms, fulfillment, and more |
| Configuration | Hardcoded in Ruby | Configuration-driven via metafields/UI |
| Who builds it | Developer only | Developer (custom) or no-code app (simple rules) |
What this means for merchants, not just developers
If you are a store owner rather than a developer, here is what these platform shifts mean for you in practical terms:
- Audit first. Use the Scripts Customizations Report to know what is running in your store before you talk to a developer. Going into a scoping call without this inventory costs you money.
- Your apps need a review. Any public app using non-expiring Admin API tokens must be updated before January 1, 2027. Ask your developer or app vendor directly whether their apps are on the expiring token model.
- Dev MCP speeds up development. Developers using MCP-integrated editors can deliver faster and with fewer context-switch errors. When evaluating developer proposals, ask whether they use the Shopify AI Toolkit or Dev MCP as part of their workflow.
- Your products already show up in AI. If your store is eligible and you have not explicitly opted out, Agentic Storefronts is already active. Your catalog structure, metafields, and product data quality now affect AI-agent recommendations, not just Google rankings.
For a deeper look at how to optimize your store for AI discovery and structured data, the Shopify developer services page covers the specific implementation work involved.
Summary: the key dates you cannot ignore
- April 15, 2026: Shopify Scripts editing and publishing locked permanently.
- May 21, 2026: Shopify CLI 4.0 released with semantic versioning.
- June 11, 2026: Web vitals monitoring (LCP, INP, CLS) added to Developer Dashboard.
- June 30, 2026: All Shopify Scripts stopped executing. No grace period.
- January 1, 2027: Public apps using non-expiring Admin API tokens will receive authentication errors.
If any of those dates trigger a gap in your current setup, that gap needs a developer with current platform knowledge, not a generalist who last touched Shopify two years ago. The platform has moved too far, too fast for that to be a safe option in 2026.
Frequently asked questions
What is Shopify Functions and how does it differ from Shopify Scripts?
Shopify Functions are compiled WebAssembly modules that run inside Shopify's own infrastructure with response times under 5ms and no cold starts. Shopify Scripts were sandboxed Ruby code that was permanently retired on June 30, 2026. Functions support more extension points, can be tested in a development store, and allow configuration-driven business logic.
What is the Shopify Dev MCP and how does it help developers?
The Shopify Dev MCP (Model Context Protocol) is a server that connects AI-assisted code editors such as Cursor, Claude Code, or Gemini CLI directly to Shopify's documentation, GraphQL schemas, and live store data. It lets you validate queries, run bulk operations, and scaffold components without leaving the editor, which cuts context-switching errors and speeds up development.
Will my Shopify apps be affected by the 2027 access token change?
If you run public apps that use non-expiring offline tokens to reach the Admin API, yes. From January 1, 2027, those apps will start receiving authentication errors. Custom apps and merchant-created apps are not affected. Ask your developer or app vendor directly to confirm whether their apps already use the expiring token model.