A German-facing website needs four things international builds skip: a statutory Impressum, granular DSGVO consent, structured B2B e-invoicing (XRechnung or ZUGFeRD), and a BFSG accessibility evidence pack. Accessibility failures can trigger fines up to €100,000; every German business has had to receive structured e-invoices since January 1, 2025. Build all four in from day one — retrofitting is expensive.
Selling into Germany? We build German-market-ready sites — compliant, documented, and handed over clean. Request a project estimate or scope it with the quote calculator.
This guide is an operational method for commissioning the work, not legal advice. For legal interpretation, retain qualified German counsel.
What Actually Changes When You Build for Germany?
The visible design barely changes; the compliance and evidence layer changes almost entirely. A German-facing site carries statutory disclosure (the Impressum), a stricter consent standard than a simple cookie bar, a phased e-invoicing obligation for business customers, and — since mid-2025 — an accessibility documentation expectation that treats accessibility and performance as things you prove rather than claim.
International agencies miss these because none of them are visible in a design mockup. A site can look finished, load fast, and still be non-compliant on launch day: the Impressum is thin, the consent banner fires tags before anyone clicks, the invoices are plain PDFs, and there is no evidence file at all. Picture a Frankfurt services firm signing off a polished build from an overseas studio, then reaching internal review: legal flags a missing Handelsregister entry, the data-protection officer rejects analytics that fired before consent, and finance asks for a ZUGFeRD sample nobody planned for. Each is a separate change order, discovered at the most expensive moment.
What follows is the field-tested method to avoid that — and what to demand from any web development company Germany buyers shortlist. For multi-market builds, our multilingual website architecture guide covers the structural side, and our USA web design services page shows how we scope international projects.
How Do You Build a Compliant Impressum?
Germany requires a reachable legal notice — the Impressum, or Anbieterkennzeichnung under §5 of the Digitale-Dienste-Gesetz (DDG) — on commercial websites, typically within one or two clicks of every page. Whether and exactly how it applies to your entity is a question for counsel, but the content a web team reliably needs to prepare is stable. Build the page to hold:
- Full legal name of the operator and its legal form (e.g., GmbH, UG, AG)
- A physical postal address — not a P.O. box alone
- A fast contact route: email plus telephone, or an equivalent electronic form
- Commercial register (Handelsregister) court and registration number, where the entity is registered
- VAT identification number (USt-IdNr.) where applicable
- The responsible person for editorial content (§18 MStV), where applicable
- Professional regulatory details for regulated professions (chamber, professional title, applicable regulations)
Three build details agencies get wrong: the Impressum must be reachable without a scavenger hunt (footer link on every page is the safe pattern); it must reflect the actual contracting entity, not the agency that built the site; and it must be maintained — a stale address or deregistered number is worse than a thin page because it looks deliberate. Put Impressum updates into your content-maintenance workflow from day one. Translating counsel's requirements into build scope is a technical job — our web development consulting service does exactly that — and choosing the right development company matters more than usual when legal pages are load-bearing. Our website handover ownership checklist covers the account and documentation transfers that keep legal pages accurate after launch.
What Does DSGVO-Compliant Consent Actually Require?
A cookie banner alone is not compliance. Under the DSGVO (GDPR) together with §25 of the Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz (TDDDG), storing or accessing information on a visitor's device — which covers cookies, pixels, and most analytics and marketing tags — generally needs prior consent, with narrow exceptions for what is strictly necessary.
The six-step implementation we use on German builds:
- Inventory every tag. Analytics, ads, heatmaps, fonts, video embeds, chat widgets — if it touches the visitor's device or sends data to a third party, it goes on the list.
- Classify strictly. Mark each as strictly necessary or consent-required. Be honest: marketing analytics is not "necessary."
- Block before consent. Non-essential tags must not fire before the visitor chooses — not even once "to see the default state." This is where most international builds fail.
- Make consent granular and reversible. Freely given, per-purpose choices; withdrawing must be as easy as granting. A single "accept all" button with a hidden decline link fails the test.
- Document everything. Consent receipts with timestamps, plus a current data-processing register and an AVV (data-processing agreement under Art. 28 DSGVO) signed with every processor that touches personal data.
- Keep it maintained. Every new tag re-enters the process. Consent management is a workflow, not a launch task.
The cost asymmetry is stark: a proper consent implementation is a few days of planned work during the build; retrofitting it means auditing every template, rebuilding the tag layer, and re-validating analytics continuity. For the broader privacy-and-SEO picture, see SEO-friendly web development and our technical SEO audit service.
What Are Germany's B2B E-Invoicing Deadlines?
This is the requirement that surprises international buyers most, because it lives in finance rather than marketing. Under the Wachstumschancengesetz (Growth Opportunities Act), Germany is phasing in mandatory structured e-invoicing for domestic B2B transactions:
| Date | Obligation |
|---|---|
| January 1, 2025 | Every German business must be able to receive structured e-invoices (XRechnung, ZUGFeRD 2.x, or Peppol BIS) meeting the European standard EN 16931 |
| January 1, 2027 | Businesses with prior-year turnover above €800,000 must also issue structured e-invoices for domestic B2B |
| January 1, 2028 | All businesses must issue structured e-invoices; plain PDFs no longer qualify |
Two facts matter for your web project. First, there has been no postponement — as of late 2026 the dates stand, despite industry pressure (AVASK's September 2026 status update). Second, Germany has no central clearance platform for B2B: transmission is decentralized (email, Peppol, portals), which means your invoicing pipeline, data model, and archive design are your responsibility.
Building ZUGFeRD or XRechnung output in from day one costs a few planning days: the invoice template, the data model, and the export pipeline are designed structured-first, then validated. Retrofitting it into a PDF-only portal later means reworking all three and re-validating against past documents — and e-invoices must be archived in structured form for the full statutory retention period. If your site issues invoices to German business customers, scope this with custom web application development from the start, and compare delivery models via fixed-price vs retainer vs time-and-materials.
What Does the BFSG Require for Websites?
Since June 28, 2025, the Barrierefreiheitsstärkungsgesetz (BFSG) — Germany's transposition of the European Accessibility Act — requires companies offering products and services online to German consumers to make their digital touchpoints accessible. The technical reference is EN 301 549, which points to WCAG 2.2 AA for web content. Fines can reach €100,000 per violation, and market-surveillance authorities can investigate consumer complaints and order measures up to deactivating the offering.
Germany enforces this differently than most EU states: through competition law, not just regulators. Within weeks of the law taking effect, private law firms began sending e-commerce operators warning letters (Abmahnungen) treating BFSG violations as unfair-competition claims — German business law firm Heuking documented the first wave, noting the letters allege violations in blanket terms backed by little more than a screenshot. For an international agency's client, receiving a German legal letter six weeks after launch is a terrible way to learn about accessibility.
Micro-enterprises (fewer than 10 employees and under €2 million annual turnover) are exempt, but must be able to show why implementation would be disproportionate — an evidence burden, not a free pass.
The practical build standard: semantic HTML, full keyboard operability, visible focus states, sufficient contrast, alt text that actually describes images, captions on video, accessible forms with real labels, and accessible PDFs for downloads. Then document it — the accessibility statement and test evidence are what procurement teams and authorities actually read. Our European Accessibility Act website compliance guide goes deeper, and the EAA readiness guide covers preparation steps.
Who Should Own What? (Domains, Hosting, Accounts)
Ownership mistakes are the quietest way German projects go wrong. Keep the .de domain registrant record (administered by DENIC, which manages more than 17 million .de domains) and the hosting accounts in your own company name — not your agency's. Sign an AVV under Art. 28 DSGVO with every processor that touches personal data: hosting, analytics, CRM, email, CDN. And assemble the evidence pack your procurement team will read before signing: Impressum, privacy notice, consent documentation, accessibility statement with test results, e-invoicing capability confirmation, and a register of processors with signed AVVs. When a German buyer can hand that pack to legal, the DPO, and finance in one meeting, deals close faster. We make ownership a contractual line item on every build — it's part of our web development consulting scoping — and every transfer is verified against the website handover ownership checklist.
How Do You Choose a Web Development Company for Germany?
Shortlist on evidence, not promises:
- Ask for a German launch checklist. A serious vendor produces one unprompted: Impressum, consent implementation, e-invoicing, BFSG evidence, AVVs, DENIC ownership. If they look surprised by any item, move on.
- Ask how consent is implemented technically. You want "tags blocked until granular consent" — not "we install a banner plugin."
- Ask for the e-invoicing plan in writing. Format choice (XRechnung vs ZUGFeRD), validation method, archive design, and which deadline applies to you.
- Demand the evidence pack as a deliverable. Accessibility statement, test results, processor register — listed in the contract, delivered at handover.
- Fix dates and demos. Calendar dates in week one, weekly client demos, and Core Web Vitals targets at launch.
Our how to choose a web development company guide covers the general vetting process, offshore vs agency vs boutique helps pick the engagement model, and web development consulting can scope the German requirements before you commit to a build.
Frequently Asked Questions
What is an Impressum and does my website need one?
The Impressum is the statutory legal notice (§5 DDG) German law requires on commercial websites: operator identity, address, contact routes, commercial register details, and VAT ID where applicable. If your site commercially targets Germany, assume you need one and have German counsel confirm the specifics.
Is a cookie banner enough for DSGVO compliance?
No. Consent must be freely given, granular per purpose, and as easy to withdraw as to grant — and non-essential tags must not fire before the visitor consents. A banner that loads analytics first and asks later is the single most common failure we see in international builds.
When does B2B e-invoicing become mandatory in Germany?
Receiving structured e-invoices has been mandatory for all German businesses since January 1, 2025. Issuing becomes mandatory on January 1, 2027 for businesses with prior-year turnover above €800,000, and on January 1, 2028 for everyone else. Accepted formats are XRechnung and ZUGFeRD (EN 16931); plain PDFs no longer qualify.
What is the BFSG and who does it apply to?
The Barrierefreiheitsstärkungsgesetz is Germany's implementation of the European Accessibility Act, in force since June 28, 2025. It requires businesses selling products or services online to German consumers to meet accessibility requirements (WCAG 2.2 AA via EN 301 549). Fines reach €100,000, and violations are pursued through competition-law warning letters as well as regulators.
Can a US or Dubai agency build a compliant German website?
Yes — if they treat the four pillars (Impressum, DSGVO consent, e-invoicing, BFSG evidence) as core scope, not post-launch fixes. Vet them on the specifics: ask for their German launch checklist, their technical consent implementation, and a sample evidence pack before you sign.
How much does a German-market-ready website cost?
A compliant small-business site typically starts around $8,000–$15,000; e-commerce with BFSG-grade accessibility and e-invoicing integration runs $20,000–$60,000+; custom B2B platforms with structured invoicing pipelines start higher. The compliance layer itself is a few thousand dollars when planned in — and multiples of that as a retrofit.
Selling into Germany without the rebuild? Tell us about your project — we'll scope the Impressum, consent, e-invoicing, and accessibility requirements into a fixed quote from day one, or start with the quote calculator.
