Inbound handoff in Spain: how to coordinate your forwarder and your warehouse without receiving chaos
Inbound Handoff in Spain: How to Coordinate Your Forwarder and Your Warehouse Without Receiving Chaos
Most inbound chaos doesn’t start when the truck arrives at the warehouse dock. It starts three days earlier, when the forwarder sends an arrival notification with incomplete information, the warehouse hasn’t confirmed an appointment, and the documentation package for customs release hasn’t been linked to the shipment details the receiving team is working from. By the time the truck arrives, the warehouse is receiving a shipment it wasn’t fully prepared for — and the forwarder considers its job complete. The gap between freight delivery and warehouse acceptance is where most disputes are created.
Why the Handoff Is the Control Point
A forwarder’s job ends, operationally speaking, when the shipment is delivered to the warehouse address. A warehouse’s job begins when it has enough information to receive the shipment correctly. These two endpoints don’t automatically align — and the gap between them is where cartons go missing, counts get disputed, and reconciliation takes weeks instead of hours.
The handoff protocol is the bridge. It’s not a complex document — it’s a set of commitments about who sends what, when, and to whom, so that by the time the truck arrives, both the forwarder and the warehouse are working from the same data.
What needs to cross the bridge before arrival: the pre-alert, the ASN (advance shipping notice), the expected quantities by SKU, and the appointment confirmation. When any of these arrive late or arrive incomplete, the receiving team either delays the truck while they scramble for information, or accepts the shipment without the documentation needed to verify it — which means disputes become opinions instead of evidence.
The pre-alert is the forwarder’s notification that the shipment is on its way, typically 24–48 hours before expected arrival. A useful pre-alert contains: the shipment identifier (booking reference, container number, or tracking reference), the estimated arrival date and time window, the number of cartons or pallets expected, the total expected unit count, and the point of contact at the forwarding company for any questions. A pre-alert that says “shipment arriving Thursday” without the rest of this information is not a pre-alert — it’s a calendar entry. The warehouse can’t prepare a receiving slot, a verification team, or the right intake documentation for a shipment it doesn’t yet know the details of.
ASN Structure: What the Warehouse Needs to Receive Correctly
An advance shipping notice is the document that tells the warehouse what to expect at the unit and carton level — not just “a shipment is coming” but “these ASINs, in these quantities, packed this way, arriving on this date.” The ASN is what makes a receiving process systematic rather than reactive.
For an importer or distributor receiving stock in Spain, a complete ASN should include: every SKU or product reference in the shipment, the quantity per SKU (total units and units per carton), the total carton count, the total pallet count if applicable, and any product-level notes relevant to receiving (fragile, this-side-up, temperature-sensitive — though temperature control is outside this operation’s scope). It should also specify whether cartons contain single SKUs (case-packed) or mixed SKUs, because this determines the counting method used at receiving.
The ASN that matters is the one that matches reality. An ASN generated from the purchase order issued to the supplier three months ago, and never updated to reflect what was actually shipped, creates the worst possible situation: a receiving team verifying a shipment against numbers they can’t trust. The responsibility for keeping the ASN current typically sits with the importer or forwarder, not the warehouse — but the warehouse suffers the consequences of an inaccurate ASN in reconciliation time and disputed counts.
A scenario that comes up regularly: a container arrives with 48 cartons. The ASN shows 50. The receiving team counts 48. The forwarder’s documentation shows 50. Now neither party can agree on whether 2 cartons were short-shipped, left at the origin port, damaged in transit, or miscounted somewhere in the chain. The resolution takes days, involves emails across multiple time zones, and produces a settlement that satisfies no one. The entire dispute could have been avoided if the forwarder had confirmed the actual loaded count before issuing the pre-alert — not the PO quantity, the actual loaded count.
Appointment Discipline: What Happens When the Truck Arrives Unannounced
Warehouses have receiving capacity constraints. A truck arriving without an appointment is a truck that may wait — sometimes for hours, sometimes until the next available slot. The cost of that wait is usually carried by the driver and ultimately billed back to the shipper. More importantly for the inbound operation, an unannounced arrival means the warehouse didn’t have time to prepare the receiving team, the dock assignment, or the documentation check for this specific shipment.
Appointment scheduling should happen as part of the pre-alert exchange, not after. When the forwarder confirms the estimated arrival date, the warehouse should confirm a receiving appointment window in the same exchange — not as a separate process started after the pre-alert. The appointment creates a commitment on both sides: the forwarder commits to delivery within the window; the warehouse commits to having receiving capacity ready.
What documents are needed at the dock depends on the shipment type and origin. Without entering customs advisory territory — which is outside this scope — the receiving team typically needs at minimum: the packing list (which should match the ASN), any delivery note or CMR, and a reference number that links the physical shipment to the digital record in the WMS. When these documents aren’t available at the dock, one of two things happens: the warehouse refuses the shipment (which creates a carrier delay and a rebooking cost) or accepts it without documentation (which makes any subsequent discrepancy unverifiable).
When Reality Differs: Exception Protocol
No inbound operation runs perfectly. Cartons arrive damaged. Unit counts don’t match the ASN. Seal integrity is compromised. Products show condition issues that weren’t present when they left the supplier. The exception protocol is the agreed process for what happens when the receiving doesn’t match the expectation.
The first principle is documentation before decision. When a carton count is short, photograph the arrival before cartons are moved, note the count on the delivery documentation before signing, and log the discrepancy with a timestamp and a description of what was found. This is the evidence that makes the subsequent claim defensible. A shortage noted in a WhatsApp message sent after the truck has left is not evidence — it’s a recollection.
The second principle is quarantine before disposition. Units whose condition is unclear — damaged outer packaging, compromised seals, wet cartons — go into quarantine rather than directly into storage. Quarantine here means a physically separate staging area with a distinct inventory state in the WMS, not a corner of the warehouse floor. The units stay in quarantine until the importer has reviewed the evidence and made a disposition decision: accept to stock, return to supplier, scrap, or hold for inspection. The warehouse executes the decision; the importer makes it.
The third principle is closure, not just logging. A discrepancy log that captures what went wrong is useful. A discrepancy log that also records how it was resolved — what the final agreed count was, what happened to the disputed units, and what the financial outcome was — is what prevents the same dispute from reopening three weeks later when someone pulls an old report and finds a number that doesn’t match.
A weekly alignment cadence between the client, the warehouse, and the forwarding company (or at least a brief written summary sent to all three) keeps inbound issues from accumulating between conversations. Discrepancies that are resolved in the same week they occur cost a fraction of what they cost when they’re discovered in a quarterly inventory audit.
Frequently Asked Questions
Q: Who is responsible for the ASN — the forwarder, the supplier, or the importer? A: The ASN reflects what was actually shipped, so the responsibility for its accuracy sits with whoever packed and loaded the shipment — typically the supplier or manufacturer. The forwarder’s role is to transmit the ASN to the warehouse (and the importer) based on information from the supplier. The importer’s role is to verify that the ASN matches the purchase order before the shipment departs, and to flag discrepancies before the truck arrives, not after. In practice, many ASNs are generated from PO data without verification against the actual loaded quantities, which is where the discrepancy chain begins.
Q: How much notice does the warehouse need before a truck arrives? A: The practical minimum for a prepared receiving is 24 hours. This allows the warehouse to assign dock space, confirm the receiving team availability, and pre-check the ASN against the WMS before the shipment arrives. Less than 24 hours is possible for small shipments, but increases the likelihood of delays at the dock. For container-level shipments, 48 hours is a more reliable window. Last-minute arrivals — same-day notification — should be treated as exceptions with an explicit escalation path rather than a standard scenario the warehouse is expected to absorb.
Q: What if the forwarder’s documentation doesn’t match the warehouse’s ASN at receiving? A: Document both versions before any units are moved. Take the packing list from the driver, compare it to the ASN in the WMS, note every discrepancy, and photograph the carton stack before unpacking begins. The discrepancy between documents is the starting point for the claim — not a reason to delay receiving indefinitely, but a condition that requires the receiving team to count carefully and record the actual received quantity precisely. The claim is made against documented evidence; if the evidence is ambiguous, the claim is weak regardless of who’s right.
Q: Can the 3PL manage the forwarder communication on behalf of the importer? A: The 3PL can be included in the communication chain — receiving pre-alerts directly, confirming appointments, flagging documentation gaps before arrival — but the commercial relationship and final decisions remain with the importer. A setup where the 3PL is the single point of contact for forwarder coordination can work operationally, as long as the escalation path for disputed counts and exception decisions is clear: the 3PL documents and flags; the importer decides. The 3PL shouldn’t be making disposition decisions on stock it doesn’t own.
Q: What is the minimum a forwarder should send before a shipment arrives? A: At minimum: the expected arrival date and time window, the shipment reference (container number or booking reference), the total carton or pallet count, the total unit count by SKU, and a packing list that matches the physical shipment. Anything less than this creates a receiving process that depends on the truck contents being self-explanatory — which they rarely are for mixed-SKU or high-variety shipments. The pre-alert should arrive in time to confirm an appointment, not at the same time as the truck.
If you’re coordinating inbound logistics between a forwarder and a new warehouse facility in Spain, describe the shipment flow — origin, frequency, product type, and any prior handoff problems — and we’ll map the control points before the first arrival.