[{"data":1,"prerenderedAt":1023},["ShallowReactive",2],{"locale-routes":3,"squeeze-paths":226,"announcements":227,"page-\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development":228,"insights-author-\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development":730,"whitepaper-teaser-agency-switch-maintenance-project-en":925},{"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":705,"description":709,"draft":710,"extension":711,"image":712,"meta":715,"navigation":716,"ogImage":717,"path":150,"publishedAt":718,"readingTime":719,"robots":717,"schemaOrg":717,"seo":720,"sitemap":724,"squeeze":710,"stem":725,"tags":726,"translationKey":728,"updatedAt":717,"__hash__":729},"insights_en\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development.md","Shopware maintenance: what a retainer must deliver","benedikt-rillox",{"type":233,"value":234,"toc":673},"minimark",[235,239,242,245,248,253,256,319,322,325,329,332,337,340,344,367,371,374,378,381,385,392,396,399,403,406,416,419,423,430,434,437,440,444,447,451,454,458,465,469,476,480,483,487,490,497,501,504,507,511,514,525,529,536,582,585,588,592,596,599,632,636,639,642,649,653],[236,237,238],"p",{},"Professional Shopware maintenance covers six building blocks: monitoring and\nalerting, security and version updates, extension and integration\nmaintenance, backups with tested recovery, prioritised bug fixes with SLAs,\nand continuous technical housekeeping. A retainer bundles these services with\nreliably reserved capacity — at nuonic starting at around €1,000 per month,\ndepending on store size, custom code and SLA.",[236,240,241],{},"Because a Shopware store is not finished after go-live. From that day on, it\nis a production system: Shopware releases updates, extensions change,\nintegrations produce new edge cases and the business develops new\nrequirements. At the same time, customers expect search, checkout, payment\nand order transfer to work whenever they need them.",[236,243,244],{},"That is what maintenance is for. Yet the term can mean very different things.\nFor one provider, it only means that somebody reads a ticket when requested.\nFor another, it includes updates, monitoring and a number of development\nhours. This makes proposals difficult to compare.",[236,246,247],{},"This article explains what a reliable Shopware maintenance agreement should\ninclude, what distinguishes a retainer, and which options nuonic clients have\nfor continuous development. The essential point is that maintenance should do\nmore than preserve today's state. When organised properly, it creates the\ntechnical and operational foundation for controlled evolution.",[249,250,252],"h2",{"id":251},"shopware-maintenance-support-and-retainers-the-difference","Shopware maintenance, support and retainers: the difference",[236,254,255],{},"The three terms describe different layers of the same responsibility:\nmaintenance prevents risk and keeps the technical platform current, support\nresponds to incidents with defined response times, and a retainer reserves\nreliable capacity for both — optionally combined with planned development. A\nretainer is therefore not a prepaid block of hours but a responsibility\nmodel.",[257,258,259,275],"table",{},[260,261,262],"thead",{},[263,264,265,269,272],"tr",{},[266,267,268],"th",{},"Term",[266,270,271],{},"Purpose",[266,273,274],{},"Typical scope",[276,277,278,293,306],"tbody",{},[263,279,280,287,290],{},[281,282,283],"td",{},[284,285,286],"strong",{},"Maintenance",[281,288,289],{},"Prevent risk and keep the technical platform current",[281,291,292],{},"Security patches, Shopware updates, extension compatibility, backups, technical housekeeping",[263,294,295,300,303],{},[281,296,297],{},[284,298,299],{},"Support",[281,301,302],{},"Respond to incidents and specific questions",[281,304,305],{},"Error analysis, bug fixes, incident communication, defined response times",[263,307,308,313,316],{},[281,309,310],{},[284,311,312],{},"Retainer",[281,314,315],{},"Reserve reliable capacity and a working relationship",[281,317,318],{},"Maintenance and support, optionally combined with planned development",[236,320,321],{},"A retainer is therefore not simply a block of hours paid in advance. Its value\nis reliability: one team knows the system, follows its condition, reserves\ncapacity and works to an agreed cadence. This reduces onboarding, coordination\nand the time until the first useful action.",[236,323,324],{},"A retainer still needs explicit boundaries. A new ERP integration is not a\nsmall maintenance request. Conversely, a critical checkout failure must not\ndisappear into a normal feature backlog. Scope, priorities, response times and\nthe treatment of larger initiatives must be part of the operating model.",[249,326,328],{"id":327},"what-professional-shopware-maintenance-includes","What professional Shopware maintenance includes",[236,330,331],{},"A store can be reachable from the outside while becoming riskier internally.\nOutdated extensions, failed queue jobs or growing error logs are often noticed\nonly once revenue is affected. Good maintenance therefore combines\nprevention, observation and response across six building blocks: monitoring\nand alerting, security and version updates, extension and integration\nmaintenance, backups and recovery, prioritised bug fixes with SLAs, and\ntechnical housekeeping.",[333,334,336],"h3",{"id":335},"monitoring-and-alerting","Monitoring and alerting",[236,338,339],{},"A basic uptime check is not enough. Depending on the system, response times,\nerror rates, queue workers, cron jobs, storage, certificates and critical\nbusiness processes should also be monitored. The aim is not to turn every\ndeviation into an alert, but to identify signals that may affect customers or\noperations.",[333,341,343],{"id":342},"security-and-version-updates","Security and version updates",[236,345,346,347,354,355,360,361,366],{},"Security fixes need a different cadence from a major feature update. Every\nupdate needs, at minimum, a dependency review, a staging test, a current backup\nand rollback path, and post-deployment checks. Shopware itself recommends, in its\n",[348,349,353],"a",{"href":350,"rel":351},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fupdate-guides\u002Fupdating-shopware",[352],"nofollow","update documentation",",\na ",[348,356,359],{"href":357,"rel":358},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Ftutorials-and-faq\u002Ftipsforusingtheadmin\u002Fcreate-test-environment",[352],"test environment",",\ncurrent backups and an\n",[348,362,365],{"href":363,"rel":364},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fsettings\u002Fsystem\u002FShopwareUpdates",[352],"extension compatibility check","\nbefore updates.",[333,368,370],{"id":369},"extension-theme-and-integration-maintenance","Extension, theme and integration maintenance",[236,372,373],{},"A Shopware store rarely consists of the core alone. Payments, shipping, ERP,\nPIM, search, tracking and custom extensions form a network of dependencies.\nMaintenance has to include that network. A green core update check does not\nprove that the complete order process works.",[333,375,377],{"id":376},"backups-and-recovery","Backups and recovery",[236,379,380],{},"“A backup exists” and “the system can be recovered” are not the same. It must\nbe clear which data and files are protected, how long recovery takes and who\nperforms it during an incident. Rollback is part of deployment planning, not\nan improvised idea after something has failed.",[333,382,384],{"id":383},"prioritised-bug-fixes-and-slas","Prioritised bug fixes and SLAs",[236,386,387,388,391],{},"Not every defect is an emergency. A broken checkout needs a different response\nfrom a cosmetic spacing issue in the account area. Our\n",[348,389,390],{"href":66},"Shopware support and maintenance service","\ntherefore uses incident classes and defined response times. Criticality and\nownership are agreed before an incident occurs.",[333,393,395],{"id":394},"technical-housekeeping","Technical housekeeping",[236,397,398],{},"Reviewing logs, removing deprecations, adding tests, analysing slow queries and\nupdating documentation are not highly visible tasks. They do, however,\ndetermine whether the next update becomes routine or a recovery project.\nTechnical debt does not disappear because there is a maintenance agreement.\nThe agreement makes it visible and possible to prioritise.",[249,400,402],{"id":401},"why-ad-hoc-support-becomes-expensive","Why ad-hoc support becomes expensive",[236,404,405],{},"Individual assignments can look flexible, but for a business-critical store\nthey move cost to the worst possible moment: the incident. Nobody\nconsistently follows update status and warning signs, the team has to relearn\nthe system before every change, and capacity is uncertain precisely when the\nproblem is urgent. On top of that come two creeping effects:",[407,408,409,413],"ul",{},[410,411,412],"li",{},"Small risks remain unresolved until they combine into a larger failure.",[410,414,415],{},"Maintenance, features and strategic requests compete in an unstructured\nlist.",[236,417,418],{},"A retainer does not remove every individual decision. It creates a reliable\nframework in which decisions are made with system context. That is the\ndifference between “someone can process tickets” and “a team continuously\nassumes responsibility.”",[249,420,422],{"id":421},"focus-maintenance-with-direction-not-a-ticket-factory","F.O.C.U.S.: maintenance with direction, not a ticket factory",[236,424,425,426,429],{},"Our ",[348,427,428],{"href":18},"F.O.C.U.S. system"," does not begin with an arbitrary\nmonthly number. It connects safe operations with measurable development. The\nfive phases — Facts, Objectives, Constraints, Execution and Scaling — are not\nfiled away after go-live; they form a recurring control loop: from a reliable\npicture of the system's condition through measurable objectives and explicit\nlimits to controlled releases and the next improvement cycle.",[333,431,433],{"id":432},"f-facts-understand-the-real-condition","F — Facts: understand the real condition",[236,435,436],{},"At the start, we review versions, custom code, extensions, infrastructure,\ndeployments, monitoring, backups, tests and known defects. We also examine\nbusiness facts: Which processes generate revenue? Where is manual work\ncreated? Which incidents have already occurred?",[236,438,439],{},"The result is not a generic checklist but an assessment of the actual system.\nWhen taking over a store built by another agency, the relationship therefore\nstarts with a code and system audit.",[333,441,443],{"id":442},"o-objectives-define-operations-and-impact-together","O — Objectives: define operations and impact together",[236,445,446],{},"“The store should run” is necessary but not measurable enough. Objectives can\ninclude availability, shorter response times, fewer checkout errors, faster\ndeployments or less manual order processing. This gives development a clear\ndirection as well: measures compete based on impact, not on the volume of the\nlatest ticket.",[333,448,450],{"id":449},"c-constraints-expose-limitations-early","C — Constraints: expose limitations early",[236,452,453],{},"Budget, team capacity, legacy extensions, missing tests, release windows and\nERP dependencies constrain every roadmap. We make those limits explicit. This\nprevents a supposedly small feature from blocking an update, or a maintenance\nbudget from being overloaded with an integration project.",[333,455,457],{"id":456},"u-execution-small-controlled-releases","U — Execution: small, controlled releases",[236,459,460,461,464],{},"Updates, bug fixes and improvements follow the same traceable path: prioritise,\nimplement, verify, deploy and observe. Depending on scope, the result is a\nmaintenance release, a development sprint or a separate project. Our\n",[348,462,463],{"href":42},"Shopware development"," page explains how we\ndeliver custom features and integrations.",[333,466,468],{"id":467},"s-scaling-learn-from-operations","S — Scaling: learn from operations",[236,470,471,472,475],{},"Monitoring, support cases and usage data generate new facts. Recurring causes\ncan be automated, slow processes improved and effective features expanded.\nMaintenance becomes the basis for\n",[348,473,474],{"href":96},"optimisation and growth"," instead of merely\npreserving the status quo.",[249,477,479],{"id":478},"three-development-options-at-nuonic","Three development options at nuonic",[236,481,482],{},"Not every store needs the same development capacity at all times. We\ntherefore separate a reliable operating baseline from the right form of\ndevelopment — with three models: a pure maintenance retainer for reliable\noperations, maintenance plus continuous development for an ongoing backlog,\nand a separate project for larger development steps.",[333,484,486],{"id":485},"option-1-a-maintenance-retainer-for-reliable-operations","Option 1: a maintenance retainer for reliable operations",[236,488,489],{},"This model suits stable stores whose business functionality changes only\noccasionally. Its focus is monitoring, security and Shopware updates, defect\nresolution and agreed response times. Smaller adjustments can be prioritised;\nlarger initiatives are assessed separately.",[236,491,492,493,496],{},"Our maintenance retainers start at around €1,000 per month, depending on store\nsize, custom code and SLA. Our overview of\n",[348,494,495],{"href":54},"Shopware costs"," explains the other licence,\nproject and operating cost blocks.",[333,498,500],{"id":499},"option-2-maintenance-plus-continuous-development","Option 2: maintenance plus continuous development",[236,502,503],{},"This model is suitable when there is a meaningful backlog to deliver alongside\nongoing operations. In addition to the maintenance baseline, we reserve\npredictable development capacity. It can be used for conversion improvements,\nautomation, new store functionality, integration work or performance.",[236,505,506],{},"F.O.C.U.S. keeps operations and product work in one system: risks remain\nvisible, objectives drive prioritisation and changes reach production through\ncontrolled releases. The advantage over changing one-off assignments is\nretained context. The team that understands the architecture and its failure\nmodes also develops the next feature.",[333,508,510],{"id":509},"option-3-a-separate-project-for-a-larger-development-step","Option 3: a separate project for a larger development step",[236,512,513],{},"An ERP integration, a B2B portal, replatforming or a new storefront concept\nshould not be forced into a small monthly allowance. Such initiatives receive\ntheir own objectives, budget, roadmap and acceptance criteria. The existing\nmaintenance retainer protects ongoing operations in parallel.",[236,515,516,517,520,521,524],{},"After go-live, the result can return to regular support. Our\n",[348,518,519],{"href":174},"COMSPOT case study"," and\n",[348,522,523],{"href":201},"Xucker case study"," show how that relationship\nworks over several years.",[249,526,528],{"id":527},"which-model-fits-which-store","Which model fits which store?",[236,530,531,532,535],{},"The short answer: a stable store without a large backlog needs the\nmaintenance retainer, a continuously prioritised backlog needs maintenance\nplus development, a clearly bounded larger step needs a separate project with\nongoing maintenance — and an unclear condition after an\n",[348,533,534],{"href":69},"agency change"," starts with a system audit. The mapping at a glance:",[257,537,538,548],{},[260,539,540],{},[263,541,542,545],{},[266,543,544],{},"Situation",[266,546,547],{},"Useful starting point",[276,549,550,558,566,574],{},[263,551,552,555],{},[281,553,554],{},"The store is stable; updates and response times need structure",[281,556,557],{},"Maintenance retainer",[263,559,560,563],{},[281,561,562],{},"There is a continuously prioritised backlog",[281,564,565],{},"Maintenance plus a development retainer",[263,567,568,571],{},[281,569,570],{},"A clearly bounded larger development step is planned",[281,572,573],{},"Separate project plus ongoing maintenance",[263,575,576,579],{},[281,577,578],{},"Another agency built the store and its condition is unclear",[281,580,581],{},"System audit, stabilisation, then the appropriate retainer level",[236,583,584],{},"The model can change. After a large project, more stabilisation capacity may\nbe useful; during a growth phase, a continuous development cadence may matter\nmore. Scope and responsibility should be adjusted deliberately, before budget\nor technology is already under pressure.",[236,586,587],{},"And if the path to the right model leads through a new partner: how the\nswitch succeeds in a running maintenance project is described in our\nwhitepaper with phase model, asset inventory and handover checklist.",[589,590],"whitepaper-teaser",{"slug":591},"agency-switch-maintenance-project",[249,593,595],{"id":594},"how-to-recognise-a-good-maintenance-agreement","How to recognise a good maintenance agreement",[236,597,598],{},"A good maintenance agreement answers ten questions concretely — from the\nsystems included, through monitoring, update procedures and response times\nper incident class, to reporting, cover and measurable metrics. Without clear\nanswers, the agreement often sells availability rather than responsibility.\nAt least these questions should have concrete answers before signing:",[600,601,602,605,608,611,614,617,620,623,626,629],"ol",{},[410,603,604],{},"Which systems, extensions and environments are included?",[410,606,607],{},"What is monitored, and who receives which alerts?",[410,609,610],{},"How are security, minor and major updates treated?",[410,612,613],{},"Which response times apply to each incident class?",[410,615,616],{},"How do backup, recovery and rollback work?",[410,618,619],{},"Which services are maintenance and which are development?",[410,621,622],{},"How are priorities, capacity and open risks reported?",[410,624,625],{},"Who actually works on the system, and how is cover organised?",[410,627,628],{},"How are larger initiatives separated from the retainer?",[410,630,631],{},"Which metrics show that operations and development are improving?",[249,633,635],{"id":634},"conclusion-the-retainer-is-the-operating-system-of-the-relationship","Conclusion: the retainer is the operating system of the relationship",[236,637,638],{},"Shopware maintenance protects revenue, data and the ability to act. A good\nretainer turns that protection into a reliable working relationship, with\nsystem context, reserved capacity, transparent priorities and a clear path\nfrom incident to improvement.",[236,640,641],{},"F.O.C.U.S. connects these layers. Facts prevent guesswork, Objectives give\ndevelopment direction, Constraints protect against unrealistic commitments,\nExecution brings changes live safely and Scaling turns operational data into\nthe next improvement cycle.",[236,643,644,645,648],{},"Clients remain flexible: reliable operations only, operations plus continuous\ndevelopment, or a separate project for the next major step. If the current\ncondition needs to be understood first, the relationship can begin with a\n",[348,646,647],{"href":30},"system audit and maintenance model",".",[333,650,652],{"id":651},"official-sources","Official sources",[407,654,655,661,667],{},[410,656,657],{},[348,658,660],{"href":350,"rel":659},[352],"Shopware: Updating Shopware",[410,662,663],{},[348,664,666],{"href":357,"rel":665},[352],"Shopware: Creating a test environment",[410,668,669],{},[348,670,672],{"href":363,"rel":671},[352],"Shopware: Updates and extension compatibility",{"title":674,"searchDepth":675,"depth":675,"links":676},"",2,[677,678,687,688,695,700,701,702],{"id":251,"depth":675,"text":252},{"id":327,"depth":675,"text":328,"children":679},[680,682,683,684,685,686],{"id":335,"depth":681,"text":336},3,{"id":342,"depth":681,"text":343},{"id":369,"depth":681,"text":370},{"id":376,"depth":681,"text":377},{"id":383,"depth":681,"text":384},{"id":394,"depth":681,"text":395},{"id":401,"depth":675,"text":402},{"id":421,"depth":675,"text":422,"children":689},[690,691,692,693,694],{"id":432,"depth":681,"text":433},{"id":442,"depth":681,"text":443},{"id":449,"depth":681,"text":450},{"id":456,"depth":681,"text":457},{"id":467,"depth":681,"text":468},{"id":478,"depth":675,"text":479,"children":696},[697,698,699],{"id":485,"depth":681,"text":486},{"id":499,"depth":681,"text":500},{"id":509,"depth":681,"text":510},{"id":527,"depth":675,"text":528},{"id":594,"depth":675,"text":595},{"id":634,"depth":675,"text":635,"children":703},[704],{"id":651,"depth":681,"text":652},[706,707,708],{"name":660,"url":350},{"name":666,"url":357},{"name":672,"url":363},"Shopware maintenance is more than updates and tickets. Here is how we combine operations, SLAs and continuous development in a F.O.C.U.S. retainer.",false,"md",{"src":713,"alt":714},"\u002Fimages\u002Finsights\u002Fshopware-wartung-retainer-weiterentwicklung.png","Benedikt Rillox presents the F.O.C.U.S. model for Shopware maintenance, retainers and continuous development",{},true,null,"2026-08-17",12,{"title":721,"description":722,"articleModifiedTime":723},"Shopware maintenance retainers: models compared","What belongs in a Shopware maintenance agreement? Retainers, SLAs, updates and three options for continuous development with F.O.C.U.S.","2026-09-10",{"loc":150,"lastmod":723},"en\u002Finsights\u002Fshopware-maintenance-retainer-development",[727,286,312],"Shopware","insights-shopware-maintenance-retainer-development","rpoBMbs1aDo19mXKpn9zzCBkpmans79BbZMCNMOjgyk",{"id":731,"title":732,"alternateName":717,"bio":733,"body":734,"description":904,"events":905,"extension":711,"heroIllustration":907,"image":909,"meta":912,"name":911,"navigation":716,"ogImage":717,"path":222,"projects":717,"publishedAt":717,"robots":717,"role":913,"sameAs":914,"schemaOrg":717,"seo":918,"sitemap":920,"slug":231,"socials":921,"squeeze":710,"stem":922,"talks":717,"translationKey":923,"updatedAt":717,"__hash__":924},"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":735,"toc":895},[736,740,746,749,752,755,759,762,765,768,771,774,778,781,784,787,810,813,817,820,823,826,843,847,850,853,859,862,866,869,872,875,879,882,885],[249,737,739],{"id":738},"about-benedikt-rillox","About Benedikt Rillox",[741,742,743],"blockquote",{},[236,744,745],{},"To me, technology is not a cost item — it's a competitive advantage.",[236,747,748],{},"I'm Benedikt Rillox, managing partner of nuonic Digital, e-commerce consultant, and developer.",[236,750,751],{},"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,753,754],{},"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.",[249,756,758],{"id":757},"my-path-in-e-commerce","My path in e-commerce",[236,760,761],{},"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,763,764],{},"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,766,767],{},"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,769,770],{},"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,772,773],{},"These stations taught me that successful commerce projects never consist of technology alone. They combine architecture, processes, people, and clear business goals.",[249,775,777],{"id":776},"from-development-to-strategy","From development to strategy",[236,779,780],{},"I am a developer, a strategist, and a problem solver.",[236,782,783],{},"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,785,786],{},"Today my focus is on designing, building, and continuously evolving demanding Shopware systems. Among other things, that includes:",[407,788,789,792,795,798,801,804,807],{},[410,790,791],{},"technical and strategic e-commerce consulting,",[410,793,794],{},"software and Shopware development,",[410,796,797],{},"architecture and system integration,",[410,799,800],{},"product ownership and project management,",[410,802,803],{},"performance and stable operations,",[410,805,806],{},"automation and process optimization,",[410,808,809],{},"technical team leadership and collaboration with agencies.",[236,811,812],{},"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.",[249,814,816],{"id":815},"i-dont-build-shops-just-so-theyre-online","I don't build shops just so they're online",[236,818,819],{},"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,821,822],{},"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,824,825],{},"That also means asking uncomfortable questions:",[407,827,828,831,834,837,840],{},[410,829,830],{},"Does this feature really need to exist?",[410,832,833],{},"Does it solve a relevant problem?",[410,835,836],{},"Will the system remain manageable in the long run?",[410,838,839],{},"Does the investment support a concrete business goal?",[410,841,842],{},"Can the platform grow without collapsing under its own complexity?",[249,844,846],{"id":845},"responsibility-begins-after-go-live","Responsibility begins after go-live",[236,848,849],{},"To me, go-live is not a success. It's the beginning of responsibility.",[236,851,852],{},"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,854,855,856],{},"That's why my work doesn't end with the handover. That's where the real value creation begins: ",[284,857,858],{},"Optimize. Automate. Scale.",[236,860,861],{},"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.",[249,863,865],{"id":864},"clarity-is-part-of-working-together","Clarity is part of working together",[236,867,868],{},"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,870,871],{},"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,873,874],{},"That's not always comfortable. But it creates clarity, protects budgets, and leads to better results.",[249,876,878],{"id":877},"what-i-stand-for","What I stand for",[236,880,881],{},"I don't want to simply be busy. I want to create impact.",[236,883,884],{},"With nuonic we build commerce systems for companies that want to grow — faster, more stable, and more profitable.",[236,886,887,888,891,892,894],{},"Others talk about digitalization. We deliver it.",[889,890],"br",{},"\nOthers plan. We build.",[889,893],{},"\nOthers wait. We go.",{"title":674,"searchDepth":675,"depth":675,"links":896},[897,898,899,900,901,902,903],{"id":738,"depth":675,"text":739},{"id":757,"depth":675,"text":758},{"id":776,"depth":675,"text":777},{"id":815,"depth":675,"text":816},{"id":845,"depth":675,"text":846},{"id":864,"depth":675,"text":865},{"id":877,"depth":675,"text":878},"Projects, references, talks and events by Benedikt Rillox — founder and strategist at nuonic Digital, e-commerce consultant and developer since 2009.",[906],"omr-festival-2026",{"src":908,"alt":674},"\u002Fimages\u002Fteam\u002Fdefender.png",{"src":910,"alt":911},"\u002Fimages\u002Fteam\u002Fbenedikt-rillox.jpg","Benedikt Rillox",{},"Founder & Strategist",[915,916,917],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fbenedikt-rillox-4122b183\u002F","https:\u002F\u002Fgithub.com\u002Fbenediktrillox","https:\u002F\u002Fwww.xing.com\u002Fprofile\u002FBenedikt_Rillox",{"title":732,"description":904,"articleModifiedTime":919},"2026-08-14",{"loc":222,"lastmod":919},{"linkedin":915,"github":916},"en\u002Fteam\u002Fbenedikt-rillox","team-benedikt-rillox","Io4iBFT4BZaQMrk8v8Woi1nCjxdLOcoLJReSh5tJVUg",{"id":926,"title":927,"author":231,"body":928,"description":1006,"draft":710,"extension":711,"file":1007,"fileLanguage":1008,"gated":716,"image":1009,"meta":1012,"navigation":716,"ogImage":717,"pageCount":719,"path":159,"publishedAt":723,"robots":717,"schemaOrg":717,"seo":1013,"sitemap":1016,"squeeze":710,"stem":1017,"tags":1018,"translationKey":1021,"updatedAt":717,"__hash__":1022},"whitepapers_en\u002Fen\u002Fwhitepapers\u002Fagency-switch-maintenance-project.md","Switching agencies in a running maintenance project",{"type":233,"value":929,"toc":1001},[930,933,936,940,984,988,991,995],[236,931,932],{},"A running online shop is not a project with a defined end but an operation — which is exactly why the hurdle of switching the agency that runs it feels so high. In practice the switch is therefore postponed longer than economically sensible: the worry about knowledge loss, downtime and chaos around access credentials is justified when the switch happens unstructured — and largely unfounded when it is planned as an orderly process with clear responsibilities.",[236,934,935],{},"This whitepaper describes the switch of an existing maintenance and development partnership as a structured process in five phases — from the decision to stable regular operations, without interrupting the shop.",[249,937,939],{"id":938},"whats-inside","What's inside",[407,941,942,948,954,960,966,972,978],{},[410,943,944,947],{},[284,945,946],{},"Typical triggers:"," six warning signs — from response times through knowledge monopolies and cost development to technical standstill — and the recommendation to document them in writing for two to three months before deciding.",[410,949,950,953],{},[284,951,952],{},"Preparation:"," contract situation, ownership and usage rights, data protection and compliance — what must be clarified before giving notice.",[410,955,956,959],{},[284,957,958],{},"The asset inventory:"," eight categories from source code through hosting, domains and licences to monitoring — with the central questions per position. The rule of thumb: every asset whose owner you cannot name within one working day is a risk — regardless of the switch.",[410,961,962,965],{},[284,963,964],{},"The switching process in five phases:"," decision and selection (2–6 weeks), preparation and notice (2–4 weeks), handover (1–3 weeks), onboarding of the new agency and stabilisation — a gliding transition instead of a big bang.",[410,967,968,971],{},[284,969,970],{},"A checklist of concrete action items"," for the entire handover.",[410,973,974,977],{},[284,975,976],{},"A practical example:"," an onboarding along the F.O.C.U.S. framework — from Facts to Scaling.",[410,979,980,983],{},[284,981,982],{},"Why our onboarding costs €0:"," the logic behind it — the familiarisation risk sits with the agency that wins the contract, not with the shop owner who dares to take the step.",[249,985,987],{"id":986},"who-the-whitepaper-is-for","Who the whitepaper is for",[236,989,990],{},"For managing directors, e-commerce and IT leads of mid-sized shop operators who are dissatisfied with their current agency — or who simply want to know how switchable their shop is today. The asset inventory pays off even if you end up staying with your agency.",[249,992,994],{"id":993},"key-facts","Key facts",[236,996,997,998,648],{},"12 pages, as of September 2026 (PDF in German). The stated timeframes are guide values for a mid-sized shop; the phases partially overlap. Important upfront: an agency switch is not about assigning blame — a professionally handled switch is in the interest of everyone involved, including the outgoing agency. How the switch to us works concretely is covered on our ",[348,999,1000],{"href":69},"agency switch page",{"title":674,"searchDepth":675,"depth":675,"links":1002},[1003,1004,1005],{"id":938,"depth":675,"text":939},{"id":986,"depth":675,"text":987},{"id":993,"depth":675,"text":994},"The structured path to a new technical partner — without interrupting shop operations. With a five-phase model, asset inventory and a checklist of concrete action items.","\u002Fdownloads\u002Fwhitepapers\u002Fwhitepaper-agentur-wechsel-einfach-gemacht.pdf","de",{"src":1010,"alt":1011},"\u002Fimages\u002Fwhitepapers\u002Fagenturwechsel-wartungsprojekt.svg","Switching agencies in a running maintenance project — five-phase model from decision to regular operations with onboarding for 0 euros",{},{"title":1014,"description":1015,"articleModifiedTime":723},"Whitepaper: switching agencies in a maintenance project","Agency switch without interrupting operations — five-phase model, asset inventory with 8 categories and a handover checklist. Free whitepaper, 12 pages.",{"loc":159,"lastmod":723},"en\u002Fwhitepapers\u002Fagency-switch-maintenance-project",[1019,286,1020],"Agency switch","E-commerce","whitepaper-agenturwechsel-wartungsprojekt","OFSxPcuAcM_IzS8BK-7c9fgdOKqXaVjmkOBY5_3OdZ0",1789408058484]