A year of Shopify, and what to build next

What has to be done by March 2027?

One deadline affects far more stores than the others: script tags. Shopify has announced that from October 1, 2026 the scriptTagCreate and scriptTagUpdate mutations return an error, and that on March 1, 2027 it will stop injecting script tags into storefronts. The same post says the deprecation applies to every API version, so pinning an old one does not defer it.

The practical question is which of your apps still work this way. Reviews widgets, popups, chat tools and older tracking tags are the usual suspects. Shopify names the replacements: a script that loads JavaScript becomes an app embed block shipped in a theme app extension, and a script that only collects analytics or conversion data becomes a web pixel.

You cannot fix this yourself if the app is a vendor's. What you can do is ask each vendor, in writing, whether the app uses script tags and when it moves, and take the answer into the decision about keeping it. An app with no answer by early in the new year is an app to replace.

• List every installed app and mark which inject something into the storefront.
• Ask each vendor whether they use script tags and what their migration date is.
• Check your own custom code and agency-built apps for scriptTagCreate or the REST ScriptTag resource.
• Test the store with the replacement in a duplicate theme before March, not in the week of.

Do our checkout and account extensions need changes?

Only if they declare metafields. Shopify's changelog says every metafield declaration in a Checkout UI or Customer Account UI extension needs an owner_type for API version 2027-01 and later, and that deployments without it will be blocked. Adding it is optional on 2026-10, so you can do it early and quietly.

Extensions that declare no metafields are unaffected. If one namespace and key applies to more than one resource type, the post says to write a separate declaration for each. It is a small change per extension, which is exactly why it gets missed: nobody schedules a ticket for a one-line edit until a deploy fails.

Customer accounts are a related area to look at. Shopify has deprecated legacy customer accounts, and since July 30, 2026 it requires the shopify-account component in the header of themes submitted to the Theme Store. That requirement applies to theme developers, not to your live store, so treat it as a signal about where login is heading rather than a task.

Should we rebuild on the new Hydrogen?

Almost certainly not this year, unless the front end is already your constraint. Shopify's Hydrogen 2026-10 announcement says the new Hydrogen is generally available, works with any JavaScript framework, and is now a library you add to an existing app rather than a framework you build on. It ships with React Router and Next.js starters, you can host anywhere, and Oxygen stays free.

The same post says existing storefronts keep working and that there is nothing you need to do today. That sentence is the whole planning guidance. General availability makes headless easier to start. It does not make it cheaper to own: you still lose the theme editor, you still replace every script-injected app, and you still maintain a codebase. We covered that trade in do you actually need headless Shopify, and the new release does not change its answer.

There is one useful consequence. If you already have a Next.js application for content or an app, adding commerce to it is a smaller decision than it was. That is a real case. A theme with a slow page is not.

Is it worth preparing for AI shopping agents?

Prepare cheaply, because the cost is mostly work you should do anyway. In October Shopify announced that one Shop MCP connection lets an agent search Shopify Catalog, build carts and create a checkout at the store selling the product. For signed-in shoppers, checkout can use saved addresses and Shop Pay. The post says orders placed this way appear in the merchant's admin like any other order.

The same post does not say whether merchants must opt in or which plans are eligible, and we have not verified either. Read the post and your admin before assuming you are in or out.

What is clear is that an agent can only recommend what it can read. Product titles that state the actual product, variant options that are structured rather than buried in a description, accurate availability and clear shipping and returns terms all help, and all of them help human shoppers and search engines too. We wrote the checklist in preparing a Shopify store for an AI shopping agent. Do that before anything that is specific to one agent protocol.

What should we ignore?

Developer previews. The changelog this quarter includes Liquid blocks and partials as a developer preview, and Hydrogen spent months in preview before this month's release. A preview is Shopify asking developers for feedback. It is not a reason to restructure a production theme, and anything built on one can change before it ships.

Also ignore the instinct to treat each edition as a to-do list. An edition is a catalog of things Shopify built, and most of them are irrelevant to any one store. Our approach is in reading the summer edition: what to act on and what to ignore: pick the two items that touch your revenue or your risk, and leave the rest.

What would we build, in order?

For a typical store doing its own merchandising on a theme, the order below keeps risk low and spend proportional. Each step is useful even if the next never happens.

• Now: audit apps for script tags and ask vendors for dates. This has a hard deadline.
• Now: add owner_type to metafield declarations in any checkout or customer account extension.
• Next quarter: clean the catalog (titles, variants, structured attributes, shipping and returns copy). It helps search, feeds and agents together.
• Then: move any remaining custom storefront JavaScript into theme app extensions and web pixels, so the theme stays maintainable.
• Only if the front end is the proven constraint: scope a headless pilot on one route, with a performance budget and a plan for the theme editor.

What this does not cover

This is a read of what Shopify's changelog said in the last three months, written on October 16, 2026. It is not a full list of deprecations: the same changelog also covers removals scheduled for API version 2027-01 (for example, the automaticDiscounts query) that matter to anyone with custom discount or data code, and your developer should read the full release notes for the version you target.

We would rather give you a short list you will do than a long one you will file. If your store has custom code or several agency-built apps, a one-day review of the first two steps is usually the most useful money to spend before the year ends. We do that kind of work under our Shopify build services.

Questions this raises

Read next

• Shopify build services
• Theme app extensions: apps that do not touch your code
• Preparing a Shopify store for an AI shopping agent