Multi-Marketplace Prep in Germany: Why Amazon.de, Kaufland.de and OTTO Need Different SKU Labels
Multi-Marketplace Prep in Germany: Why Amazon.de, Kaufland.de and OTTO Need Different SKU Labels
FBA Prep Germany
We streamline your German Amazon operations by handling FBA prep, managing removal orders, and forwarding shipments to any German Fulfillment Center for FBA and Vendor accounts.
You have one physical product. Same EAN, same carton, same supplier. But you are selling it on Amazon.de, Kaufland.de, and OTTO Market at the same time — and each platform has a different opinion about what that product's label should look like before it enters their system.
This is where multi-marketplace prep in Germany breaks down. Sellers often assume that a single label applied at the factory or at a generic prep center will satisfy all three channels. In practice, one-label-fits-all is the most common cause of receiving rejections and delayed listings across German marketplaces.
Amazon.de requires an FNSKU label that overrides the manufacturer barcode. Kaufland.de and OTTO Market work from EAN-based routing, but their packaging expectations, return-label logic, and carton-level requirements differ from each other and from Amazon FBA inbound standards. If your prep workflow does not account for these divergences per SKU and per channel, you will face rework, re-labelling costs, or inventory that cannot be received at all. This article maps the differences so you can decide which handoff to fix first.
Why the Same SKU Needs Three Different Prep Approaches
The root issue is that Amazon.de, Kaufland.de, and OTTO Market each operate a different fulfilment model, and their inbound requirements reflect that model — not your product catalogue.
Amazon FBA in Germany runs on a closed inventory system. Every unit entering an Amazon FC must carry an FNSKU — a platform-specific barcode that ties the unit to your seller account and your specific ASIN. The manufacturer EAN is suppressed or covered. This is not optional. A unit arriving at an Amazon FC in Bad Hersfeld or Rheinberg with only an EAN will either be refused at receiving or misrouted into commingled inventory, which creates a different set of problems.
Kaufland.de operates a marketplace model where sellers typically fulfil from their own warehouse or a 3PL. Kaufland does not run an FBA-equivalent closed FC network in the same way. Inbound to Kaufland-connected fulfilment means your EAN must be clean, scannable, and match the product listing exactly. There is no FNSKU layer. The label discipline here is about EAN accuracy and carton-level documentation, not platform barcode replacement.
OTTO Market sits in a similar position to Kaufland for label logic — EAN-driven, no proprietary barcode overlay — but OTTO's packaging and returns routing requirements can differ in practice, particularly for categories like electronics, textiles, and bulky goods. Running FBA prep services in Germany without separating these flows at the prep stage means you are either over-labelling for Kaufland and OTTO or under-labelling for Amazon.
Amazon.de: FNSKU Is the Control Point
For Amazon FBA inbound in Germany, the FNSKU label is the single most important prep control point. It must be applied before the unit enters the Amazon FC — either at the factory, at a pre-Amazon storage buffer, or at a dedicated FBA prep center in Germany.
Key rules that apply to Amazon.de inbound prep:
- The FNSKU must be scannable and cover or replace the manufacturer barcode on the unit
- Polybag requirements apply to soft goods, loose items, and anything that could spill or tangle — Amazon's category-specific rules define when a polybag is mandatory
- Carton labels must include the FBA shipment ID and box number, generated from Seller Central after the inbound plan is created
- Units without a valid FNSKU may be refused at the FC or placed in an unconfirmed receive queue, delaying availability to sell
If you are running the same SKU to Amazon.de and other channels, the FNSKU label must be applied as a channel-specific step — not at the factory level where it would contaminate stock destined for Kaufland or OTTO.
Kaufland.de and OTTO: EAN Accuracy and Return Routing
For Kaufland.de and OTTO Market, the label discipline is different but equally important. Neither platform uses a proprietary barcode overlay. The EAN on the unit must match the listing exactly — any mismatch between the physical barcode and the platform catalogue entry will cause a receiving failure or a listing suppression.
Where these two platforms diverge from each other:
- Kaufland.de fulfilment may require specific carton-level documentation and delivery scheduling that differs from standard B2C courier shipments
- OTTO Market has category-specific packaging rules, particularly for returns — some categories require the original packaging to be intact and resaleable on return, which affects how units are prepped before first dispatch
- Return-label logic differs: Amazon returns route back through the Amazon returns network; Kaufland and OTTO returns route to the seller's nominated return address in Germany, which must be registered and operational
A seller running all three channels from one prep batch without channel-specific sorting will typically discover the problem only after a return arrives at the wrong address or a Kaufland shipment is refused because carton documentation references an Amazon inbound plan number.
The Polybag and Packaging Divergence Point
Polybag and secondary packaging rules are where multi-marketplace prep in Germany creates the most rework. Amazon FBA has published category-specific polybag requirements — units that meet the threshold must be bagged and sealed before FC entry.
Kaufland.de and OTTO Market do not apply the same polybag mandate at inbound. However, OTTO's returns policy for certain categories effectively requires that the product arrive at the customer in resaleable condition, which means the packaging prep decision shifts from inbound to outbound. A unit that is polybag-sealed for Amazon FBA may need to be repacked differently if the same SKU is being dispatched direct-to-consumer via OTTO.
The practical control point here is to separate your prep runs by channel before any secondary packaging is applied. Units destined for Amazon FBA prep in Germany should be polybag-processed and FNSKU-labelled as a dedicated batch. Units going to Kaufland or OTTO should be held at EAN-clean status until channel-specific dispatch prep is confirmed.
Return-Label Differences and Why They Matter for Prep Planning
Return routing is often treated as an afterthought in prep planning, but for multi-marketplace sellers in Germany, it is a direct consequence of how each channel handles the post-sale flow — and it affects what information must be on the unit label before it is first dispatched.
Amazon FBA returns in Germany are processed through Amazon's own returns network. The customer receives a return label generated by Amazon, and the unit comes back to an Amazon FC or to a returns processing address nominated in Seller Central. The seller does not need to print or attach a return label to the outbound unit. The FNSKU on the unit is sufficient for Amazon to route the return correctly within its system.
Kaufland.de and OTTO Market operate differently. Returns from these channels route back to the seller's nominated return address — which must be a physical address in Germany or the EU, registered with the platform. If no valid return address is registered, the platform may block the listing or refuse to process customer returns. This means that before you list on Kaufland or OTTO, you need a confirmed return address in Germany that can receive, sort, and process returned units.
For sellers running B2C and B2B fulfillment in Germany across multiple channels, this creates a practical prep planning requirement: the return routing for each channel must be confirmed before the first unit ships, not after the first return arrives. A prep center handling multi-channel stock should be tracking which units belong to which return flow, because a Kaufland return arriving at an Amazon prep address — or vice versa — creates an exception that costs time and margin to resolve. Warehouse services in Germany that handle multi-marketplace accounts typically manage this through channel-tagged inventory records at the SKU level.
Choosing the Right Prep Sequence for Multi-Channel Stock
When the same physical SKU is going to Amazon.de, Kaufland.de, and OTTO Market, the prep sequence matters as much as the prep rules. The most common mistake is treating prep as a single pass — label everything at once, pack everything the same way, and sort by channel at dispatch. This approach fails because FNSKU labelling for Amazon FBA cannot be undone cleanly if the unit is later redirected to Kaufland or OTTO.
A workable prep sequence for multi-channel stock in Germany looks like this:
- Receive all units at EAN-clean status — no FNSKU, no channel-specific label applied yet
- Confirm channel allocation per SKU batch before any labelling begins
- Run Amazon FBA prep as a dedicated batch: FNSKU application, polybag if required, carton labelling per the active inbound plan
- Run Kaufland and OTTO batches separately: EAN verification, channel-specific carton documentation, return address confirmation
- Hold any unallocated stock in a pre-Amazon storage buffer until channel demand is confirmed
This sequence adds a planning step but removes the rework cost that comes from mixed batches. A prep center Europe-wide that handles multi-marketplace accounts will typically enforce this channel-separation rule as a standard operating procedure, not an optional upgrade.
Amazon FBA Inbound Check
Before sending any unit to an Amazon FC in Germany, confirm:
- FNSKU generated and matched to the correct ASIN
- Manufacturer barcode covered or suppressed
- Polybag applied if category requires it
- Carton label includes active FBA shipment ID
Missing any of these at FC receiving will delay inventory availability.
Kaufland.de Inbound Check
Before dispatching to Kaufland fulfilment or a Kaufland-connected warehouse:
- EAN on unit matches the Kaufland listing exactly
- No FNSKU overlay applied to this batch
- Carton documentation references Kaufland order or delivery reference, not an Amazon shipment ID
- Return address registered and active on the platform
OTTO Market Dispatch Check
Before dispatching units to OTTO Market customers or fulfilment:
- EAN clean and scannable — no Amazon-specific label overlay
- Packaging meets OTTO category requirements for resaleability on return
- Return address in Germany confirmed and registered with OTTO
- Channel-tagged in warehouse system to prevent return misrouting
Which Handoff Should You Fix First?
If you are running the same SKU across Amazon.de, Kaufland.de, and OTTO Market and you have not yet separated your prep flows by channel, the first handoff to fix is labelling at the point of receipt — before any channel-specific prep is applied.
The decision rule is straightforward: no unit should receive an FNSKU label until its channel allocation is confirmed. Once an FNSKU is applied, that unit is committed to the Amazon FBA flow. Redirecting it to Kaufland or OTTO requires label removal and re-inspection, which adds cost and time that compounds across volume.
The second handoff to fix is return routing. If you do not have a confirmed return address in Germany registered with Kaufland and OTTO, your listings on those platforms carry a structural risk that no amount of prep quality will resolve. This is a pre-launch check, not a post-problem fix.
The third area to audit is your prep center's channel-separation discipline. A prep center handling multi-marketplace FBA prep in Germany should be running channel-tagged batches, not a single mixed prep pass. If your current setup does not enforce this separation, the rework cost will appear in your cost-to-serve figures before it appears in any platform report.
Sellers who get this right treat multi-marketplace prep as three distinct inbound workflows that happen to share a physical product — not one workflow with minor label variations. That framing change is what prevents the rejection cycles that erode margin on high-volume SKUs.
If you are managing the same SKU across Amazon.de, Kaufland.de, and OTTO Market and need a prep operation that separates these flows correctly, FLEX. handles multi-channel FBA prep in Germany with channel-tagged batching, FNSKU application, and return address management built into the standard workflow.
Reach out to discuss your current prep setup and which channel handoff makes sense to fix first.
