Skip to content
E-commerce

Germanized for WooCommerce: full DACH compliance in 2026

Maciej Rostocki 12 min read Updated 2026-05-12
Germanized for WooCommerce: full DACH compliance in 2026

Selling to Germany, Austria, or Switzerland from a Polish WooCommerce store requires 14 legal elements that WooCommerce in its default configuration does not deliver. Missing are unit prices (PAngV), full GoBD-compliant invoice numbering, a legally accurate Lieferzeit field, separate B2B handling with VAT ID validation, Double Opt-In for the newsletter, a Versandkostenrechner before checkout, and product warnings for cosmetics and food. Germanized for WooCommerce closes that gap in a way recognized by German law firms (Vendidero holds Trusted Shops certification and IT-Recht Kanzlei audits since 2014). In this article we describe concretely: what Germanized adds, when Free is enough versus Pro or Premium, a 12-point checklist for launching a German shop, and the most common gotchas (Polylang × Germanized, GoBD numbering, Kleinunternehmerregelung).

What Germanized adds to WooCommerce by legal definition

German commercial law (HGB), consumer protection law (BGB §312 and onwards), Preisangabenverordnung (PAngV since 2022), product labeling regulations, and GoBD requirements for bookkeeping and archiving electronic documents form a set of roughly 30 specific technical requirements for an e-commerce shop selling to DE. WooCommerce by design is built for UK and US law. Germanized for WooCommerce adds 14 modules filling this gap.

First group: pricing and price display. PAngV (Preisangabenverordnung) requires displaying a unit price (Grundpreis) for every product sold by weight, volume, or length. Concretely: a 500 ml bottle of olive oil at 12 EUR must show “24 EUR/litre” on the product list, in the cart, and on the invoice. Germanized does this automatically once you enter the unit (g/kg/ml/l/cm/m) and the reference quantity in product attributes.

Second group: order documentation. Germanized automatically generates four PDF documents per order: order confirmation (Bestellbestätigung), invoice (Rechnung), credit note for returns (Stornorechnung or Gutschrift), and Widerrufsbelehrung (notice of the right of withdrawal). Each document contains the mandatory fields: a GoBD-compliant sequential invoice number (not reset annually), date of issue, date of delivery, full seller address with NIP/USt-IdNr, line items with VAT broken down per category.

Third group: returns handling. A German consumer has 14 days to return without giving a reason. Germanized adds a “Return product” button in the customer panel, generates a PDF return form, calculates deadlines in line with the Widerrufsbelehrung, and automatically notifies the seller of any return request. Without Germanized the shop owner has to handle returns manually with the risk of faulty documentation in case of an audit.

Fourth group: B2B vs B2C separation. Germanized distinguishes user roles and displays net or gross prices according to context. For a B2B customer with a valid VAT ID (validated real-time via the VIES API) the shop shows net prices plus VAT 0% (reverse charge for EU intra-community trade). For a B2C customer always gross. Without Germanized this logic must be written by hand in the child theme: about 300 lines of code plus tests.

Free vs Pro vs Premium: which one is enough when

Germanized comes in three licensing tiers. Free is available in the WordPress repository, Pro is 79 EUR/year, Premium is 199 EUR/year. The difference is not cosmetic and the choice has real consequences for the work of the shop administrator.

Free is enough for a B2C shop with 5-30 SKUs, no VAT ID validation, no automatic DHL/DPD handling, no professional PDF invoices (Free generates plain HTML invoice with simple CSS, no logo, no custom layout). A practical example: a small cosmetics producer selling 12 SKUs to PL and DE, averaging 80 orders/month, uses Free and manually processes 1-2 returns per month.

Pro at 79 EUR/year adds: real-time VAT ID validation via VIES (cuts B2B processing time from 24h manual checks to 2 seconds automatic), professional PDF invoices with logo and custom layout (Maciej has customized this for 6 portfolio clients to match company branding), proforma invoices before payment (typical for B2B Vorkasse), automatic invoice emailing tied to order status, multi-tax classes per category (for example books 7%, cosmetics 19%, food 7% in a single shop), Lieferzeit synchronized with stock, Trusted Shops auto-feed for reviews.

Premium at 199 EUR/year adds on top: shipping integrations with DHL Versandlabel, DPD, and Hermes API (generating labels directly in the order panel, automatic tracking number sent to the customer), multi-warehouse with separate Lieferzeit per location, GoBD-zertifizierte archiving (ZIP export with metadata for the tax office in case of audit), e-Rechnung XRechnung format for B2G orders (public sector from 2025).

Hanse Studio recommendation: Free for a first MVP up to 50 orders per month, Pro for 50-1000 orders/mo or any B2B, Premium for 1000+ orders/mo, multi-warehouse, or public sector orders.

12-point checklist for launching a German shop

A concrete list of requirements to tick off before Go-Live of a shop selling to DE. Each item maps to compliance with a specific article of law.

  1. AGB (Allgemeine Geschäftsbedingungen): general terms of sale, required by §305 BGB. Do not draft them yourself: subscribe with a law firm (IT-Recht Kanzlei 9.90 EUR/mo or Trusted Shops Legal Package 24 EUR/mo subscription with updates on law changes).
  2. Datenschutzerklärung: DSGVO privacy policy, required by GDPR art. 13. Same acquisition path as AGB.
  3. Impressum: full seller data, required by §5 TMG. Complete company name, address, NIP/USt-IdNr, KRS/HRB, authorized person, email plus phone.
  4. Widerrufsbelehrung: notice of the right of withdrawal 14 days, required by §312g BGB plus EU CRD. Germanized generates automatically with the return-address field.
  5. PAngV unit price: price per unit of measure, required by §4 PAngV from 2022. Germanized turns this on once a reference unit and weight are entered per product.
  6. Versandkostenrechner: shipping cost calculation before checkout, required by §6 PAngV. WooCommerce has it natively, Germanized adds “ab 4,90 EUR” next to every product.
  7. Lieferzeit per product: delivery time, required by §312j BGB. Germanized synchronizes with stock (“Sofort lieferbar” when stock > 0, “Versand in 3-5 Tagen” on backorder).
  8. Double Opt-In newsletter: double subscription confirmation, required by §7 UWG. Mailpoet with Germanized or Brevo natively handles this.
  9. GoBD-compliant Rechnungsnummer: sequential invoice numbering, not reset yearly, 10-year archiving. Germanized sets the year-prefixed sequence format.
  10. VAT ID validation: USt-IdNr validation through VIES API for B2B reverse charge. Germanized Pro handles natively, adds VAT ID field in checkout for user role “wholesale”.
  11. Cookie consent: DSGVO consent, separate plugin (Complianz or CookieYes). Germanized does not cover this.
  12. Trusted Shops Seal: optional, but a real 30-40% conversion lift in DE. 99-249 EUR/mo, Germanized Pro enables the auto-feed to reviews after order.

The full setup with tests takes 16-24 hours of Hanse Studio work. After deployment the client receives a PDF audit with the 12 points marked and a note describing how each was confirmed.

B2B vs B2C in Germanized: customer separation

DACH shops often serve both consumers (B2C) and businesses (B2B) at the same time. The tax, legal, and UX logic differs significantly. Germanized separates these contexts via user roles and an additional “Type of customer” field in checkout.

A B2B customer with a valid EU VAT ID (validated real-time via VIES) sees net prices without VAT, receives an invoice with reverse charge wording (“Steuerschuldnerschaft des Leistungsempfängers”, art. 196 of the EU VAT Directive), and has no 14-day right of withdrawal (B2B returns are not protected by consumer law). A B2B customer with a domestic VAT ID (DE issuer, DE recipient) sees net prices plus 19% VAT. A B2B customer with a PL issuer and DE recipient without a VAT ID sees gross prices as B2C.

A B2C customer always sees gross prices, the 14-day withdrawal applies, automatic notification of cancellation is sent, and a standard invoice is issued. This kind of separation prevents the main audit errors at the Finanzamt: issuing a VAT invoice for an exempt B2B customer (consequence: corrective invoice plus interest) or omitting the Widerrufsbelehrung for B2C (consequence: administrative fine up to 50,000 EUR).

A complete comparison of B2B versus B2C WooCommerce configuration is described in our article on the B2B vs B2C WooCommerce store.

DACH payments: SEPA, Klarna, Vorkasse, card

The German consumer pays differently than the Polish one. According to the 2024 ECC Köln study: 28% of online transactions in DE are PayPal, 22% Lastschrift (SEPA Direct Debit), 17% credit card, 14% Klarna (invoice or installments), 10% Sofort/Klarna Sofort (fork after the original Sofort was closed in 2023), 9% bank transfer or Vorkasse. BLIK and Apple Pay together account for less than 2% in DE, so investing in those gateways is low priority.

The Hanse Studio configuration for a PL shop selling to DE: Stripe as the primary gateway (it handles card plus Klarna plus Apple/Google Pay in a single integration plugin), Mollie as a secondary gateway for SEPA Direct Debit (Stripe SEPA requires a separate setup, Mollie has it native), Vorkasse added as a manual method (after the order the customer gets an IBAN, the shop sends goods once payment is booked, typical for B2B with 7-30 day terms).

Lastschrift (SEPA Direct Debit) via Mollie requires a separate customer consent inserted in the order content plus IBAN validation. Klarna integrates with Stripe with DE-specific separation (Klarna Pay in 3, Klarna Pay Later 30 days, Klarna Financing for larger amounts). Every Klarna payment in DE requires consent under BGB §13 (information about the consequences of non-repayment); Germanized adds that field automatically.

A detailed comparison of payment gateways is in our article on WooCommerce payments.

DACH shipping: DHL, DPD, Hermes integrations

The German consumer expects delivery in 2-3 working days, with a tracking number, with the option to pick up at a parcel locker (DHL Packstation) or partner point (Hermes ShopShop). Germanized Premium offers ready-made API integrations for the three main carriers: DHL Versandlabel API (5 EUR/mo plus per label), DPD Predict API, Hermes Trackingversand.

Practical workflow: an order comes in, status “processing”, the admin clicks “Versandlabel erzeugen” in the order panel, the system generates a PDF label in A6 format for a Zebra or Brother thermal printer. The tracking number is written back to the order automatically. The customer receives an email with a link to the tracking page (DHL Sendungsverfolgung or DPD Predict). Average handling time drops from 8-12 minutes manually to 30-45 seconds automatically.

The Versandkostenrechner before checkout calculates the cost based on the weight attribute of the product plus the parcel size plus the destination country. DHL Päckchen up to 2 kg domestic 4.99 EUR, Päckchen 2-10 kg 8.49 EUR, Paket 10-31.5 kg 13.99 EUR. A PL shop selling to DE typically uses GLS or DPD Cross-Border, average cost 7-12 EUR per parcel and delivery in 4-6 working days.

Common gotchas and how to avoid them

Practical pitfalls we have seen during DACH client deployments at Hanse Studio. Each one cost someone time or money before we identified it.

Pitfall one: Polylang and Germanized strings conflict. Germanized registers about 800 translated strings (labels, form labels, PDF document content). Polylang does not include them by default, it requires registration in the child theme via the Polylang string registration mechanism. Without that the PL customer sees German labels in checkout, the DE customer sees Polish ones. Solution: a dedicated i18n.php file in the child theme registering 30-50 most important Germanized strings plus manual translations in the Polylang Strings translations panel.

Pitfall two: GoBD invoice numbering yearly reset. WooCommerce by default generates order numbers sequentially, but many accounting plugins reset numbering on January 1. This violates GoBD (numbering must be continuous over the shop’s lifetime). Germanized uses a year-prefixed sequential numbering format but some integrations (for example a Comarch Optima bridge) reset. Solution: lock reset in Germanized Pro settings plus an additional lock in the child theme via a WooCommerce order-number filter.

Pitfall three: VAT 19% vs Kleinunternehmerregelung 0%. A small DE business up to 22,000 EUR annual turnover may opt for Kleinunternehmerregelung (VAT exempt). In that case the invoice must contain the clause “Gemäß §19 UStG wird keine Umsatzsteuer berechnet”. Germanized handles this through an admin panel setting, but the client must activate it. The mistake: activating Kleinunternehmer in a shop that has already crossed 22k EUR turnover triggers retrospective correction of all invoices for the year, plus interest.

Pitfall four: no Widerrufsbelehrung in the order language. A customer from Austria places a German-language order, receives a German Widerrufsbelehrung. A customer from the German-speaking part of Switzerland gets the German version too. But a French-speaking customer from a Swiss French canton expects FR. Germanized has DE and EN, FR requires manual translation. Without an FR version a French-speaking Swiss customer has grounds to claim withdrawal outside the 14-day deadline.

Pitfall five: conflict with EU VAT compliance plugins like WooCommerce EU VAT Number. Germanized has its own VAT ID validation mechanism through VIES. Activating both plugins simultaneously triggers double validation (two API calls per order, checkout delayed by 4-6 seconds) plus field display conflicts (“EU VAT Number” instead of “USt-IdNr”). Solution: disable the WooCommerce EU VAT Number plugin (Germanized Pro fully replaces it). If the shop already used the older plugin, check meta_key migration for existing customers (Germanized uses _billing_vat_id, some older plugins _eu_vat_number).

Pitfall six: ProductSafety verordnung (GPSR) from 13 December 2024. The new EU regulation requires displaying manufacturer data (name, address, email or URL) for every product, plus safety warnings per category (toys, cosmetics, electronics). Germanized Pro added support in version 3.18 (November 2024). Shops live before that date without an upgrade risk an abmahnung from competitors or consumer organizations (Verbraucherzentrale). An audit by our law firm for a DACH client in December 2024 flagged 4 products with missing GPSR data; the fix took 90 minutes after the plugin upgrade.

FAQ

Does Germanized work with every WooCommerce theme?

Yes, but it works best with Astra, GeneratePress, and Storefront (fewer CSS conflicts with the extra checkout fields). For custom themes with special checkout logic (for example one-page checkout from the Cartflows plugin), expect 2-4 hours of tuning to align the spots where Germanized injects fields.

Can I run 3 languages (PL, DE, EN) with Polylang plus Germanized?

Yes, but it requires custom string registration in the child theme i18n.php (around 30-50 most important Germanized strings). Without that the customer sees a mixed-language checkout. Hanse Studio includes this setup by default in the retainer.

What about GDPR/DSGVO with Germanized?

Germanized covers product-level compliance (Lieferzeit, PAngV, prices, invoices) but does not cover cookie consent. Cookie consent requires a separate plugin (Complianz Premium 49 EUR/year or CookieYes Pro 60 EUR/year). Without it the site breaches GDPR art. 6 and risks an abmahnung (administrative fine of 500-2,500 EUR for a first warning).

Is Germanized Premium worth 199 EUR/year?

Yes, when the shop processes more than 1000 orders per month to DE or runs a multi-warehouse with different delivery times per location. Automatic DHL/DPD label generation saves 6-10 minutes per order. At 1000 orders/mo that is 100-167 hours saved per year, paying back the license within the second month.

Conclusions and next step

Selling to DACH from WooCommerce without Germanized is possible, but it costs 200-300 hours of writing custom code in the child theme plus ongoing maintenance of legal changes. Germanized is 79-199 EUR/year and covers regulatory updates on a weekly basis through Vendidero (a company holding Trusted Shops certification and IT-Recht Kanzlei audits).

Hanse Studio deploys Germanized as part of the “WooCommerce DACH” package (from 8,000 PLN setup plus 800 PLN/mo retainer): full configuration of the 12-point checklist, Stripe plus Mollie plus Klarna integration, a custom invoice template with the client’s branding, a PDF audit with compliance items marked. See our DACH e-commerce services or contact us for a quote. The full comparison of WooCommerce to other platforms is in our article on WooCommerce for SMBs in 2026.

§ From the studio

A new article every month, zero spam.

One case study or technical deep-dive. No clickbaits, no „10 reasons". Unsubscribe with one click.

— Related articles
E-commerce

PrestaShop/Shopify to WooCommerce migration: 2026 checklist

2026-01-05 · 9 min read
E-commerce

WooCommerce payments: Przelewy24, Stripe, PayU, 2026 comparison

2025-12-29 · 11 min read
E-commerce

B2B vs B2C WooCommerce store: 8 configuration differences

2025-12-22 · 11 min read
Back to all posts
Scroll to Top