

![]()
Most FBA sellers who ship inventory to a German prep facility have a rough idea of what happens inside — labels go on, boxes get repacked, pallets get built. What they rarely see is the sequence of handoffs, the documentation generated at each stage, and the specific points where a missed step causes a failed FC receiving scan or a delayed inbound plan. This walkthrough covers the full German FBA prep process in order: from the moment your freight arrives at the prep centre dock to the moment the pallet clears the Amazon.de FC gate. Each stage has a defined owner, a defined output, and a defined failure mode. Understanding that sequence is the first step toward deciding which part of your forwarding to Amazon in Germany setup needs attention.
When a freight consignment arrives at the prep centre, the first task is not labelling — it is counting. Every carton is checked against the packing list and the Advance Shipment Notification submitted to Amazon Seller Central. The prep team logs the number of cartons received, the number of units per carton, and any visible damage to outer packaging. This receiving record becomes the baseline for the entire batch. If the physical count does not match the ASN, the discrepancy is flagged before any prep work begins.
This stage matters more than sellers typically expect. An ASN mismatch that goes undetected at receiving will surface later as a unit-count discrepancy at the Amazon FC — and at that point, the seller carries the burden of reconciliation. A competent FBA prep centre in Germany closes the loop at inbound, not at dispatch. The receiving report generated here documents carton count, unit count, SKU breakdown, and any exception notes. That document travels with the batch through every subsequent prep stage and forms the audit trail if Amazon raises a receiving query after the shipment closes.

Once the inbound count is confirmed, individual units are inspected before any prep work begins. The inspection checks for physical damage, incorrect product inside the carton, missing components, and packaging that does not meet Amazon's condition requirements for new inventory. Units that pass inspection move to the labelling queue. Units that fail are quarantined and logged with a condition note — typically categorised as damaged, mislabelled by the supplier, or short-shipped.
Condition grading at this stage prevents a specific and costly failure: a damaged or non-conforming unit reaching the Amazon FC and triggering a customer complaint or an unfulfillable inventory flag. For sellers sourcing from manufacturers outside the EU, this inspection step also catches labelling errors introduced during production — wrong barcodes, missing safety warnings, or packaging that does not match the active ASIN listing. The prep team documents every quarantined unit with a photo record and notifies the seller before proceeding. No prep work is applied to a unit whose condition status is unresolved. This is a control point that protects both the inbound plan and the seller's account health metrics on Amazon.de.
FNSKU labelling is the most operationally precise stage in the German FBA prep process. Each unit receives a printed FNSKU label that corresponds exactly to the active shipment plan in Seller Central. The label is applied at unit level — not carton level — and the barcode is scanned after application to verify that the printed code reads correctly and matches the expected FNSKU for that SKU. A label that applies correctly but scans incorrectly is a receiving failure waiting to happen at the FC.
The labelling workflow at a structured FBA prep centre in Germany runs as a three-step sequence: print from the confirmed shipment plan, apply to the unit, scan to verify. Any unit that fails the post-application scan is relabelled before it moves forward. This scan-verify step is what separates a prep centre operating to Amazon inbound standards from one that applies labels in bulk without confirmation. For sellers with multiple ASINs in a single batch, the prep team also verifies that no label has been applied to the wrong product — a mix-up that Amazon's FC receiving system will catch, but only after the shipment has been checked in and the error has already created an inventory discrepancy.
Where Amazon's prep requirements specify polybagging — typically for soft goods, loose sets, or products with small components — the polybag is applied after labelling, with the FNSKU visible through the bag. The suffocation warning label is applied to the outside of the bag where required by Amazon's packaging guidelines.

After unit-level prep is complete, units are packed into master cartons that meet Amazon's inbound carton requirements. This means each carton contains a single ASIN unless the shipment plan specifies a mixed-SKU carton, the carton weight and dimensions fall within Amazon's published limits, and the carton label — carrying the FBA shipment ID and the carton number — is applied to the correct face of the box. A carton that exceeds the weight limit or carries a label on the wrong panel may be refused at the FC dock or flagged during the receiving scan.
The carton compliance check at this stage covers four outputs: the physical carton label printed from Seller Central, the weight recorded on the shipment plan, the dimension recorded on the shipment plan, and the actual measured weight and dimension of the packed carton. Where the actual figures differ from the plan — because the seller estimated rather than measured — the prep centre updates the shipment plan before the carton is sealed. Sending a carton to an Amazon FC in Germany with declared dimensions that do not match the physical carton is a common source of receiving delays and can trigger a manual check-in process that holds the entire shipment. Carton repacking as part of FBA prep Germany execution is the stage that prevents that outcome.
Once all cartons are labelled, weighed, and compliance-checked, the prep centre builds the pallet to Amazon.de specification. Amazon Germany FCs typically require Euro pallets, stacked to a defined height limit, with cartons arranged so that carton labels face outward and are scannable without breaking the pallet wrap. The pallet label — a PRO label generated from the Amazon partnered carrier booking or the seller's own carrier arrangement — is applied to all four sides of the pallet before wrapping is completed.
Booking the FC delivery appointment is a step that sellers using a prep centre for the first time often underestimate. Amazon Germany FCs operate on a booked-slot system. A pallet that arrives without a confirmed appointment will not be accepted at the dock. The prep centre coordinates the appointment booking against the carrier's collection schedule, ensuring the delivery window aligns with the confirmed pick-up date. For sellers using Amazon's partnered carrier programme, the appointment is generated automatically when the shipment is confirmed in Seller Central. For sellers using their own carrier for Amazon FC forwarding in Germany, the appointment must be booked separately through the FC's carrier portal.
Final dispatch generates a receiving-to-dispatch report for the batch: unit count by ASIN, carton count, pallet count, shipment ID, carrier reference, and confirmed delivery appointment. This document is the seller's operational record for the entire prep cycle and the first reference point if Amazon raises a receiving discrepancy after the shipment closes at the FC.

The prep workflow described above is not complicated in principle — but it requires consistent execution across eight distinct stages, each with its own documentation output and its own failure mode. A single missed scan at labelling, an unreconciled ASN at receiving, or a pallet that arrives at the FC without a booked appointment can hold an entire batch for days. For sellers building volume on Amazon.de, those delays translate directly into lost buy box time and inventory unavailable to sell during peak demand windows.
FLEX. manages every stage of this workflow from a German prep facility, covering inbound receiving and ASN reconciliation through to pallet build, FC appointment booking, and final dispatch. Every batch generates a receiving-to-dispatch report that gives the seller a complete unit-level audit trail. For sellers who have experienced receiving discrepancies, label errors, or appointment failures with a previous prep setup, that documentation layer is often the first thing that was missing.
If you are evaluating pre-Amazon storage in Germany, need a structured FBA prep workflow for a new product range, or want to understand what a compliant forwarding to Amazon in Germany operation looks like in practice, the FLEX. team can walk through your specific requirements. Reach out to the FLEX. team today via our contact form for a no-obligation quote tailored to your product range and sales volume. A more profitable fulfillment strategy could be closer than you think.
Forwarding to Amazon in Germany involves eight sequential stages — inbound receiving, ASN reconciliation, unit inspection, FNSKU labelling with scan verification, polybagging where required, carton repacking and compliance check, pallet build to Amazon.de specification, and FC appointment booking. Each stage has a defined owner and generates documentation that protects the seller if Amazon raises a receiving query. A prep centre that manages all eight stages and provides a receiving-to-dispatch report for every batch removes the most common sources of FC receiving delays and inventory discrepancies on Amazon.de.
