[{"data":1,"prerenderedAt":1037},["ShallowReactive",2],{"locale-routes":3,"page-\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits":169,"insights-author-\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits":846},{"home":4,"privacy":7,"framework-focus":10,"framework":13,"framework-principles":16,"imprint":19,"contact":22,"shopware-agency-b2b":25,"shopware-agency-electronics":28,"shopware-agency-development":31,"shopware-agency":34,"shopware-agency-pricing":37,"shopware-agency-migration":40,"shopware-agency-seo":43,"shopware-agency-support":46,"location-hamburg":49,"location-munich":52,"about":55,"about-mission":58,"about-partners":61,"services-consulting":64,"services-development":67,"services":70,"services-optimization":73,"services-growth":76,"insights-ai-sales-channels-shopware":79,"insights-b2b-shop-starten-checkliste":82,"insights-ecommerce-deadlines-2026-27":85,"insights-e-invoice-b2b-shopware-xrechnung-zugferd":88,"insights-handelskoenig-b2b-quotes":91,"insights-shopware-5-eol":94,"insights-shopware-6-7-release":97,"insights-shopware-6-8-outlook":100,"insights-shopware-6-plans-pricing-2026":103,"insights-shopware-gmv-2026":106,"insights-shopware-vs-shopify-2026":109,"insights-shopware-maintenance-retainer-development":112,"insights-withdrawal-button-shopware-6":115,"whitepaper-agentic-commerce-b2b-beschaffung":118,"whitepaper-compliance-2026-27":120,"whitepapers":123,"whitepaper-kanalverbund-marktplatz-shop-agentic":126,"whitepaper-shopware-6-boutique-vs-grossagentur-tco":128,"case-comspot-focus":130,"case-handelskoenig-focus":133,"case-lupa-focus":136,"case-topi-focus":139,"case-xucker-focus":142,"talks-beyond-seo-scuc-2026":145,"talks":148,"talks-shopware-container-hosting-hitc-2026":151,"talks-symfony-cli-docker-scuc-2025":154,"webinars":157,"team-alex-jank":160,"team-benedikt-rillox":163,"team":166},{"de":5,"en":6},"\u002F","\u002Fen",{"de":8,"en":9},"\u002Fdatenschutz","\u002Fen\u002Fprivacy",{"de":11,"en":12},"\u002Fframework\u002Ffocus","\u002Fen\u002Fframework\u002Ffocus",{"de":14,"en":15},"\u002Fframework","\u002Fen\u002Fframework",{"de":17,"en":18},"\u002Fframework\u002Fprinzipien","\u002Fen\u002Fframework\u002Fprinciples",{"de":20,"en":21},"\u002Fimpressum","\u002Fen\u002Fimprint",{"de":23,"en":24},"\u002Fkontakt","\u002Fen\u002Fcontact",{"de":26,"en":27},"\u002Fshopware-agentur\u002Fb2b","\u002Fen\u002Fshopware-agency\u002Fb2b",{"de":29,"en":30},"\u002Fshopware-agentur\u002Felektronikhandel","\u002Fen\u002Fshopware-agency\u002Felectronics-retail",{"de":32,"en":33},"\u002Fshopware-agentur\u002Fentwicklung","\u002Fen\u002Fshopware-agency\u002Fdevelopment",{"de":35,"en":36},"\u002Fshopware-agentur","\u002Fen\u002Fshopware-agency",{"de":38,"en":39},"\u002Fshopware-agentur\u002Fkosten","\u002Fen\u002Fshopware-agency\u002Fpricing",{"de":41,"en":42},"\u002Fshopware-agentur\u002Fmigration","\u002Fen\u002Fshopware-agency\u002Fmigration",{"de":44,"en":45},"\u002Fshopware-agentur\u002Fseo","\u002Fen\u002Fshopware-agency\u002Fseo",{"de":47,"en":48},"\u002Fshopware-agentur\u002Fsupport","\u002Fen\u002Fshopware-agency\u002Fsupport",{"de":50,"en":51},"\u002Fstandorte\u002Fhamburg","\u002Fen\u002Flocations\u002Fhamburg",{"de":53,"en":54},"\u002Fstandorte\u002Fmuenchen","\u002Fen\u002Flocations\u002Fmunich",{"de":56,"en":57},"\u002Fueber-uns","\u002Fen\u002Fabout",{"de":59,"en":60},"\u002Fueber-uns\u002Fmission","\u002Fen\u002Fabout\u002Fmission",{"de":62,"en":63},"\u002Fueber-uns\u002Fpartner","\u002Fen\u002Fabout\u002Fpartners",{"de":65,"en":66},"\u002Fleistungen\u002Fberatung","\u002Fen\u002Fservices\u002Fconsulting",{"de":68,"en":69},"\u002Fleistungen\u002Fentwicklung","\u002Fen\u002Fservices\u002Fdevelopment",{"de":71,"en":72},"\u002Fleistungen","\u002Fen\u002Fservices",{"de":74,"en":75},"\u002Fleistungen\u002Foptimierung","\u002Fen\u002Fservices\u002Foptimization",{"de":77,"en":78},"\u002Fleistungen\u002Fwachstum","\u002Fen\u002Fservices\u002Fgrowth",{"de":80,"en":81},"\u002Finsights\u002Fai-verkaufskanaele-shopware","\u002Fen\u002Finsights\u002Fai-sales-channels-shopware",{"de":83,"en":84},"\u002Finsights\u002Fb2b-shop-starten-checkliste-shopware","\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist",{"de":86,"en":87},"\u002Finsights\u002Fe-commerce-fristen-2026-27","\u002Fen\u002Finsights\u002Fe-commerce-deadlines-2026-27",{"de":89,"en":90},"\u002Finsights\u002Fe-rechnung-b2b-shopware-xrechnung-zugferd","\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd",{"de":92,"en":93},"\u002Finsights\u002Fhandelskoenig-b2b-angebotsanfragen","\u002Fen\u002Finsights\u002Fhandelskoenig-b2b-quote-requests",{"de":95,"en":96},"\u002Finsights\u002Fshopware-5-eol","\u002Fen\u002Finsights\u002Fshopware-5-end-of-life",{"de":98,"en":99},"\u002Finsights\u002Fshopware-6-7-release-update-vorteile","\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits",{"de":101,"en":102},"\u002Finsights\u002Fshopware-6-8-ausblick-roadmap-vorbereitung","\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation",{"de":104,"en":105},"\u002Finsights\u002Fshopware-6-lizenzen-kosten-2026","\u002Fen\u002Finsights\u002Fshopware-6-plans-pricing-2026",{"de":107,"en":108},"\u002Finsights\u002Fshopware-gmv-berechnung-1-million-grenze","\u002Fen\u002Finsights\u002Fshopware-gmv-calculation-one-million-threshold",{"de":110,"en":111},"\u002Finsights\u002Fshopware-vs-shopify-vergleich-2026","\u002Fen\u002Finsights\u002Fshopware-vs-shopify-comparison-2026",{"de":113,"en":114},"\u002Finsights\u002Fshopware-wartung-retainer-weiterentwicklung","\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development",{"de":116,"en":117},"\u002Finsights\u002Fwiderrufsbutton-shopware-6","\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6",{"de":119},"\u002Fwhitepapers\u002Fagentic-commerce-b2b-beschaffung",{"de":121,"en":122},"\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27","\u002Fen\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27",{"de":124,"en":125},"\u002Fwhitepapers","\u002Fen\u002Fwhitepapers",{"de":127},"\u002Fwhitepapers\u002Fkanalverbund-marktplatz-shop-agentic",{"de":129},"\u002Fwhitepapers\u002Fshopware-6-boutique-vs-grossagentur-tco",{"de":131,"en":132},"\u002Fcase-studies\u002Fcomspot-focus","\u002Fen\u002Fcase-studies\u002Fcomspot-focus",{"de":134,"en":135},"\u002Fcase-studies\u002Fhandelskoenig-focus","\u002Fen\u002Fcase-studies\u002Fhandelskoenig-focus",{"de":137,"en":138},"\u002Fcase-studies\u002Flupa-focus","\u002Fen\u002Fcase-studies\u002Flupa-focus",{"de":140,"en":141},"\u002Fcase-studies\u002Ftopi-focus","\u002Fen\u002Fcase-studies\u002Ftopi-focus",{"de":143,"en":144},"\u002Fcase-studies\u002Fxucker-focus","\u002Fen\u002Fcase-studies\u002Fxucker-focus",{"de":146,"en":147},"\u002Fvortraege\u002Fbeyond-seo-scuc-2026","\u002Fen\u002Ftalks\u002Fbeyond-seo-scuc-2026",{"de":149,"en":150},"\u002Fvortraege","\u002Fen\u002Ftalks",{"de":152,"en":153},"\u002Fvortraege\u002Fshopware-container-hosting-hitc-2026","\u002Fen\u002Ftalks\u002Fshopware-container-hosting-hitc-2026",{"de":155,"en":156},"\u002Fvortraege\u002Fsymfony-cli-docker-scuc-2025","\u002Fen\u002Ftalks\u002Fsymfony-cli-docker-scuc-2025",{"de":158,"en":159},"\u002Fwebinare","\u002Fen\u002Fwebinars",{"de":161,"en":162},"\u002Fteam\u002Falex-jank","\u002Fen\u002Fteam\u002Falex-jank",{"de":164,"en":165},"\u002Fteam\u002Fbenedikt-rillox","\u002Fen\u002Fteam\u002Fbenedikt-rillox",{"de":167,"en":168},"\u002Fteam","\u002Fen\u002Fteam",{"id":170,"title":171,"author":172,"body":173,"citations":814,"description":823,"draft":824,"extension":825,"image":826,"meta":829,"navigation":830,"ogImage":831,"path":99,"publishedAt":832,"readingTime":833,"robots":831,"schemaOrg":831,"seo":834,"sitemap":837,"stem":839,"tags":840,"translationKey":844,"updatedAt":838,"__hash__":845},"insights_en\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits.md","Shopware 6.7: What the major release adds and why upgrading is worthwhile","benedikt-rillox",{"type":174,"value":175,"toc":781},"minimark",[176,188,191,196,208,223,227,236,241,255,258,261,265,268,271,275,278,281,285,288,291,295,298,306,310,313,457,460,464,471,474,478,481,484,488,491,494,498,501,504,508,511,531,535,550,553,557,560,564,567,571,574,578,581,585,588,592,595,599,602,606,609,640,653,657,664,721,725,728,731,735],[177,178,179,180,187],"p",{},"Shopware 6.7 is the current major release: published on June 17, 2025 and\nextended monthly since, up to the verified state\n",[181,182,186],"a",{"href":183,"rel":184},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.12.2",[185],"nofollow","6.7.12.2"," of\nJuly 23, 2026. It modernizes accessibility, caching, and the Administration\n(Vite, Vue 3, Pinia) and delivered native language management, B2B Individual\nPricing, Product Bundles, the Withdrawal Button, and Agentic Commerce in its\nminor releases.",[177,189,190],{},"This division often causes confusion. Shopware 6.7.0.0 primarily changed\naccessibility, caching, the Administration, and the developer stack; the\ncommerce features followed later within the same 6.7 line. This article\ntherefore considers the whole development: the benefits merchants receive\ntoday, what extensions and themes may need to change, and how to upgrade\nwithout unnecessary operational risk.",[192,193,195],"h2",{"id":194},"what-does-a-shopware-major-release-mean","What does a Shopware major release mean?",[177,197,198,199,203,204,207],{},"A Shopware major release bundles technical changes where complete backward\ncompatibility is not always possible; new commerce capabilities often arrive\nin the minor versions that follow. In practice: ",[200,201,202],"strong",{},"6.7.0.0"," establishes the\nmodernized platform foundation, the ",[200,205,206],{},"6.7.x"," releases add features,\nimprovements, and fixes on top of it — and plugins, apps, themes, and\ncustomizations must explicitly support the new foundation. A major upgrade\ntherefore requires more testing than a routine patch update.",[177,209,210,211,216,217,222],{},"Shopware 6.7.0.0 was ",[181,212,215],{"href":213,"rel":214},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fnews\u002Fnew-major-release-shopware-6-7\u002F",[185],"officially released on June 17,\n2025",".\nAccording to the ",[181,218,221],{"href":219,"rel":220},"https:\u002F\u002Fdeveloper.shopware.com\u002Frelease-notes\u002F",[185],"release notes\noverview",", Shopware 6.6 moved\ninto extended support, receiving security fixes but none of the active product\nline's new functionality.",[192,224,226],{"id":225},"the-most-important-changes-in-shopware-670","The most important changes in Shopware 6.7.0",[177,228,229,230,235],{},"Five changes define the 6.7.0 release: accessibility enabled by default with\nthe European Accessibility Act in mind, the Administration's move from Webpack\nto Vite, the full switch to Vue 3 with Pinia, a fundamentally reworked cache,\nand updated core libraries such as DBAL 4 and PHPUnit 11. The complete\ntechnical list is in the ",[181,231,234],{"href":232,"rel":233},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Fblob\u002Ftrunk\u002FRELEASE_INFO-6.7.md",[185],"official release\ninformation",".",[237,238,240],"h3",{"id":239},"_1-accessibility-improvements-are-enabled-by-default","1. Accessibility improvements are enabled by default",[177,242,243,244,249,250,254],{},"Shopware revised storefront templates, font sizes, semantic HTML, focus\nbehavior, and other controls with the\n",[181,245,248],{"href":246,"rel":247},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Fdir\u002F2019\u002F882\u002Foj\u002Feng",[185],"European Accessibility Act","\nin mind. Some\nof these changes were already available in 6.6 behind the\n",[251,252,253],"code",{},"ACCESSIBILITY_TWEAKS"," feature flag. They are enabled by default in 6.7.",[177,256,257],{},"This is an important foundation, not an automatic guarantee of an accessible\nstore. Custom themes, CMS content, color contrast, alternative text, forms,\nand extensions still need to be reviewed.",[177,259,260],{},"The upgrade provides a better core baseline. Agencies spend less effort working\naround old markup structures and can test the individual storefront against a\nmore modern standard.",[237,262,264],{"id":263},"_2-the-administration-moves-from-webpack-to-vite","2. The Administration moves from Webpack to Vite",[177,266,267],{},"Shopware 6.7 modernizes the Administration build process by replacing Webpack\nwith Vite. This improves modern frontend workflows but is a real compatibility\nboundary for Administration extensions.",[177,269,270],{},"Plugins with custom Admin modules generally need adjusted builds or separate\nversions for 6.6 and 6.7. An upgrade review must check whether the exact\ninstalled plugin version explicitly supports 6.7.",[237,272,274],{"id":273},"_3-vue-3-and-pinia-modernize-the-administration","3. Vue 3 and Pinia modernize the Administration",[177,276,277],{},"Shopware 6.7 leaves Vue 3 compatibility mode and uses Vue 3 natively. Pinia\nreplaces Vuex for state management.",[177,279,280],{},"Merchants do not immediately see this change, but it improves maintainability,\nextensibility, and compatibility with the current Vue ecosystem. Developers\nneed to inspect custom Admin components, mixins, stores, and component\noverrides.",[237,282,284],{"id":283},"_4-caching-is-fundamentally-reworked","4. Caching is fundamentally reworked",[177,286,287],{},"Shopware combines and delays cache invalidations to avoid unnecessarily\ndiscarding entries. The separate Store API caching layer was removed. The goal\nis a higher cache hit rate, lower storage use, and more stable performance when\ndata changes frequently.",[177,289,290],{},"A cache rework is not a universal performance switch. Reverse proxy, Redis,\nqueue workers, product indexing, custom subscribers, and hosting need to be\nconsidered together. Load tests and real cache-hit measurements belong in the\npost-upgrade review.",[237,292,294],{"id":293},"_5-core-libraries-are-updated","5. Core libraries are updated",[177,296,297],{},"Important updates include DBAL 4, PHPUnit 11, League OAuth2 Server, and DomPDF.\nThey prepare Shopware for current PHP, database, and framework versions.",[177,299,300,301,235],{},"Custom code using internal library APIs may need changes. Bespoke database\nqueries, tests, document generation, and authentication logic deserve a focused\nreview against the ",[181,302,305],{"href":303,"rel":304},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Fblob\u002Ftrunk\u002FUPGRADE-6.7.md",[185],"official upgrade\nguide",[192,307,309],{"id":308},"what-was-added-later-across-the-shopware-67-line","What was added later across the Shopware 6.7 line?",[177,311,312],{},"Since 6.7.0, Shopware has extended the platform through regular minor\nreleases – from the faster OpenSearch search in 6.7.2, through native\nlanguage management, B2B expansion, video, and the Withdrawal Button, to\nAgentic Commerce and AI Discovery Files in 6.7.10 through 6.7.12. This table\nsummarizes the most relevant steps for merchants and project owners; each\nversion links to its official release notes on GitHub.",[314,315,316,329],"table",{},[317,318,319],"thead",{},[320,321,322,326],"tr",{},[323,324,325],"th",{},"Version",[323,327,328],{},"Focus and examples",[330,331,332,345,357,369,381,393,405,417,429,441],"tbody",{},[320,333,334,342],{},[335,336,337],"td",{},[181,338,341],{"href":339,"rel":340},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.2.0",[185],"6.7.2",[335,343,344],{},"Faster OpenSearch product search plus performance, SEO, and accessibility improvements",[320,346,347,354],{},[335,348,349],{},[181,350,353],{"href":351,"rel":352},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.3.0",[185],"6.7.3",[335,355,356],{},"Native installation and maintenance of Shopware languages without a separate language pack",[320,358,359,366],{},[335,360,361],{},[181,362,365],{"href":363,"rel":364},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.4.0",[185],"6.7.4",[335,367,368],{},"Extended Subscriptions, new B2B Components, and Copilot Data Insights",[320,370,371,378],{},[335,372,373],{},[181,374,377],{"href":375,"rel":376},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.6.0",[185],"6.7.6",[335,379,380],{},"Security, caching, and Administration improvements",[320,382,383,390],{},[335,384,385],{},[181,386,389],{"href":387,"rel":388},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.7.0",[185],"6.7.7",[335,391,392],{},"More detailed GA4 ecommerce events, 3D improvements, and revised cookie consent",[320,394,395,402],{},[335,396,397],{},[181,398,401],{"href":399,"rel":400},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.8.0",[185],"6.7.8",[335,403,404],{},"Video as a native media type, B2B Individual Pricing, and integrated GMV Reporting",[320,406,407,414],{},[335,408,409],{},[181,410,413],{"href":411,"rel":412},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.9.0",[185],"6.7.9",[335,415,416],{},"Withdrawal Button, Product Bundles, and Copilot chat history",[320,418,419,426],{},[335,420,421],{},[181,422,425],{"href":423,"rel":424},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.10.0",[185],"6.7.10",[335,427,428],{},"Experimental Agentic Commerce sales channel and extended Analytics foundations",[320,430,431,438],{},[335,432,433],{},[181,434,437],{"href":435,"rel":436},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.11.0",[185],"6.7.11",[335,439,440],{},"Better mail preview, search redirects, and a new storefront component system",[320,442,443,454],{},[335,444,445,5,450],{},[181,446,449],{"href":447,"rel":448},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.12.1",[185],"6.7.12.1",[181,451,453],{"href":183,"rel":452},[185],"2",[335,455,456],{},"AI Discovery Files, search options, a Rule Builder extension, and fixes",[177,458,459],{},"Not every capability is included in Community Edition. B2B, AI, Analytics, and\nother commercial features may require a particular Shopware plan or separate\nservice.",[192,461,463],{"id":462},"better-performance-for-large-catalogs","Better performance for large catalogs",[177,465,466,467,470],{},"Version ",[181,468,341],{"href":339,"rel":469},[185],"\nsignificantly improved product search with OpenSearch. In its release\nannouncements, Shopware reports improvements between 33 and 200 percent\ndepending on the environment.\nLater releases added searches by EAN and manufacturer number and direct product\npage redirects when exactly one item matches.",[177,472,473],{},"This is especially relevant to B2B stores and spare-parts catalogs where buyers\nsearch with known identifiers. The actual result still depends on the index,\nanalyzers, data quality, and infrastructure.",[192,475,477],{"id":476},"language-management-moves-into-shopware-core","Language management moves into Shopware core",[177,479,480],{},"Starting with 6.7.3, available Shopware translations can be installed and\nupdated natively. The former language-pack extension is no longer required for\nthese languages and will not be supported from Shopware 6.8 onward.",[177,482,483],{},"International stores remove one plugin dependency. Custom snippets, localized\ncontent, SEO metadata, and editorial translation workflows still need clear\nownership.",[192,485,487],{"id":486},"b2b-quoting-and-individual-prices","B2B, quoting, and individual prices",[177,489,490],{},"The 6.7 line progressively expanded B2B Components: organizational units,\nbudgets, approvals, quoting, customer-specific assortments, and rule-based\nIndividual Pricing from 6.7.8. The upgrade is also strategically relevant to\nB2B merchants because Shopware plans to end support for the older B2B Suite\nwith 6.8 – new B2B capabilities are being built exclusively in B2B Components.",[177,492,493],{},"The plan, data migration, and functional coverage need to be assessed before\nchanging systems.",[192,495,497],{"id":496},"media-products-and-commerce-functionality","Media, products, and commerce functionality",[177,499,500],{},"Video has been a native media type since 6.7.8, making it easier to use\nconsistently in products and CMS content. Product Bundles allow related items\nto be sold as a package. Subscriptions, 3D functionality, and quotation\nprocesses have also continued to evolve across 6.7.",[177,502,503],{},"The commercial benefit does not come from activation alone. A function creates\nvalue when it reliably replaces plugins, manual work, or custom development.",[192,505,507],{"id":506},"compliance-and-better-measurement","Compliance and better measurement",[177,509,510],{},"In addition to its accessibility foundations, the 6.7 line delivers four\npractical compliance and measurement tools: the Withdrawal Button for the\ndigital withdrawal process that has been mandatory in Germany since June\n2026, extended GA4 ecommerce events, integrated GMV Reporting, and a revised\ncookie consent flow. These are tools, not automatic legal compliance –\nconfiguration, consent, and analytics data quality still require\nstore-specific validation.",[512,513,514,522,525,528],"ul",{},[515,516,517,518,521],"li",{},"The Withdrawal Button supports the ",[181,519,520],{"href":117},"legally required digital withdrawal\nworkflow"," relevant to affected\nGerman B2C stores since June 2026.",[515,523,524],{},"Extended GA4 events add basket, checkout, brand, and category information.",[515,526,527],{},"Integrated GMV Reporting automates aggregated reporting for relevant\nShopware Accounts.",[515,529,530],{},"Cookie consent and Administration transparency have been improved.",[192,532,534],{"id":533},"agentic-commerce-and-ai-discovery","Agentic Commerce and AI Discovery",[177,536,537,538,541,542,545,546,549],{},"From 6.7.10, Shopware progressively opened the platform to AI channels: an\nexperimental Agentic Commerce sales channel publishes product data through\nplatform-specific feeds – initially for OpenAI – and attributes AI-generated\ntraffic using existing affiliate mechanisms. Version 6.7.11 added an\nexperimental MCP server, and 6.7.12 added optional AI Discovery Files such as\n",[251,539,540],{},"llms.txt"," and ",[251,543,544],{},"agents.md",". Our article on\n",[181,547,548],{"href":81},"AI sales channels with Shopware","\nshows how to turn this into a measurable pilot channel.",[177,551,552],{},"The word experimental matters. These capabilities are suitable for controlled\nevaluation, not automatically as a fixed foundation for business-critical\nprocesses. Permissions, data scope, monitoring, and fallbacks need definition.",[192,554,556],{"id":555},"a-new-foundation-for-storefront-development","A new foundation for storefront development",[177,558,559],{},"Shopware 6.7.11 introduced Twig UX Components, a Vite-based storefront dev\nserver, CSS custom properties generated from theme settings, and a global\nJavaScript event system. Existing themes are not automatically rewritten –\nbut new components and incremental modernization gain a clearer, reusable\ndevelopment path.",[192,561,563],{"id":562},"why-upgrading-to-shopware-67-is-worthwhile","Why upgrading to Shopware 6.7 is worthwhile",[177,565,566],{},"Five reasons make the case: active development now happens only in the 6.7\nline, better technical future-readiness through Vue 3, Vite, and the new\ncache, measurable performance and stability gains, less legacy work before\nShopware 6.8 planned for 2027, and access to current functionality from B2B\nIndividual Pricing to Agentic Commerce.",[237,568,570],{"id":569},"active-development","Active development",[177,572,573],{},"New core and commercial functionality appears in the active 6.7 line, while\n6.6 in extended support primarily receives security corrections.",[237,575,577],{"id":576},"technical-future-readiness","Technical future-readiness",[177,579,580],{},"Vue 3, Pinia, Vite, current libraries, and new caching create a foundation for\nfuture extensions and Shopware versions.",[237,582,584],{"id":583},"performance-and-stability","Performance and stability",[177,586,587],{},"Caching, search, Administration, and failure handling have improved across many\nreleases. Large catalogs and integration-heavy setups can benefit measurably.",[237,589,591],{"id":590},"less-legacy-work-before-shopware-68","Less legacy work before Shopware 6.8",[177,593,594],{},"Resolving deprecations, plugin compatibility, and infrastructure requirements\nunder 6.7 reduces the eventual step to 6.8, which Shopware plans for 2027.",[237,596,598],{"id":597},"access-to-current-functionality","Access to current functionality",[177,600,601],{},"B2B Individual Pricing, native video, language management, Product Bundles,\nAgentic Commerce, and AI Discovery are compelling when they match the business\nmodel.",[192,603,605],{"id":604},"what-to-consider-before-upgrading","What to consider before upgrading",[177,607,608],{},"Never trial a major upgrade directly in production. The checklist runs from\nplugin and theme compatibility, through Admin extensions (Vite, Vue 3,\nPinia), infrastructure versions, and API integrations, to backups, rollback,\nand a maintenance window. Especially important: 6.7.12.0 contained a critical\nissue – install at least 6.7.12.1. The critical checks in detail:",[512,610,611,614,617,620,623,626,629,637],{},[515,612,613],{},"compatibility of every plugin, app, and theme,",[515,615,616],{},"custom Admin extensions affected by Vite, Vue 3, and Pinia,",[515,618,619],{},"storefront overrides and accessibility markup,",[515,621,622],{},"PHP, database, Redis, OpenSearch, and Node versions,",[515,624,625],{},"queue workers, cron jobs, reverse proxy, and cache configuration,",[515,627,628],{},"ERP, PIM, CRM, payment, and shipping integrations,",[515,630,631,632,636],{},"changes from the ",[181,633,635],{"href":303,"rel":634},[185],"official upgrade guide"," and deprecations,",[515,638,639],{},"backups, rollback, and a maintenance window.",[177,641,642,643,648,649,652],{},"Important: Shopware 6.7.12.0 contained a critical issue and, according to the\n",[181,644,647],{"href":645,"rel":646},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fnews\u002Fshopware-6-release-news-july-2026\u002F",[185],"July 2026 release news",",\nmust not be installed. Use at least\n",[181,650,449],{"href":447,"rel":651},[185]," or a\nnewer approved patch release.",[192,654,656],{"id":655},"recommended-upgrade-process","Recommended upgrade process",[177,658,659,660,663],{},"Nine steps take the upgrade live without unnecessary operational risk: from a\nsystem inventory, through compatibility confirmations, a production-like\nstage, and the technical upgrade, to automated tests, business tests, a\nperformance comparison, launch and rollback planning, and close monitoring.\nThe ",[181,661,305],{"href":303,"rel":662},[185]," adds\nthe technical details per version.",[665,666,667,673,679,685,691,697,703,709,715],"ol",{},[515,668,669,672],{},[200,670,671],{},"Inventory the system:"," Document versions, extensions, custom code,\ninfrastructure, and integrations.",[515,674,675,678],{},[200,676,677],{},"Confirm compatibility:"," Obtain vendor releases and replace abandoned\nextensions.",[515,680,681,684],{},[200,682,683],{},"Create a production-like stage:"," Reproduce data volume, configuration,\nworkers, search, and caching.",[515,686,687,690],{},[200,688,689],{},"Perform the technical upgrade:"," Check Composer conflicts, migrations,\nAdmin builds, and logs.",[515,692,693,696],{},[200,694,695],{},"Run automated tests:"," Cover APIs, checkout, rules, payments, and core\nbusiness processes.",[515,698,699,702],{},[200,700,701],{},"Run business tests:"," Involve sales, service, content, and logistics with\nrealistic scenarios.",[515,704,705,708],{},[200,706,707],{},"Compare performance:"," Measure response times, queues, search, cache hits,\nand database load before and after.",[515,710,711,714],{},[200,712,713],{},"Plan launch and rollback:"," Define owners, monitoring, maintenance window,\nand abort criteria.",[515,716,717,720],{},[200,718,719],{},"Monitor closely:"," Watch logs, orders, payments, feeds, and integrations\nduring the first days.",[192,722,724],{"id":723},"conclusion-67-is-now-a-mature-product-line","Conclusion: 6.7 is now a mature product line",[177,726,727],{},"At launch, Shopware 6.7 was primarily a technical foundation. More than a year\nlater, it has become a substantial product line with improvements to search,\nB2B, media, compliance, Analytics, Administration, and AI commerce.",[177,729,730],{},"The upgrade is particularly worthwhile for merchants who want current\nfunctionality, a modern platform, and preparation for 6.8. Its success still\ndepends on a complete compatibility review and production-like testing.",[237,732,734],{"id":733},"official-sources","Official sources",[512,736,737,743,749,755,761,768,774],{},[515,738,739],{},[181,740,742],{"href":213,"rel":741},[185],"Shopware 6.7 official major release overview",[515,744,745],{},[181,746,748],{"href":232,"rel":747},[185],"Shopware 6.7 release information and technical changes",[515,750,751],{},[181,752,754],{"href":303,"rel":753},[185],"Shopware 6.7 upgrade guide",[515,756,757],{},[181,758,760],{"href":219,"rel":759},[185],"Shopware release notes in the developer documentation",[515,762,763],{},[181,764,767],{"href":765,"rel":766},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fchangelog\u002F",[185],"Shopware changelog",[515,769,770],{},[181,771,773],{"href":645,"rel":772},[185],"July 2026 release news for 6.7.12.1",[515,775,776],{},[181,777,780],{"href":778,"rel":779},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases",[185],"Shopware 6.7 GitHub releases",{"title":782,"searchDepth":783,"depth":783,"links":784},"",2,[785,786,794,795,796,797,798,799,800,801,802,809,810,811],{"id":194,"depth":783,"text":195},{"id":225,"depth":783,"text":226,"children":787},[788,790,791,792,793],{"id":239,"depth":789,"text":240},3,{"id":263,"depth":789,"text":264},{"id":273,"depth":789,"text":274},{"id":283,"depth":789,"text":284},{"id":293,"depth":789,"text":294},{"id":308,"depth":783,"text":309},{"id":462,"depth":783,"text":463},{"id":476,"depth":783,"text":477},{"id":486,"depth":783,"text":487},{"id":496,"depth":783,"text":497},{"id":506,"depth":783,"text":507},{"id":533,"depth":783,"text":534},{"id":555,"depth":783,"text":556},{"id":562,"depth":783,"text":563,"children":803},[804,805,806,807,808],{"id":569,"depth":789,"text":570},{"id":576,"depth":789,"text":577},{"id":583,"depth":789,"text":584},{"id":590,"depth":789,"text":591},{"id":597,"depth":789,"text":598},{"id":604,"depth":783,"text":605},{"id":655,"depth":783,"text":656},{"id":723,"depth":783,"text":724,"children":812},[813],{"id":733,"depth":789,"text":734},[815,816,817,818,819,821,822],{"name":742,"url":213},{"name":748,"url":232},{"name":754,"url":303},{"name":767,"url":765},{"name":820,"url":219},"Shopware release notes (developer documentation)",{"name":773,"url":645},{"name":780,"url":778},"Shopware 6.7 modernizes performance, accessibility, and technology. We explain the key additions across the 6.7 line and a safe upgrade process.",false,"md",{"src":827,"alt":828},"\u002Fimages\u002Finsights\u002Fshopware-6-7-release-2026.png","Benedikt Rillox presenting the key Shopware 6.7 improvements covering performance, accessibility, technology, and commerce",{},true,null,"2026-08-17",11,{"title":835,"description":836},"Shopware 6.7: New features and upgrade benefits","What is new in Shopware 6.7? Explore performance, accessibility, Vite, Vue 3, B2B, Agentic Commerce, and a safe upgrade process.",{"loc":99,"lastmod":838},"2026-08-18","en\u002Finsights\u002Fshopware-6-7-release-update-benefits",[841,842,843],"Shopware","Update","Technology","insights-shopware-6-7-release","KZdLBF_jCVi0GIrcWSLAvkA630Si5I1n8gjso7istB8",{"id":847,"title":848,"alternateName":831,"bio":849,"body":850,"description":1020,"events":1021,"extension":825,"heroIllustration":1023,"image":1025,"meta":1028,"name":1027,"navigation":830,"ogImage":831,"path":165,"projects":831,"robots":831,"role":1029,"schemaOrg":831,"seo":1030,"sitemap":1031,"slug":172,"socials":1032,"stem":1034,"talks":831,"translationKey":1035,"__hash__":1036},"team_en\u002Fen\u002Fteam\u002Fbenedikt-rillox.md","Benedikt Rillox — Founder & Strategist","Benedikt is managing partner of nuonic Digital, e-commerce consultant, and developer. Since 2009 he has been designing, building, and guiding digital platforms — from code through product ownership to strategic leadership.",{"type":174,"value":851,"toc":1011},[852,856,862,865,868,871,875,878,881,884,887,890,894,897,900,903,926,929,933,936,939,942,959,963,966,969,975,978,982,985,988,991,995,998,1001],[192,853,855],{"id":854},"about-benedikt-rillox","About Benedikt Rillox",[857,858,859],"blockquote",{},[177,860,861],{},"To me, technology is not a cost item — it's a competitive advantage.",[177,863,864],{},"I'm Benedikt Rillox, managing partner of nuonic Digital, e-commerce consultant, and developer.",[177,866,867],{},"Since 2009 I have been designing, building, and guiding digital platforms. My path led from hands-on software development through product ownership and technical team leadership into entrepreneurial responsibility.",[177,869,870],{},"That's why I know e-commerce from very different perspectives: from the code, from product development, from budget responsibility, and from strategic leadership. Today I combine these experiences to build commerce systems that don't just work technically, but measurably move businesses forward.",[192,872,874],{"id":873},"my-path-in-e-commerce","My path in e-commerce",[177,876,877],{},"I started out as a developer for web and e-commerce projects using technologies like Shopware, TYPO3, PHP, and Symfony. During that time I delivered solutions for smaller companies as well as for well-known brands and corporations — including Unilever, Paul Hewitt, and Framily.",[177,879,880],{},"At A-Z Gartenhaus my role evolved from Shopware developer to product owner. There I helped build and lead a ten-person development team and was responsible for the strategic evolution of the commerce platform and its connected third-party systems.",[177,882,883],{},"For the Legero United group I took on budget responsibility as product owner and coordinated the technical development of the Superfit, legero, and Think! shops.",[177,885,886],{},"As tech lead for ByteClub I planned and built the commerce platforms of the group with brands like COMSPOT, Shifter, GfBD, and IM.F.B. Further projects included ongoing support and the Shopware 6 rebuild for Xucker, as well as the design and development of a Shopware payment plugin for topi that digitizes B2B leasing and buy-on-invoice.",[177,888,889],{},"These stations taught me that successful commerce projects never consist of technology alone. They combine architecture, processes, people, and clear business goals.",[192,891,893],{"id":892},"from-development-to-strategy","From development to strategy",[177,895,896],{},"I am a developer, a strategist, and a problem solver.",[177,898,899],{},"I can dive deep into technical details without losing sight of the actual goal: What impact should a solution have for the company, its people, and its customers?",[177,901,902],{},"Today my focus is on designing, building, and continuously evolving demanding Shopware systems. Among other things, that includes:",[512,904,905,908,911,914,917,920,923],{},[515,906,907],{},"technical and strategic e-commerce consulting,",[515,909,910],{},"software and Shopware development,",[515,912,913],{},"architecture and system integration,",[515,915,916],{},"product ownership and project management,",[515,918,919],{},"performance and stable operations,",[515,921,922],{},"automation and process optimization,",[515,924,925],{},"technical team leadership and collaboration with agencies.",[177,927,928],{},"Across more than 25 client projects I have seen what makes digital initiatives fail — and what makes them succeed. Good technology needs a clear direction, realistic requirements, and the courage to make decisions.",[192,930,932],{"id":931},"i-dont-build-shops-just-so-theyre-online","I don't build shops just so they're online",[177,934,935],{},"A shop can work technically and still be too slow, too complicated, or economically ineffective. That's why at nuonic we don't just look at individual features. We look at the whole system: architecture, processes, integrations, performance, customer journey, and the ability to grow in the future.",[177,937,938],{},"I don't believe in best practices when they merely mean copying what everyone else is already doing. I believe in solutions that fit a company's business model, its team, and its actual goals.",[177,940,941],{},"That also means asking uncomfortable questions:",[512,943,944,947,950,953,956],{},[515,945,946],{},"Does this feature really need to exist?",[515,948,949],{},"Does it solve a relevant problem?",[515,951,952],{},"Will the system remain manageable in the long run?",[515,954,955],{},"Does the investment support a concrete business goal?",[515,957,958],{},"Can the platform grow without collapsing under its own complexity?",[192,960,962],{"id":961},"responsibility-begins-after-go-live","Responsibility begins after go-live",[177,964,965],{},"To me, go-live is not a success. It's the beginning of responsibility.",[177,967,968],{},"Only in day-to-day operations does a platform prove whether it truly holds up: whether it stays stable, whether the team can work with it efficiently, and whether it can evolve without unnecessary friction.",[177,970,971,972],{},"That's why my work doesn't end with the handover. That's where the real value creation begins: ",[200,973,974],{},"Optimize. Automate. Scale.",[177,976,977],{},"I don't think in short-term projects, but in commerce systems that carry their weight for the long run. Technology shouldn't just cover today's needs — it should open up new possibilities.",[192,979,981],{"id":980},"clarity-is-part-of-working-together","Clarity is part of working together",[177,983,984],{},"Good results don't come from saying yes to every idea. That's why I also say no — to bad requirements, to short-term thinking, and to projects without a discernible direction.",[177,986,987],{},"I prefer working with decision-makers who take ownership. With teams that are ready to genuinely change things instead of merely managing existing problems. And with companies that see technology as an investment — not as a necessary cost item.",[177,989,990],{},"That's not always comfortable. But it creates clarity, protects budgets, and leads to better results.",[192,992,994],{"id":993},"what-i-stand-for","What I stand for",[177,996,997],{},"I don't want to simply be busy. I want to create impact.",[177,999,1000],{},"With nuonic we build commerce systems for companies that want to grow — faster, more stable, and more profitable.",[177,1002,1003,1004,1007,1008,1010],{},"Others talk about digitalization. We deliver it.",[1005,1006],"br",{},"\nOthers plan. We build.",[1005,1009],{},"\nOthers wait. We go.",{"title":782,"searchDepth":783,"depth":783,"links":1012},[1013,1014,1015,1016,1017,1018,1019],{"id":854,"depth":783,"text":855},{"id":873,"depth":783,"text":874},{"id":892,"depth":783,"text":893},{"id":931,"depth":783,"text":932},{"id":961,"depth":783,"text":962},{"id":980,"depth":783,"text":981},{"id":993,"depth":783,"text":994},"Projects, references, talks and events by Benedikt Rillox — founder and strategist at nuonic Digital, e-commerce consultant and developer since 2009.",[1022],"omr-festival-2026",{"src":1024,"alt":782},"\u002Fimages\u002Fteam\u002Fdefender.png",{"src":1026,"alt":1027},"\u002Fimages\u002Fteam\u002Fbenedikt-rillox.jpg","Benedikt Rillox",{},"Founder & Strategist",{"title":848,"description":1020},{"loc":165},{"linkedin":1033,"github":782},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fbenedikt-rillox-4122b183\u002F","en\u002Fteam\u002Fbenedikt-rillox","team-benedikt-rillox","v_3soXCfOhR229BeXf4LbuPOy_IZ5RoXQ3YPFywykxw",1787059086150]