The Dead Stock Audit: A Quarterly Protocol for Inventory Health in French Warehouses
11.05.2026
New EU Withdrawal Rights from June 2026: Preparing Your French Returns Operation
12.05.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 shipment arrives at your prep facility outside Paris or LiĆØge. The cartons look intact. The packing list says 500 units. But when the receiving team opens the boxes and counts SKU by SKU, only 462 units are present. The factory shipped short ā and without a formal inbound receiving protocol, that discrepancy would have travelled silently all the way to Amazon's fulfilment centre, where it would surface as an inventory shortfall you cannot explain and cannot recover.
Factory under-shipping is one of the most financially damaging inbound failures in e-commerce logistics, precisely because it is invisible at the carton level. The solution is not faster shipping. It is a structured inbound quality control process that catches the variance at the prep stage, documents it formally, and creates the evidence trail your procurement team needs to act.
What the FLEX. Inbound Receiving Protocol Actually Checks
When a shipment arrives at a FLEX. facility, the receiving process is not a passive scan-and-stack operation. Every inbound consignment goes through a structured sequence designed to catch discrepancies before a single unit moves toward FBA prep or storage.
The protocol begins with a carton-count check against the advance shipping notice. Each carton is weighed and compared against the declared gross weight. Any carton that falls outside the expected weight band is flagged immediately and opened for a full SKU-level count. Cartons showing external damage ā crushed corners, moisture marks, broken seals ā are photographed before opening, creating a timestamped visual record that forms part of the warehouse receiving report.
Inside each flagged carton, every SKU is counted individually. Quantities are recorded against the purchase order line, not just the packing list, because factories occasionally update packing lists without updating the order. This distinction matters: a packing list can be amended after the fact; a purchase order cannot. The FBA inspection service layer then cross-references the counted quantities against the inbound plan before any prep work begins, ensuring that Amazon is never sent a shipment built on unverified stock figures.
The Control Point: SKU-Level Counting
The most common weak assumption in inbound logistics is that carton count equals unit count. It does not. A factory packing 48 units per carton may ship 10 cartons but fill the last two cartons with only 36 units each. The outer count looks correct. The unit count is short by 24.
FLEX. performs SKU-level counting as a standard step in the inbound receiving workflow, not as an exception triggered only when something looks wrong. Every SKU in every opened carton is counted against the purchase order quantity. Variances of even a single unit are recorded in the inbound log. This granular count is what makes inventory reconciliation possible after the fact ā and what gives procurement teams a defensible figure when raising a supplier claim.
The Consequence: Invisible Stock Erosion
When short-shipped units go uncounted at the prep stage, the financial damage compounds across the supply chain. Amazon receives fewer units than the inbound plan declares, which can trigger receiving discrepancies at the fulfilment centre. Those discrepancies are difficult to resolve once the shipment is closed, and Amazon's own reconciliation process may not recover the full unit value.
Beyond the Amazon layer, the seller carries phantom inventory in their system ā stock that appears available but does not physically exist. This leads to overselling, stock-out events, and suppressed listings at the worst possible moment. The cost is not just the missing units.
Photo Documentation: The Evidence Layer That Changes Supplier Disputes
A discrepancy report without photographic evidence is a claim. A discrepancy report with timestamped photographs of damaged cartons, short-packed boxes, and unit counts laid out on the receiving bench is a case file.
For sellers shipping from factories in Asia or Eastern Europe into France or Benelux, this photo record is often the only evidence that survives a supplier dispute. Factories routinely deny short-shipping claims when no third-party documentation exists. A formal warehouse receiving report with attached photographs, signed by the receiving operator and timestamped at the facility, is a materially different document from a seller's internal spreadsheet note.
How the Formal Discrepancy Report Supports Supplier Claims
The discrepancy report produced at the end of the inbound receiving process is a structured document, not a complaint email. It records the purchase order number, the declared quantity, the counted quantity, the variance by SKU, the condition of affected cartons, and the photographic evidence references. It is signed by the receiving operator and timestamped against the arrival record.
This document serves three distinct functions in the supply chain. First, it gives the procurement team a factual basis for raising a formal supplier claim ā one that specifies the exact units missing rather than an approximate shortfall. Second, it provides the seller with an accurate inventory figure before the goods enter the FBA prep workflow, preventing a mislabelled inbound plan from being submitted to Amazon. Third, it creates an audit trail that can be referenced if Amazon's own receiving count differs from the prep centre's count, which is a known friction point in Amazon inbound shippingĀ and Benelux routing scenarios.
It is important to note that a discrepancy report documents an operational fact. It does not guarantee a legal or commercial outcome in a supplier dispute ā that depends on the contract terms between the buyer and the factory. What it does provide is the documented evidence that makes a claim credible and specific, rather than contested and vague. Sellers who operate without this layer often find that supplier negotiations stall because neither party has a reliable unit count from an independent third party.
Where the Discrepancy Report Fits in the Prep Workflow
The discrepancy report is not a post-shipment administrative task. It is generated during the inbound receiving step, before any FBA prep work begins. This sequencing is deliberate. If prep work starts on an unverified unit count, labels get applied to a quantity that may not match the inbound plan, and the error propagates forward into Amazon's system.
At FLEX., the receiving report is completed and reviewed before the prep team receives a work order. If a variance is identified, the client is notified with the full report and photographs before any decision is made about how to proceed. This handoff point ā between receiving and prep ā is where the pre-Amazon storage buffer becomes a decision window rather than a waiting room.
Operating Model Owner
FLEX. owns the inbound receiving step end to end. The receiving operator counts, photographs, and logs every variance. The client receives the warehouse receiving report before prep begins. No units move to the prep queue until the count is confirmed and signed off.
Visibility Checkpoint
Every discrepancy is logged at SKU level against the purchase order, not the packing list. Clients can see the variance figure, the affected carton references, and the photographic evidence in the report. This data feeds directly into inventory reconciliation before the inbound plan is submitted.
Exception and Escalation Rule
If a variance exceeds the agreed tolerance threshold, the shipment is held and the client is contacted before any further handling. FLEX. does not proceed with prep on a disputed quantity. The exception is escalated to the client with the full discrepancy report attached for supplier claim use.
The Decision Every Inbound Shipment Forces
Every consignment that arrives at a prep facility presents the same fork: process it on trust, or verify it on evidence. Processing on trust is faster in the short term. It is also how short-shipped units disappear into the supply chain without a trace, how phantom inventory accumulates in seller accounts, and how supplier disputes become unwinnable because no independent count was ever taken.
The inbound discrepancy report is the mechanism that converts receiving from a passive handoff into an active quality gate. For brands shipping into France, Belgium, or the Netherlands ā where Amazon FC forwarding timelines are tight and supplier relationships cross multiple time zones ā having a documented, timestamped, SKU-level count at the prep stage is not a premium add-on. It is the baseline protection that makes inventory reconciliation possible and supplier claims credible.
If your current inbound process does not produce a formal discrepancy report with photographic evidence for every flagged shipment, the question is not whether you will encounter a short-shipping event. It is whether you will have the documentation to do anything about it when you do. The FBA prep services and receiving protocols described here are the operational layer that closes that gap.
If your inbound shipments are arriving in France or Benelux without a formal receiving protocol, FLEX. can apply SKU-level counting, photo documentation, and structured discrepancy reporting to every consignment before prep begins.
Contact the FLEX. team to discuss how the inbound receiving workflow can be integrated into your existing supply chain ā and what a formal discrepancy report means for your next supplier claim.
