I attended the fifth SCUC – my third visit overall. Unlike a regular conference with hundreds or even thousands rushing through crowded halls to attend one-sided presentations, SCUC’s format in which themes are proposed and presented by the participants results in compelling panels, presentations, and open discussions. The mixture of Developers, PMs, ecommerce agencies and representatives, Shopware staff from all kinds of departments keeps the discussions grounded in reality rather than purely technical.

And then there’s the childcare. A lot of tech events claim to be „like a family,“ but SCUC takes this idea quite literally. I came with my daughter for the second time, and seeing familiar faces you saw in person the year before, getting to know people I only bumped on Zoom or Github in a kid friendly environment makes it all the more charming.

Now, my highlights.

Revamped Shopware CLI

Soner presented his work on an enhanced development workflow combining Docker and the Shopware CLI. The goal is making Shopware setup faster, and get a store running in a few minutes, with a fewer commands than today. The CLI is being expanded to consolidate a lot of console commands, making the whole setup process significantly more intuitive. Very promising stuff, especially for developers onboarding new projects.

An honest discussion about Shopware vs. Shopify

Agencies shared how they handle client expectations — getting a nice-looking shop ready fast without spending too much cash, while often underestimating the complexity of what they actually need. Developers, on the other hand, tend to underestimate what is in my opinion Shopify’s main selling point: a low friction onboarding process. Speaking as a former Shopify store owner/developer: you hand over a credit card and within a few months (if not weeks) you can have your store live – and then you realize key features are missing, and they will either cost money as a third party app or dev time. It is an open, never-ending discussion of pros vs. cons. As a Shopware Developer, my main takeaway is that your code is only as good as the solution it provides to the client.

Shopware Nexus – a marketplace for reusable integrations

Nexus is Shopware’s answer to the endless cycle of building custom middleware to connect Shopware with ERPs, CRMs, PIMs, and payment systems — and then maintaining and debugging it forever.

The idea is to replace all of that with a native, event-driven orchestration layer. Something happens in your store — an order comes in, a customer signs up, a return is processed — and Nexus routes that event to wherever it needs to go: Slack, your accounting system, an API endpoint. The marketplace angle is the „build once, reuse everywhere“ part: instead of rebuilding the same integration patterns for every client project, agencies can create standardized, reusable workflows. Less custom development, fewer things breaking during upgrades, lower long-term costs. It’s currently in beta, with a broader release expected later this year/early next year.

Caching in Shopware: The Big Picture

A solid technical session on the different cache layers in Shopware. As a backend developer it was useful to get a clearer mental map of how caching actually works — not just in Shopware specifically, but the broader concepts. The kind of session where you leave with a slightly better understanding of something you thought you already understood.

Speckit and Spec-Driven Development

Speckit is built around spec-driven development — the idea that the most valuable thing a developer can do isn’t write code, but precisely define what the code should do. In an AI-assisted world, that is a groundbreaking shift. The tool helps translate client requirements into structured specifications that can then guide AI-generated code and documentation. The quality of the output depends on the quality of the spec – how detailed and well organized the dev’s input is.

If I’m not being replaced by a machine in the next five years (fingers crossed), this feels like the kind of tool I’ll actually be using. Not to write less code necessarily, but to write better specs — and let the AI handle more of the implementation. It’s a different way of thinking about the job. Promising? Absolutely. A little unnerving? Definitely.

Other articles from this category