Shopware Community Day 2026: Four Launches – and What They Mean for Your Shop

Three stages, 60 talks, more than 1,500 attendees and, at the end of the day, a whole lot of new insights. This time, the Shopware Community Day (SCD) on June 10, 2026 in Cologne was more than the annual gathering of the Shopware community. Attendees got a glimpse of the vision Shopware is pursuing for the future: moving away from a pure shop system towards infrastructure for a commerce landscape in which it is no longer just people doing the shopping, but increasingly AI agents as well. Let's get started – here is our take on what SCD 2026 delivered.

In short: Nobody needs to rebuild anything this week. What you can actually use right away is Shopware Payments, a payment processing solution built into the platform and based on PayPal, initially for Germany and Austria. Nexus and Copilot target integrations and admin work, while the Experience Studio is explicitly a research project. The most important preparation costs nothing: all Shopware users should keep their shop up to date and get their product data in order.

When Machines Go Shopping

In the keynote, Co-CEO Sebastian Hamann posed an uncomfortable question: What still makes a merchant interesting when software makes the purchase decision? His answer had two parts. For AI agents, what matters is whether a shop can be connected technically – for example, whether it provides machine-readable data and open interfaces. For people, on the other hand, the opposite matters: trust and, above all, a shopping experience that is memorable.

“Shopware's role is to help merchants act early in this transition, stay in control and turn uncertainty into opportunity."

– Sebastian Hamann, Co-CEO of Shopware

Behind this statement lies a thesis that ran through the entire SCD: in AI commerce, the winners are those who have their business context together – inventory, prices, customer relationships, order history. Today, for many merchants, this context is scattered across ERP, CRM, PIM and a good dozen other systems. That is exactly where the four new Shopware products presented in the keynote come in.

Four Products, One Architecture

all four innovations at a glance on Shopware

Nexus: An End to the Interface Patchwork?

Anyone who runs a shop knows the math: a considerable share of every project goes not into the shop itself, but into the connections around it. Connecting the inventory management system, syncing stock levels, sending invoices back – with every interface built and maintained individually. Shopware puts this share at a good half of the project effort. From our own experience with Xentral, Pickware and custom ERP integrations, we can say: that figure is about right.

Nexus is set to change that. Shopware's idea is an event-driven orchestration layer in Shopware that reacts to events. An order has come in, stock levels have changed, a return is reported – and the information is passed on to the connected systems. Instead of programming everything anew for each project, you configure workflows that survive updates and version changes. Announced at SCD 2025, Nexus has been running as an open beta since the beginning of the year and has now officially launched.

Important for managing expectations – and Shopware itself is quite clear about this: Nexus is not a migration tool, not a data warehouse, and it replaces neither ERP nor PIM. It doesn't move entire product catalogs; it connects the different systems. It is aimed at teams with a certain level of developer know-how. If you already know Shopware's own Flow Builder, you get its big sister here, so to speak: the Flow Builder automates workflows within Shopware, while Nexus orchestrates across different systems.

Copilot: From Explaining to Doing – in Beta

Shopware Copilot was already introduced last year. What's new are the agentic capabilities that Shopware has now released as a beta: the assistant creates promotions, changes hundreds of products in one go or translates shop content. Not on its own, but when it has been asked to. Every change starts out as a draft, a human reviews it, and only after approval are the adjustments finally applied. On top of that, there are defined role permissions, an allowlist of the data areas the assistant is permitted to access at all, and hosting on European servers.

This is a sensible step in terms of security. Anyone testing Copilot today has a diligent “clerk working under the four-eyes principle" at hand, not an autonomous employee. For the day-to-day operations of many shops, the former is probably the more useful one anyway.

Payments: The Most Tangible Innovation – with One Gap

With Shopware Payments, payment processing moves into the platform itself. Payment cards, Apple Pay, Google Pay, Klarna and the PayPal payment methods can now be managed where orders and data already reside; processing runs on PayPal's regulated infrastructure, and according to the provider, payouts are made within 24 hours. The whole thing is available immediately in Germany and Austria, with further EU countries and the USA to follow. Very important: Shopware explicitly emphasizes that nobody has to switch to Shopware Payments – existing payment providers will continue to work.

One thing is missing at launch, however: a published price list. Shopware speaks of transaction-based, competitive pricing terms. So far, specific costs are only available on request. Before Shopware merchants consider switching, they should therefore do a proper comparison: transaction fees per payment method and sale, payout schedule and refund costs – all compared with what your current payment service provider charges.

Experience Studio: A Look into the Lab

The fourth innovation presented was the Experience Studio, which focuses on emotion, trust and brand identity. Put simply: merchants describe the shopping experience they want and get a working frontend within minutes. The idea behind it makes sense – if agents take over the functional part of shopping, the human experience becomes the differentiator. However, Shopware itself calls it a research preview. Shopware already allows users to test the technology, experiment with prompts and generate their own shopping experiences.

Two Acronyms You Should Know

Beneath the four products lies the actual platform news of the day: 100 percent MCP coverage and UCP readiness. It sounds like tech jargon, but it affects the future of your visibility.

MCP (Model Context Protocol) is an open standard through which AI tools communicate with software. Full coverage means: practically everything you can do in Shopware can now also be done by an AI tool – within the permissions granted by the merchant. UCP (Universal Commerce Protocol) was introduced in early 2026 by Google, Shopify and others and governs how AI agents find products, fill shopping carts and pay – for example directly in Google's AI Mode or in Gemini, without the customer ever opening the shop website. “UCP-ready" means: Shopware shops are prepared for such channels.

The unspectacular truth behind it: no protocol in the world can help a shop with incomplete product data. Well-maintained attributes, Schema.org markup and a machine-readable overview such as llms.txt are the foundation on which these integrations will later build. We have described what this looks like in practice using our FAQ Professional plugin as an example.

What You Can Do Now – and What Can Wait

Stay up to date. The agentic building blocks are arriving piece by piece with the regular releases; the Agentic Commerce Sales Channel, for example, was already included in the April update 6.7.9.0. Shopware has also confirmed that there will be no new major release in 2026 – so if you are on a current 6.7.x version, you're in good shape and will automatically benefit from the developments. Our Shopware changelog provides an overview.

Clean up your data. Complete attributes, clean categories, structured content. This work pays off no matter which protocol ultimately prevails – and it's the part of the work nobody can do for you.

Take inventory of your interfaces. Which integrations are running, who maintains them, what do they cost per year? Without this overview, Nexus cannot be properly evaluated later. And with it, by the way, a lot of other things can be too.

Watch Payments, don't rush. Requesting terms is worthwhile as soon as a provider switch or consolidation is on the agenda anyway. Until then: if you're satisfied, there's no reason to hurry.

All in all, this Community Day was a statement of direction, not a mandatory task for shop operators. Shopware is transforming itself from a shop system into commerce infrastructure, promising that data and control will remain with the merchant. Whether Nexus really reduces integration costs and what Payments costs in the end will be shown by the first real-world projects. The homework that already pays off today is the same as before the keynote: current version, clean data, documented interfaces.

Want to know which of this is relevant for your shop and what can safely wait? Get in touch with us – we'll advise you honestly and straightforwardly.

Sources: Press release from shopware AG dated 06/10/2026 · Shopware Nexus · Shopware Payments announcement · t3n dated 06/10/2026

Shopware product news