

![]()
When Amazon.de logs a receiving discrepancy — missing units, a condition dispute, or a shortfall against your inbound plan — the seller's ability to recover that inventory value depends almost entirely on what the prep centre documented before the shipment left the warehouse. Amazon does not accept verbal accounts or carrier estimates. It accepts timestamped records: goods-in receipts, prep completion sign-offs, carton-level photos, and carrier handoff confirmations. Without a complete documentation chain from the point of FBA prep in Germany through to FC delivery, an inbound dispute is close to unwinnable. This article maps the exact records a German 3PL must generate at each stage.
A seller ships 400 units of a mid-range electronics accessory to an Amazon FC in Germany. Amazon's receiving system logs 362 units. The seller contacts Seller Central and opens an inbound discrepancy case. Amazon requests proof of the quantity handed to the carrier. The prep centre has a packing list — but it was generated from the purchase order, not from a physical count at goods-in. The carrier has a signed CMR, but the unit count on it matches the purchase order figure, not an independently verified count. The case closes without reimbursement.
This is the documentation gap in practice. The failure is not that units went missing — it is that no independent count was recorded at the moment the prep centre took physical custody of the goods. Every stage of the FBA prep workflow in Germany must generate its own timestamped record, because Amazon's dispute process treats each stage as a separate evidentiary layer. A gap at goods-in cannot be patched by a clean carrier handoff document, and a clean goods-in receipt cannot compensate for missing carton photos at the point of pallet build.

The goods-in receipt is the first and most critical document in the FBA prep documentation chain. It must be generated the moment the inbound shipment arrives at the prep centre, before any prep work begins. A proper goods-in receipt for Amazon FBA prep documentation purposes records the date and time of arrival, the number of cartons or pallets received, the SKU-level unit count per carton (not just total units), the condition of packaging on arrival, and the name of the person who performed the count. A photograph of the inbound delivery — showing carton labels, pallet configuration, and any visible damage — should accompany this record.
Where sellers lose disputes is when the goods-in receipt is generated from the supplier's packing list rather than from a physical count. If a supplier ships 400 units but 12 arrive damaged and are set aside, the goods-in receipt must reflect 388 units accepted into prep, with a separate damage note for the 12. Passing the supplier's figure through to the FBA shipment plan without an independent count creates a unit discrepancy that Amazon will not resolve in the seller's favour. Pre-Amazon storage facilities operating as part of an FBA prep workflow must treat goods-in as a formal custody transfer, not an administrative formality.
Once goods-in is complete, the prep centre begins the physical work: FNSKU labelling, poly-bagging, bubble-wrapping, bundling, or whatever the ASIN requires. At the point prep is complete and cartons are sealed, a second document must be generated: the prep completion sign-off. This record confirms the number of units prepped per SKU, the number of cartons sealed, the carton weight and dimensions, and the FNSKU applied. It should reference the Amazon shipment ID and the inbound plan reference so the document can be matched to the specific FBA shipment during a dispute.
Carton-level photos taken immediately after sealing are not optional for dispute-ready FBA prep documentation. Each carton should be photographed showing the Amazon FBA carton label, the FNSKU label on a sample unit visible through an open flap or before sealing, and the carton number within the shipment sequence. When Amazon raises a receiving discrepancy against a specific carton, a timestamped photo showing that carton sealed and labelled correctly at the prep centre is the primary evidence that shifts the burden of proof toward the carrier or the FC receiving process. Without it, the seller has no independent record of what was inside that carton when it left the 3PL handoff records.

For palletised shipments to Amazon Germany FCs, the pallet build stage generates its own documentation requirement. A pallet manifest must record which cartons are on which pallet, the total unit count per pallet, the pallet weight, and the pallet label reference. Pallet-level photographs — showing the completed pallet with the Amazon pallet label visible, the carton stack configuration, and the stretch-wrap condition — create a visual record of what left the prep centre. If a pallet arrives at the FC with damaged cartons or a broken stretch-wrap, the photo record establishes whether the damage occurred before or after carrier collection.
The carrier handoff confirmation is the final document in the pre-FC chain. This is not the same as the carrier's own CMR or proof of collection. The prep centre must generate its own handoff record: the date and time the carrier collected, the number of pallets or cartons handed over, the carrier name and driver details, and a reference to the carrier's collection document. Ideally, the driver signs the prep centre's handoff record as well as the carrier's own paperwork. When an Amazon inbound dispute in Germany involves a shortfall between what the prep centre says it shipped and what the FC says it received, this dual-signed handoff confirmation is the document that separates a recoverable dispute from an unresolvable one. Amazon FC forwarding in Germany without this record leaves the seller exposed at every stage of the dispute process.
Generating the right documents is necessary but not sufficient. The documents must be structured so they can be submitted quickly and coherently when Amazon opens a receiving discrepancy case. Each FBA shipment should have a single documentation folder — physical or digital — that contains the goods-in receipt, the prep completion sign-off with carton-level photos, the pallet manifest with pallet photos, and the carrier handoff confirmation, all cross-referenced to the same Amazon shipment ID. When a dispute is opened, the seller or their account manager should be able to pull the complete chain for that shipment within minutes, not days.
Timing matters in Amazon inbound dispute resolution in Germany. Amazon's case management system has response windows, and submitting incomplete evidence in the first response often results in a case closure that is difficult to reopen. A prep centre operating as a professional FBA prep service in Germany should maintain these records for a minimum retention period aligned with Amazon's dispute window — and should be able to deliver the full documentation set to the seller on request without delay. Sellers using a 3PL that cannot produce this chain on demand should treat that gap as an operational risk, not a minor administrative shortcoming. The cost of a single unresolved discrepancy case often exceeds the cost of implementing a proper documentation protocol across an entire quarter's shipments.

If your current prep centre cannot produce a goods-in receipt with an independent unit count, that is the first gap to close. It is the foundation record. Every downstream document — the prep completion sign-off, the carton photos, the pallet manifest, the carrier handoff confirmation — depends on an accurate opening count. Without it, a discrepancy at any later stage has no reliable baseline to argue from.
If the goods-in count is solid but carton-level photos are missing, that is the second priority. Amazon's receiving discrepancy process at German FCs frequently centres on specific carton shortfalls, and a photo record is the most direct evidence available to the seller. Pallet photos and carrier handoff confirmations follow in priority order. The goal is a complete, cross-referenced chain that can be submitted as a single coherent package — not a collection of partial records assembled under time pressure after a case is already open.
If you are working with a German 3PL that does not currently generate this documentation chain as standard practice, that is worth addressing before the next inbound shipment, not after the next dispute. FLEX. operates FBA prep services in Germany with documentation protocols built around Amazon inbound dispute requirements — if you want to review your current handoff setup or discuss what a compliant documentation chain looks like for your shipment volume, that conversation is worth having before the next receiving shortfall appears in Seller Central.
A complete FBA prep documentation chain for Amazon Germany inbound shipments requires four distinct records: a goods-in receipt with an independent unit count, a prep completion sign-off with carton-level photos, a pallet manifest with pallet photos, and a prep centre carrier handoff confirmation separate from the carrier's own CMR. Each document must reference the Amazon shipment ID so the full chain can be submitted quickly when a receiving discrepancy case is opened. Sellers whose German 3PL cannot produce this chain on demand are carrying an unpriced dispute risk on every shipment they send to an Amazon FC.
Contact the FLEX. team today to ensure your supply chain is audit-ready and eliminate unpriced dispute risks on your Amazon shipments.
