Withdrawal Button – EU Compliant § 356a BGB

• Partial withdrawal: on the confirmation page the customer can now tick which order items to withdraw. Default: all items selected = full withdrawal. When a subset is picked, a snapshot of the withdrawn items (label + quantity at submission time) is stored on the withdrawal and displayed in the back office and customer account. Covers § 356a BGB for partial withdrawals.
• Customer account overview "My withdrawals": new page /account/withdrawals listing every withdrawal of the logged-in customer including status, reason, optional partial-item list and rejection notice. The sidebar link appears automatically when the withdrawal button is enabled in the account menu.
• Reject withdrawal with reason: the back office can now reject a withdrawal directly when a statutory exception under § 312g(2) BGB applies (custom-made goods, perishable items, opened hygiene seal, opened sealed data carrier, inseparably mixed, other). Modal with mandatory free-text reason; new mail template kommora_withdrawal_rejected notifies the customer with the verbatim reason; status rejected has its own badge in list, detail and customer account.
• Period-start option "Order completed": additional choice next to "Order date" and "Shipping date". Suitable for services, software and subscription contracts where the contract is treated as fulfilled when the order state transitions to completed. Fallback when the order is not yet completed: order date (so the withdrawal is never accidentally hidden).
• Bugfix "Show withdrawal link in order confirmation": the toggle in the plugin settings has had no effect since it was introduced (no wiring in code). A new mail subscriber now appends a legally compliant right-of-withdrawal block with link directly to the HTML and plain body of the order confirmation email as soon as the toggle is enabled — works out of the box on any shop without editing the mail template. Language is detected from the mail body content (DE/EN).
• Footer button visible even with a collapsed hotline accordion: in some themes the hotline column is collapsed by default as a Bootstrap collapse or collapses on mobile. Previously the button was injected into the collapse content and therefore hidden until the customer manually expanded the accordion. The anchor lookup now actively checks the collapse state and appends the button to the column itself when the accordion is closed — below the hotline section and always visible. When the accordion is open (default on MAN/Opel/BPW etc.) the existing behaviour is kept.
• Footer button fix for themes with an empty

  placeholder:

  the previous Tier-2 selector matched an empty inline

  left over by the theme CMS in some shops. Our block-level button ended up inside an inline

  and was silently dropped from the layout by the browser. The selector is gone, the column tier kicks in cleanly.

NEUE FEATURES

─────────────

• Drei automatische Status-Benachrichtigungen an den Kunden: bei

  Statuswechsel auf „In Bearbeitung" oder „Abgeschlossen" sowie bei

  Speicherung des Rückerstattungs-Status erhält der Kunde automatisch

  eine passende Info-Mail. Jeder Trigger einzeln ab-/zuschaltbar in der

  neuen Plugin-Konfig-Card „Kunden-Status-Benachrichtigungen". Drei

  neue editierbare Mail-Templates mit Twig-Variablen (Bestellnummer,

  Erstattungsbetrag, Kundenname).

• Eigene CSS-Klasse(n) und freies CSS für den Footer-Button: ohne

  Core-Edit kann der Widerruf-Button 1:1 an einen bestehenden Theme-

  Button (z. B. Newsletter-Button) angepasst werden. Wenn eine Custom-

  Klasse oder Custom-CSS gesetzt ist, übernimmt das Plugin gar keine

  eigenen Inline-Farben mehr — User-Styles greifen ohne Override.

• Vor- und Nachname als zwei separate Pflichtfelder im Widerrufs-

  formular (§ 356a Abs. 2 Nr. 1 BGB n.F. / Art. 11a RL 2011/83/EU,

  anwendbar ab 19.06.2026). Bei eingeloggten Kunden aus dem Account

  vorausgefüllt. Bei Abweichung zur Bestellung wird ein interner

  Hinweis ins Notiz-Feld geschrieben (keine Frontend-Hürde — der

  Widerruf wird trotzdem akzeptiert).

• Alle vom Plugin verwalteten Mail-Templates mit „Kommora:"-Prefix in

  der Beschreibung. Klar erkennbar in der Mail-Template-Liste,

  insbesondere ab Shopware 6.7 (das einen eigenen Standard-

  Widerrufsbutton mitbringt).

BEHOBEN

─────────────

• Die Auswahl „Button-Stil" (Primär / Sekundär / Umriss) hatte bisher

  keinen optischen Effekt — Inline-Hintergrundfarbe überdeckte die

  Bootstrap-Variante. Bei Umriss-Varianten wird jetzt kein Inline-

  Background mehr gesetzt; der Unterschied ist visuell sichtbar.

• Custom-Field-Selector für ERP-/externe Bestellnummern war im Plugin-

  Konfig-Backend auf Shopware 6.6 unsichtbar. Ursache: die für 6.7

  benötigte Datei .vite/entrypoints.json war versehentlich aus dem

  ZIP-Paket excluded, das Webpack-Bundle für 6.6 war veraltet. Beide

  Bundles + Manifest jetzt korrekt im Paket.

• Hilfetext am Feld „Link zum Muster-Widerrufsformular": Verweis auf

  das in 1.1.1 entfernte Feld „Ziel des Widerrufsbuttons" entfernt.

  Stattdessen klargestellt, dass sowohl relativer Pfad als auch

  absolute URL akzeptiert werden.

• Hilfetext am Feld „Rückerstattungs-Tracking anzeigen": erklärt jetzt

  was die Option tatsächlich macht (zusätzlicher Card-Block in der

  Widerrufs-Detailansicht mit Refund-Status + Erstattungsbetrag).

• ERP-Bestellnummer-Lookup im Gast-Widerrufsformular brach mit „500

  Internal Server Error" ab, wenn der Custom-Field-Name Leerzeichen

  enthielt. Custom-Field-Lookup nutzt jetzt eine robuste PHP-Side-

  Filterung statt JSON-Pfad-Filter.

Changes in First & Lastname matching.

Fixed bug at Customfield of Ordernumber

Set First & Lastname as required fields

* New: Selectable order identification for ERP setups. Under "Order identification" in the plugin configuration you can now choose whether the customer enters the Shopware order number on the guest withdrawal form (default) or an external number stored in an order custom field (e.g. the ERP order number). When the ERP option is active, a dropdown lists all custom fields belonging to a custom-field set linked to the order entity – no need to type technical field names. An optional fallback to the Shopware order number (default on) keeps legacy orders without a populated ERP value accessible.

* New: For logged-in customers, the order picker dropdown now shows the external order number as the primary value in ERP mode, with the Shopware order number in parentheses – consistent with what the customer sees on their invoice / delivery note and what your back office uses.

* New: The external order identifier the customer entered is stored on the withdrawal (new column `external_order_identifier`) and shown in the admin list and detail view. The Twig variable `externalOrderIdentifier` is available in mail templates and on the Flow Builder event `kommora_withdrawal.submitted`.

New: Configuration option "Disable date filtering (show all orders)". The order selection dropdown then shows all of the customer's orders without pre-calculating a withdrawal period and without a remaining-days display – relevant in view of Article 11a of Directive 2011/83/EU (applicable from 19 June 2026), which requires the withdrawal function to be available throughout the legal withdrawal period (which starts upon receipt of the goods, § 356(2)(1) BGB)

Changes in Mailintegration

* Improvement: The footer withdrawal button now also appears with themes that replace the default footer with their own building blocks (e.g. ThemeWare). A theme-independent mechanism inserts the button into the footer service hotline area if the theme does not provide the default block – without a duplicate button on the default theme.

* Improvement: The withdrawal button now always leads directly to the plugin's integrated withdrawal form (at /kommora/withdrawal). The field for changing the button path was removed, as it caused confusion and the plugin form (including e-mail confirmation and audit functionality) is the core of the solution anyway.

* Note: The optional link to the statutory model withdrawal form (PDF) remains configurable as before.

* Fixed: On Shopware 6.7 the withdrawal page could fail with "Unfortunately, something went wrong" because an internal method removed in 6.7 was called. The page now renders reliably on Shopware 6.5, 6.6 and 6.7.

* Fixed: With an empty URL field the withdrawal button pointed to a non-existent address (redirect loop in maintenance mode). Now reliably falls back to /kommora/withdrawal.

* Improvement: Clearer naming of the two URL fields (button target vs. model PDF link).

* Fixed: With an empty URL field the withdrawal button pointed to a non-existent address, which could cause a redirect loop in maintenance mode. The button now reliably falls back to the always-reachable internal address /kommora/withdrawal.

* Improvement: The two URL fields are now clearly named – "Withdrawal button target (path or external URL)" for the button target and "Model withdrawal form link (PDF, optional)" for the plain PDF download link. The help texts clarify which field does what.

Bugfix in URL Matching

* Fixed: Withdrawal confirmation and shop notification are now reliably dispatched on the first submission — independent of the Flow-Builder.

* Note: The default flow installed by the plugin is automatically deactivated during the update. Mail templates remain editable in the admin.

* Fixed: The "Resend e-mails" button now reliably dispatches the withdrawal confirmation and the shop notification — including in shop environments where the previous flow-builder based dispatch silently dropped the mails.

* Fixed: The confirmation dialog for "Resend e-mails" is now displayed reliably.

* Improvement: Internal console command aligned with current Shopware recommendations.

* New: "Resend e-mails" button in the withdrawal detail. Lets you resend the withdrawal confirmation to the customer and the notification to the shop operator at any time — for example when a mail was caught by a spam filter or did not arrive on the first try.

* New: Console command for administrators to also re-trigger withdrawal e-mails via SSH.

* A 60-second cooldown between resends prevents accidental duplicate sends.

* Fixed: 500 error "STOREFRONT__CLASS_DONT_HAVE_TWIG_INJECTED" when calling the withdrawal page. The storefront controller now receives Twig correctly via setter injection.

* Fixed: Mail template variable resolution now goes through a dedicated flow storer (WithdrawalEventStorer). This makes it work consistently on Shopware 6.5 and 6.6.

* Fixed: Duplicate "Withdraw contract" entry in the footer. The notice now appears only once as a button in the service hotline column, no longer additionally as a list link in the "Information" column.

* Second, separate email to the shop operator on every withdrawal submission (dedicated mail template type `kommora_withdrawal_submitted_shop`, fully editable via Flow Builder).

* The new flow sequence is added idempotently during the update — existing customizations to the default flow remain untouched.

* `WithdrawalSubmittedEvent` and `WithdrawalStatusChangedEvent` now implement `ScalarValuesAware`, so all event variables (order number, customer name, reason, …) reliably resolve in the mail templates.

Initial release: Two-step withdrawal process, guest access, 5 placement options, admin list and detail view, refund tracking, dashboard widget, reminder email, automatic order status, CMS element, Flow Builder integration.