§ 312j BGB: When Online Orders Become Binding

Important notice Legal, tax and industry-specific information concerns Germany and expressly identified EU law. It is provided for general orientation and does not replace individual advice. Last review of the cited legal situation: July 2026 Show the full notice

Unless stated otherwise, the legal, tax or industry-specific information on this page reflects the law applicable in Germany and German official and professional practice. Directly applicable EU law and references to other jurisdictions are identified separately. The information was researched with due diligence using sources available as of the stated review date. For binding guidance on your specific project, please contact the competent chamber or a qualified specialist, such as a lawyer or tax adviser. The current statutes and official regulations always prevail.

A restaurant accepts online pre-orders. A bakery lets customers reserve bread for the next morning. A florist offers bouquets for pickup. As soon as the process is not merely a non-binding enquiry but a paid order for consumers, § 312j BGB can become relevant.

What the Paragraph Regulates

Where the order is placed using a button, the entrepreneur fulfils the obligation under subsection (3) sentence 1 only if this button is labelled in an easily legible manner with nothing other than the words “order with obligation to pay” or with a corresponding unambiguous wording.

§ 312j BGB sets out special duties in electronic commerce with consumers. It covers situations where a consumer orders something online and a payment obligation may arise. The best-known part is the so-called button solution: the final order button must be labelled so that an average person clearly understands that clicking it triggers a paid order.

The purpose is straightforward: people should not be pushed into a contract through unclear buttons, hidden costs or confusing intermediate steps. A general button such as “Continue”, “Order” or “Complete booking” is not automatically enough. The wording needs to clearly indicate the payment obligation. The statute names “zahlungspflichtig bestellen” as the guiding wording in German, but allows an equally unambiguous formulation.

Importantly, § 312j BGB does not apply to every contact form. A normal enquiry, callback request or non-binding reservation request is different from an order process in which consumers trigger a paid service or product order.

Who Is Affected

§ 312j BGB becomes relevant mainly when a website contains a binding online order process for consumers. For our typical customer groups, this can affect:

• Restaurants, pizzerias, cafes and takeaway businesses - for example with pre-orders, pickup orders or delivery requests where the click is meant to trigger a paid order. More context is available on our pages for restaurant websites, pizzeria websites, cafe websites and takeaway and delivery websites.
• Bakeries and ice cream parlours - for example with pre-orderable cakes, loaves, ice cream boxes or catering products if price, quantity and pickup are already fixed in a binding way. See our notes on a bakery website and a website for ice cream parlours.
• Florists, jewellers and local retailers - for example with pickup orders, product reservations with a payment obligation or binding product enquiries. Details are available on the website for florists and the website for jewellers.

The decisive point is not whether the website calls itself a shop. The decisive point is whether the flow is intended to operate like a binding order. If only an enquiry is sent and the contract is concluded separately later, the situation is different.

Typical Use Cases

For gastronomy websites, the borderline is very practical. A menu with prices is usually not yet an order process. A form where someone submits “two pizzas, 7 p.m., pickup” can be designed in several ways: as a non-binding enquiry, as a reservation or as a binding order. The text, button labels and confirmation emails should therefore fit together.

For bakeries, the question often arises with pre-orders. If customers merely request a callback, this is not the classic button-solution scenario. If they choose products, enter quantities, see the total price and confirm a binding order, the flow moves closer to an electronic order process. Then the issue is not only the button, but also the information immediately before the final step: goods, quantity, total price, pickup or delivery conditions and possible extra costs.

For florists and local retailers, a product reservation can also mean different things. “Send enquiry” sounds non-binding. “Buy now” or “order with obligation to pay” sounds binding. Problems arise when the text promises something non-binding but the confirmation is treated like a contract. A website should therefore not accidentally create more legal commitment than the business can operationally handle.

For jewellers and other retailers with higher-value goods, availability, individualisation and consultation often matter. For small businesses, an enquiry or reservation flow is often more suitable than a full shop. The website should then clearly show that no automatic purchase contract is concluded yet.

Exceptions and De Minimis Rules

§ 312j BGB presupposes a consumer contract in electronic commerce. Pure internal B2B flows, general contact forms or non-binding enquiries are not the core case of the button solution. A table reservation without a payment obligation is also different from a binding order with a total price.

Still, the question should not be reduced to online payment. Even if payment happens on site, the online click can trigger a paid order if the business treats the order as already binding. Conversely, an online form is not automatically a shop if it clearly communicates that it is only an enquiry and that the contract is confirmed later.

This distinction matters for small businesses. Anyone who does not want to operate a shop should deliberately design the website as an enquiry, reservation or pre-order process and avoid creating the impression of a full online purchase through button wording, basket logic or automatic order confirmations.

Consequences of Violations

§ 312j paragraph 4 BGB contains a strict consequence: a contract is concluded only if the entrepreneur fulfils the obligation under paragraph 3. If the final button does not clearly indicate the payment obligation, the contract may therefore not be validly concluded. For businesses, this creates uncertainty: was the order effective? Must delivery take place? Can payment be demanded?

There are also competition-law risks. Unclear order buttons can be challenged by consumer associations or competitors. For small businesses, even correcting a badly designed order flow can be burdensome: texts, confirmation emails, price logic, form fields and terms references often have to be reviewed together.

The Court of Justice of the European Union has emphasised under the Consumer Rights Directive that the wording on the button itself is decisive. Information elsewhere in the flow cannot freely compensate for an unclear button label. That is why practical implementation matters.

Practical Implementation on the Website

The most important decision is made before the design: should the website trigger a binding order or only transmit an enquiry? For many small businesses, the enquiry route is more suitable. It avoids shop, payment and availability logic and lets the business confirm the order manually.

As part of website creation from the ground up, such flows can be planned deliberately and kept lean: clear enquiry or pre-order forms, understandable help text, consistent confirmations and suitable contact paths for gastronomy or retail businesses. If online payment is not needed, an internal web solution can send entries in a structured way to the mailbox or a small overview; payment, pickup and final confirmation then happen outside the website.

We do not build our own shop systems with basket and online payment. Specialised platforms exist for that, with the required compliance. If a business uses an online ordering system, reservation tool or another specialist provider, Velvionix can integrate it cleanly into the website - by widget, iframe or button link, provided the provider offers a stable technical option. Contract, costs and payment processing run directly between the business and the provider; Velvionix handles the clean website integration.

Frequently Asked Questions

Does every contact form need an “order with obligation to pay” button?

No. A normal contact form typically does not trigger a payment obligation. § 312j BGB becomes relevant when the click is meant to trigger a paid order or comparable contractual declaration.

Can the button solution apply without online payment?

Yes, it can. The decisive point is not only when payment happens, but whether the online click already creates a paid order.

Is “Buy now” always sufficient?

Not automatically. The German statute names “zahlungspflichtig bestellen” and requires an equally unambiguous wording. Whether another label is sufficient depends on its clarity.

Is a non-binding pre-order allowed?

Yes, but it should be designed as non-binding. Button, confirmation and process should not suggest that a purchase contract has already been concluded.

Why does Velvionix not offer custom shop systems?

Because shop and payment flows can trigger many follow-up obligations. Velvionix can embed specialised ordering, reservation or shop systems into the website, but does not build its own checkout. If online payment is not needed, a lean enquiry or pre-order form is often more suitable, with payment and confirmation handled outside the website.

What does Velvionix handle for ordering or reservation systems?

Velvionix handles the website structure, clear user guidance and technical integration of suitable systems. If a business already uses a specialised ordering or reservation system, it can be connected in a traceable way; if online payment is not needed, a lean enquiry or pre-order process may be enough.