Germanized hosting where the checkout is a legal document.
German consumer law prescribes what a store must show, when, and in what order. Most of those requirements land on pages a cache would rather serve to everybody.
The wording is regulated.
This is not data protection - it is consumer and price-indication law, and it changes what the page has to say.
Price displays that vary by customer
Whether tax is included, and what the base price per unit is, depends on who is buying and where they are. A cached page showing one of those answers to the wrong customer is a legal problem.
Withdrawal terms delivered, not just linked
The right-of-withdrawal notice has to reach the buyer with the order confirmation. That is an email with an attachment that must actually arrive, not a page they might visit.
Invoices kept for a decade
German retention obligations run to years, and the documents must be producible. That is a backup and archive requirement rather than a plugin setting.
Order confirmations with the required content
Confirmation emails carry prescribed information. Generating them reliably matters more than generating them quickly, so sends are recorded.
The order button says the right thing
The label on the final button is prescribed. It is content, and it must not be replaced by a theme or a caching layer serving an older page.
Cached pages that quote the wrong terms.
The risk on a German store is not a slow checkout. It is a cached page presenting a price basis or a term that does not apply to the customer reading it.
- Price presentation keyed to the customer's context
- Withdrawal documents delivered with confirmation
- Invoices archived for the retention period
- Prescribed labels protected from stale caching
Fast, and legally the right page.
Everything here is a caching-correctness problem dressed as a compliance one. The page can be instant as long as it is the page that customer must be shown.
What we change for German stores
Each row is a place where consumer law and full-page caching disagree about whether one response can serve everybody.
| Setting | What we do | Why |
|---|---|---|
| Price presentation | Cache keyed to the customer's tax and unit-price context | Whether tax is shown as included and what the base unit price is depend on the buyer, so a single cached figure is wrong for some of them by definition. |
| Withdrawal documents | Attached to confirmation and delivery confirmed | The notice has to reach the buyer rather than exist on a page, so a mail failure is a legal gap and not a missing email. |
| Invoice archive | Retained for the statutory period and producible | German retention runs for years and the documents must be reproducible on request, which is an archive question rather than a store feature. |
| Prescribed labels | Protected from being served from an older cached page | The order button wording is specified, so a stale cached response can present a label that no longer complies. |
| Confirmation logging | Sends recorded with their outcome | A confirmation that silently failed leaves no evidence the required information was ever provided to the customer. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why can't German price displays be fully cached?
Is linking to the withdrawal terms enough?
How long do invoices need to be kept?
Does this replace GDPR compliance?
Show every customer the right page.
Move the store across. Migration is free, compliance settings reviewed.