Skip to content
Personal, from the Hildesheim region
Law & data protection

Withdrawal Button 2026: What Your Website Now Needs

Since 19 June 2026, Section 356a BGB requires an electronic withdrawal function. Who is affected, who is not - and how to implement it properly in your shop.

13 min read WiderrufsbuttonRechtOnlineshopMittelstandVerbraucherschutz

Since 19 June 2026, a new duty applies to contracts concluded online in Germany: Section 356a of the German Civil Code (BGB) requires an electronic withdrawal function (Federal Law Gazette 2026 I No. 28). Anyone who lets consumers conclude distance contracts with a statutory right of withdrawal through an online interface - a website, an order form, a booking system or an app - must make withdrawing as technically accessible as ordering. That sounds like a topic for large mail-order retailers, yet it equally affects trades and service businesses that let customers commission work or book paid appointments online. The other direction matters just as much: many businesses in the Hildesheim region are not affected at all, because no contract is concluded through their website or because their services fall under one of the statutory exemptions. This article separates the two cases cleanly - what has to be done, what expressly does not, and what a robust implementation inside the ordering flow looks like. As a web agency from the Hildesheim region we assess this soberly, without warning-letter panic.

Withdrawal button since 19 June 2026: what the website must doDecision path: do I need the function?1 Contract via online interface?website, order form, booking tool, appSec. 356a (1)2 Consumer as contracting party?pure B2B orders are not coveredSec. 13 BGB3 Right of withdrawal exists?check exemptions (Sec. 312g (2))Sec. 312g BGBall three answers: yesfunction is mandatoryat least one nono function neededCancellation button under Sec. 312k BGB applies since 1 July 2022 -separate duty, separate label, separate confirmation.Withdrawal flow: four steps to confirmation1Button: withdraw from contractpermanently available, prominentSec. 356a (1)2Enter the contract detailsname, contract reference, contactSec. 356a (2)3Confirm: confirm withdrawala second button sends it offSec. 356a (3)4Acknowledgement in the inboxtext form, date and timeSec. 356a (4)Sent in time counts as received in time (paragraph 5).The period is 14 days without giving reasons (Sec. 355 (2) BGB).Timeline of the rule13 exemptions: Sec. 312g (2)22 Nov 2023Directive (EU) 2023/267319 Dec 2025transposition deadline for member states19 Jun 2026Sec. 356a BGB becomes applicable

What has applied since 19 June 2026

The rule has a European origin. Directive (EU) 2023/2673 of 22 November 2023 was published in the Official Journal of the European Union on 28 November 2023 (EUR-Lex). It amended the Consumer Rights Directive 2011/83/EU and inserted a new Article 11a on the withdrawal function. Member states had to transpose the requirements into national law by 19 December 2025 and have applied them since 19 June 2026 (Directive (EU) 2023/2673). In Germany this was done by the Act amending consumer contract and insurance contract law, promulgated on 3 February 2026 (Federal Law Gazette 2026 I No. 28). The new Section 356a BGB carries the official heading Electronic withdrawal function for distance contracts and has applied since 19 June 2026 (Federal Law Gazette 2026 I No. 28).

What the provision demands can be summarised in five steps. Under paragraph 1, distance contracts concluded through an online interface require a withdrawal function that is legibly labelled withdraw from contract or with a correspondingly unambiguous wording, permanently available throughout the withdrawal period, prominently placed and easily accessible (Section 356a BGB). Paragraph 2 describes the details the consumer must be able to submit: their name, information identifying the contract or the part of it the withdrawal refers to, and an electronic means of communication for the acknowledgement. Paragraph 3 requires a second button labelled confirm withdrawal or an equivalent wording, which actually sends the declaration. Under paragraph 4, the trader must without undue delay provide an acknowledgement of receipt on a durable medium containing the content of the declaration plus the date and time of receipt. Paragraph 5 finally clarifies that a declaration sent in time counts as having been received in time (Section 356a BGB).

A directive on financial services - with effect for all online contracts

Directive (EU) 2023/2673 carries financial services in its title, and that is precisely what causes misunderstandings. The new Article 11a was not inserted into the special chapter on financial services, however, but into the general part of the Consumer Rights Directive. It therefore applies to distance contracts concluded through an online interface (EUR-Lex). The German transposition follows suit: Section 356a BGB sits in the general law on withdrawal and attaches not to a sector but to the way the contract is concluded (Federal Law Gazette 2026 I No. 28).

Who the duty really affects

Three conditions must come together for Section 356a BGB to apply. First, a contract must be concluded through an online interface - website, order form, booking system or app. Second, the contracting party must be a consumer within the meaning of Section 13 BGB. Third, a statutory right of withdrawal must exist for that contract at all. If one of the three is missing, no duty to provide a withdrawal function arises. That is exactly why a sober look at your own website pays off before anything is built. The size of the underlying market is clear: 79 percent (Bitkom) of internet users in Germany shop online regularly, and German online retail reached a turnover of 88.8 billion euros (HDE) in 2024.

Online shop with consumer customers

The classic case: goods are ordered through the basket, the contract is concluded online, the right of withdrawal exists. Here the withdrawal function is mandatory - regardless of how large the range of products is.

Trade business with online commissioning

Anyone accepting binding orders through a form, for maintenance, cleaning or installation, concludes a distance contract. Whether an exemption applies depends on the type of service; for businesses with web design for the trades this is the first thing to check.

Paid online appointment booking

If the booking flow already concludes a contract for consideration rather than merely sending an enquiry, the same applies. For date-bound services in certain areas, however, an exemption applies (Section 312g (2) no. 9 BGB).

Subscriptions and memberships

Courses, care packages or digital services on subscription are affected twice over: as a rule they need a withdrawal function under Section 356a BGB and, in addition, the cancellation button under Section 312k BGB.

Not affected is anyone whose website only receives enquiries. A contact or enquiry form that leads to a quotation and later to a contract concluded by phone, email or on site is not a distance contract concluded through an online interface. Businesses that supply commercial customers exclusively also remain outside the scope: the right of withdrawal under Section 312g BGB belongs to consumers, not to companies. For many businesses in Hildesheim, Sarstedt or Bad Salzdetfurth the assessment ends right here - and that is a legitimate result, not an omission.

The short version for your business

If your website informs and collects enquiries, nothing changes. If people can place binding orders or paid bookings through your website and your customers are consumers, check two things: whether a right of withdrawal exists for the specific service - and whether your ordering flow already provides the function required by Section 356a BGB.

Withdrawal button and cancellation button: two sections, two jobs

The cancellation button under Section 312k BGB is regularly confused with the withdrawal button, even though the two serve different purposes. The cancellation button has existed since 1 July 2022; it was introduced by the Act on fair consumer contracts of 10 August 2021 (Federal Law Gazette I p. 3433). It concerns continuing obligations and ends a running contract for the future. The withdrawal button, by contrast, concerns the opening phase of a contract and leads to its unwinding. Anyone subject to both duties needs both buttons - one does not replace the other.

FeatureWithdrawal button (Sec. 356a BGB)Cancellation button (Sec. 312k BGB)
Applies since19 June 20261 July 2022
Use caseDistance contract with right of withdrawal via an online interfaceContinuing obligation in electronic commerce
First labelwithdraw from contractcancel contracts here
Second labelconfirm withdrawalcancel now
EffectUnwinding of the concluded contractTermination of the contract for the future
Acknowledgementwithout undue delay, with content, date and timeimmediately, electronically in text form
Consequence if missingcompetition-law complaints possiblecancellation at any time without notice period (Sec. 312k (6) BGB)

A second difference concerns the consequences. If the cancellation button is missing, the consumer may end the contract at any time without observing a notice period (Section 312k (6) BGB) - an immediate and tangible legal effect. For a missing withdrawal function, Section 356a BGB provides no comparable sanction; what matters in practice are complaints under competition law. Both must be kept apart from the withdrawal instruction: anyone who fails to inform consumers properly about the right of withdrawal has to expect the period to end later. It expires at the latest twelve months and 14 days (Section 356 BGB) after the regular start of the period, while the regular period is 14 days (Section 355 (2) BGB) and runs without any need to give reasons.

When no withdrawal function is needed

Section 312g (2) BGB lists 13 contract types (Section 312g BGB) for which the right of withdrawal does not exist, unless the parties have agreed otherwise. Where there is no right of withdrawal, there is nothing to withdraw from - and therefore no duty under Section 356a BGB. For local businesses these cases are the relevant ones:

  • Custom-made goods: goods that are not prefabricated and whose production depends on an individual choice or specification by the consumer, or which are clearly tailored to personal needs (Section 312g (2) no. 1 BGB) - the classic case in furniture and metal fabrication and in bespoke manufacturing.
  • Perishable goods: goods liable to deteriorate rapidly or whose expiry date would quickly be exceeded (Section 312g (2) no. 2 BGB) - relevant for farm shops, bakeries and delicatessens.
  • Sealed hygiene products: sealed goods that are not suitable for return for reasons of health protection or hygiene if the seal was removed after delivery (Section 312g (2) no. 3 BGB).
  • Date-bound services: accommodation for purposes other than residential, transport of goods, car rental, supply of food and drink and further services connected with leisure activities, where the contract provides for a specific date or period (Section 312g (2) no. 9 BGB).
  • Urgent repairs on express request: contracts where the consumer expressly asked the trader to visit for urgent repair or maintenance work (Section 312g (2) no. 11 BGB); this does not extend to further services that were not expressly requested.
  • Notarially recorded contracts: contracts recorded by a notary (Section 312g (2) no. 13 BGB).

In addition, there is the case where the right of withdrawal does exist but expires early. For service contracts for consideration it expires once the service has been supplied in full, provided the consumer expressly agreed beforehand that performance would begin before the withdrawal period ends and confirmed awareness of losing the right of withdrawal upon full performance (Section 356 BGB). For businesses that deliver at short notice this is the more practical lever than any list of exemptions - though it requires carefully worded consent texts inside the ordering flow rather than a blanket tick box.

The exemption for bespoke goods is read narrowly

Not every option turns a product into a bespoke item. What matters is whether production actually follows individual specifications by the consumer; choosing a colour from a handful of standard variants generally does not suffice. Anyone claiming the exemption under Section 312g (2) no. 1 BGB for an entire range should be able to justify that classification per product group. In case of doubt, providing the withdrawal function is the calmer route than an interpretation that may not hold later.

The technical requirements step by step

Where the duty applies, implementation is manageable - but it has more components than the word button suggests. Six building blocks belong to it, and all six touch the design of the page. That is why the withdrawal function is not purely a legal topic but belongs in the same workshop as web design and usability.

  1. Placement: the function belongs somewhere reachable throughout the entire withdrawal period - typically in the customer account, in the order confirmation and additionally through a fixed entry point in the service area or footer. A link you only find three levels down hardly meets the criterion of being easily accessible.
  2. Labelling: withdraw from contract is the wording named in the statute; correspondingly unambiguous alternatives are permitted (Section 356a BGB). Creative paraphrases are an unnecessary risk at this point.
  3. Input fields: the consumer must be able to submit their name, information identifying the contract and an electronic means of communication for the acknowledgement (Section 356a BGB). If the withdrawal refers only to part of the contract, that must be expressible too.
  4. Confirmation function: only a second button labelled confirm withdrawal actually sends the declaration (Section 356a BGB). This intermediate page is not an obstacle but the sequence the statute envisages.
  5. Acknowledgement of receipt: without undue delay after receipt, a confirmation goes to the consumer on a durable medium - containing the content of the declaration plus date and time (Section 356a BGB). In practice this is an automatically generated email that doubles as evidence.
  6. Logging: anyone who wants to prove the time of receipt later needs a server-side log with a timestamp. It is not spelled out in the wording, but it follows in practice from the receipt rule in paragraph 5.

Fewer fields, fewer drop-offs

Research by the Baymard Institute shows that average order and contact forms contain around 11 form fields (Baymard Institute), although in many cases about half would suffice. The same applies to the withdrawal flow: keep mandatory fields to what the statute actually requires.

Usable on a smartphone

Around 66 percent (HDE) of online turnover is now generated on mobile devices. Controls should therefore clearly exceed the minimum size of 24 by 24 (WCAG 2.2) CSS pixels and keep enough distance from one another.

Confirmation that arrives

The acknowledgement has to reach the recipient, not merely be sent. A properly configured sender domain with the usual email authentication methods lowers the risk of the message ending up in the spam folder with the evidence missing.

The quiet benefit of the receipt rule

Under paragraph 5, the declaration of withdrawal counts as having been received within the period if it was sent through the withdrawal function before the period expired (Section 356a BGB). That relieves both sides: the consumer does not have to prove receipt, and the business has a traceable timestamp from a clean log instead of an argument about postal delivery times. This is exactly why logging is not an accessory but the actual operational benefit of the function.

Typical implementation mistakes

The mistakes that show up in practice are rarely legally complicated. They arise where a duty is pressed into a grown ordering flow after the fact, without thinking the sequence through from the start. Six patterns keep recurring.

Hidden entry point

The function sits behind a login only existing customers have, or deep inside the terms and conditions. The criterion of being prominently placed and easily accessible in Section 356a BGB demands the opposite.

Idiosyncratic labelling

Wordings such as cancel order or register a return describe something other than statutory withdrawal. Anyone departing from the statutory wording must be able to justify that it means the same thing.

Overly broad mandatory fields

Customer number, invoice number, reason for withdrawal and bank details as mandatory fields: the statute requires considerably less in paragraph 2, and a reason for the withdrawal may not be demanded at all (Section 355 (1) BGB).

Missing confirmation page

The declaration is sent with a single click. Section 356a BGB provides for a separate confirmation function in paragraph 3; the second, deliberate step is then missing.

Late or incomplete acknowledgement

A confirmation that only goes out after manual processing in the office is not without undue delay. If date and time are missing, a content element the statute expressly requires is missing too.

Withdrawal instruction not updated

The withdrawal instruction and the model withdrawal form stay unchanged even though an additional route now exists. A reference to the function belongs in the instruction and in the order confirmation.

How large the warning-letter risk is can be judged soberly. For infringements of statutory information and labelling duties in electronic commerce, competitors cannot claim reimbursement of their warning costs under Section 13 (4) UWG, and a contractual penalty is excluded on a first warning if the business regularly employs fewer than 100 employees (Section 13a (2) UWG). Whether the withdrawal function counts as an information and labelling duty in that sense or stands beside it as a separate design duty has not been settled conclusively. Independently of that, claims by consumer and business associations remain possible. The realistic expectation is therefore: not a mass phenomenon, but an avoidable point of conflict.

The withdrawal function is not an extra form, it is the proof that an ordering flow has been thought through to the end.

Working principle from our projects on ordering and booking processes

Review checklist for operators

  • Is a contract actually concluded through the website, order form, booking system or app - or is only an enquiry submitted?
  • Are the contracting parties consumers, or is the business exclusively with companies?
  • Does a right of withdrawal exist for the specific service, or does one of the exemptions in Section 312g (2) BGB apply?
  • Is the withdrawal function reachable throughout the entire withdrawal period - including for customers without an account?
  • Does the first button carry the label withdraw from contract or a correspondingly unambiguous wording?
  • Can name, contract identification and contact route for the acknowledgement be entered - and nothing beyond that as a mandatory field?
  • Does the separate confirmation function labelled confirm withdrawal exist?
  • Does the acknowledgement go out automatically, without undue delay and with date and time?
  • Is receipt logged server-side and retained so that it remains provable later?
  • Are the withdrawal instruction, the order confirmation and - where present - the cancellation button under Section 312k BGB aligned with one another?

This list does not replace legal advice, but it sorts the questions into the order in which they are sensibly answered. Anyone reaching a no at the first three points can safely skip the remaining seven. Anyone answering yes three times has a clear task list instead of a diffuse unease.

What this means for ordering and booking flows

Technically the implementation is usually unspectacular: an additional sequence in the ordering system, a form with three details, a confirmation page and an automatic email with a timestamp. It becomes demanding where orders live in several systems - the shop, the booking calendar and the merchandise management - and the withdrawal function has to reach all three. That is why our work on an online shop from Hildesheim starts with an inventory of the existing ordering and booking flows before a single line of code is written. How a shop for regional retailers is built in principle is described in the article on online shops for local retailers; anyone combining collection and shipping will find the processes in the text on click and collect for local retailers.

Taking stock

We check where contracts are actually concluded, which of them are consumer contracts and for which a right of withdrawal exists. The result is a classification per service instead of a blanket assumption.

Build and confirmation logic

Withdrawal function, confirmation page, automatic acknowledgement with date and time and the logging are built into the existing ordering flow - aligned with the customer account, the order confirmation and the instruction texts.

Keeping it current

New services, new booking routes and further legal developments feed back into the classification. As part of website maintenance we review the flow again at fixed intervals.

Legal duties attached to a website rarely arrive alone. Anyone using product photography should clarify in parallel whether the image rights for website photos are properly settled; anyone thinking about server location and availability will find the criteria in the article on choosing web hosting for local businesses and in our service on web hosting and domains. The compulsory programme also includes the mandatory imprint details under the DDG and a properly configured cookie banner under the GDPR. Where appointments are assigned online, it is worth looking at online appointment booking for local businesses as well - there the question of whether a contract is already being concluded is particularly often unclear. Already 64 percent (Bitkom) have booked an appointment online at least once. For the ordering flow itself the rule is: an additional mandatory step must not undermine conversion optimisation - on the contrary, clear sequences build trust. And because around 70 percent (Baymard) of baskets are abandoned on average, any simplification in the ordering process is money in the bank anyway. If you are unsure whether Section 356a BGB affects your business, talk to us - the assessment is usually settled in one conversation.

This article is based on data from: Section 356a BGB (electronic withdrawal function for distance contracts) on gesetze-im-internet.de, published by the Federal Ministry of Justice, with paragraphs 1 to 5 on labelling, placement, required details, confirmation function, acknowledgement of receipt and the receipt rule; the Federal Law Gazette with the act transposing Directive (EU) 2023/2673, promulgated as the Act amending consumer contract and insurance contract law on 3 February 2026 (Federal Law Gazette 2026 I No. 28), with Section 356a BGB applying from 19 June 2026; EUR-Lex with Directive (EU) 2023/2673 of 22 November 2023 (Official Journal of 28 November 2023), the newly inserted Article 11a on the withdrawal function in Directive 2011/83/EU, the transposition deadline of 19 December 2025 and the application date of 19 June 2026; in addition Section 312g BGB on the 13 exemptions from the right of withdrawal, Section 355 BGB on the 14-day withdrawal period without any duty to give reasons, Section 356 BGB on the maximum period of twelve months and 14 days and on expiry once services have been supplied in full, Section 312k BGB on the cancellation button in force since 1 July 2022 on the basis of the Act on fair consumer contracts of 10 August 2021 (Federal Law Gazette I p. 3433) and Sections 13 and 13a UWG on warning costs and contractual penalties. Market data come from the German Retail Federation (HDE) on online turnover and the mobile share of turnover, from the Baymard Institute on basket abandonment and the number of form fields, from Bitkom on the share of regular online shoppers and on online appointment booking, and from the Web Content Accessibility Guidelines (WCAG 2.2) on the minimum size of controls. This article is guidance and does not replace legal advice.

Related Articles