[{"data":1,"prerenderedAt":848},["ShallowReactive",2],{"locale-routes":3,"page-\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6":169,"insights-author-\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6":766},{"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":735,"description":744,"draft":745,"extension":746,"image":747,"meta":750,"navigation":751,"ogImage":752,"path":117,"publishedAt":753,"readingTime":754,"robots":752,"schemaOrg":752,"seo":755,"sitemap":758,"stem":759,"tags":760,"translationKey":764,"updatedAt":752,"__hash__":765},"insights_en\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6.md","Withdrawal button 2026: requirement, implementation and Shopware 6 guide","alex-jank",{"type":174,"value":175,"toc":711},"minimark",[176,193,200,206,211,219,222,225,247,255,259,277,280,357,361,364,369,376,379,383,386,393,397,400,403,407,410,413,417,420,424,427,434,438,447,451,454,458,461,464,470,473,477,488,491,531,546,550,557,566,583,590,594,620,627,631],[177,178,179,180,184,185,192],"p",{},"Since 19 June 2026, online shops concluding distance contracts with consumers\nthat carry a statutory right of withdrawal must provide an electronic\nwithdrawal function – the ",[181,182,183],"em",{},"withdrawal button"," – under ",[186,187,191],"a",{"href":188,"rel":189},"https:\u002F\u002Fwww.gesetze-im-internet.de\u002Fbgb\u002F__356a.html",[190],"nofollow","section 356a\nBGB",": a clearly labelled\nbutton, a separate confirmation step and an immediate acknowledgement of\nreceipt. Shopware 6 includes the function natively from version 6.7.9.0,\nbackported to the 6.6 line.",[177,194,195,196,199],{},"The new duty is often misunderstood in both directions. It does not apply to\nevery website or a genuinely B2B-only shop, but it is not a concern reserved\nfor large merchants either. The decisive question is whether a business\nconcludes online contracts with consumers for which a statutory right of\nwithdrawal exists. This article explains the requirement and the practical\npath for Shopware 6. For the wider regulatory roadmap, see our ",[186,197,198],{"href":87},"e-commerce\ndeadlines for 2026\u002F27",".",[201,202,203],"blockquote",{},[177,204,205],{},"This article provides technical and practical guidance, not legal advice.\nSpecial cases – including digital content, services, marketplaces,\ninternational shops and mixed B2B\u002FB2C models – should be assessed for the\nindividual business model and applicable law.",[207,208,210],"h2",{"id":209},"what-is-a-withdrawal-button-and-what-is-it-for","What is a withdrawal button, and what is it for?",[177,212,213,214,218],{},"The withdrawal button is not a way to register a return or cancel an order in\nan ERP. It is the prescribed digital route for submitting a ",[215,216,217],"strong",{},"declaration of\nwithdrawal",". By using it, the customer states that they want to withdraw from\ntheir contract within the withdrawal period.",[177,220,221],{},"The rule closes the gap between concluding a contract online and withdrawing\nfrom it. A customer who can enter into a contract through a shop interface\nshould also be able to submit their withdrawal there, without hunting for\ncontact details or a PDF form. The model withdrawal form, email and post remain\nvalid channels. The electronic function is an additional required channel.",[177,223,224],{},"For merchants, the distinction matters:",[226,227,228,235,241],"ul",{},[229,230,231,234],"li",{},[215,232,233],{},"Withdrawal"," is a consumer right with statutory time limits and legal\nconsequences.",[229,236,237,240],{},[215,238,239],{},"Return"," is the physical shipment of goods back to the merchant. It may\nfollow a withdrawal, but it is not the declaration itself.",[229,242,243,246],{},[215,244,245],{},"Goodwill return"," is a voluntary, contractually broader service. It does\nnot replace the legally required withdrawal function.",[177,248,249,250,254],{},"The German legal basis is ",[186,251,253],{"href":188,"rel":252},[190],"section 356a of the Civil Code\n(BGB)",". It requires both a\nwithdrawal function and a subsequent confirmation function, followed by an\nimmediate acknowledgement of receipt on a durable medium.",[207,256,258],{"id":257},"when-does-a-shop-need-a-withdrawal-button","When does a shop need a withdrawal button?",[177,260,261,262,265,266,271,272,199],{},"As a practical rule, the button is needed where a business concludes a\n",[215,263,264],{},"distance contract through an online user interface"," with a consumer and\nthat contract carries a statutory right of withdrawal. This includes classic\nB2C goods shops, but also many online service, digital-content and subscription\ncontracts. The rule has applied since 19 June 2026 under the ",[186,267,270],{"href":268,"rel":269},"https:\u002F\u002Feur-lex.europa.eu\u002Flegal-content\u002FDE\u002FTXT\u002FPDF\u002F?uri=CELEX%3A72024L0825DEU_202602019",[190],"German act\nimplementing the consumer-rights\nreform",",\nwhich implements ",[186,273,276],{"href":274,"rel":275},"https:\u002F\u002Feur-lex.europa.eu\u002Flegal-content\u002FEN\u002FTXT\u002F?uri=CELEX%3A32023L2673",[190],"Directive (EU) 2023\u002F2673",[177,278,279],{},"That does not mean every product has a right of withdrawal. Section 312g BGB\ncontains exceptions, for example for certain sealed goods once opened,\nmade-to-order goods and digital content after the legally required consents.\nThe position needs to be assessed properly for the assortment and process. A\nshop with a few exempt products should not switch the function off too quickly:\nit will often also offer other contracts that remain eligible.",[281,282,283,299],"table",{},[284,285,286],"thead",{},[287,288,289,293,296],"tr",{},[290,291,292],"th",{},"Shop model",[290,294,295],{},"Withdrawal button?",[290,297,298],{},"Why",[300,301,302,314,325,336,346],"tbody",{},[287,303,304,308,311],{},[305,306,307],"td",{},"B2C goods shop",[305,309,310],{},"usually yes",[305,312,313],{},"Online distance selling with a statutory withdrawal right",[287,315,316,319,322],{},[305,317,318],{},"B2C subscription, course or digital service",[305,320,321],{},"often yes",[305,323,324],{},"The rule is not limited to goods",[287,326,327,330,333],{},[305,328,329],{},"Genuine B2B-only shop",[305,331,332],{},"no",[305,334,335],{},"No contract with a consumer",[287,337,338,341,343],{},[305,339,340],{},"Information or corporate website",[305,342,332],{},[305,344,345],{},"No contract is concluded online",[287,347,348,351,354],{},[305,349,350],{},"Shop selling only contracts with valid withdrawal exclusions",[305,352,353],{},"obtain advice",[305,355,356],{},"Exceptions depend on product and contract",[207,358,360],{"id":359},"how-does-the-law-require-the-process-to-work","How does the law require the process to work?",[177,362,363],{},"Section 356a BGB requires three steps: a clearly labelled withdrawal function\nthat stays available throughout the withdrawal period, a separate confirmation\nfunction after only the necessary details have been requested, and an\nimmediate acknowledgement of receipt on a durable medium. A link to the\nwithdrawal policy alone is not enough – the workflow is short but fully\nprescribed.",[365,366,368],"h3",{"id":367},"_1-a-clearly-labelled-withdrawal-function-that-is-always-available","1. A clearly labelled withdrawal function that is always available",[177,370,371,372,375],{},"The function must be clearly legible and labelled ",[215,373,374],{},"“Withdraw from contract”","\nor another unambiguous equivalent. During the withdrawal period, it must be\nconstantly available, prominently placed and easy to access. Labels such as\n“return”, “send back” or “cancel” are not safe substitutes because they do not\nunambiguously express withdrawal.",[177,377,378],{},"The law does not set a specific pixel position. What matters is actual\ndiscoverability in the shop – including on mobile, for guest orders and where\naccount access is restricted. A hidden text link among many footer links or a\nmandatory login creates needless risk.",[365,380,382],{"id":381},"_2-request-only-necessary-information-then-ask-for-a-separate-confirmation","2. Request only necessary information, then ask for a separate confirmation",[177,384,385],{},"After the click, the shop may request information needed to identify the\nconsumer and the contract concerned. This typically includes a name, order or\ncontract number and an electronic channel for the acknowledgement. The\ncustomer may enter those details or confirm information already held.",[177,387,388,389,392],{},"The declaration must then be sent through a separate, clearly labelled\nconfirmation function – for example, ",[215,390,391],{},"“Confirm withdrawal”",". The process\nmust not be blocked by unnecessary mandatory fields: a reason for withdrawal,\na return method or an account password do not belong in the required path.",[365,394,396],{"id":395},"_3-send-an-immediate-acknowledgement-that-can-be-retained-as-evidence","3. Send an immediate acknowledgement that can be retained as evidence",[177,398,399],{},"Once the confirmation function has been activated, the merchant must promptly\nsend an acknowledgement on a durable medium, usually by email. It must at least\ncontain the declaration's content and the date and time it was received. Only\nthen is the statutory online process complete.",[177,401,402],{},"This is more than a UX concern. A withdrawal submitted through the function\nbefore the deadline is deemed to have been received in time. Deliverability,\nlogging and a reliable internal handling route are therefore part of the\nfeature.",[207,404,406],{"id":405},"do-i-need-the-button-if-i-offer-free-returns-and-goodwill-at-any-time","Do I need the button if I offer free returns and goodwill at any time?",[177,408,409],{},"Yes, where the conditions above are met. A free returns policy is customer\nfriendly, but it does not change the legal obligation to provide the electronic\nwithdrawal function. It also answers a different question: what happens to the\ngoods? Withdrawal answers how the customer declares, on time, that they want to\nend the contract.",[177,411,412],{},"A returns portal can complement the workflow by creating labels, tracking a\nshipment and handling refunds. It does not automatically replace the\nwithdrawal button. It would need to meet every part of the statutory process:\nan unambiguous declaration, the necessary identification, a separate\nconfirmation and an immediate acknowledgement. Do not infer this from a\nportal's name; test and assess the actual workflow.",[207,414,416],{"id":415},"b2b-large-merchants-and-ordinary-websites-who-is-exempt","B2B, large merchants and ordinary websites: who is exempt?",[177,418,419],{},"Only businesses without withdrawable online consumer contracts are exempt:\ngenuinely B2B-only shops and websites where no contract is concluded online.\nThere is no exemption based on size, turnover or small-business status – a\none-person shop selling B2C at a distance is just as affected. Mixed B2B\u002FB2C\nshops need the function for their consumer business.",[365,421,423],{"id":422},"genuinely-b2b-only-shops-do-not-need-a-withdrawal-button","Genuinely B2B-only shops do not need a withdrawal button",[177,425,426],{},"The provision protects consumers. A shop that demonstrably sells exclusively\nto businesses is outside its scope. “Exclusively” matters: B2B pricing, a VAT\nID field or an indication in the terms alone do not automatically turn a freely\naccessible shop into a B2B-only shop. If consumers can in fact order, the B2C\nposition should be checked.",[177,428,429,430,433],{},"A ",[186,431,432],{"href":27},"mixed B2B\u002FB2C shop"," needs the function for its\nconsumer business. Whether it is shown only in selected sales channels or to\nselected customer groups is a technical configuration based on a legal prior\ndecision, not merely cosmetic.",[365,435,437],{"id":436},"not-only-for-large-merchants-no-general-size-threshold","Not only for large merchants: no general size threshold",[177,439,440,441,446],{},"There is no general exemption for small businesses, turnover or headcount. A\none-person shop selling B2C at a distance may be just as affected as an\ninternational merchant. The ",[186,442,445],{"href":443,"rel":444},"https:\u002F\u002Fwww.ihk.de\u002Fosnabrueck\u002Frecht-und-fair-play\u002Frecht\u002Finternetrecht\u002Fwiderrufsbutton-ab-juni-2026-6975440",[190],"IHK's guidance","\nexpressly describes the scope as independent of size, revenue and legal form.",[365,448,450],{"id":449},"not-every-website-needs-a-button","Not every website needs a button",[177,452,453],{},"A website with services, references, a contact form and a newsletter, but no\nconsumer contract concluded online, does not need a withdrawal button. That\ncan change where an appointment booking, payment, course registration or\ndigital purchase forms a contract directly on the site. Again, the actual\ncontract is decisive.",[207,455,457],{"id":456},"footer-or-order-list-where-should-the-withdrawal-button-appear","Footer or order list: where should the withdrawal button appear?",[177,459,460],{},"The safe standard in Shopware 6 is a clearly visible button in the footer,\ncomplemented by contextual entry points in the order confirmation and customer\naccount. The law does not prescribe a fixed position, but it does require\nconstant, easy accessibility throughout the withdrawal period – including for\nguests and on mobile. The order list alone is therefore not a sufficient sole\nroute.",[177,462,463],{},"The order list in the customer account is not specified by law as the required\nlocation. It can be very useful because the customer sees the relevant order\nand its data can be prefilled. But it should not be the only route: guest\ncustomers and people without working account access could otherwise be excluded.",[177,465,466,467,469],{},"In Shopware 6, a clear footer button is the standard approach. Shopware's\ndocumentation describes a dedicated withdrawal-request page and the option to\nshow the ",[215,468,374],{}," button in the footer. In a standard\nstorefront, this is a sensible starting point, provided its accessibility is\ntested in the actual theme and on mobile devices.",[177,471,472],{},"The extra contextual entry improves usability without replacing general\naccess. Do not confuse the two: the withdrawal policy still needs to be correctly\navailable in the footer and checkout; that is a separate obligation.",[207,474,476],{"id":475},"implementing-it-in-shopware-6-native-from-6790","Implementing it in Shopware 6: native from 6.7.9.0",[177,478,479,480,483,484,487],{},"Shopware introduced the native withdrawal function in ",[215,481,482],{},"version 6.7.9.0"," and\nbackported it to the 6.6 line. According to Shopware, it is part of the core\nand also available in Community Edition. For a standard storefront, it is\ntherefore usually the best route: no extra plugin stack, a configurable footer\nentry point and a system-level basis for form and acknowledgement. Our article\non ",[186,485,486],{"href":99},"Shopware 6.7 and the benefits of updating","\nprovides the broader technical release context.",[177,489,490],{},"The exact wording in the admin may differ by patch level, but the workflow is\nstraightforward:",[492,493,494,500,510,519,525],"ol",{},[229,495,496,499],{},[215,497,498],{},"Check version and theme."," Use at least 6.7.9.0, or a Shopware 6.6 patch\nlevel containing the backport. Headless, custom themes and other frontends\nneed a deliberate integration.",[229,501,502,505,506,509],{},[215,503,504],{},"Assign the withdrawal-request page."," Under ",[181,507,508],{},"Settings → Basic\ninformation → Shop pages",", assign the layout for that page.",[229,511,512,505,515,518],{},[215,513,514],{},"Enable the footer function.",[181,516,517],{},"Law and privacy",", enable the\n“Withdraw from contract” button in the footer.",[229,520,521,524],{},[215,522,523],{},"Check flow and email."," The event flow for a submitted withdrawal form\nmust be active, the customer message deliverable and the internal recipient\ndefined. An HTTP 200 after form submission is not a substitute for a\ndelivered acknowledgement.",[229,526,527,530],{},[215,528,529],{},"Test end to end."," Test as a guest and logged-in user, on mobile, with\nreal mailboxes and with the intended hand-off to support, ERP and returns.",[177,532,533,534,539,540,545],{},"Shopware documents the footer setting in its ",[186,535,538],{"href":536,"rel":537},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-en\u002Fsettings\u002Fbasic-information#revocation-request-in-the-storefront",[190],"basic information\ndocumentation",".\nShopware's ",[186,541,544],{"href":542,"rel":543},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fnews\u002Fwithdrawal-button-requirement-germany-2026\u002F",[190],"article on the withdrawal-button\nrequirement","\nexplains the introduction in 6.7.9.0 and its 6.6 backport.",[207,547,549],{"id":548},"older-shopware-6-versions-shopware-5-and-headless-plugin-or-custom-integration","Older Shopware 6 versions, Shopware 5 and headless: plugin or custom integration",[177,551,552,553,556],{},"If you cannot update to a supported 6.6\u002F6.7 level, do not improvise the\nstatutory function with an ordinary contact form. For older Shopware 6 versions\nand special requirements, we have had good experiences with mediameets’\n",[215,554,555],{},"“Withdrawal button & online withdrawal form”"," plugin. According to the\nvendor, it supports several Shopware 6 versions and covers form, confirmation\nand email workflow:",[226,558,559],{},[229,560,561],{},[186,562,565],{"href":563,"rel":564},"https:\u002F\u002Fstore.shopware.com\u002Fde\u002Fmedia50620347541m\u002Fwiderrufsbutton-online-widerrufsformular-nach-eu-richtlinie-2023-2673.html",[190],"mediameets plugin for Shopware 6",[177,567,568,569,574,575,578,579,582],{},"There is also a ",[186,570,573],{"href":571,"rel":572},"https:\u002F\u002Fstore.shopware.com\u002Fde\u002Fmedia82172519414m\u002Fwiderrufsbutton-online-widerrufsformular-nach-eu-richtlinie-2023-2673.html",[190],"mediameets extension for Shopware\n5",".\nThat is an interim measure, not a recommendation for permanent operation:\nShopware 5 has been end-of-life since July 2024. Read our ",[186,576,577],{"href":96},"Shopware 5 EOL\nassessment",", and see our ",[186,580,581],{"href":42},"Shopware 6\nmigration page"," for a planned move.",[177,584,585,586,589],{},"For headless shops, the same principle applies whether you use core or a\nplugin: the frontend itself must visibly and consistently provide the required\nexperience. Do not merely check that a form exists in the backend. Verify that\nthe public storefront actually delivers the button, two-step flow,\nacknowledgement email and accessibility. With a custom frontend, this belongs\nto ",[186,587,588],{"href":33},"Shopware development",", not just the\nadministration.",[207,591,593],{"id":592},"pre-launch-checklist","Pre-launch checklist",[226,595,596,599,602,605,608,611,614,617],{},[229,597,598],{},"Do we distinguish B2C, B2B-only and mixed sales channels correctly?",[229,600,601],{},"Is “Withdraw from contract” easy to reach without login, search or contacting\nsupport, including on mobile?",[229,603,604],{},"Is the second action clearly labelled “Confirm withdrawal”?",[229,606,607],{},"Does the form request only the necessary information and not a reason for\nwithdrawal?",[229,609,610],{},"Does the customer promptly receive an email with content, date and time?",[229,612,613],{},"Does the declaration reach support, ERP and the returns process without a\nmanual media break?",[229,615,616],{},"Does the workflow work with real email addresses, guest orders, the custom\ntheme and every relevant language?",[229,618,619],{},"Have recipients, retention and responsibilities been aligned with privacy and\nlegal advice?",[177,621,622,623,626],{},"The withdrawal button is not a major commerce project. But it is not a footer\nlink to add without testing either. Thinking about workflow, evidence and\ntechnical integration together does more than meet a new obligation: it\nremoves avoidable friction for support teams and customers. For updates, email\ndelivery and continuous technical checks, our ",[186,624,625],{"href":48},"Shopware support\nteam"," can help.",[365,628,630],{"id":629},"sources-and-further-information","Sources and further information",[226,632,633,639,645,651,658,664,671,677,683,690,697,704],{},[229,634,635],{},[186,636,638],{"href":188,"rel":637},[190],"Section 356a BGB: electronic withdrawal function for distance contracts",[229,640,641],{},[186,642,644],{"href":268,"rel":643},[190],"German act implementing the consumer-rights reform, 3 February 2026",[229,646,647],{},[186,648,650],{"href":274,"rel":649},[190],"Directive (EU) 2023\u002F2673: consumer protection rules for distance contracts",[229,652,653],{},[186,654,657],{"href":655,"rel":656},"https:\u002F\u002Fwww.bmjv.de\u002FSharedDocs\u002FPressemitteilungen\u002FDE\u002F2025\u002F0903_Widerrrufsbutton.html",[190],"German Federal Ministry of Justice: proposal for simple digital online-purchase withdrawals",[229,659,660],{},[186,661,663],{"href":443,"rel":662},[190],"IHK Osnabrück: withdrawal button mandatory since 19 June 2026",[229,665,666],{},[186,667,670],{"href":668,"rel":669},"https:\u002F\u002Fohn.haendlerbund.de\u002Frecht\u002Fpolitik-gesetze\u002Fwiderrufsbutton-ausnahmen-kleine-shops",[190],"Händlerbund: exemptions for small shops?",[229,672,673],{},[186,674,676],{"href":536,"rel":675},[190],"Shopware documentation: revocation request in the storefront",[229,678,679],{},[186,680,682],{"href":542,"rel":681},[190],"Shopware: Germany's withdrawal-button requirement 2026",[229,684,685],{},[186,686,689],{"href":687,"rel":688},"https:\u002F\u002Fforum.shopware.com\u002Ft\u002Fwiderrufsbutton-in-shopware-6-7-9-0-wo-aktivieren-wie-umsetzen\u002F109001",[190],"Shopware Community Forum: activation and implementation from 6.7.9.0",[229,691,692],{},[186,693,696],{"href":694,"rel":695},"https:\u002F\u002Fdigitalmann.de\u002Fblog\u002Fwiderrufsbutton-shopware-6-6-einrichten",[190],"digitalman: set up the withdrawal button in Shopware 6.6",[229,698,699],{},[186,700,703],{"href":701,"rel":702},"https:\u002F\u002Fstore.shopware.com\u002Fen\u002Fmedia50620347541m\u002Fwithdrawal-button-online-withdrawal-form-according-to-eu-directive-2023-2673.html",[190],"mediameets: withdrawal button for Shopware 6",[229,705,706],{},[186,707,710],{"href":708,"rel":709},"https:\u002F\u002Fstore.shopware.com\u002Fen\u002Fmedia82172519414m\u002Fwithdrawal-button-online-withdrawal-form-according-to-eu-directive-2023-2673.html",[190],"mediameets: withdrawal button for Shopware 5",{"title":712,"searchDepth":713,"depth":713,"links":714},"",2,[715,716,717,723,724,729,730,731,732],{"id":209,"depth":713,"text":210},{"id":257,"depth":713,"text":258},{"id":359,"depth":713,"text":360,"children":718},[719,721,722],{"id":367,"depth":720,"text":368},3,{"id":381,"depth":720,"text":382},{"id":395,"depth":720,"text":396},{"id":405,"depth":713,"text":406},{"id":415,"depth":713,"text":416,"children":725},[726,727,728],{"id":422,"depth":720,"text":423},{"id":436,"depth":720,"text":437},{"id":449,"depth":720,"text":450},{"id":456,"depth":713,"text":457},{"id":475,"depth":713,"text":476},{"id":548,"depth":713,"text":549},{"id":592,"depth":713,"text":593,"children":733},[734],{"id":629,"depth":720,"text":630},[736,737,738,739,740,741,742,743],{"name":638,"url":188},{"name":644,"url":268},{"name":650,"url":274},{"name":657,"url":655},{"name":663,"url":443},{"name":670,"url":668},{"name":676,"url":536},{"name":682,"url":542},"When the withdrawal button is mandatory, what section 356a BGB requires and how to implement it properly in Shopware 6, natively or with a plugin.",false,"md",{"src":748,"alt":749},"\u002Fimages\u002Finsights\u002Fwithdrawal-button-shopware-6.png","Alex Jank presenting the three-step digital withdrawal process with withdrawal function, confirmation and email proof",{},true,null,"2026-08-18",12,{"title":756,"description":757},"Withdrawal button 2026: requirement and Shopware 6 setup","Withdrawal button since 19 June 2026: who needs it, what section 356a BGB requires and how B2C shops configure it in Shopware 6.",{"loc":117},"en\u002Finsights\u002Fwithdrawal-button-shopware-6",[761,762,763],"Shopware","E-commerce law","Compliance","insights-withdrawal-button-shopware-6","kzpo97DYYfVfd3VdzTeHIJH1wnaDomat1hdl9POXL6E",{"id":767,"title":768,"alternateName":769,"bio":770,"body":771,"description":826,"events":827,"extension":746,"heroIllustration":829,"image":831,"meta":834,"name":833,"navigation":751,"ogImage":752,"path":162,"projects":752,"robots":752,"role":835,"schemaOrg":752,"seo":836,"sitemap":837,"slug":172,"socials":838,"stem":841,"talks":842,"translationKey":846,"__hash__":847},"team_en\u002Fen\u002Fteam\u002Falex-jank.md","Alex Jank — Founder & Architect","Alexander Jank","Alex is responsible for system design, scalability, integrations, and stability. He has seen more systems from the inside than most — and is nuonic's go-to person for sound technology decisions.",{"type":174,"value":772,"toc":821},[773,777,780,783,786,790,796,802,808,814,818],[207,774,776],{"id":775},"about-alex","About Alex",[177,778,779],{},"Alexander \"Alex\" Jank started writing software at twelve — PHP, self-taught, to maintain his school's website. Even before that, he knew he wanted to become an entrepreneur in IT. While still at school he read books on software architecture and tried out everything he could get his hands on; Visual Basic .NET followed PHP, and before graduating he built his first online shop — an ice hockey store, first with Gambio, then with xt:Commerce.",[177,781,782],{},"After three semesters of business informatics (the business part was the more interesting one), he chose practice over the lecture hall: a trainer qualification (AEVO), the external examination as a certified IT specialist for application development — and years of custom software built with Symfony and Nuxt.js. Among them: construction-progress tracking for housing projects, the admin interface of a restaurant ordering, reservation and delivery platform, an idea portal, and a web-to-print solution.",[177,784,785],{},"Shopware entered the picture in 2021. The first client ran on Shopware 5 — Alex didn't know Shopware at the time, but signed on anyway: \"It's Symfony after all. And what could be worse than the internals of API Platform?\" The approach proved right. In 2022 he crossed paths with Benedikt on a shared Shopware project — and in 2023 the two founded today's nuonic Digital GmbH & Co. KG.",[207,787,789],{"id":788},"focus-areas","Focus areas",[177,791,792,795],{},[215,793,794],{},"Architecture & technology decisions."," Alex has seen many systems from the inside — grown ones, tangled ones, and genuinely good ones. That's exactly why he can assess software architecture quickly and reliably: which decision still holds up in five years, and which one gets expensive?",[177,797,798,801],{},[215,799,800],{},"DevOps."," There are few DevOps engineers who also know this much Shopware and architecture. Alex factors deployment, operations, and infrastructure in from day one — not as an afterthought following the final sprint.",[177,803,804,807],{},[215,805,806],{},"Performance — end to end."," Not just \"which code runs faster\", but the whole picture: What is an LCP? How should fonts be loaded? How do you keep images small, what do you do with icons — and how do you cache properly without trading one problem for another?",[177,809,810,813],{},[215,811,812],{},"Integrations."," Often unglamorous — transforming data and batching it differently — but decisive in almost every project. Alex builds them so they don't spring surprises in production.",[207,815,817],{"id":816},"beyond-the-code","Beyond the code",[177,819,820],{},"Alex lives in Fürstenfeldbruck near Munich and is a regular at the Shopware Stammtisch Munich — that's where he test-drove his SCUC talk in 2025. He balances work with the gym and running, cycling and the water — swimming as well as sailing — and cooking. And whenever nuonic needs graphics or photos, his brother occasionally helps out with a marketing eye.",{"title":712,"searchDepth":713,"depth":713,"links":822},[823,824,825],{"id":775,"depth":713,"text":776},{"id":788,"depth":713,"text":789},{"id":816,"depth":713,"text":817},"Projects, references, talks and events by Alex Jank — founder and architect at nuonic Digital: system design, DevOps and performance.",[828],"mittwald-agentur-barcamp-2026",{"src":830,"alt":712},"\u002Fimages\u002Fteam\u002Fsegelboot.png",{"src":832,"alt":833},"\u002Fimages\u002Fteam\u002Falex-jank.jpg","Alex Jank",{},"Founder & Architect",{"title":768,"description":826},{"loc":162},{"linkedin":839,"github":840},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Falexander-jank-23a261160\u002F","https:\u002F\u002Fgithub.com\u002Fjankal","en\u002Fteam\u002Falex-jank",[843,844,845],"beyond-seo-scuc-2026","symfony-cli-docker-scuc-2025","shopware-container-hosting-hitc-2026","team-alex-jank","4nv4kS_IhfmcA34LN5YfRL1UKSUmmkgeecfZwfkzGIY",1787059073156]