Eight pallets arrived. Four did not.
The shipment was booked as a 12-pallet move on a Wednesday afternoon flight from Los Angeles to Atlanta. The arrival manifest at ATL shows 8 pallets pulled. The other 4 are documented at the LAX origin warehouse, missed the flight cutoff for reasons the airline’s exception report describes as “rebooking required,” and are tentatively scheduled on the Friday flight unless capacity moves them earlier. The airway bill is split. The forwarder now has two physically separated portions of one shipment, with two different recovery clocks running.
The 8 pallets at ATL are recoverable inside the standard window. The 4 pallets at LAX are not yet a recovery problem at all — they’re booking exception freight sitting in someone else’s queue. The consignee in Atlanta is receiving 8 pallets on Thursday. The 4 catching up will arrive on different routing on a different day, possibly early next week.
Consignee sees it as a partial arrival. Forwarder sees two open files — different clocks, different costs, neither one closed.
The shipment that’s both delivered and not delivered
Most freight scenarios resolve cleanly into delivered or not delivered. OS&D residual recovery sits in a category that doesn’t resolve that way. The portion that arrived has been moved, dispatched, and signed for. The POD reflects partial delivery against the airway bill quantity. The freight bill, if it goes out as configured, is partial. The customer relationship now has an open file: the consignee has product, the consignee is missing product, and the question of when the rest is arriving is a moving target.
The tracking interfaces at most airlines don’t handle this well. The original airway bill shows partial pulls. The rebooking creates a secondary tracking string that may or may not be linked to the original. The consignee’s receiving system, set up to expect 12 pallets against a single reference, has to be manually updated to register the partial and reserve a future receipt for the catch-up. That manual reconciliation is usually where the customer-facing friction starts.
The forwarder is now managing not one shipment but a residual recovery while the main shipment continues downstream. Both pieces are the forwarder’s responsibility. Neither one is closed.
Why catch-up freight is structurally slower
The 4 residual pallets at LAX are booking exception freight. They missed the cutoff that they were supposed to make, which means they’re now competing for capacity against new bookings on the next available flight. Airlines don’t generally prioritize catch-up freight against active bookings. The same booking pressure that produced the partial decides what flies next. If Friday’s flight is capacity-constrained, the residual rolls again.
Some airlines have priority routing for split shipments. Most don’t. The forwarder requesting expedite on the catch-up portion is paying a premium against a category the airline isn’t set up to move fast. The premium may or may not produce earlier movement. Sometimes the freight catches the next flight cleanly. Sometimes it sits in the rebooking queue for several rotations because larger shipments with full bookings are taking the available capacity.
While the residual sits, storage clocks are running at LAX. The 4 pallets are accumulating fees against an account that didn’t authorize them. The forwarder is now managing storage exposure on freight that was supposed to have departed by now.
The consignee call that has no clean version
The hardest part of an OS&D residual is the consignee call. The 8 pallets arrived. The consignee’s receiving crew unloaded them. The downstream handling started. Three days later, the forwarder is calling to set expectations on the 4 catching up — except the expectations are unstable because the airline hasn’t confirmed which flight the residual is making. The call goes from “the catch-up arrives Friday” to “the catch-up rolled to Monday” to “the catch-up rolled again, currently scheduled Tuesday but not confirmed.”
Each version of that call is accurate. Each version damages the relationship anyway. The consignee’s downstream operation, planned around the original 12-pallet shipment, has to either reset against the partial and absorb the 4-pallet shortage indefinitely, or hold downstream activity until the residual lands. Either choice is costly. The forwarder providing the rolling ETAs isn’t producing the cost — the airline’s rebooking queue is — but the forwarder is the party in the conversation.
The honest version of that call describes the structure of the situation: the residual is in the airline’s rebooking queue, the priority is not under the forwarder’s control, and the most likely flight is X but the alternate is Y if the preferred flight is full. The dishonest version commits to a specific arrival date that the airline hasn’t confirmed. Most consignees can hear the difference, and the forwarder’s credibility on the relationship depends on which version the call actually is.
What the recovery sequence requires
Recovering an OS&D residual cleanly requires three operational capacities that aren’t usually packaged together. First: storage management at the origin airport — knowing exactly when the residual will move, which storage tariffs are applying during the wait, and whether the freight can be repositioned to a cheaper holding posture if the wait runs long. Second: rebooking visibility — direct relationships with the airline’s freight booking desk to read priority status on the residual and apply available expedite paths. Third: catch-up routing — once the residual flies, recovery on the destination side has to coordinate with the original delivery so the consignee’s receiving operation knows when to expect it.
Most forwarders manage the first and the third reasonably well. The second — actually reading the residual’s place in the airline’s queue — is harder, and the difference between a forwarder with a working line into the freight booking desk and a forwarder routing through standard customer service is mostly in how quickly they learn the residual rolled again. Neither one is moving the residual themselves. The airline’s queue is the airline’s queue. What the working line buys is a few hours of warning before the consignee finds out, and occasionally an expedite slot when one comes available.
The piece that arrives and the piece that doesn’t
The clean version of OS&D recovery has the residual catching the next available flight, the catch-up landing 48 to 72 hours after the partial, and the consignee receiving the full shipment inside a single planning cycle. The clean version is the most common outcome — most split shipments resolve inside the week without significant friction. The reason most forwarders don’t think about OS&D as a structural problem is that most of them don’t see the version where the residual rolls multiple times.
The version that creates real customer-relationship damage is the one where the residual ages out of normal rebooking priority and starts behaving like exception freight. At that point the recovery operator is no longer running catch-up — they’re closer to inventory recovery. The catch-up that should have flown Friday and lands Tuesday afternoon costs more than the original move ever priced in.
The forwarder relationship that handles OS&D well isn’t the one with the lowest standard rate. It’s the one whose rebooking visibility prevents the residual from aging into exception status in the first place. Airport recovery operators with airline freight-desk relationships are reading the rebooking queue from inside the system, not from the customer service line.
What closes the file
An OS&D recovery closes when the catch-up freight is delivered, the consignee has the full shipment, and the storage exposure at the origin has been resolved. That close happens cleanly if the rebooking moved on the first or second cycle. It happens messily if the rebooking rolled multiple times — the consignee absorbs an unexpected delay, the storage exposure has to be reconciled against the freight bill, and the customer relationship has friction that wasn’t present at booking.
The forwarder’s exposure across that range isn’t a function of the original move. It’s a function of how the residual recovery was managed in the days after the partial. Hand the residual side of split shipments to a desk that watches the rebooking queue actively, before it ages into exception status.
