<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog RSS</title>
    <link>https://stefanpilz.ltd/en/blog</link>
    <atom:link href="https://stefanpilz.ltd/en/feed.xml" rel="self" type="application/rss+xml" />
    <description>Latest blog posts from Stefan Pilz Ltd.</description>
    <language>en</language>
          <item>
        <title>Shopware Migration: Costs and Process - Honest Figures Instead of Bait Offers</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/297-shopware-migration-costs-and-process-honest-figures</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/297-shopware-migration-costs-and-process-honest-figures</guid>
        <pubDate>Tue, 25 Aug 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> A Shopware migration for small stores with a standard theme often costs a <strong>mid four-digit to low five-digit amount</strong>, medium stores with custom design and 10-20 plugins <strong>considerably more</strong>, and complex B2B projects with ERP integration sit far above - agencies typically quote 10-15 k€, 20-35 k€ and 35-50 k€+ for these categories. The honest truth: any number before analyzing your store is a guess. What can be named seriously are the <strong>cost drivers</strong> - and they are right here.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>How Much Does a Shopware Plugin Cost? Real Project Figures</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/295-how-much-does-a-shopware-plugin-cost-real-project-figures</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/295-how-much-does-a-shopware-plugin-cost-real-project-figures</guid>
        <pubDate>Thu, 13 Aug 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Small Shopware plugins with a clearly defined function typically cost <strong>1,500-4,000 €</strong>, medium extensions with backend logic or integrations <strong>4,000-10,000 €</strong>, complex B2B and integration plugins sit above that. Agencies often quote 5,000-25,000 € for comparable projects. The biggest cost driver is almost never the programming itself - it is unclear requirements and overlooked edge cases.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware Agency or Freelancer: What Fits Your Project?</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/293-shopware-agency-or-freelancer-what-fits-your-project</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/293-shopware-agency-or-freelancer-what-fits-your-project</guid>
        <pubDate>Wed, 05 Aug 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> There is no universally right answer - but there are clear patterns. An agency (typically 110-180 €/h) pays off when you need design, marketing, content and development at the same time, or when you are planning a large project with many parallel workstreams. A freelancer (typically 65-120 €/h) is the better choice for concrete technical tasks: plugins, migrations, performance, ongoing maintenance. And hardly anyone knows the third option: <strong>combining both</strong> - which is exactly how I regularly work with agencies myself.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>GMV in Shopware: How Your Revenue Is Measured - and Why You Don&#039;t Need an Extension for It</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/291-gmv-in-shopware-how-your-revenue-is-measured-and-why-you-do-not-need-an-extension</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/291-gmv-in-shopware-how-your-revenue-is-measured-and-why-you-do-not-need-an-extension</guid>
        <pubDate>Wed, 29 Jul 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Since April 14, 2026, Shopware collects GMV (Gross Merchandise Value) automatically - for all shops from version 6.7.8 with a connected Shopware Account and accepted contractual basis. The functionality is <strong>built into the core</strong>: you install no app from the store and see no classic extension - just a settings page under <em>Settings &gt; System &gt; GMV Reporting</em>. The calculation uses <strong>net values</strong> (no taxes), <strong>minus discounts and vouchers</strong>, <strong>including shipping costs</strong> - and importantly: <strong>returns do not reduce GMV</strong>. Only two aggregated values are transmitted once per day: the GMV total and the order count.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware Maintenance 2026: Why Small Regular Updates Beat a Risky Version Jump</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/275-shopware-maintenance-2026-why-small-regular-updates-beat-a-risky-version-jump</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/275-shopware-maintenance-2026-why-small-regular-updates-beat-a-risky-version-jump</guid>
        <pubDate>Wed, 22 Jul 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> A store that has not seen updates for two years is not saved effort - it is a postponed emergency project with an unknown price tag. The 2026 release reality shows why: security fixes, legally required features like the withdrawal button and new channels like agentic commerce all arrive through regular updates. Update monthly in small steps and you get all of this on the side. Jump versions and you pay for everything at once - plus risk.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>AI Readability for Shopware Stores: Why AI Can Only Recommend Your Store If It Understands It</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/287-ai-readability-for-shopware-stores-why-ai-can-only-recommend-your-store-if-it-understands-it</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/287-ai-readability-for-shopware-stores-why-ai-can-only-recommend-your-store-if-it-understands-it</guid>
        <pubDate>Wed, 08 Jul 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> More and more buying decisions start in ChatGPT, Perplexity or Copilot instead of Google. Whether your store gets recommended there is decided not by your ad budget, but by whether AI systems can <strong>find, read and trust</strong> your store. That is exactly what the <a href="https://www.agenticcommerce.shop/">AI Readability Scanner</a> by Shopware and the Agentic Commerce Alliance tests on three layers: AI Discovery, Catalog Readability and Transaction Readiness. The good news: an existing Shopware store does not need to be rebuilt for this - but it does need to be technically prepared.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Next-Generation Content in Shopware: Why Shopping Experiences Alone Are No Longer Enough</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/285-next-generation-content-in-shopware-why-shopping-experiences-alone-are-no-longer-enough</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/285-next-generation-content-in-shopware-why-shopping-experiences-alone-are-no-longer-enough</guid>
        <pubDate>Sat, 27 Jun 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Shopware is fundamentally rebuilding its content system: layouts will be defined as <strong>data</strong> (Content API) instead of Twig markup, the technical foundation - storefront components based on Twig UX Components - already shipped with 6.7.11, and a new page builder is in its discovery phase. The most important message for anyone with upgrade trauma: <strong>nothing existing gets broken</strong> - Shopping Experiences and the new system are meant to coexist for a long time. Customer-facing features are not expected before 2027.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware 6.7.11 Developer Check: Twig UX Components, Vite Dev Server and a Better Storefront Architecture</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/271-shopware-6-7-11-developer-check-twig-ux-components-vite-dev-server</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/271-shopware-6-7-11-developer-check-twig-ux-components-vite-dev-server</guid>
        <pubDate>Thu, 18 Jun 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Shopware 6.7.11.0 (released June 16, 2026) is the most interesting storefront release in a long time: a new component system based on Twig UX Components, a Vite-based dev server replacing <code>composer watch:storefront</code>, theme configuration as native CSS custom properties and a global JavaScript event system. None of it forces an immediate rebuild - but whatever you build new from now on should be built on the new foundation.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware After Community Day 2026: What Merchants Should Actually Take Away from AI, B2B and Agentic Commerce</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/273-shopware-after-community-day-2026-what-merchants-should-actually-take-away</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/273-shopware-after-community-day-2026-what-merchants-should-actually-take-away</guid>
        <pubDate>Sat, 13 Jun 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> At Shopware Community Day on June 10, 2026 in Cologne, Shopware presented four products: <strong>Nexus</strong> (integration orchestration, generally available), <strong>Copilot</strong> (AI assistant, agentic capabilities in development), <strong>Payments</strong> (native payments, available in DE/AT) and <strong>Experience Studio</strong> (research preview). The guiding theme: Shopware as open commerce infrastructure for the "agentic era". My assessment: two of the four announcements can be evaluated concretely today, two are watch items - and the most important preparation happens in your own data anyway.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware Development 2026: What Works in Real Projects - and What Only Sounds Good in Theory</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/283-shopware-development-2026-what-works-in-real-projects</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/283-shopware-development-2026-what-works-in-real-projects</guid>
        <pubDate>Thu, 28 May 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> The difference between a Shopware project that runs calmly and one that turns every release day into a risk rarely lies in the code - it lies in the pipeline around it. From my project experience: Docker as the local base, <code>shopware-cli</code> for builds and project tasks, deployments through the Deployment Helper instead of FTP, and a staging environment that deserves the name. None of this is rocket science - but the combination decides.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Optimizing Shopware Product Data: Why Google Merchant Center, AI Search and Product Feeds Belong Together</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/281-optimizing-shopware-product-data-google-merchant-center-ai-search-and-feeds</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/281-optimizing-shopware-product-data-google-merchant-center-ai-search-and-feeds</guid>
        <pubDate>Sun, 17 May 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Google Merchant Center, the new Agentic Commerce feed and your own shop search share one common truth: your product data. Structure it cleanly once - titles, attributes, variants, GTINs, availability, images - and you serve all three channels at the same time. Neglect it, and you lose three times over. Here is my checklist from real Shopware projects.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Agentic Commerce in Shopware: Why the New AI Product Feed Is More Than Another Sales Channel</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/269-agentic-commerce-in-shopware-why-the-new-ai-product-feed-is-more-than-another-sales-channel</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/269-agentic-commerce-in-shopware-why-the-new-ai-product-feed-is-more-than-another-sales-channel</guid>
        <pubDate>Sun, 10 May 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Shopware 6.7.10.0 (released May 6, 2026) introduces a new, experimental sales channel type for agentic commerce: products can be exposed as a JSONL feed for AI platforms, starting with the OpenAI integration. Orders and traffic from AI platforms are tracked through the existing affiliate infrastructure. It sounds like a feature checkbox - in reality it is the entry point into a channel where AI agents read your product data instead of humans clicking through your storefront.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware 6.7.9 Overview: Withdrawal Button, Product Bundles and Copilot Chat History - What Actually Matters</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/279-shopware-6-7-9-overview-withdrawal-button-product-bundles-copilot-chat-history</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/279-shopware-6-7-9-overview-withdrawal-button-product-bundles-copilot-chat-history</guid>
        <pubDate>Sun, 26 Apr 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> Shopware 6.7.9.0 (April 16, 2026) is a release with a clear priority list: the <strong>withdrawal button</strong> is mandatory homework with a deadline, <strong>JSON-LD</strong> behind a feature flag is the underrated SEO win, <strong>product bundles</strong> (Evolve and up) and <strong>Copilot chat history</strong> are useful for their respective audiences - and the Agentic Commerce sales channel was postponed to 6.7.10. Here is my relevance check instead of a plain feature list.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Withdrawal Button in Shopware 6: What Merchants Must Check Before June 19, 2026</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/267-withdrawal-button-in-shopware-6-what-merchants-must-check-before-june-19-2026</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/267-withdrawal-button-in-shopware-6-what-merchants-must-check-before-june-19-2026</guid>
        <pubDate>Sat, 18 Apr 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> From June 19, 2026, online shops selling to consumers in Germany must offer an electronic withdrawal button - clearly visible, usable directly in the shop, with an immediate confirmation of receipt. Shopware ships a native withdrawal form since version 6.7.9.0 (April 16, 2026), placed via Shopping Experiences and backported to Shopware 6.6. The technology is there - the real work is integrating it cleanly into your theme and sales channels.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>Shopware Community Edition 2026: When CE Is Enough - and When It Becomes a Cost Trap</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/277-shopware-community-edition-2026-when-ce-is-enough-and-when-it-becomes-a-cost-trap</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/277-shopware-community-edition-2026-when-ce-is-enough-and-when-it-becomes-a-cost-trap</guid>
        <pubDate>Wed, 08 Apr 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> The Shopware Community Edition in 2026 is a complete, MIT-licensed shop system you can run a real business on - not a demo, not a trial. But the honest answer to "is CE enough?" does not depend on the software. It depends on three factors: your revenue (keyword: Fair Usage Policy from 1 million € GMV), your need for B2B and content features, and the question of who carries the technical responsibility.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>PHP 8.5 Is Here: The Changes That Actually Matter for Developers</title>
        <link>https://stefanpilz.ltd/en/blog/60-php/263-php-8-5-the-changes-that-actually-matter-for-developers</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/60-php/263-php-8-5-the-changes-that-actually-matter-for-developers</guid>
        <pubDate>Tue, 31 Mar 2026 00:00:00 +0200</pubDate>
        <description><![CDATA[<p><strong>In short:</strong> PHP 8.5 brings the pipe operator <code>|&gt;</code>, a new URI extension, <code>#[\NoDiscard]</code> and more flexible constant expressions - but also deprecations and behavior changes you should check before upgrading.</p>
<p>With <strong>PHP 8.5</strong>, developers get a release that is not just about a few cosmetic language tweaks. This version introduces several features that improve readability, modernize common coding patterns, and sharpen the language in ways that will be noticeable in real projects.</p>
<p>At the same time, PHP 8.5 is not a release you should upgrade to blindly. Alongside the new features, there are also deprecations and behavior changes that can affect older codebases. That combination makes PHP 8.5 especially interesting: it adds useful new tools, but it also expects developers to clean up some legacy habits.</p>]]></description>
                <category>PHP</category>
              </item>
          <item>
        <title>Shopware Intelligence+ for Shopware Community Edition: Is the New AI Feature Really Worth It?</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/265-shopware-intelligence-for-shopware-community-edition-is-the-new-ai-feature-really-worth-it</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/265-shopware-intelligence-for-shopware-community-edition-is-the-new-ai-feature-really-worth-it</guid>
        <pubDate>Wed, 25 Mar 2026 00:00:00 +0100</pubDate>
        <description><![CDATA[<p>With <strong>Shopware Intelligence+</strong>, Shopware is bringing new AI-powered services into the platform that are especially interesting for users of the <strong>Shopware Community Edition</strong>. That is the key point here: if you are running the Community Edition, you do not automatically have to miss out on modern AI features.</p>
<p>Many merchants deliberately use the Community Edition because it is flexible, avoids higher ongoing plan costs, and can be adapted well to individual business needs. That is exactly why the question matters: what does <strong>Shopware Intelligence+ for Shopware Community Edition</strong> actually mean in practice, and is it really worth using?</p>
<p>The short answer is yes, the topic is relevant. But not every store needs every AI feature right away. What really matters is your business model, which tasks currently consume too much time, and where artificial intelligence can create measurable value instead of just sounding innovative.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
          <item>
        <title>My New Shopware Plugin: Shoe Size Table &amp; Size Advisor</title>
        <link>https://stefanpilz.ltd/en/blog/64-shopware-plugins/259-shopware-6-plugin-shoe-size-table-size-advisor</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/64-shopware-plugins/259-shopware-6-plugin-shoe-size-table-size-advisor</guid>
        <pubDate>Tue, 24 Mar 2026 00:00:00 +0100</pubDate>
        <description><![CDATA[<p>I have developed a new <strong>Shopware plugin</strong> that solves a very common problem in ecommerce: choosing the right shoe size on the product detail page. With my <strong>Shoe Size Table &amp; Size Advisor</strong>, customers can find their recommended size faster and with much more confidence.</p>
<p>In online shoe retail, wrong size decisions often lead to avoidable returns, uncertainty during the buying process, and sometimes even abandoned purchases. That is exactly where this plugin comes in. It adds an interactive size advisor to the product detail page and helps customers make a better decision before they buy.</p>]]></description>
                <category>Shopware Plugins</category>
              </item>
          <item>
        <title>A-Z Product Filter for Shopping Experiences: My New Shopware Plugin for Better Product Navigation</title>
        <link>https://stefanpilz.ltd/en/blog/64-shopware-plugins/255-a-z-product-filter-plugin-for-shopware</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/64-shopware-plugins/255-a-z-product-filter-plugin-for-shopware</guid>
        <pubDate>Wed, 11 Mar 2026 00:00:00 +0100</pubDate>
        <description><![CDATA[<p>I have developed a new <strong>Shopware plugin</strong>: the <strong>A-Z Product Filter for Shopping Experiences</strong>. The goal is simple: make product listings easier to navigate, especially in shops with larger catalogs, brand overviews, or category pages with many visible products.</p>
<p>As product ranges grow, navigation often becomes more difficult. Customers may know roughly what they are looking for, but long listings still create friction. That is exactly why I built this plugin. It adds an alphabetical filter to <strong>Shopware Shopping Experiences</strong> and helps users move through listings faster and more intuitively.</p>]]></description>
                <category>Shopware Plugins</category>
              </item>
          <item>
        <title>Headless with Shopware: Architecture Decisions, TCO, and the Reality of Running It</title>
        <link>https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/261-headless-with-shopware-architecture-decisions-tco-and-the-reality-of-running-it</link>
        <guid isPermaLink="true">https://stefanpilz.ltd/en/blog/58-shopware-expert-tips/261-headless-with-shopware-architecture-decisions-tco-and-the-reality-of-running-it</guid>
        <pubDate>Thu, 26 Feb 2026 00:00:00 +0100</pubDate>
        <description><![CDATA[<p>Headless is one of those ecommerce topics that sounds compelling almost immediately. More frontend freedom, modern technologies, better performance, more control over the user experience, and the ability to deliver content across multiple touchpoints. Especially in combination with Shopware, it can look like the natural next step for ambitious commerce projects.</p>
<p>But in practice, the real question is not whether headless is modern. The real question is this: <strong>is headless the right architectural decision for this specific Shopware project?</strong></p>
<p>That is where things get interesting. Headless can be a very strong solution. But it can also introduce more complexity, more cost, and more operational responsibility without delivering enough business value to justify it.</p>]]></description>
                <category>Shopware Expert Tips</category>
              </item>
      </channel>
</rss>
