Shopify DotDev 2026: The Platform Is Rebuilding For The Next Era Of Commerce

Shopify just held its biggest developer event yet, and it renamed itself while doing it.

Shopify DotDev, held on July 21 and 22, 2026 at the Automotive Building in Toronto, marked a clear break from the company’s previous Editions.dev format. For the first time, the event stretched across two full days instead of one, and it sold out. Shopify has not published an official explanation for the change, so the most reasonable reading is that last year’s single day could no longer contain everything on the roadmap.

That roadmap is overwhelmingly about AI. Almost everything demoed on stage traces back to the Winter ’26 Edition, which Shopify calls the RenAIssance Edition. It includes more than 150 updates across twelve product categories: Sidekick, agentic commerce, online store, retail, marketing, checkout, operations, the Shop app, B2B, finance, shipping, and the developer platform.

That is a lot of ground to cover. This article goes through each category in order so nothing gets left out.

Day 1: Where Shopify Reset The Developer Story

The Opening Frame Was Bigger Than A Product Keynote

DotDev opened with a Tobi Lütke and Harley Finkelstein fireside on the main stage, followed by Shopify leadership’s keynote and the Build Awards.

The official schedule makes the intent obvious. Shopify wanted the first hour to frame the event as a statement about the platform’s future, not as a cascade of feature notes. The rest of the day then moved through talks, workshops, breakouts, and product booths built around storefront development, apps, retail, B2B, marketing, analytics, and partner growth.

That format mattered because the agenda itself told the story. Shopify did not isolate “developer” topics in one corner and “commerce” topics in another. It put them together, which is exactly how the company seems to think about the platform now. If the roadmap is truly AI-first, then storefronts, apps, analytics, and operations all need to be speaking the same language.

Liquid Is Back At The Center Of Theme Development

One of the clearest signals from Day 1 came from Ben Sehl’s session, “Liquid: Back to the future.” Shopify’s own description says the company is simplifying the way themes are built and bringing Liquid back to the center, with theme architecture updates meant to support developers and coding agents alike. That is a meaningful shift because it suggests:

The theme direction was reinforced by Shopify’s developer changelog. Around the same period, Shopify introduced LiquidDoc for snippets and blocks, skeleton themes, block previews in the theme editor, and support for JavaScript and stylesheet tags in snippets. Those are not flashy changes on their own, but they point to a larger architectural preference: themes should be more modular, more structured, and less dependent on improvised workarounds that become hard to manage over time.

App Analytics Moved Closed To The Merchant Workflow

Day 1 also gave app developers something that has been missing for a long time: a native way to understand their own products inside Shopify.

In the session “The analytics layer: Programmable, embeddable, and built for your app,” Shopify described a model where app data belongs in Shopify Analytics and developers can model, query, and surface analytics through Shopify’s own stack. That matters because app teams have traditionally had to stitch together external dashboards to understand install behavior, feature adoption, and retention.

The changelog announcement went further. Shopify said its analytics layer is now a full-stack platform for apps, allowing developers to model, query, embed, and enrich analytics without managing their own infrastructure. It also said app data can flow into Shopify Analytics through analytics-queryable metafields and App Events. That changes the economics of app building. It makes measurement more native, reporting faster to set up, and product decisions easier to ground in the same environment merchants already use.

Events And Metafields Become More Precise

Another major theme on Day 1 was event-driven automation. Shopify’s changelog says apps can now subscribe to events for Order, Collection, InventoryItem, InventoryShipment, and Location, and can subscribe to metafield changes on Product, Order, Customer, Collection, and Location. ProductVariant Metafields are supported through the Product topic. That sounds technical because it is, but the implication is simple.

The schedule backed that up with a workshop titled “Replace noisy webhooks with precise Events.” That title is doing real work. It acknowledges a familiar problem in commerce software, where broad webhook patterns often force developers to pull in too much data and filter it later. Shopify’s answer is to make the event model more selective and more useful so apps can work from cleaner signals.

That same logic showed up in other workshop titles too, especially “Building dynamic, multi-class discounts with Functions” and “Composable collections: Build on the Collection Sources API.” Together, those sessions suggest Shopify wants more business logic to be expressed through platform-native primitives, with metafields, events, and Functions forming the core of how apps respond to a live catalog.

Shopify Spent Real Time On Security, POS, And B2B

Day 1 was not only about themes and app analytics. Shopify also devoted sessions to secure app building, customer accounts, POS, and B2B.

The breakout “How to build secure Shopify apps in 2026” framed security as a modern concern that includes authentication and AI workflows, which is a reminder that the developer environment itself is now changing. Security is no longer just about permissions. It is also about the tools people use to build.

On the customer side, “Why Customer Accounts are worth the upgrade,” and related account and extensibility sessions showed Shopify pushing developers toward richer merchant and buyer experiences. On the retail side, the conference spent time on POS, including “Why you should bet on POS” and “How POS UI extensions create better merchant experiences,” which reinforces that Shopify sees in-person commerce as part of the same platform story. On the B2B side, sessions such as “How to win bigger with B2B on Shopify” and “The opportunity of B2B and selling through Shopify Collective” made it clear that Shopify wants partners to think beyond standard DTC storefronts.

Day 2: Shopify Talked About Commerce Beyond The Storefront

The Second Day Shifted From Building Stores To Building Commerce Platforms

If Day 1 was about simplifying how the platform is built, Day 2 was about where commerce is going next. The lineup moved into agentic commerce, AI discovery, the Catalog API, and the Universal Commerce Protocol. That ordering was not accidental. It showed Shopify thinking about commerce as a system that increasingly extends beyond the storefront and into AI-mediated discovery and checkout flows.

The Catalog API Became The Discovery Layer

One of the most important sessions was “The next chapter of the Catalog API.” Shopify describes the new Catalog API as the foundation for developer-built shopping experiences, with product discovery, personalization, UCP checkout paths, and monetization all built around it. That is a much bigger role than a typical catalog feed. It makes product data the base layer for whatever comes next.

That view lines up with Shopify’s broader Spring ’26 messaging. Shopify says the Catalog API is UCP’s discovery layer and that it turns billions of products from millions of merchants into structured, queryable data across AI surfaces. The important word there is “structured.” If the future of commerce is going to include AI agents helping people shop, then product data has to be organized in a way that machines can reliably use.

Universal Commerce Protocol Was Presented As The Long Game

The session “UCP origin story: Behind the scenes of how and why we built it” made the protocol feel less abstract. Shopify says UCP is live across millions of Shopify stores and that the session would explain why commerce needed a protocol, what principles shaped it, and where it goes next. Another workshop, “Building shopping into any surface with Catalog & UCP,” went further and promised a search-to-buy loop that can be built into any surface.

Shopify’s Winter ’26 and Spring ’26 messaging makes the strategic point even clearer. The company says UCP is the open standard for how AI agents transact with merchants, and that it gives AI systems one shared language to understand commerce from discovery to checkout. That is one of the most consequential changes in the whole roadmap because it tries to standardize the merchant-AI relationship instead of leaving every platform to invent its own version of it.

Agentic Checkout Changed the Meaning of Customization

One of the most practical sessions on Day 2 was “How Shopify Functions help you succeed in agentic checkouts.” Shopify says Checkout UI extensions are restricted in agentic checkouts, but merchants can still support their most important customizations through Functions, additional fields, fees, and other platform capabilities. That is not just a technical note. It is a clue about how Shopify expects checkout to change.

They need customization that survives in machine-mediated flows. That is why Functions matter so much in the new world Shopify is building toward. They are part of the answer to a very modern problem: how to preserve merchant control when the shopper is no longer the only participant in the transaction.

AI Discovery Became A First-class Commerce Problem

Day 2 also made a strong case that AI discovery is now a real partner concern, not just a buzzword. The session “AI discovery: What’s real, what’s hype, and what to do” was framed as a mythbusting guide for partners, covering what to ignore, what Shopify already handles, and where real value still lives. The wording matters. Shopify is trying to separate practical opportunity from noise in a space that has generated plenty of both.

That message fits the larger merchant story too. Shopify’s AI commerce work now spans major AI channels, and its Agentic Storefronts let merchants sell through surfaces such as ChatGPT, Microsoft Copilot, AI Mode in Google Search, and the Gemini app.

In other words:

Agencies And App Builders Are Being Asked To Adapt Too

The final layer of Day 2 was ecosystem change. Sessions such as “The end of the one-size-fits-all storefront” and “Built to last: Building for the Shopify App Store in 2026” show that Shopify expects agencies and app developers to adjust their business models as AI changes what merchants need. The first session talks about moving from a single storefront pattern toward more personalized experiences. The second talks about app categories, AI commoditization, and what builders should stop building. That is a candid message for any ecosystem.

Why This event matters to Glood

For Glood.AI, DotDev 2026 did not introduce a new idea so much as it confirmed an existing one. The Shopify roadmap shown across both days pointed in the same direction Glood.AI is already moving towards: structured product data, event-driven workflows, stronger personalization, and shopping experiences that are designed to work across more than one surface. In that sense, the event was less a surprise than a validation.

What Shopify’s Roadmap Says About The Market

The larger signal from DotDev is that product discovery is moving into a different phase.

Shopify’s agentic commerce messaging suggests that shopping will not always begin on a storefront in the old sense. It may begin inside an AI assistant, through a structured catalog search, or in a checkout flow that is partially mediated by software. That changes the role of recommendation systems and merchandising layers. They are no longer just storefront add-ons. They become part of the infrastructure that helps products get found, understood, and purchased.

For a company like Glood.AI, that is an important shift. It means the work is not only about making a product page smarter. It is about helping merchants stay visible and relevant in a commerce environment where discovery is increasingly shaped by systems that read, sort, and interpret product data. The more Shopify standardizes that layer through products like Catalog API and UCP, the more the market moves toward the kind of logic Glood.AI is built for.

Conclusion

Shopify DotDev 2026 was less about announcing new features and more about revealing where the platform is headed. Across two days, Shopify connected themes, analytics, Events, Functions, the Catalog API, and the Universal Commerce Protocol into a single vision for AI-first commerce.

The message was consistent throughout: commerce is moving beyond the traditional storefront. Merchants will increasingly need systems that can serve both human shoppers and AI agents, making structured product data, event-driven automation, and native platform capabilities more important than ever.

For the broader Shopify ecosystem, this signals a shift in how apps and storefronts will be built. Success will come from working with Shopify's native architecture rather than around it.

For Glood.AI, the event served as a validation rather than a change in direction. The areas Shopify is investing in, from product discovery and merchandising to AI-driven shopping experiences, closely align with the problems Glood is already solving, reinforcing that its approach is becoming increasingly relevant as Shopify's platform evolves.