Shopify DotDev 2026: Developer Takeaways & Shopify Plus Insights
Danny Ginn and I spent a couple of days in Toronto at Shopify DotDev 2026, representing 85SIXTY and connecting with the broader Shopify developer ecosystem.
As a technical lead, I always go into these events looking for the practical stuff. What can we actually build with? What’s changing under the hood? And what does it mean for the merchants we’re supporting?
This year’s event had plenty to dig into, especially around Shopify’s evolving developer tools, app architecture, APIs, and AI.
But for me, the biggest value wasn’t necessarily the announcements. It was getting hands-on with the technology and talking directly with the engineers building it.
Day 1: Getting Hands-On with Shopify's Latest Developer Tools
Day one was easily the highlight.
Shopify led the sessions, and we spent hours in the weeds doing code-alongs, downloading repositories, and testing capabilities like Next Generation Events and static app architectures.
These weren’t just demos. We were actually building things, seeing how the pieces fit together, and asking questions about how they would work in more complex environments.
Having the actual Shopify engineers in the room to answer highly specific questions about things like webhook reconciliation was huge. You just don’t get that from reading docs.
It’s one of the things I value most about being part of the Shopify partner ecosystem. Direct access to the people building the platform helps us make better technical decisions for the merchants we support.
A couple of technical areas stood out.
Next Generation Events: More Control Over Shopify Integrations
Shopify’s Next Generation Events introduces a more flexible approach to handling platform events, including field-level triggers, custom GraphQL payloads, and filtering.
For developers working on complex Shopify integrations, this is worth paying attention to.
When you’re connecting Shopify to an ERP, PIM, CRM, or other business systems, reliable event handling matters. You’re often managing large amounts of data across multiple platforms, and not every system needs to receive every update.
Having more control over what triggers an event and what data gets delivered can help reduce unnecessary processing and simplify integration architecture.
It’s the kind of improvement that might not make for the flashiest keynote, but can have a meaningful impact on how we build and maintain Shopify solutions for clients.
Static App Architecture: Do We Really Need Another Backend?
Another interesting area was Shopify’s work around static app architectures.
The concept is pretty straightforward: not every custom Shopify app experience needs its own traditional backend.
Shopify is making it possible to build certain app experiences using more of the platform’s native capabilities, including Metaobjects, Shopify Functions, and UI extensions.
That opens up some interesting possibilities.
For merchants, fewer moving parts can mean less infrastructure to maintain, fewer potential points of failure, and potentially lower long-term development costs.
It doesn’t mean every complex application should suddenly be rebuilt this way. There are still plenty of use cases where custom backend infrastructure makes sense.
But it’s another option we can evaluate when designing solutions, particularly when a merchant’s requirements can be handled effectively with Shopify’s native capabilities.
And that’s a direction I like seeing.
AI Is Changing Shopify Development, but Architecture Still Matters
AI was another major theme throughout DotDev, which probably surprises no one.
Shopify continues to invest in AI-assisted development and agentic commerce, including tools that help developers build faster and infrastructure that helps products become accessible to AI-powered shopping experiences.
There’s a lot of opportunity here, but I think it’s important to separate what’s possible from what’s practical.
AI can help accelerate development, generate code, and reduce some of the repetitive work involved in building ecommerce experiences.
But it doesn’t replace the need for good architecture.
You still need to understand how your data is structured, how systems communicate, where the dependencies exist, and what happens when something fails.
That becomes even more important as merchants adopt AI-powered tools and connect more systems across their commerce operations.
Why Structured Product Data Matters for AI Commerce
One of the broader shifts Shopify is making involves how products are discovered through AI-powered shopping experiences.
Technologies like Shopify Catalog and the Universal Commerce Protocol are part of Shopify’s investment in making commerce information more accessible to AI agents.
For merchants, this puts even more importance on the quality of their product data.
Product attributes, descriptions, availability, variants, and categorization need to be accurate and consistently structured.
That’s important for traditional ecommerce operations, but it’s also increasingly relevant to SEO and AI search visibility.
If an AI shopping assistant is trying to identify the right product for a customer, it needs enough reliable information to understand what that product is and how it compares with alternatives.
From an engineering perspective, this reinforces something we’ve been focused on for a long time: good data architecture is foundational to good commerce experiences.
AI doesn’t change that. It makes it more important.
Shopify - Universal Commerce Protocol
Day 2: Learning from the Shopify Partner Ecosystem
Day two shifted toward partner-led sessions, with agencies and app developers sharing what they’ve been building.
It was awesome to see the scale and complexity of some of these projects, particularly around B2B commerce, automotive, and more specialized implementations.
But I also think there’s a missed opportunity for the ecosystem as a whole.
A lot of presentations naturally focus on the finished product. Here’s what we built, here’s what it does, and here’s how successful it was.
That’s valuable, but as engineers, we often learn the most from the messy middle.
What broke? What didn’t scale the way you expected? What architectural decisions did you have to revisit? What creative workarounds were required to get the project across the finish line?
Those are the conversations I want more of.
Complex Shopify development rarely follows a perfectly straight path. Whether you’re dealing with custom integrations, B2B requirements, international storefronts, or complicated product data, there are always decisions that require some real engineering judgment.
Sharing those technical hurdles helps everyone in the ecosystem get better.
And ultimately, that benefits the merchants relying on the platform.
What Does Shopify DotDev 2026 Mean for Merchants?
For merchants running on Shopify or Shopify Plus, my biggest takeaway is that the platform continues to give developers more ways to solve complex problems without automatically adding more custom infrastructure.
A few areas are worth evaluating:
- Integration architecture: Next Generation Events creates opportunities to rethink how Shopify communicates with ERPs, PIMs, CRMs, and other systems. For merchants with complex integrations, it’s worth reviewing whether newer event capabilities could simplify existing workflows.
- Custom app development: Static app architectures and native Shopify capabilities may reduce the need for custom backend infrastructure in certain use cases. The right approach depends on the requirements, but it’s worth considering before defaulting to a fully custom build.
- AI readiness and product data: As AI-powered product discovery evolves, merchants should pay attention to how product information is structured, maintained, and made accessible across systems. Clean, consistent data supports both existing commerce operations and emerging discovery channels.
- Long-term scalability: More features and more apps aren’t always the answer. Sometimes the better engineering decision is simplifying the architecture, reducing dependencies, or using more of what Shopify already provides.
None of these changes mean merchants need to rebuild their stores tomorrow.
But they do create opportunities to evaluate what’s working, what’s becoming unnecessarily complex, and where the platform may offer a better way forward.
Final Thoughts from Shopify DotDev 2026
Overall, it was a great trip.
I came away with a clearer understanding of where Shopify is heading, more confidence in the technical direction we’re taking at 85SIXTY, and a few new ideas we’re excited to explore with our clients.
The hands-on workshops were valuable, but having direct access to Shopify’s engineers and exchanging ideas with other developers was probably the best part.
There’s a lot happening across ecommerce right now, and it’s easy to get caught up in the next big announcement.
For me, the interesting part is figuring out what actually makes a difference once you start building.
That’s where the real work happens, and it’s what makes events like DotDev worth attending.
Leave a comment:
You must be logged in to post a comment.