Customs Clearance for Ecommerce Imports into Germany: What Every Non-EU Seller Must Know
04.06.2026
Building a German Delivery Promise: How Carrier Mix Shapes What You Can Guarantee
05.06.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.
Most established Amazon EU sellers reach a point where FBA stops being a cost-efficient default and starts becoming a structural liability. The trigger is rarely one thing. It is the combination: inbound placement fees applied to every shipment, storage limits that cut available capacity during Q4, and per-unit fulfilment costs that compound as average order value stays flat. At that point, the question is not whether FBA is useful — it clearly is — but whether it should be the only fulfilment layer in a pan-European network.
The operational problem is that most sellers lack a structured framework for deciding which channels and markets to serve via FBA and which to route through a 3PL. Without that framework, the default is to keep everything in FBA because it is familiar, and to absorb the cost overrun as a margin leak that never gets formally diagnosed.
This article gives you a working decision model. It covers the FBA cost structure as it stands today, the 3PL cost structure as a realistic alternative, the channel and market logic for choosing between them, and the hybrid network architecture that most scaling sellers eventually need. If you are selling across Germany, France, Spain, and Italy and running everything through Amazon Pan-EU FBA, the framework here will help you identify which handoff to fix first.
How the FBA Cost Structure Works Against You at Scale
FBA pricing has several layers that are easy to underestimate when you are small and painful to ignore when you are scaling. The base fulfilment fee covers pick, pack, and last-mile delivery. On top of that, you pay monthly storage fees that increase significantly in Q4, aged inventory surcharges when stock sits beyond a threshold, and — increasingly — inbound placement fees that apply when Amazon decides your shipment needs to be split across multiple fulfilment centres rather than sent to a single FC of your choice.
The inbound placement fee is the most structurally disruptive change in recent FBA history. It means that even a well-prepared shipment, with correct FNSKU labels, compliant carton dimensions, and accurate packing lists, can attract an additional per-unit charge simply because Amazon's inventory placement algorithm routes it to a distant FC. Sellers who previously sent consolidated pallets to a single German FC now face split inbound plans with fees attached to each leg.
The consequence for pan-European sellers is a cost structure that is no longer predictable at the SKU level. When you cannot model your landed cost per unit with confidence, you cannot price accurately, and you cannot compare FBA against 3PL fulfilment on a like-for-like basis. The first step in any network review is to build a per-SKU cost-to-serve model that includes all FBA fees — not just the headline fulfilment rate — and then compare that against what a 3PL fulfilment operation in Germany or another anchor market would actually cost per shipped order.
- Inbound placement fees: apply when Amazon splits your inbound plan across multiple FCs
- Aged inventory surcharges: triggered when units exceed storage thresholds without selling
- Q4 storage multipliers: monthly storage rates increase sharply from October through December
- Removal fees: charged when you need to recover or dispose of stranded inventory
The FBA Model: What You Control and What You Do Not
FBA gives you access to Prime badge, Amazon's last-mile carrier network, and customer trust built into the marketplace. For high-velocity SKUs on Amazon.de, Amazon.fr, or Amazon.es, that access has real commercial value. The Prime conversion premium is not trivial, and Amazon's delivery promise in Germany — often next-day for Prime members — is difficult to replicate independently.
What FBA does not give you is inventory control. Once your stock enters an Amazon FC, Amazon decides where it goes, how it is stored, and when it is moved between FCs under the Pan-EU FBA program. If you enrol in Pan-EU, Amazon can redistribute your inventory across its European FC network — which reduces your per-country storage cost but means your units may be in Spain when demand spikes in Germany.
The control trade-off matters most for sellers with seasonal SKUs, slow-moving lines, or products that require specific handling. For those SKUs, the lack of visibility into FC location, combined with the cost of removal orders when stock becomes stranded or aged, can erode the margin advantage that FBA's fulfilment fee appeared to offer. Sellers running omnichannel fulfilment — serving both Amazon and their own DTC channel — face an additional constraint: FBA inventory cannot be used to fulfil non-Amazon orders without a separate Multi-Channel Fulfilment arrangement, which carries its own fee structure.
The 3PL Model: What You Gain and What It Costs
A 3PL fulfilment operation gives you inventory ownership at every stage. Your stock sits in a warehouse you have contracted, you can see it, you can redirect it, and you can use it to fulfil orders from any channel — Amazon via FBM or Seller Fulfilled Prime, your own Shopify or WooCommerce store, B2B wholesale orders, or marketplace channels outside Amazon. That flexibility has a real cost, but it also has a real value that FBA-only sellers systematically undercount.
The 3PL cost structure typically includes inbound handling, storage per pallet or cubic metre per week, pick and pack per order, outbound carrier cost, and returns handling. Unlike FBA, these costs are visible line items in a contract. You can model them per SKU, per channel, and per market. When you run that model against your FBA cost-to-serve for the same SKU, the comparison is often closer than sellers expect — particularly for slow-moving lines, bulky products, or orders that would attract FBA's higher-tier fulfilment fees.
The practical constraint with 3PL is carrier integration and SLA management. FBA's delivery promise is built on Amazon's carrier contracts. A 3PL serving German customers needs DHL, DPD, or equivalent carrier integrations with competitive transit times. Pre-Amazon storage in Germany, positioned close to Amazon's FC network, can also serve as a buffer for FBA inbound — holding stock before it enters the FC, smoothing placement fees, and giving you a recovery point if Amazon rejects a shipment.
Choosing Between FBA and 3PL: The Channel and Market Decision
The most useful framework is not FBA versus 3PL as a binary choice. It is a channel-by-channel and market-by-market routing decision. For each SKU and each sales channel, you are asking: where does this unit need to be, who controls it, and what does it cost to get it to the customer from that position?
A practical routing logic looks like this. High-velocity Amazon SKUs with strong Prime conversion belong in FBA — the placement fee is offset by the conversion premium and the delivery promise. Slow-moving SKUs, bulky items, and products with high return rates are candidates for 3PL fulfilment via FBM or SFP, where you control the storage cost and the returns handling. DTC and B2B orders should almost always route through a 3PL, because FBA's Multi-Channel Fulfilment fees are rarely competitive against a direct 3PL pick-and-pack rate for non-Amazon orders.
Germany is the natural anchor market for this hybrid architecture. It is the largest e-commerce market in the DACH region, Amazon.de is the highest-volume Amazon marketplace in continental Europe, and the German FC network is dense enough that a 3PL fulfilment operation near Frankfurt, Leipzig, or the Rhine-Ruhr corridor can serve both Amazon inbound and DTC last-mile from a single inventory position. B2C and B2B fulfilment in Germany from a single 3PL location is operationally achievable and cost-efficient at moderate volumes.
Building a Hybrid FBA Plus 3PL Network: The Architecture That Works
A hybrid network does not mean splitting your inventory randomly between FBA and a 3PL. It means designing a deliberate routing logic where each fulfilment layer handles the order types and SKU profiles it is best suited for, and where the two layers share a common inventory visibility layer so you are not managing two separate stock pools blind.
The architecture that works for most scaling sellers in the DACH and pan-European context looks like this. A 3PL warehouse in Germany holds your master inventory buffer. From that buffer, FBA inbound shipments are prepared and dispatched to Amazon FCs on a rolling schedule — this is where Amazon FC forwarding in Germany adds value, because the 3PL can manage the inbound plan, apply FNSKU labels, build compliant cartons, and book the FC appointment without the seller needing to manage each step. Simultaneously, the same 3PL warehouse fulfils DTC and B2B orders directly, using DHL or DPD for German and DACH delivery.
For other European markets — France, Spain, Italy — the decision depends on volume. At lower volumes, Pan-EU FBA redistribution handles those markets adequately, even with the placement fee overhead. At higher volumes, a secondary 3PL node in France or Spain may be justified, particularly if you are running a significant DTC channel in those markets or if your return rate on Amazon.fr or Amazon.es is high enough to make FBA returns handling expensive.
The critical control point in this architecture is the inventory split decision. You need a rule — ideally automated through your OMS or ERP — that determines which units go to FBA and which stay in the 3PL buffer. That rule should be based on sell-through velocity, channel mix, and the per-unit cost-to-serve comparison you built in the first step. Without that rule, the hybrid network drifts back toward FBA-heavy allocation by default, and the cost savings from the 3PL layer never materialise.
- Set a velocity threshold: SKUs above the threshold go to FBA; below it stay in 3PL
- Review the split quarterly — velocity changes with seasonality and promotions
- Track FBA placement fees per SKU to catch cost creep before it compounds
- Use the 3PL buffer as a returns recovery point for FBA removal orders
When Germany Is the Right 3PL Anchor Market
Germany earns its position as the anchor market in a pan-European hybrid network for several operational reasons, not just because it is the largest market. Amazon's German FC network — with major nodes at sites including Bad Hersfeld, Rheinberg, and Leipzig — means that a 3PL positioned in central Germany can reach multiple FCs within a single transit day. That proximity reduces the risk of inbound appointment delays and gives you a practical buffer if Amazon rejects a shipment at the FC gate.
German carrier infrastructure is also the most developed in continental Europe for e-commerce. DHL's domestic network, DPD's B2B coverage, and the density of Packstation locations mean that a 3PL fulfilment operation in Germany can offer competitive delivery promises to German consumers without relying on Amazon's last-mile. For sellers running Seller Fulfilled Prime on Amazon.de, that carrier access is a prerequisite — SFP requires next-day or same-day delivery to Prime customers, which is only achievable with the right carrier contract and cut-off discipline.
From a B2B and omnichannel perspective, Germany is also where most DACH wholesale and retail distribution flows originate. A 3PL fulfilment partner in Germany that handles both B2C and B2B fulfilment gives you a single inventory position for all DACH demand, reducing the working capital tied up in distributed stock. That single position also simplifies German VAT compliance, since you are not triggering storage-based VAT registration in multiple countries unnecessarily.
FBA: Choose It When
Route SKUs to FBA when velocity is high, the Prime badge drives measurable conversion, and the per-unit fulfilment fee is competitive against your 3PL pick-and-pack rate. FBA works best for standardised, lightweight products with predictable sell-through and low return complexity. If the SKU sells consistently on Amazon.de or Amazon.fr and does not require special handling, FBA's delivery promise justifies the fee.
3PL: Choose It When
Route SKUs to a 3PL when they are slow-moving, bulky, high-return, or needed across multiple channels. European 3PL fulfilment gives you inventory control, visible storage costs, and the ability to serve DTC and B2B orders from the same stock. If your FBA aged inventory surcharges are rising or your removal order costs are climbing, those SKUs belong in a 3PL buffer, not an Amazon FC.
Hybrid: The Default for Scale
Most sellers above a moderate annual volume need both layers. The hybrid model routes fast Amazon SKUs to FBA and everything else to a 3PL anchor — typically in Germany for DACH and pan-EU coverage. The decision rule must be explicit and reviewed regularly. Without a defined split, inventory allocation drifts toward FBA by default, and the cost advantage of the 3PL layer is never captured.
What to Decide and Where to Start
The FBA versus 3PL question is not a one-time architecture decision. It is an ongoing routing discipline that needs to be revisited as your SKU mix changes, as Amazon adjusts its fee structure, and as your channel mix evolves. The sellers who manage this well treat it as a cost-to-serve exercise, not a loyalty question about Amazon.
The practical starting point is a per-SKU cost-to-serve model that includes every FBA fee — fulfilment, storage, placement, aged inventory, and removal — and compares it against a realistic 3PL rate for the same unit. That comparison will almost always reveal a segment of your catalogue where 3PL fulfilment is cheaper, and a segment where FBA remains the right choice. The hybrid network architecture follows from that analysis, not the other way around.
For sellers based in or selling into the DACH region, Germany is the logical anchor for the 3PL layer. The FC proximity, carrier infrastructure, and B2C and B2B fulfilment capability make it the most operationally efficient single-node position for a pan-European hybrid network. If you are also running significant volume on Amazon.fr or Amazon.es, a secondary 3PL node in France or Spain may be worth modelling once your German anchor is stable.
The most common mistake at this stage is delaying the network review because the current setup is familiar. FBA costs compound quietly. Placement fees, aged inventory surcharges, and removal costs do not appear as a single line item — they are distributed across your P&L in ways that are easy to miss until the margin impact is significant. The time to model the hybrid architecture is before the cost creep becomes a crisis, not after.
If you are evaluating whether to add a 3PL layer to your FBA network — or restructuring an existing hybrid setup — FLEX. operates e-commerce fulfilment in Germany with direct Amazon FC forwarding capability, B2C and B2B order fulfilment, and returns handling from a single DACH inventory position.
Speak with the FLEX. operations team about your current SKU mix, channel split, and FBA cost structure. We will help you identify which handoff to fix first and what a hybrid network would cost to run from Germany.
