German Warehouse Fulfillment Services: What Growing Brands Should Expect
15.07.2026
Fulfillment Center Bavaria Munich: Why Location Matters for FBA Inbound Speed
15.07.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
A non-EU seller launches on Amazon.de, sets prices, and assumes one VAT rate covers the whole catalogue. Weeks later, Seller Central flags a pricing or invoicing inconsistency, and the seller realizes some SKUs should have carried the reduced 7% rate instead of the standard 19% rate, or that VAT registration should have started before the first German sale, not after. The German standard VAT rate is 19%, applied to most goods and services, while a reduced 7% rate applies to a defined set of categories such as certain food items, books, and a few other goods. Which rate applies, and when a non-EU seller must register at all, depends on product classification, storage location, and sales volume, not on guesswork at listing stage. This article lays out the decision points a seller needs to confirm before invoicing German customers, so the rate charged matches what tax authorities expect and what Amazon's own compliance checks are looking for.
Standard Rate Versus Reduced Rate: Where the Split Actually Falls
The 19% standard rate is the default position in Germany. Unless a product falls into one of the categories eligible for the reduced 7% rate, the seller should assume 19% applies. This matters operationally because Amazon's tax settings at SKU level determine what VAT rate gets calculated and displayed on the invoice, and that setting has to match the actual legal classification of the product, not an assumption carried over from a different marketplace.
Sellers coming from marketplaces with different VAT structures sometimes copy a UK or US tax mapping directly into their German listings. That mismatch is one of the most common sources of incorrect VAT charging. A product correctly zero-rated or reduced-rated elsewhere may sit squarely in the 19% category in Germany, and the reverse can also happen. Getting the rate wrong is not just a compliance issue; it changes the price the customer sees and the margin the seller actually keeps once VAT is remitted. Before going live on Amazon.de, each ASIN's tax code should be checked against current German classification, not carried over from another country's settings.
What Must Be Confirmed Before the First German Sale
A non-EU seller needs three things settled before pricing goes live on Amazon.de: the VAT registration status in Germany, the correct tax classification per product category, and the invoice template configuration inside Seller Central. Registration timing depends on where inventory sits and how sales are structured; storing stock in a German fulfillment centre generally creates a registration obligation from the first unit stored, regardless of sales volume, which is different from the distance-selling threshold logic that applies to cross-border EU sales handled under the One Stop Shop scheme.
This is also where VAT registration services earn their keep, because the registration date, the tax office assignment, and the VAT ID format all need to be correct before the first invoice is issued, not retrofitted afterward.
What Breaks When the Rate or Registration Is Wrong
Charging the wrong rate creates two separate problems. First, the seller may owe a back-payment to the tax authority for undercharged VAT, which comes out of margin that has often already been spent or reinvested. Second, Amazon's own systems can flag pricing or invoicing anomalies during routine account health checks, and a pattern of inconsistent VAT treatment across similar SKUs is a common trigger.
Customers who receive an invoice with an unexpected VAT line, or who query why a competitor's identical product shows a different tax treatment, sometimes escalate to a refund request or an A-to-z claim. That interacts directly with account health metrics, and repeated disputes of this kind can slow down or restrict selling privileges while the account is reviewed.
Registration Timing, Storage Location, and the OSS Question
For a non-EU seller, the trigger for German VAT registration is usually tied to where goods are physically stored, not where the company is incorporated. If inventory sits in a German Amazon fulfillment centre under FBA, that storage generally creates a local VAT obligation from the point stock arrives, separate from any distance-selling rules that apply to shipments sent directly from outside Germany to German customers.
This is where the One Stop Shop (OSS) scheme and local German VAT registration serve different purposes and are often confused. OSS simplifies reporting for cross-border B2C sales within the EU when goods move from one member state to a customer in another, letting a seller file one consolidated return instead of registering in every destination country. It does not, however, replace the need for local VAT registration in a country where the seller physically stores inventory. A seller using FBA with stock in a German FC still needs a German VAT registration for that storage activity, even if OSS is used for other intra-EU distance sales. Confirming which regime applies to which flow of goods, before goods move, is the control point that prevents mismatched invoicing later.
Before listing products on Amazon.de, confirm:
- Each ASIN's tax classification matches current German 7%/19% category rules, not a rate copied from another marketplace.
- German VAT registration is active (or in process) if inventory will be stored in a German fulfillment centre.
- The VAT ID format assigned matches what Amazon's tax settings expect for invoice generation.
- Invoice templates display the legal seller name, VAT ID, and correct rate per line item, not a blended default.
- Someone owns the ongoing review of tax codes as the catalogue grows or changes.
Common points where VAT handling breaks down:
- New SKUs added without a tax classification review, defaulting to whatever rate the account template last used.
- Storage added in a second German fulfillment centre without updating registration or reporting obligations.
- OSS reporting used to cover a sale that actually required local German registration because of FBA storage.
- Invoice disputes from customers who received a different VAT treatment than a competitor selling an identical product.
- Back-payment exposure discovered only during an annual reconciliation rather than caught at listing stage.
Checks that support ongoing VAT compliance services:
- Quarterly review of ASIN tax codes against current German classification guidance.
- Confirmation that registration status is current in every country where stock is physically stored.
- Reconciliation between Amazon's reported VAT collected and what was actually remitted.
- A documented process for handling reduced-rate product additions before they go live.
Ownership questions worth answering before scaling on Amazon.de:
- Who reviews new SKU tax settings before the listing is activated?
- Who monitors registration triggers when storage footprint changes, for example adding a second German FC?
- Who reconciles OSS filings against local German registration obligations so nothing is double-counted or missed?
- Who responds when a customer disputes an invoice's VAT line, and how quickly?
Putting the Rate Decision Into an Operating Routine
Getting the rate right once is not the same as staying right as the catalogue grows. A seller adding new products, moving into Amazon FBA prep services for the first time, or expanding storage into a second German facility needs a repeatable check, not a one-off audit. The practical sequence looks like this: classify the product's tax category before it is listed, confirm registration status matches the storage footprint, set the invoice template to reflect the correct rate per SKU, and review the whole set quarterly rather than only when a problem surfaces.
Sellers already using EU VAT for international sellers frameworks across multiple marketplaces should treat Germany as its own check, not an extension of a French or Italian rate table. The reduced and standard rate categories differ by country, and reverse charge VAT EU mechanics for B2B transactions add another layer that needs separate confirmation from the B2C consumer rate discussed here. None of this replaces a proper tax review; it defines what an operator should confirm is in place before assuming the pricing is correct.
Rate owner
The seller (or their appointed tax advisor) owns product tax classification. Amazon applies the rate configured in Seller Central; it does not independently verify that the classification is legally correct for each product category.
Document checkpoint
German VAT ID, tax office assignment letter, and per-SKU tax classification records should exist before the first Amazon.de invoice is generated, not retrieved after a dispute.
Escalation rule
If a customer disputes a VAT line or Seller Central flags a pricing anomaly, pause new listings in that category until the classification is reconfirmed with a qualified advisor.
What to Confirm Before Assuming the Rate Is Correct
The 19% standard rate covers most of what a non-EU seller lists on Amazon.de, with the 7% reduced rate reserved for a narrower set of categories. The decision that actually protects the account is not which rate number to memorize, but whether registration timing, product classification, and invoice configuration are checked before goods move and reviewed as the catalogue changes. Storage location, not company domicile, usually determines when German registration becomes necessary, and OSS covers a different flow of sales than local FBA storage does.
None of this is a substitute for a qualified tax advisor reviewing the seller's specific product mix and storage footprint. What this article offers is a way to organize the questions before the advisor call, so the seller arrives with the right classification and registration data already gathered rather than discovering gaps after Amazon has already flagged an inconsistency. Getting the operational side lined up, including where inventory physically sits and how invoices are templated, reduces the chance that a correct legal answer arrives too late to prevent a back-payment or a dispute.
Confirming the correct German VAT treatment is a tax question that belongs with a qualified advisor or dedicated VAT registration services provider, and this article does not substitute for that review. Where FLEX. can help is the operational layer around it: making sure inventory location, storage timing, and fulfillment handoffs are documented clearly enough that your tax advisor has accurate data to work from. If you are setting up Amazon FC forwarding in Germany or reviewing storage footprint ahead of a VAT registration decision, FLEX. can walk through the logistics side while your tax obligations are verified separately.
