Web Development for Germany
Germany is the market where a small legal oversight arrives as a letter with a bill attached. Most of those mistakes are made during the build.
Germany is the most legally exacting web market in Europe, and the enforcement mechanism is unusual: competitors and industry associations can send a formal warning letter, an Abmahnung, that comes with legal costs attached. Most of the triggers are things a developer either did or failed to do.
The Impressum is a legal obligation with a specific content list
Under §5 of the Digitale-Dienste-Gesetz, which replaced the TMG in May 2024, commercial sites must carry a legal notice with defined content — including the responsible entity, contact details and, where applicable, register and VAT identification. It has to be reachable in a couple of clicks from any page. A missing or incomplete Impressum is one of the most common Abmahnung triggers, and it takes an hour to get right.
Self-host your fonts
In January 2022 a Munich court held that loading Google Fonts from Google's servers without consent transmitted the visitor's IP address unlawfully and awarded damages. Whatever one thinks of the reasoning, a wave of warning letters followed. The fix is trivial: host the font files yourself. This site does, for exactly this reason.
Cookie consent must be a genuine opt-in
Under §25 TDDDG, non-essential cookies and similar technologies need consent before they are set — not after the banner is dismissed, and not on scroll. The pattern that fails here is a banner that reports consent while the tags have already fired.
Germans buy on invoice, and a checkout without it converts badly
Kauf auf Rechnung — receive the goods, then pay — is culturally normal and commercially significant in Germany in a way it is not in most markets. Offering only cards is a conversion decision, not a neutral one. SEPA direct debit and PayPal matter too, and note that giropay was discontinued at the end of 2024, so integration guides referencing it are out of date.
E-invoicing began in January 2025
Since 1 January 2025, domestic German B2B businesses must be able to receive structured electronic invoices in the EN 16931 format — XRechnung or ZUGFeRD. Issuing obligations phase in from 2027 for larger businesses and 2028 more broadly. A PDF by email is no longer an electronic invoice for this purpose, and any billing system you build now should be designed for structured output.
What you get
Tech stack
Why work with me
No German client yet, and I will say that rather than imply otherwise. My European work is in the UK, Switzerland and France. What transfers is European compliance engineering and e-commerce architecture; German-language customer support does not, and you should weigh that.
The German risks are engineering risks. Impressum, self-hosted fonts, tag blocking before consent, correct price display and a real withdrawal flow are all build decisions. They cost almost nothing during development and a great deal once a letter arrives.
I already build this way. This site self-hosts its fonts and has no third-party render-blocking requests at all. That was a performance decision that happens to be the German legal answer too.
Same working day, and you own the code. Cairo is one hour ahead of Berlin. Repository in your name on delivery, no lock-in, no proprietary framework.
Related work
Real shipped projects in this space.
In-depth guides on this
Practical articles on the decisions and the costs, before you hire anyone.
Questions before you hire
What actually triggers an Abmahnung?
Do I really have to self-host fonts?
Does the January 2025 e-invoicing rule apply to me?
Do I need to offer purchase on invoice?
Can you work without German-language support?
Why hire outside Germany?
Ready to start your project?
Send your brief. You will get a written quote and a clear plan within 24 hours. First consultation is free.