[{"data":1,"prerenderedAt":1001},["ShallowReactive",2],{"locale-routes":3,"squeeze-paths":226,"announcements":227,"page-\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation":228,"insights-author-\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation":806},{"home":4,"shopware-margin-check":7,"shopware-plugin-report":10,"privacy":13,"framework-focus":16,"framework":19,"framework-principles":22,"imprint":25,"contact":28,"newsletter-confirmed":31,"shopware-agency-b2b":34,"shopware-agency-electronics":37,"shopware-agency-development":40,"shopware-extension-b2b-quote-management":43,"shopware-agency-geo":46,"shopware-agency":49,"shopware-agency-pricing":52,"shopware-cost-calculator":55,"shopware-agency-migration":58,"shopware-agency-seo":61,"shopware-agency-support":64,"shopware-agency-switch":67,"location-hamburg":70,"location-munich":73,"about":76,"about-mission":79,"about-partners":82,"services-consulting":85,"services-development":88,"services":91,"services-optimization":94,"services-growth":97,"insights-ai-sales-channels-shopware":100,"insights-b2b-quote-management-release":103,"insights-b2b-shop-starten-checkliste":106,"insights-ecommerce-deadlines-2026-27":109,"insights-e-invoice-b2b-shopware-xrechnung-zugferd":112,"insights-ecommerce-search-that-finds":115,"insights-warranty-notice-vs-garan-label":118,"insights-warranty-label-shopware-6":121,"insights-handelskoenig-b2b-quotes":124,"insights-shopware-5-eol":127,"insights-shopware-6-7-release":130,"insights-shopware-6-8-outlook":133,"insights-shopware-6-plans-pricing-2026":136,"insights-shopware-6-migration-noetig":139,"insights-shopware-gmv-2026":142,"insights-shopware-vs-shopify-2026":145,"insights-shopware-maintenance-retainer-development":148,"insights-withdrawal-button-shopware-6":151,"whitepaper-agentic-commerce-b2b-beschaffung":154,"whitepaper-agenturwechsel-wartungsprojekt":157,"whitepaper-compliance-2026-27":160,"whitepapers":163,"whitepaper-kanalverbund-marktplatz-shop-agentic":166,"whitepaper-shopware-6-boutique-vs-grossagentur-tco":169,"case-comspot-focus":172,"case-converge-focus":175,"case-framily-focus":178,"case-ghs-waescherutsche-focus":181,"case-handelskoenig-focus":184,"case-lupa-focus":187,"case-shifter-focus":190,"case-searchhub-comspot":193,"case-topi-focus":196,"case-xucker-focus":199,"talks-beyond-seo-scuc-2026":202,"talks":205,"talks-shopware-container-hosting-hitc-2026":208,"talks-symfony-cli-docker-scuc-2025":211,"webinars":214,"team-alex-jank":217,"team-benedikt-rillox":220,"team":223},{"de":5,"en":6},"\u002F","\u002Fen",{"de":8,"en":9},"\u002Fshopware-margen-check","\u002Fen\u002Fshopware-margin-check",{"de":11,"en":12},"\u002Fshopware-plugin-report","\u002Fen\u002Fshopware-plugin-report",{"de":14,"en":15},"\u002Fdatenschutz","\u002Fen\u002Fprivacy",{"de":17,"en":18},"\u002Fframework\u002Ffocus","\u002Fen\u002Fframework\u002Ffocus",{"de":20,"en":21},"\u002Fframework","\u002Fen\u002Fframework",{"de":23,"en":24},"\u002Fframework\u002Fprinzipien","\u002Fen\u002Fframework\u002Fprinciples",{"de":26,"en":27},"\u002Fimpressum","\u002Fen\u002Fimprint",{"de":29,"en":30},"\u002Fkontakt","\u002Fen\u002Fcontact",{"de":32,"en":33},"\u002Fnewsletter\u002Fbestaetigt","\u002Fen\u002Fnewsletter\u002Fconfirmed",{"de":35,"en":36},"\u002Fshopware-agentur\u002Fb2b","\u002Fen\u002Fshopware-agency\u002Fb2b",{"de":38,"en":39},"\u002Fshopware-agentur\u002Felektronikhandel","\u002Fen\u002Fshopware-agency\u002Felectronics-retail",{"de":41,"en":42},"\u002Fshopware-agentur\u002Fentwicklung","\u002Fen\u002Fshopware-agency\u002Fdevelopment",{"de":44,"en":45},"\u002Fshopware-agentur\u002Fentwicklung\u002Fb2b-angebotsverwaltung-preisanfragen","\u002Fen\u002Fshopware-agency\u002Fdevelopment\u002Fb2b-quote-management-price-requests",{"de":47,"en":48},"\u002Fshopware-agentur\u002Fgeo","\u002Fen\u002Fshopware-agency\u002Fgeo",{"de":50,"en":51},"\u002Fshopware-agentur","\u002Fen\u002Fshopware-agency",{"de":53,"en":54},"\u002Fshopware-agentur\u002Fkosten","\u002Fen\u002Fshopware-agency\u002Fpricing",{"de":56,"en":57},"\u002Fshopware-agentur\u002Fkosten-rechner","\u002Fen\u002Fshopware-agency\u002Fcost-calculator",{"de":59,"en":60},"\u002Fshopware-agentur\u002Fmigration","\u002Fen\u002Fshopware-agency\u002Fmigration",{"de":62,"en":63},"\u002Fshopware-agentur\u002Fseo","\u002Fen\u002Fshopware-agency\u002Fseo",{"de":65,"en":66},"\u002Fshopware-agentur\u002Fsupport","\u002Fen\u002Fshopware-agency\u002Fsupport",{"de":68,"en":69},"\u002Fshopware-agentur\u002Fwechsel","\u002Fen\u002Fshopware-agency\u002Fswitch",{"de":71,"en":72},"\u002Fstandorte\u002Fhamburg","\u002Fen\u002Flocations\u002Fhamburg",{"de":74,"en":75},"\u002Fstandorte\u002Fmuenchen","\u002Fen\u002Flocations\u002Fmunich",{"de":77,"en":78},"\u002Fueber-uns","\u002Fen\u002Fabout",{"de":80,"en":81},"\u002Fueber-uns\u002Fmission","\u002Fen\u002Fabout\u002Fmission",{"de":83,"en":84},"\u002Fueber-uns\u002Fpartner","\u002Fen\u002Fabout\u002Fpartners",{"de":86,"en":87},"\u002Fleistungen\u002Fberatung","\u002Fen\u002Fservices\u002Fconsulting",{"de":89,"en":90},"\u002Fleistungen\u002Fentwicklung","\u002Fen\u002Fservices\u002Fdevelopment",{"de":92,"en":93},"\u002Fleistungen","\u002Fen\u002Fservices",{"de":95,"en":96},"\u002Fleistungen\u002Foptimierung","\u002Fen\u002Fservices\u002Foptimization",{"de":98,"en":99},"\u002Fleistungen\u002Fwachstum","\u002Fen\u002Fservices\u002Fgrowth",{"de":101,"en":102},"\u002Finsights\u002Fai-verkaufskanaele-shopware","\u002Fen\u002Finsights\u002Fai-sales-channels-shopware",{"de":104,"en":105},"\u002Finsights\u002Fb2b-angebotsverwaltung-shopware-store-release","\u002Fen\u002Finsights\u002Fb2b-quote-management-shopware-store-release",{"de":107,"en":108},"\u002Finsights\u002Fb2b-shop-starten-checkliste-shopware","\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist",{"de":110,"en":111},"\u002Finsights\u002Fe-commerce-fristen-2026-27","\u002Fen\u002Finsights\u002Fe-commerce-deadlines-2026-27",{"de":113,"en":114},"\u002Finsights\u002Fe-rechnung-b2b-shopware-xrechnung-zugferd","\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd",{"de":116,"en":117},"\u002Finsights\u002Fecommerce-suche-die-findet","\u002Fen\u002Finsights\u002Fecommerce-search-that-finds",{"de":119,"en":120},"\u002Finsights\u002Fgewaehrleistungshinweis-vs-garan-label","\u002Fen\u002Finsights\u002Fwarranty-notice-vs-garan-label",{"de":122,"en":123},"\u002Finsights\u002Fgewaehrleistungslabel-shopware-6","\u002Fen\u002Finsights\u002Fwarranty-label-shopware-6",{"de":125,"en":126},"\u002Finsights\u002Fhandelskoenig-b2b-angebotsanfragen","\u002Fen\u002Finsights\u002Fhandelskoenig-b2b-quote-requests",{"de":128,"en":129},"\u002Finsights\u002Fshopware-5-eol","\u002Fen\u002Finsights\u002Fshopware-5-end-of-life",{"de":131,"en":132},"\u002Finsights\u002Fshopware-6-7-release-update-vorteile","\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits",{"de":134,"en":135},"\u002Finsights\u002Fshopware-6-8-ausblick-roadmap-vorbereitung","\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation",{"de":137,"en":138},"\u002Finsights\u002Fshopware-6-lizenzen-kosten-2026","\u002Fen\u002Finsights\u002Fshopware-6-plans-pricing-2026",{"de":140,"en":141},"\u002Finsights\u002Fshopware-6-migration-noetig","\u002Fen\u002Finsights\u002Fshopware-6-migration-necessary",{"de":143,"en":144},"\u002Finsights\u002Fshopware-gmv-berechnung-1-million-grenze","\u002Fen\u002Finsights\u002Fshopware-gmv-calculation-one-million-threshold",{"de":146,"en":147},"\u002Finsights\u002Fshopware-vs-shopify-vergleich-2026","\u002Fen\u002Finsights\u002Fshopware-vs-shopify-comparison-2026",{"de":149,"en":150},"\u002Finsights\u002Fshopware-wartung-retainer-weiterentwicklung","\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development",{"de":152,"en":153},"\u002Finsights\u002Fwiderrufsbutton-shopware-6","\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6",{"de":155,"en":156},"\u002Fwhitepapers\u002Fagentic-commerce-b2b-beschaffung","\u002Fen\u002Fwhitepapers\u002Fagentic-commerce-b2b-procurement",{"de":158,"en":159},"\u002Fwhitepapers\u002Fagenturwechsel-wartungsprojekt","\u002Fen\u002Fwhitepapers\u002Fagency-switch-maintenance-project",{"de":161,"en":162},"\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27","\u002Fen\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27",{"de":164,"en":165},"\u002Fwhitepapers","\u002Fen\u002Fwhitepapers",{"de":167,"en":168},"\u002Fwhitepapers\u002Fkanalverbund-marktplatz-shop-agentic","\u002Fen\u002Fwhitepapers\u002Fchannel-network-marketplace-shop-agentic",{"de":170,"en":171},"\u002Fwhitepapers\u002Fshopware-6-boutique-vs-grossagentur-tco","\u002Fen\u002Fwhitepapers\u002Fshopware-6-boutique-vs-large-agency-tco",{"de":173,"en":174},"\u002Fcase-studies\u002Fcomspot-focus","\u002Fen\u002Fcase-studies\u002Fcomspot-focus",{"de":176,"en":177},"\u002Fcase-studies\u002Fconverge-focus","\u002Fen\u002Fcase-studies\u002Fconverge-focus",{"de":179,"en":180},"\u002Fcase-studies\u002Fframily-focus","\u002Fen\u002Fcase-studies\u002Fframily-focus",{"de":182,"en":183},"\u002Fcase-studies\u002Fghs-waescherutsche-focus","\u002Fen\u002Fcase-studies\u002Fghs-waescherutsche-focus",{"de":185,"en":186},"\u002Fcase-studies\u002Fhandelskoenig-focus","\u002Fen\u002Fcase-studies\u002Fhandelskoenig-focus",{"de":188,"en":189},"\u002Fcase-studies\u002Flupa-focus","\u002Fen\u002Fcase-studies\u002Flupa-focus",{"de":191,"en":192},"\u002Fcase-studies\u002Fshifter-focus","\u002Fen\u002Fcase-studies\u002Fshifter-focus",{"de":194,"en":195},"\u002Fcase-studies\u002Fshopware-suchintegration","\u002Fen\u002Fcase-studies\u002Fshopware-search-integration",{"de":197,"en":198},"\u002Fcase-studies\u002Ftopi-focus","\u002Fen\u002Fcase-studies\u002Ftopi-focus",{"de":200,"en":201},"\u002Fcase-studies\u002Fxucker-focus","\u002Fen\u002Fcase-studies\u002Fxucker-focus",{"de":203,"en":204},"\u002Fvortraege\u002Fbeyond-seo-scuc-2026","\u002Fen\u002Ftalks\u002Fbeyond-seo-scuc-2026",{"de":206,"en":207},"\u002Fvortraege","\u002Fen\u002Ftalks",{"de":209,"en":210},"\u002Fvortraege\u002Fshopware-container-hosting-hitc-2026","\u002Fen\u002Ftalks\u002Fshopware-container-hosting-hitc-2026",{"de":212,"en":213},"\u002Fvortraege\u002Fsymfony-cli-docker-scuc-2025","\u002Fen\u002Ftalks\u002Fsymfony-cli-docker-scuc-2025",{"de":215,"en":216},"\u002Fwebinare","\u002Fen\u002Fwebinars",{"de":218,"en":219},"\u002Fteam\u002Falex-jank","\u002Fen\u002Fteam\u002Falex-jank",{"de":221,"en":222},"\u002Fteam\u002Fbenedikt-rillox","\u002Fen\u002Fteam\u002Fbenedikt-rillox",{"de":224,"en":225},"\u002Fteam","\u002Fen\u002Fteam",[8,11,9,12],[],{"id":229,"title":230,"author":231,"body":232,"citations":774,"description":783,"draft":784,"extension":785,"image":786,"meta":789,"navigation":790,"ogImage":791,"path":135,"publishedAt":792,"readingTime":793,"robots":791,"schemaOrg":791,"seo":794,"sitemap":798,"squeeze":784,"stem":799,"tags":800,"translationKey":804,"updatedAt":791,"__hash__":805},"insights_en\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation.md","Shopware 6.8: Outlook, roadmap, changes, and preparation","benedikt-rillox",{"type":233,"value":234,"toc":737},"minimark",[235,244,247,250,277,282,293,296,308,311,315,318,321,338,341,345,348,361,365,368,371,375,387,390,394,409,412,416,423,426,430,442,445,449,458,461,465,474,477,481,489,492,496,499,502,506,515,522,526,529,534,541,545,548,552,555,559,562,566,569,573,576,580,587,591,594,611,615,618,622,639,643,660,664,678,682,685,688,692,695,698,701,705],[236,237,238,239,243],"p",{},"Shopware 6.8 will be the next major release after Shopware 6.7. Originally\nexpected in 2026, it has officially been postponed to ",[240,241,242],"strong",{},"2027",". As of August\n17, 2026, Shopware has not published a specific date or final scope.",[236,245,246],{},"The release is nevertheless relevant today. The public upgrade guide already\nshows initial technical changes, some extensions have a confirmed end of\nsupport, and the 6.7 line contains migration paths, feature flags, and\ndeprecations for the next major step.",[236,248,249],{},"A reliable outlook needs to distinguish three categories:",[251,252,253,260,271],"ol",{},[254,255,256,259],"li",{},[240,257,258],{},"Officially confirmed:"," The broad schedule and strategic priorities.",[254,261,262,265,266,270],{},[240,263,264],{},"Technically in preparation:"," Changes in the evolving ",[267,268,269],"code",{},"UPGRADE-6.8.md","\nthat may still change before release.",[254,272,273,276],{},[240,274,275],{},"Under discussion:"," RFCs and drafts that are not release commitments.",[278,279,281],"h2",{"id":280},"what-shopware-has-officially-confirmed-about-68","What Shopware has officially confirmed about 6.8",[236,283,284,285,292],{},"Three things are officially confirmed: Shopware ",[286,287,291],"a",{"href":288,"rel":289},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fnews\u002Fnext-major-version-6-8-planned-for-2027\u002F",[290],"nofollow","announced on November 12,\n2025 that 6.8 would move from 2026 to\n2027",",\nnames stability, documentation, and Agentic AI as its priorities for the\nextended period, and extends support for Shopware 6.6 until 6.8 becomes\navailable. As the reason for the postponement, the company cites the balance\nbetween progress, robustness, stability, and developer experience.",[236,294,295],{},"Shopware names three priorities for the extended development period:",[297,298,299,302,305],"ul",{},[254,300,301],{},"platform stability, performance, and security,",[254,303,304],{},"improved documentation and developer experience,",[254,306,307],{},"continued development of Agentic AI capabilities.",[236,309,310],{},"Extended support for Shopware 6.6 will continue until 6.8 becomes available.\nThis gives merchants on 6.6 more time, but extended support should not be\nconfused with the active feature development happening in 6.7.",[278,312,314],{"id":313},"why-the-postponement-can-be-beneficial","Why the postponement can be beneficial",[236,316,317],{},"A major release permits breaking changes — and every such change creates work\nfor extension vendors, agencies, and merchants. The longer cycle buys\neveryone time: for stabilization, extension migrations, longer-visible\ndeprecations, and a planned replacement of the B2B Suite and language pack.\nShopware has also shown that visible commerce capabilities can be delivered\nthrough 6.7 minor releases.",[236,319,320],{},"The longer cycle offers several opportunities:",[297,322,323,326,329,332,335],{},[254,324,325],{},"6.7 can be stabilized and expanded further.",[254,327,328],{},"Extension vendors have more migration time.",[254,330,331],{},"Deprecations can remain visible longer before removal.",[254,333,334],{},"Merchants can replace the B2B Suite, language pack, and custom legacy code in\na planned way.",[254,336,337],{},"Architectural changes can be prepared through feature flags and testing.",[236,339,340],{},"The extra time is not a reason to do nothing until 2027. Teams that begin all\nchanges only at release waste the preparation window.",[278,342,344],{"id":343},"what-a-major-release-is-likely-to-change","What a major release is likely to change",[236,346,347],{},"Shopware major releases are traditionally the point at which obsolete APIs,\nservices, configuration options, and compatibility layers are removed. New\nvisible features may appear as well, but the most important result is often a\ncleaner technical foundation.",[236,349,350,351,356,357,360],{},"The ",[286,352,355],{"href":353,"rel":354},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Fblob\u002Ftrunk\u002FUPGRADE-6.8.md",[290],"current upgrade guide on Shopware's\ntrunk"," is\nuseful for this reason. It is\na ",[240,358,359],{},"living developer document, not a final release contract",". The following\npoints represent its status in August 2026.",[278,362,364],{"id":363},"in-preparation-removal-of-deprecations","In preparation: removal of deprecations",[236,366,367],{},"Shopware marks APIs and configuration as deprecated in 6.7 before removing\nthem in 6.8. The affected areas include old cache options, Administration\nblocks, services, events, and API behavior.",[236,369,370],{},"Most of this is invisible to a standard store. Custom plugins and deep\nintegrations can use these interfaces directly. Deprecation logs and upgrade\ndocumentation should therefore be reviewed before 6.8 is released.",[278,372,374],{"id":373},"axios-1-becomes-the-administration-default","Axios 1 becomes the Administration default",[236,376,377,378,381,382,386],{},"Shopware 6.7 already supports Axios 1 alongside the older client. Custom\nAdministration extensions can opt in using ",[267,379,380],{},"useAxiosV1: true",". The ",[286,383,385],{"href":353,"rel":384},[290],"current\n6.8 guide","\nmakes Axios 1 the default.",[236,388,389],{},"Relevant differences include request cancellation, error codes, and some\ndefaults. Plugin developers should test HTTP calls with the new client under\n6.7 rather than assume a compatibility mode will remain available.",[278,391,393],{"id":392},"webhooks-receive-a-dedicated-messenger-transport","Webhooks receive a dedicated Messenger transport",[236,395,350,396,400,401,404,405,408],{},[286,397,399],{"href":353,"rel":398},[290],"current 6.8\nguide","\ndescribes a dedicated ",[267,402,403],{},"webhook"," transport. Operators who\noverride Messenger receivers or ",[267,406,407],{},"shopware.admin_worker.transports"," need to add\nit. Otherwise, webhooks may no longer be processed after the update.",[236,410,411],{},"This is a small configuration change with major operational impact. Default\nsetups may work automatically, while custom worker configurations need an\nexplicit review.",[278,413,415],{"id":414},"the-cache-rework-continues","The cache rework continues",[236,417,418,419,422],{},"Shopware 6.7 removed the previous Store API cache layer and prepared a new HTTP\ncaching model. The ",[286,420,399],{"href":353,"rel":421},[290],"\nremoves obsolete configuration and moves\nselected cacheable Store API GET routes into the standard HTTP cache.",[236,424,425],{},"Operators should document and measure reverse proxy behavior, cache keys,\ninvalidation, and response headers under 6.7 instead of copying old settings\nblindly.",[278,427,429],{"id":428},"agentic-commerce-moves-out-of-the-core","Agentic Commerce moves out of the core",[236,431,432,433,437,438,441],{},"The experimental Agentic Commerce sales channel was tested in the 6.7 core.\nThe ",[286,434,436],{"href":353,"rel":435},[290],"current 6.8 upgrade\nguide","\ninstructs merchants to install the\n",[267,439,440],{},"SwagAgenticCommerce"," extension before updating to retain configured sales\nchannels and functionality.",[236,443,444],{},"This suggests a more modular evolution outside the core. Merchants using the\nexperimental channel should document data, feed URLs, configuration, and\ntracking before migration.",[278,446,448],{"id":447},"b2b-suite-ends-b2b-components-become-the-target","B2B Suite ends; B2B Components become the target",[236,450,451,452,457],{},"Shopware ",[286,453,456],{"href":454,"rel":455},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fextensions\u002Fb2b-suite-administration",[290],"confirms in its\ndocumentation","\nthat the legacy B2B Suite will no longer be supported from\n6.8. New B2B functionality is already being developed in B2B Components.",[236,459,460],{},"Affected merchants need more than an extension swap. Organizations, employees,\nroles, budgets, approvals, quotes, order lists, customer-specific catalogs,\nand individual pricing all require assessment. A production B2B migration is\na dedicated business project.",[278,462,464],{"id":463},"the-former-language-pack-will-no-longer-be-supported","The former language pack will no longer be supported",[236,466,467,468,473],{},"Since 6.7.3, Shopware can manage available translations natively from the core.\n",[286,469,472],{"href":470,"rel":471},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fextensions\u002Flanguage-pack",[290],"According to the\ndocumentation",",\nthe language-pack extension will no longer be supported from 6.8.",[236,475,476],{},"Before moving, review installed languages, custom snippets, plugin\ntranslations, and deployment workflows. Core migration does not replace an\neditorial translation strategy.",[278,478,480],{"id":479},"storefront-and-developer-experience","Storefront and developer experience",[236,482,451,483,488],{},[286,484,487],{"href":485,"rel":486},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.11.0",[290],"6.7.11","\nintroduced Twig UX Components, a Vite-based storefront dev\nserver, CSS custom properties generated from theme settings, and a global\nJavaScript event system. These building blocks point toward reusable components\nand modern development workflows.",[236,490,491],{},"It is not yet confirmed which foundations become mandatory in 6.8 or replace\nexisting mechanisms. New themes and components should still consider the\ncurrent 6.7 approaches to avoid creating fresh legacy code.",[278,493,495],{"id":494},"agentic-ai-remains-a-strategic-priority","Agentic AI remains a strategic priority",[236,497,498],{},"Shopware explicitly names Agentic AI as a focus through 6.8. The 6.7 line\nalready includes Agentic Commerce feeds, AI Discovery Files, Copilot blueprints,\nand an experimental MCP server.",[236,500,501],{},"This does not mean every future AI capability will ship in 6.8 or Community\nEdition. Shopware may deliver features through minor releases, commercial\nextensions, or services. The strategic direction is confirmed; individual\nproduct details are not.",[278,503,505],{"id":504},"under-discussion-an-entity-based-cart","Under discussion: an entity-based cart",[236,507,508,509,514],{},"A ",[286,510,513],{"href":511,"rel":512},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Fdiscussions\u002F14610",[290],"public Shopware\nRFC"," discusses\nreplacing the session-based cart with an\nentity-based system targeting 6.8. Stated goals include multiple carts per\ncustomer, better performance, and reduced architectural complexity.",[236,516,517,518,521],{},"Its status is ",[240,519,520],{},"Draft",". It must not be presented as a committed feature. The\nRFC is still useful because it indicates which fundamental commerce models\nShopware is exploring.",[278,523,525],{"id":524},"what-merchants-should-prepare-now","What merchants should prepare now",[236,527,528],{},"Seven preparations pay off regardless of the final release date: keep\nShopware 6.7 current, document the extension inventory, review custom code\nfor deprecations, migrate B2B Suite and language pack, document the\ninfrastructure, build automated core tests, and reserve budget and a release\nwindow. Each one reduces the eventual major-upgrade risk — even if the 6.8\nscope still changes.",[530,531,533],"h3",{"id":532},"_1-keep-shopware-67-current","1. Keep Shopware 6.7 current",[236,535,536,537,540],{},"A maintained 6.7 system exposes deprecations, migration paths, and new\ncompatibility options early. Jumping from an old 6.6 or neglected 6.7 version\ndirectly to 6.8 would change more variables at once. What the\n",[286,538,539],{"href":132},"update to Shopware 6.7"," brings and\nhow to run it cleanly is covered separately.",[530,542,544],{"id":543},"_2-create-an-extension-inventory","2. Create an extension inventory",[236,546,547],{},"Record vendor, version, business criticality, maintenance status, and possible\nreplacement for every plugin, app, and theme. Unmaintained extensions deserve\nparticular attention.",[530,549,551],{"id":550},"_3-review-custom-code-for-deprecations","3. Review custom code for deprecations",[236,553,554],{},"Static analysis, tests, and logs should reveal outdated APIs, Administration\noverrides, Axios calls, cache configuration, and event subscribers. Every\ndeprecation removed under 6.7 reduces later major-upgrade risk.",[530,556,558],{"id":557},"_4-migrate-b2b-suite-and-language-pack","4. Migrate B2B Suite and language pack",[236,560,561],{},"Both support endings are officially documented. Affected projects should\ncomplete analysis and migration well before the 6.8 production update.",[530,563,565],{"id":564},"_5-document-the-infrastructure","5. Document the infrastructure",[236,567,568],{},"Record PHP, database, Redis, OpenSearch, queue workers, cron, reverse proxy,\nNode toolchain, deployment, and observability. Final 6.8 system requirements\nare pending, but undocumented custom configuration is already a risk.",[530,570,572],{"id":571},"_6-build-automated-core-tests","6. Build automated core tests",[236,574,575],{},"At minimum, login, search, cart, checkout, payment, order transfer, customer\naccount, and core API flows should be reproducible. Without regression tests,\nevery release candidate becomes a large manual project.",[530,577,579],{"id":578},"_7-reserve-budget-and-a-release-window","7. Reserve budget and a release window",[236,581,582,583,586],{},"Major upgrades require analysis, adaptation, testing, deployment, and\nmonitoring. A placeholder in the roadmap and budget prevents 6.8 from becoming\nunplanned maintenance. The easiest way is to anchor it in an ongoing\n",[286,584,585],{"href":150},"maintenance retainer"," that\nplans for major upgrades from the outset.",[278,588,590],{"id":589},"what-merchants-should-not-do-yet","What merchants should not do yet",[236,592,593],{},"Just as important as the preparation is the boundary: the year 2027 is not a\nlaunch date, an RFC is not a confirmed feature, and today's trunk guide is\nnot a release contract. Basing architecture or budget decisions solely on\nunconfirmed 6.8 details builds on sand. In concrete terms:",[297,595,596,599,602,605,608],{},[254,597,598],{},"Do not infer a final launch date from the year 2027.",[254,600,601],{},"Do not sell an RFC as a confirmed feature.",[254,603,604],{},"Do not design production architecture solely around today's trunk guide.",[254,606,607],{},"Do not postpone every useful 6.7 feature because 6.8 is planned.",[254,609,610],{},"Do not wait for the first release candidate to analyze B2B Suite or language\npack migration.",[278,612,614],{"id":613},"a-realistic-internal-timeline","A realistic internal timeline",[236,616,617],{},"The internal timeline splits into three phases: clean-up work from today\nuntil an official preview, production-like testing during the\nrelease-candidate phase, and a controlled, unhurried rollout after the final\nrelease. Teams that take the first phase seriously turn the other two into\nroutine work instead of crisis projects.",[530,619,621],{"id":620},"now-until-an-official-preview","Now until an official preview",[297,623,624,627,630,633,636],{},[254,625,626],{},"update and stabilize 6.7,",[254,628,629],{},"inventory extensions and custom code,",[254,631,632],{},"resolve deprecations,",[254,634,635],{},"start confirmed migrations,",[254,637,638],{},"expand automated tests.",[530,640,642],{"id":641},"during-release-candidates","During release candidates",[297,644,645,648,651,654,657],{},[254,646,647],{},"update a production-like stage,",[254,649,650],{},"verify final system requirements,",[254,652,653],{},"test plugins and themes using approved versions,",[254,655,656],{},"compare performance and core business processes,",[254,658,659],{},"plan rollback and maintenance windows.",[530,661,663],{"id":662},"after-the-final-release","After the final release",[297,665,666,669,672,675],{},[254,667,668],{},"do not automatically update production on day one,",[254,670,671],{},"assess first patches and vendor approvals,",[254,673,674],{},"weigh individual risk and required features,",[254,676,677],{},"deploy with monitoring and a post-release review.",[278,679,681],{"id":680},"is-it-worth-waiting-for-68","Is it worth waiting for 6.8?",[236,683,684],{},"For most active stores, the answer is no. Shopware 6.7 continues to receive\nfeatures, performance improvements, and security updates, while 6.8 is\nplanned for 2027 but has neither a fixed date nor a final scope. A maintained\n6.7 foundation is at the same time the best preparation for 6.8 — waiting\nbrings no advantage.",[236,686,687],{},"Remaining on an older version may mean foregoing improvements for a long time\nand increasing the eventual migration step.",[278,689,691],{"id":690},"conclusion-68-preparation-begins-by-cleaning-up-67","Conclusion: 6.8 preparation begins by cleaning up 6.7",[236,693,694],{},"The reliable 6.8 outlook currently consists less of a completed feature list\nthan a clear direction: release in 2027 with more emphasis on stability,\nperformance, security, developer experience, and Agentic AI.",[236,696,697],{},"Technical preparations are already visible. Axios 1, webhook transport, cache\ncleanup, modular Agentic Commerce, and the end of B2B Suite and language pack\nprovide concrete work packages.",[236,699,700],{},"The best time to prepare is not release day. Teams that maintain 6.7, remove\ndeprecations, automate tests, and finish confirmed migrations turn 6.8 into a\nplanned upgrade rather than an emergency project.",[530,702,704],{"id":703},"official-sources","Official sources",[297,706,707,713,719,725,731],{},[254,708,709],{},[286,710,712],{"href":288,"rel":711},[290],"Shopware: Next major version 6.8 planned for 2027",[254,714,715],{},[286,716,718],{"href":353,"rel":717},[290],"Evolving technical upgrade guide for Shopware 6.8",[254,720,721],{},[286,722,724],{"href":454,"rel":723},[290],"Shopware B2B Suite end of support with 6.8",[254,726,727],{},[286,728,730],{"href":470,"rel":729},[290],"Shopware language pack documentation",[254,732,733],{},[286,734,736],{"href":511,"rel":735},[290],"Entity-based cart RFC – Draft status",{"title":738,"searchDepth":739,"depth":739,"links":740},"",2,[741,742,743,744,745,746,747,748,749,750,751,752,753,754,764,765,770,771],{"id":280,"depth":739,"text":281},{"id":313,"depth":739,"text":314},{"id":343,"depth":739,"text":344},{"id":363,"depth":739,"text":364},{"id":373,"depth":739,"text":374},{"id":392,"depth":739,"text":393},{"id":414,"depth":739,"text":415},{"id":428,"depth":739,"text":429},{"id":447,"depth":739,"text":448},{"id":463,"depth":739,"text":464},{"id":479,"depth":739,"text":480},{"id":494,"depth":739,"text":495},{"id":504,"depth":739,"text":505},{"id":524,"depth":739,"text":525,"children":755},[756,758,759,760,761,762,763],{"id":532,"depth":757,"text":533},3,{"id":543,"depth":757,"text":544},{"id":550,"depth":757,"text":551},{"id":557,"depth":757,"text":558},{"id":564,"depth":757,"text":565},{"id":571,"depth":757,"text":572},{"id":578,"depth":757,"text":579},{"id":589,"depth":739,"text":590},{"id":613,"depth":739,"text":614,"children":766},[767,768,769],{"id":620,"depth":757,"text":621},{"id":641,"depth":757,"text":642},{"id":662,"depth":757,"text":663},{"id":680,"depth":739,"text":681},{"id":690,"depth":739,"text":691,"children":772},[773],{"id":703,"depth":757,"text":704},[775,777,778,780,782],{"name":776,"url":288},"Shopware: next major version 6.8 planned for 2027",{"name":718,"url":353},{"name":779,"url":454},"Shopware B2B Suite – end of support with 6.8",{"name":781,"url":470},"Shopware language pack – end of support with 6.8",{"name":736,"url":511},"Shopware 6.8 is planned for 2027. We separate the confirmed roadmap, technical preparations, and open proposals and explain what merchants should do now.",false,"md",{"src":787,"alt":788},"\u002Fimages\u002Finsights\u002Fshopware-6-8-ausblick-2027.png","Benedikt Rillox presenting the Shopware 6.8 outlook for 2027 with roadmap and preparation steps",{},true,null,"2026-08-17",10,{"title":795,"description":796,"articleModifiedTime":797},"Shopware 6.8: Outlook and preparation","What is known about Shopware 6.8? The official 2027 roadmap, possible technical changes, retiring extensions, and practical preparation.","2026-08-21",{"loc":135,"lastmod":797},"en\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation",[801,802,803],"Shopware","Roadmap","Update","insights-shopware-6-8-outlook","LvTMehXytSZBj3il-yzEmOFK1fOQHnwnPoNh7Kj7DJ4",{"id":807,"title":808,"alternateName":791,"bio":809,"body":810,"description":980,"events":981,"extension":785,"heroIllustration":983,"image":985,"meta":988,"name":987,"navigation":790,"ogImage":791,"path":222,"projects":791,"publishedAt":791,"robots":791,"role":989,"sameAs":990,"schemaOrg":791,"seo":994,"sitemap":996,"slug":231,"socials":997,"squeeze":784,"stem":998,"talks":791,"translationKey":999,"updatedAt":791,"__hash__":1000},"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":233,"value":811,"toc":971},[812,816,822,825,828,831,835,838,841,844,847,850,854,857,860,863,886,889,893,896,899,902,919,923,926,929,935,938,942,945,948,951,955,958,961],[278,813,815],{"id":814},"about-benedikt-rillox","About Benedikt Rillox",[817,818,819],"blockquote",{},[236,820,821],{},"To me, technology is not a cost item — it's a competitive advantage.",[236,823,824],{},"I'm Benedikt Rillox, managing partner of nuonic Digital, e-commerce consultant, and developer.",[236,826,827],{},"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.",[236,829,830],{},"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.",[278,832,834],{"id":833},"my-path-in-e-commerce","My path in e-commerce",[236,836,837],{},"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.",[236,839,840],{},"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.",[236,842,843],{},"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.",[236,845,846],{},"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.",[236,848,849],{},"These stations taught me that successful commerce projects never consist of technology alone. They combine architecture, processes, people, and clear business goals.",[278,851,853],{"id":852},"from-development-to-strategy","From development to strategy",[236,855,856],{},"I am a developer, a strategist, and a problem solver.",[236,858,859],{},"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?",[236,861,862],{},"Today my focus is on designing, building, and continuously evolving demanding Shopware systems. Among other things, that includes:",[297,864,865,868,871,874,877,880,883],{},[254,866,867],{},"technical and strategic e-commerce consulting,",[254,869,870],{},"software and Shopware development,",[254,872,873],{},"architecture and system integration,",[254,875,876],{},"product ownership and project management,",[254,878,879],{},"performance and stable operations,",[254,881,882],{},"automation and process optimization,",[254,884,885],{},"technical team leadership and collaboration with agencies.",[236,887,888],{},"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.",[278,890,892],{"id":891},"i-dont-build-shops-just-so-theyre-online","I don't build shops just so they're online",[236,894,895],{},"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.",[236,897,898],{},"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.",[236,900,901],{},"That also means asking uncomfortable questions:",[297,903,904,907,910,913,916],{},[254,905,906],{},"Does this feature really need to exist?",[254,908,909],{},"Does it solve a relevant problem?",[254,911,912],{},"Will the system remain manageable in the long run?",[254,914,915],{},"Does the investment support a concrete business goal?",[254,917,918],{},"Can the platform grow without collapsing under its own complexity?",[278,920,922],{"id":921},"responsibility-begins-after-go-live","Responsibility begins after go-live",[236,924,925],{},"To me, go-live is not a success. It's the beginning of responsibility.",[236,927,928],{},"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.",[236,930,931,932],{},"That's why my work doesn't end with the handover. That's where the real value creation begins: ",[240,933,934],{},"Optimize. Automate. Scale.",[236,936,937],{},"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.",[278,939,941],{"id":940},"clarity-is-part-of-working-together","Clarity is part of working together",[236,943,944],{},"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.",[236,946,947],{},"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.",[236,949,950],{},"That's not always comfortable. But it creates clarity, protects budgets, and leads to better results.",[278,952,954],{"id":953},"what-i-stand-for","What I stand for",[236,956,957],{},"I don't want to simply be busy. I want to create impact.",[236,959,960],{},"With nuonic we build commerce systems for companies that want to grow — faster, more stable, and more profitable.",[236,962,963,964,967,968,970],{},"Others talk about digitalization. We deliver it.",[965,966],"br",{},"\nOthers plan. We build.",[965,969],{},"\nOthers wait. We go.",{"title":738,"searchDepth":739,"depth":739,"links":972},[973,974,975,976,977,978,979],{"id":814,"depth":739,"text":815},{"id":833,"depth":739,"text":834},{"id":852,"depth":739,"text":853},{"id":891,"depth":739,"text":892},{"id":921,"depth":739,"text":922},{"id":940,"depth":739,"text":941},{"id":953,"depth":739,"text":954},"Projects, references, talks and events by Benedikt Rillox — founder and strategist at nuonic Digital, e-commerce consultant and developer since 2009.",[982],"omr-festival-2026",{"src":984,"alt":738},"\u002Fimages\u002Fteam\u002Fdefender.png",{"src":986,"alt":987},"\u002Fimages\u002Fteam\u002Fbenedikt-rillox.jpg","Benedikt Rillox",{},"Founder & Strategist",[991,992,993],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fbenedikt-rillox-4122b183\u002F","https:\u002F\u002Fgithub.com\u002Fbenediktrillox","https:\u002F\u002Fwww.xing.com\u002Fprofile\u002FBenedikt_Rillox",{"title":808,"description":980,"articleModifiedTime":995},"2026-08-14",{"loc":222,"lastmod":995},{"linkedin":991,"github":992},"en\u002Fteam\u002Fbenedikt-rillox","team-benedikt-rillox","Io4iBFT4BZaQMrk8v8Woi1nCjxdLOcoLJReSh5tJVUg",1789408057641]