Shopware introduced four connected products at Community Day 2026 and said its commerce core now provides 100% MCP coverage and Universal Commerce Protocol readiness.
The launches are Shopware Nexus, an event-driven integration layer; an agentic Shopware Copilot; Shopware Payments; and Experience Studio, a research preview for generating commerce frontends and story-led shopping experiences.
The four-product list is the release headline. For B2B commerce teams, the stronger buyer claim is that Shopware wants to keep data, business rules, agent actions, payments, and customer experience inside one merchant-controlled context layer.
Key Takeaways
- Shopware announced Nexus, Copilot, Payments, and Experience Studio at Community Day 2026.
- The company says its commerce core now has 100% MCP coverage and is ready for Universal Commerce Protocol.
- Shopware reports 60% faster response times and 10x faster deployments on Shopware PaaS.
- Nexus is intended to replace fragmented middleware and reduce integration costs by 40%.
- Shopware Payments is available in Germany and Austria, with the EU and United States planned next.
How Shopware’s Four Products Fit Together
Shopware Nexus is the context layer. It synchronizes data and events across systems such as ERP, CRM, and PIM, then supplies that joined context to Copilot and other workflows. Shopware says merchants operate across more than 15 disconnected tools on average and can spend up to 52% of implementation effort wiring systems together.
Copilot is the action layer. It moves from answering questions to executing workflows while using role restrictions, entity whitelisting, and draft-and-review controls. Shopware Payments closes the transaction loop through PayPal infrastructure, while Experience Studio is intended to turn prompts into functional storefront experiences.
The syndicated launch release presents the four products as one architecture. That framing matters because a capable agent cannot safely price, recommend, or transact when catalog data and business rules disagree across systems.
100% MCP Coverage Is the More Important Claim
MCP coverage turns commerce functions into tools that approved agents can call. Universal Commerce Protocol addresses how agents and businesses can work across discovery, buying, and support. Together, the protocols make Shopware’s core accessible to AI-driven commerce workflows rather than limiting AI to a storefront assistant.
When we covered Feedonomics Agentic Catalog Exports, the gap was product data prepared for AI surfaces. Shopware is addressing the layers around that feed: the internal context, workflow execution, payments, and customer-facing experience.
Our read: 100% MCP coverage is not automatically an advantage. The advantage appears only when a merchant can expose the right action, with the right data, to the right agent, while preserving pricing rules, approval paths, customer permissions, and an audit trail.
That makes the launch relevant to teams using our framework for choosing a B2B ecommerce platform. Agent compatibility now belongs beside ERP integration, catalog complexity, pricing logic, and total cost of ownership in the platform test.
What B2B Commerce Teams Should Test
- Test a complex account. Ask an agent to handle contract pricing, approval limits, regional availability, and a configurable product in one workflow.
- Inspect the context source. Confirm which ERP, CRM, PIM, and commerce fields informed every recommendation and action.
- Validate permission controls. Check role restrictions, entity whitelisting, human review, and the ability to block high-risk transactions.
- Measure integration work. Compare Nexus’s claimed 40% integration-cost reduction against the connectors and custom logic your stack actually requires.
- Protect the human experience. Track whether agent-assisted buying improves conversion without increasing corrections, disputes, or the agentic commerce trust tax.
Shopware is not merely adding an AI feature to a commerce platform. It is presenting a full architecture for agents that discover, reason, act, and transact. B2B buyers should judge it on whether merchant control survives that entire chain.
Frequently Asked Questions
Shopware introduced four connected products: Shopware Nexus, an agentic Shopware Copilot, Shopware Payments, and Experience Studio. The products are designed to join business context, AI-driven actions, payments, and customer-facing commerce experiences.
Shopware says every action in its commerce core is accessible to AI tools and agents through Model Context Protocol. Merchants still need to decide which actions each agent can call and how permissions, approvals, logging, and rollback are enforced.
Shopware Nexus is a native, event-driven orchestration and synchronization layer. It is designed to connect fragmented systems such as ERP, CRM, and PIM, automate data mapping, and provide joined business context to commerce workflows and AI agents.
Not yet. Shopware says its PayPal-powered native payments product is currently available in Germany and Austria. The company plans to expand availability to the rest of the European Union and the United States.
