Shopify DotDev 2026: what actually shipped for developers

Shopify's developer event grew up this year. DotDev 2026 ran July 21 and 22 at the Automotive Building in Toronto, the first time the format stretched past a single day, and the first time it sold out. It replaces what used to be called Editions.dev.

Conference recaps are a bad way to learn what changed, though. Keynote slides describe direction; the shopify.dev changelog describes shipped code. So this post works from the changelog. Three substantial things landed on July 21 itself, a pile of smaller-but-breaking changes landed around them, and the difference between "generally available" and "developer preview" matters more this release than usual.

1. Liquid templates can compose pages now

The headline theme change, and the one that will reshape how themes are structured, is the Liquid July '26 developer preview. It adds two tags:

• {% block 'name', param: value %}...{% endblock %} renders a theme block straight from a template. It behaves like {% render %}, except the body content between the tags is available inside the block as {{ block.content }}. Blocks compose by nesting.
• {% partial 'name' %}...{% endpartial %} names a region of server-rendered HTML that JavaScript can refresh on its own, without a full page load and without moving rendering into a client-side framework.

Put together, page structure lives in one .liquid file that a human (or a coding agent) can read top to bottom. Shopify's own reference implementation, the skeleton theme rc-v2.0.0, has no sections folder, no JSON templates, and no schema presets at all. That is a genuinely different theme architecture, and it is worth understanding before it stops being a preview.

2. Events took another step toward replacing webhooks

Shopify's next-generation Events are the intended successor to webhook topic subscriptions. Instead of subscribing to products/update and receiving every product change with a fixed payload you then diff, an Event subscription declares which entity you care about, which lifecycle action, which fields must change to trigger delivery, and what GraphQL shape you want back.

The July 21 update added topics for Order, Collection, InventoryItem, InventoryShipment, and Location, and, more interestingly, metafield change triggers on Product, Order, Customer, Collection, and Location. ProductVariant metafields come through the Product topic. Both $app metafields and regular metafields are supported, subject to the usual access scopes.

If your app currently subscribes to every product update purely to notice that one metafield moved, that whole category of waste is what this removes.

3. Apps got a real analytics layer

The third July 21 entry, full-stack capabilities to power app analytics, is the one most likely to delete code you already wrote. Apps can now mark metafields analytics-queryable so they become ShopifyQL dimensions, emit App Events that are queryable alongside Shopify's own commerce data, query it all through a versioned ShopifyQL API with schema-level reference docs, and embed the result with web components (<s-shopifyql-metric-card>, <s-metrics-bar>) that handle charting and locale formatting for you.

There are two enrichment APIs on top: an Annotations API so your app can mark events on a merchant's charts (needs the read_analytics_annotations and write_analytics_annotations scopes), and a Metric Targets API so merchant-set goals are readable programmatically. It lands in API version 2026-10.

The quieter changes that will break something

Announcements get the attention. Deprecations get the 3am pager. These all landed in the same window and none of them were on a keynote slide:

The pattern in that table is worth naming: Shopify is tightening. Queries that used to fail silently now error. Billing is consolidating. Checkout extension APIs that let you block the buyer journey imperatively are being replaced. Loose behaviour that themes and apps quietly depended on is being made explicit, which is good for the platform and briefly painful for you.

Day two: the agentic half

The second day picked up the thread from the Spring '26 Edition: the Catalog API as the discovery layer, the Universal Commerce Protocol as the transaction layer, and Shopify Functions as the way merchant checkout customisations survive when the checkout is being driven by an agent rather than a human clicking through a storefront.

None of that is new since June, but the framing sharpened. If a shopper buys through ChatGPT, Copilot, Google's AI Mode, or Gemini, your carefully built storefront is not in the loop. Your Functions still are. That is a strong argument for pushing commerce logic down into Functions rather than up into theme JavaScript, and it is the kind of architectural call that outlives whichever framework you are using this year.

What to actually do this week

1. Read the three July 21 changelog entries end to end. They are short, and they are the source of truth over any recap, including this one.
2. Clone the skeleton theme rc-v2.0.0 branch and read templates/product.liquid. It takes two minutes and it is the clearest statement of where theme architecture is heading.
3. Audit your app's webhook subscriptions. Every topic you subscribe to only to diff a payload is a candidate for an Event trigger once Events leaves preview.
4. If your app ships a dashboard, price out how much of it ShopifyQL plus <s-shopifyql-metric-card> could delete before you build more of it.
5. Put the 2026-10 removals in the table above on a calendar. Silent breakage on a version bump is the worst kind.

Read together, the release says something consistent. Structure is moving back into Liquid where it is legible. Data delivery is moving from "send everything, sort it out downstream" to "declare precisely what you need." And the buyer is increasingly not a person looking at your markup. In all three cases the mechanical work shrinks and the judgment about how a store is architected gets more valuable, which is the same shift we wrote about after Spring '26, now with a changelog behind it.