Detention fees have a structural property that makes them unusually damaging: they are almost always discovered after the dispute window has closed. The clock runs during the shipping event. The invoice arrives three to four weeks later. By that point, the carrier has the contractual upper hand, the documentation to challenge the charge is scattered across email threads and driver logs, and the desk has already moved on to 20 other shipments. The fee gets paid.
The math behind this is worth running explicitly, because most desks do not track detention as a percentage of freight spend. They track it as a recurring nuisance line item. The difference matters.
What the Numbers Look Like at Different Volumes
Detention rates vary significantly by carrier, equipment type, and region. For a rough but realistic model, consider a European freight desk handling primarily FCL ocean freight with a mix of continental European road legs. Carrier detention rates for dry 20ft and 40ft containers in this segment typically run in the range of $80 to $180 per container per day after free time expires, with higher rates applying from day 4 or 5 onward. Some carrier contracts escalate the daily rate in tiers: days 1-3 at one rate, days 4-7 at a higher rate, day 8 onwards at a significantly higher rate.
For a desk handling 80 loads per month across 5 to 8 active carriers, even a 6% disruption rate means roughly 5 containers per month encounter a situation where detention risk is elevated. If half of those actually incur detention (3 containers), and the average exposure is 2.5 days at $130 per day, that is approximately $975 per month in preventable detention. Over a year, that is roughly $11,700. Not catastrophic in isolation, but this is just the calculable portion. Escalated rates for longer overruns, demurrage on top of detention, and the administrative time spent on invoice review and failed disputes add meaningfully to the real cost.
| Monthly loads | 6% disruption rate | 50% incur detention | Est. monthly cost | Est. annual cost |
|---|---|---|---|---|
| 40 | ~2.4 containers | ~1.2 containers | ~$390 | ~$4,700 |
| 80 | ~4.8 containers | ~2.4 containers | ~$780 | ~$9,400 |
| 200 | ~12 containers | ~6 containers | ~$1,950 | ~$23,400 |
These are conservative estimates using $130/day and 2.5 days average. Desks on lanes with higher carrier rates, or with longer average overrun times, will see higher numbers. The point is not the precise figure but the structure of the cost: it compounds from a small disruption rate into a meaningful annual line item that most desks are not tracking explicitly.
The Invoice Timing Problem
The reason this becomes a "hidden tax" rather than a manageable operational cost is the invoice timing. Carriers typically consolidate detention charges into monthly invoices. If your detention event happened on the 5th of the month, you may not see the charge until the invoice cycle closes and the bill arrives, which can be 3 to 5 weeks later. By then, several things have happened.
The driver records that could document when the container was actually gated in or returned are no longer fresh. The desk coordinator who handled the disruption has been through 20 other shipments and cannot reliably reconstruct what happened. Any correspondence with the carrier about the disruption event has been buried in the email thread archive. And the formal dispute window in most carrier contracts is 7 to 14 days from invoice receipt, which itself is already 3 weeks after the fact.
This is not an accident of carrier billing systems. It is a structural feature of how detention fees work: the information asymmetry favors the carrier. They know exactly when the clock started (gate-out timestamp in their TOS system). They know exactly when it stopped (empty return at depot confirmation). The freight forwarder's records are more scattered, more dependent on manual inputs, and arrive on the desk three weeks after the fact when urgency has fully dissipated.
Where Disputes Actually Succeed
Detention disputes that succeed share a common characteristic: the freight forwarder had real-time documentation of the gate-out and empty return events, and they identified a factual discrepancy between their records and the carrier's calculation within the dispute window.
The most frequently successful dispute grounds are: carrier miscalculation of free time (the contract specifies business days; the carrier billed calendar days), incorrect gate-out timestamp (the carrier's TOS recorded the timestamp from when the booking was confirmed rather than actual gate-out), and terminal congestion where the terminal itself caused a delay in empty return acceptance. The last category is the hardest to prove without contemporaneous documentation.
Disputes based on "we were not notified promptly" are rarely successful unless the carrier contract explicitly specifies a notification requirement. Most do not. The desk's responsibility to monitor is assumed.
What Prevention Actually Requires
Reducing detention is not primarily a documentation problem, though documentation helps with disputes. It is a response time problem. The window between "clock starts" and "desk has a reroute plan in place" determines how much of the fee is preventable. Ports where the desk gets an alert within 2 hours and has an approved reroute plan within 6 hours typically avoid most of the detention exposure. Ports where the first notification reaches the desk coordinator 8 to 12 hours into the event, via an email in a shared inbox, do not.
We are not saying that all detention fees are preventable. Some disruptions are severe enough that every available routing incurs some detention exposure, and the goal shifts to minimizing rather than eliminating the cost. But the category of preventable detention (where an earlier alert and faster response would have avoided the fee entirely) is, based on the desks we have talked with, typically 60 to 70% of the total detention invoice. That is a meaningful fraction to recover with changes to the response workflow rather than changes to the carrier contracts.
Tracking detention as a distinct cost category, separated from general freight surcharges on your P&L, is the starting point. If you do not know your current monthly detention figure as a number, you cannot set a target for it and you cannot measure whether your response workflow is improving. The math above is conservative. Run the actual numbers for your volume and your current disruption rate, and the case for fixing the response loop will be apparent.