Entering the German market: an eCommerce checklist

Translating your store into German is the smallest and easiest part of entering that market. The barrier in Germany is operational and formal, not linguistic. Before the first parcel ships, you need packaging registration, a settled VAT position, a compliant Impressum, product data in the shape German channels expect, the payment methods shoppers there actually use, and a plan for returns and support. Here is the checklist, in the order that makes sense to work through it.

Why this is not a translation project

Germany is the default first foreign market for many European sellers: large, well served by carriers, full of people comfortable buying online. That familiarity is exactly the trap. It suggests you can lift what works at home and swap the language, when in practice the market asks different questions of your operations.

Our own rough split, from work on German catalogs and feeds rather than from a formal study: content translation is around 20 percent of the effort. The other 80 sits in compliance, product data, logistics, payments and support. Sequence matters here, because some of these items block selling entirely while others only cost you conversion.

Compliance: a checklist where every line has an owner

This section is not a legal briefing. Treat it as a list where each item gets a named owner and a date. What applies to you depends on what you sell and to whom, so confirm the final list with an adviser.

Packaging: register in LUCID before your first shipment

The German Packaging Act (VerpackG) covers anyone shipping packaged goods into the country, including companies based abroad. Registration in the LUCID register has to happen before the packaging is placed on the market ("vor dem Inverkehrbringen", § 9 VerpackG), and producers who are not properly registered are prohibited from placing packaging on the market at all.

Two obligations sit alongside registration and are easy to miss. The first is a system participation agreement (Systembeteiligung) for packaging that ends up with private consumers, which in practice means every shipping box. The second is regular volume reporting, both to the system operator and to LUCID. Marketplaces must verify that sellers have done this, and may not let goods from unregistered companies be sold on their platforms.

Check the EU calendar too. Regulation (EU) 2025/40 on packaging replaces the previous directive and starts to apply on 12 August 2026, with some requirements phased in later. If you are launching in Germany this year, review it with an adviser rather than relying on guides written two years ago.

Electricals and batteries: ElektroG and a German representative

Selling electrical or electronic equipment adds ElektroG and registration with stiftung ear. A company without an establishment in Germany cannot register itself: it has to mandate an authorised representative (Bevollmächtigter) based in Germany, who takes over the producer obligations. Equipment may only be placed on the market once registration has been granted. Batteries fall under a separate regime (BattG) handled by the same authority.

VAT: the EU threshold and the One Stop Shop

Distance sales to consumers in the EU are governed by a single EUR 10 000 annual threshold. Below it, VAT may be accounted for in the country where the seller is established. Above it, VAT is due in the customer country, and instead of registering separately in each member state you can file through the One Stop Shop in one country of identification.

Two points cause most of the confusion. First, the threshold covers your sales to all EU countries combined, not just Germany. Second, OSS does not cover every situation: if you hold stock in a German warehouse, your own or a fulfilment provider, the VAT picture changes and needs to be worked through with a tax adviser before launch, not after the first quarter.

The Impressum and consumer information

§ 5 DDG (Digitale-Dienste-Gesetz) requires service providers to keep certain information permanently available and easy to find: the name and address of establishment, details enabling fast electronic contact, the commercial register entry and number, the VAT identification number where one exists, and the supervisory authority for regulated activities. It is one page, and it is the first thing anyone auditing your store will open.

Consumer information duties sit on top of that: the right of withdrawal and how you communicate it, the full price including delivery costs, seller details visible at the point of purchase. The GPSR (Regulation (EU) 2023/988) also requires safety information and an EU responsible person on product pages, which matters most for sellers established outside the EU. Deadlines and exemptions vary by product category, so do not copy terms from another market.

The same list in one place, including the column most plans leave out, namely who owns each item:

As of 4 August 2026. Indicative only; scope depends on your assortment and selling model.

What German shoppers expect

Compliance decides whether you are allowed to sell. Expectations decide whether anyone buys. The first difference shows up at the checkout, because the payment mix in Germany is rarely the one a cross-border seller arrives with.

The EHI Retail Institute Online-Payment study (2024 data, published in May 2025, 153 retail companies) reports these shares of revenue in German online retail:

• PayPal: 28.5% of revenue, the largest single method.
• Buy on invoice (Kauf auf Rechnung): 25.8%, paying after the goods arrive, still the number two method.
• Direct debit (Lastschrift): 17.3%.
• Credit and international debit cards: 12.3%.

The practical conclusion is uncomfortable for a store built around cards alone: without PayPal and without paying after delivery, you are shutting out a large share of the market. Buy on invoice is normally implemented through a provider that takes on the credit risk, which makes it a margin and integration decision rather than a plugin choice.

Beyond payments, three expectations come up again and again in this market:

• Complete product data: dimensions, material, mounting, what is in the box. A shopper who cannot find a spec does not send a question, they close the tab.
• Predictable delivery and returns: a concrete date rather than a "3 to 8 days" range, and a returns procedure written out plainly.
• Support in German: answers in the customer language, complaints included. English is often tolerated, but it weakens trust in a store nobody has heard of yet.

Product data: where market entry is won or lost

This is where entry plans usually come apart. A catalog that was good enough at home turns out to be incomplete in Germany, because the sales channels there are far stricter about data structure than about copywriting.

Required attributes are set per category

There is no single field set for the whole catalog. The category decides which attributes are mandatory, and the same field can accept different values in different category templates. Curtains and construction hardware are filled in differently even when both rows come out of the same product database. That is why mapping is done per category, not once per export.

Units, formats and controlled vocabularies

The second layer is formatting. Channels rarely accept free text where a list exists, and those lists can be surprisingly narrow:

• Units: some categories accept exactly one unit of length, so an abbreviation instead of the required German term gets the row rejected.
• Controlled values: colours and countries of origin come from a closed German list, so your own shade names have to be mapped onto it.
• Encoding: non-ASCII characters in technical fields can turn into question marks when exported to the file format a channel requires.
• Variants: every variant needs a unique combination of attributes, otherwise the channel reads two records as a duplicate and drops one.

Translation is not localisation

Localisation covers everything a customer sees: the title, the description and the bullets, but also colour, size and material names. On top of that comes content policy: several channels reject descriptions containing promotional language, URLs or certificate claims without proof, so marketing copy translated word for word simply will not pass. We run this as a service under AI catalog translations, with native review built into the workflow.

Rejections come from missing data, not from price

Sellers whose listings will not go live usually suspect price or competition first. The real list is more mundane: an empty required field, a unit outside the vocabulary, an incomplete attribute group, a variant missing part of its theme. These errors cascade, because one broken parent record can take down every variant beneath it. How to catch them before you upload is covered in our piece on building marketplace feeds with Claude Code.

Logistics and returns: delivery time sells, a return is a process

Delivery time is not only an operating cost, it is part of conversion. Your offer is compared against a store shipping from inside Germany, and the gap between "tomorrow" and "in four days" weighs more in the basket than a few euros of price difference. That makes the choice of local stock or a faster carrier service a commercial decision, not just a logistics one.

Returns deserve to be designed as a process rather than handled as an exception over email:

• Return address: sending goods back across a border reads as risk to the customer and stretches the cycle. A local address or a consolidation service changes that perception.
• Instructions and label: in German, in the parcel or in the account, without anyone having to contact support.
• Timelines and status: customers should know when the return arrived and when the refund went out. Silence at this stage generates most of the inbound messages.
• Measurement: return rate per category and the most common reasons. That data improves product pages, it is not just a warehouse cost.

Support changes shape too, because a second market roughly doubles the volume of "where is my order" questions, in another language and against different expectations. Much of that traffic can be handled automatically when order and carrier status is available to a system rather than only to a person in an admin panel. We cover that under AI customer service.

What a second market demands from the platform itself

A second market is not a language toggle in the admin. It is usually the moment you discover where your current store stops:

• Prices and taxes per market: separate price lists, the correct rate and price presentation that matches local convention.
• Content per market, not just per language: different assortments, different banners, different delivery information.
• Separate URLs and hreflang: language versions must be distinguishable for search engines and AI systems, not swapped by a script on the same address.
• Currencies and formats: numbers, units, addresses and invoice data.
• Feeds per channel and per market: one source catalog, many outputs, each with its own validation.

If any of those points needs a workaround, the second market will cost more manual work than it returns in revenue. A good test: can product data go out to the storefront and to the channels at the same time, without retyping? A sound structured data layer and a tidy catalog are what make that possible. How we set it up at platform level is described separately, and the operational context is collected in our guide to AI for ecommerce.

Sequence: what comes first and what can wait

The most important part is the order of work. The sequence below follows one principle: first whatever blocks selling outright, then whatever costs conversion, and last whatever can be improved while live.

• 1. Blocking compliance: packaging registration, ElektroG where relevant, VAT and OSS, the Impressum. Without these the rest of the work is unusable.
• 2. Product data: a clean source catalog, attributes per category, units and vocabularies. This takes longest and is underestimated most often.
• 3. Payments and delivery: the methods the market expects and an honest delivery date.
• 4. Returns and support: a returns process and German-language replies, before the first campaign runs.
• 5. Content and visibility: localised descriptions, language versions, marketing content. Important, but the least blocking.

At Seedlight we start these projects with a Blueprint, a review of data, processes and the platform, before anyone writes code for a second language version. The heaviest work almost always turns up where nobody planned for it, which is the catalog. If your first step into Germany is a marketplace rather than your own store, our sister agency covers that angle in their piece on selling on Amazon Germany. The packaging and tax obligations are identical either way.